unwiredhokie
12-17-2008, 04:14 PM
I've got a scenario where the wireless bridge is not as transparent as I'd like it to be. In the following network, the networks on Unit C(ath0) are not accessible if Unit B (Bullet2) is in bridging mode.
A(Voyage AP)<------>B-br0-(B2)<-->C-eth0-(Voyage ALIX)-ath0
wlan0-X.X.2.1 X.X.2.9 X.X.2.10 X.X.3.1
|
Ethernet connected PC X.X.2.11
Does _not_ allow A to ping C(ath0). It does allow communication to C(eth0) as expected.
If I put the B2 into routing mode just so.
A(Voyage AP)<------>B-ath0(B2)-eth0<------->C-eth0-(Voyage AP)-ath0
wlan0-X.X.2.1 X.X.2.9 X.X.3.254/25 X.X.3.129/25 X.X.3.1/25
and issue
route add -net 172.23.3.0 netmask 255.255.255.128 gw 172.23.3.129
on B, then traffic from A routes to C(ath0) and back (assuming C has a default route pointing back to B).
In fact, I would like to install a second radio in C (ath1) and route to yet other systems with yet other network addresses which of course must be able to flow back through B.
Two questions:
1) What setting might be used for B to make the first arrangement work such that B is really transparent? Do I need MAC cloning? It seems that might work except for the pesky locally connected PC (Can't wait for the router board with three slots!!)
2) I can live with the routed solution but need to have the network routes issued automatically on reboot. Where is the recommended place to store such commands in the CLI login? Normally I'd use something like rc.local. /etc/rc.d/rc looks like a script in /etc/persistent/ would be the right location.
Unfortunately, the routed solution completely breaks OSPF available on the ALIX/Voyage boards since the B2 (or it's cousins) cannot do OSPF.
Suggestions welcome
Regards,
Edwin
A(Voyage AP)<------>B-br0-(B2)<-->C-eth0-(Voyage ALIX)-ath0
wlan0-X.X.2.1 X.X.2.9 X.X.2.10 X.X.3.1
|
Ethernet connected PC X.X.2.11
Does _not_ allow A to ping C(ath0). It does allow communication to C(eth0) as expected.
If I put the B2 into routing mode just so.
A(Voyage AP)<------>B-ath0(B2)-eth0<------->C-eth0-(Voyage AP)-ath0
wlan0-X.X.2.1 X.X.2.9 X.X.3.254/25 X.X.3.129/25 X.X.3.1/25
and issue
route add -net 172.23.3.0 netmask 255.255.255.128 gw 172.23.3.129
on B, then traffic from A routes to C(ath0) and back (assuming C has a default route pointing back to B).
In fact, I would like to install a second radio in C (ath1) and route to yet other systems with yet other network addresses which of course must be able to flow back through B.
Two questions:
1) What setting might be used for B to make the first arrangement work such that B is really transparent? Do I need MAC cloning? It seems that might work except for the pesky locally connected PC (Can't wait for the router board with three slots!!)
2) I can live with the routed solution but need to have the network routes issued automatically on reboot. Where is the recommended place to store such commands in the CLI login? Normally I'd use something like rc.local. /etc/rc.d/rc looks like a script in /etc/persistent/ would be the right location.
Unfortunately, the routed solution completely breaks OSPF available on the ALIX/Voyage boards since the B2 (or it's cousins) cannot do OSPF.
Suggestions welcome
Regards,
Edwin