> Hello,
>
well - g'day Bart .... Thanks for the reply
Since I sent out my emails, I have discovered your ebtables work - can't
see how I missed it before ... obviously failed to see the significance
in my situation!!
> ---- Original Message -----
> snip snip ...
> > ... In essence, I want to build a NetBeui bridge.
> snip snip ...
> > I have two ethernet cards in the bridge, eth0 and eth1. eth0 is
> > connected to the local side (192.168.123.0 - 255.255.255.0) of the
> > router and eth1 to the ISP (144.136.170.0 - 255.255.252.0) side.
> > They are initialising okay at boot as I can run up a terminal, do:
> snip snip ...
>
>
> When the bridge doesn't know where the destination computer is, it will
> broadcast the packet on all (or some, if it uses STP) of it's network cards.
> But if I understand your network correctly this shouldnt be a problem, as
> your router is between the internet and your bridge. The router will not
> forward these ARP messages to the internet.
>
aaaah - my attempts at painting the word picture describing my setup
have failed!!! Let's try some ascii art (uh oh!)
+-----------------+
| cable modem |
+-------+---------+
|
| ISP Assigned +---------------+
+----+----+ IP address | |
| +-------------------------+ PC #1 |
| |ISP assigns | |
| HUB |IP via DHCP +---------------+
| +------------------------------+
| +---+ |
+---------+ | |
| |
| |
|ISP Assigned |
|IP address |
+--------+------------+ +--+-------+
| h/w router + switch | | eth1 |
+---+---------+-----+-+ | |
| router | | | BRIDGE |
| assigns | + | |
| IP via | +------------+ eth0 |
| DHCP | +----------+
router | | router
Assigned | | Assigned
IP address | | IP address
+--+--+ +--+--+
| | | |
|PC #2| |PC #3|
| | | |
+-----+ +-----+
phew! So: to state my problem again - in less wordy terms now
that I may refer to my picture!
My main goal is to route NetBeui over the bridge, allowing
Windows PC's #1, #2 and #3 to all see each other in their
network neighbourhoods. A secondary goal is to be able to
use the BRIDGE PC as a workstation (to mess about with
linux ...). A third potential goal is to get the bridge
solution small enough that I could run it from a low feature
PC permanently powered-up.
So - the nub of it is that the bridge is effectively spanning
router upstream to downstream - hence the very real need to
have it NOT FORWARD any tcp/ip related traffic - including
ARP, DHCP etc etc ... In future, if I can get this all
working okay, it may well also take over the routing duties
of the dedicated router. I guess another solution to my
problem would be a router that forwards all "unprocessed"
packets - which is then what my linux bridge/router would be.
> If you only want to bridge NetBEUI you can use ebtables:
> ebtables -A FORWARD -p NetBEUI -j ACCEPT
> ebtables -P FORWARD DROP
> These 2 rules will allow NetBEUI traffic to be bridged and will drop
> everything else.
> See http://users.pandora.be/bart.de.schuymer/ebtables/
> Hope this was a little helpful.
immensely - thanks.
As I mentioned earlier, I discovered your ebtables stuff last night.
I immediately tried to apply the relevant patches to 2.4.2, but they
failed ... not violently, but enough to drive me to update my kernel
to 2.4.13 and go from there - I am still Linux newbie enough to make
this more attractive than chasing the patch failures!!
Looking at the ebtables, iptables and brctl stuff, it looks
promising that I will be able to augment my existing setup
with ebtables to kill FORWARDing on everything but NetBeui.
I'll keep the list posted ...
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
