Valadimir, I have encountered a problem that I hope you can help with.  It seems that 
when layer 3 bridging is disabled, wireless clients cannot connect.  It seems as 
though 
routing is not being setup correctly.

The hardware is a Soekris 4521, but only one card (netcs0) installed and enabled.

Note that 10.0.0.1 is the default gateway and is a linux box directly connected to the 
Soekris via an ethernet switch.  The ip of eth0 is 10.0.0.2.

First, with layer 3 bridging enabled, with one device in the bridge (netcs0), and 
immediately following a boot, "netstat -nr" shows the following:

Kernel IP routing table
Destination  Gateway    Genmask         Flags   MSS Window  irtt Iface
10.0.0.1     0.0.0.0    255.255.255.255 UH       40 0          0 eth0
10.0.0.0     0.0.0.0    255.255.0.0     U        40 0          0 eth0
10.0.0.0     0.0.0.0    255.255.0.0     U        40 0          0 netcs0
0.0.0.0      10.0.0.1   0.0.0.0         UG       40 0          0 eth0

After a wireless client (notebook computer) connects the routing table looks like the 
following:

Kernel IP routing table
Destination  Gateway    Genmask         Flags   MSS Window  irtt Iface
10.0.0.1     0.0.0.0    255.255.255.255 UH       40 0          0 eth0
10.0.5.243   0.0.0.0    255.255.255.255 UH       40 0          0 netcs0
10.0.0.0     0.0.0.0    255.255.0.0     U        40 0          0 eth0
10.0.0.0     0.0.0.0    255.255.0.0     U        40 0          0 netcs0
0.0.0.0      10.0.0.1   0.0.0.0         UG       40 0          0 eth0

All is well with the above, the wireless client connects and can surff the net.

Now, if I go into config and disable layer 3 bridging, I see the following immediately 
after 
boot.

Kernel IP routing table
Destination  Gateway    Genmask         Flags   MSS Window  irtt Iface
10.0.0.0     0.0.0.0    255.255.0.0     U        40 0          0 eth0
10.0.0.0     0.0.0.0    255.255.0.0     U        40 0          0 netcs0
0.0.0.0      10.0.0.1   0.0.0.0         UG       40 0          0 eth0

And with the above, wireless clients cannot connect.  If I execute the following, the 
wireless client can connect.

ip route add 10.0.0.1/32 dev eth0
ip addr add 10.0.0.1/32 dev eth0

After finding the dhcp assigned address assigned to the wireless client, I can execute 
something like the following:

ip route add 10.0.5.242/32 dev netcs0

and the wireless client can sruff the net.  Basically, I have done manually what I 
beleive 
Wisp-Dist is intended to do.

As best I can tell from looking at the scripts is that parprouted is the only 
difference when 
turning layer 3 bridging on and off.

The if.config file is below.  The only difference between failure and success is 
setting 
ENABLE_PARP_BRIDGING="yes".

eth0_IPADDR="10.0.0.2/16"
br0_IPADDR="10.0.1.3/16"
ENABLE_L2_BRIDGING="no"
netcs0_IPADDR="10.0.1.3/16"
NAT_IFACE="eth0"
BR_IFACES="netcs0 "
IFACES="eth0 netcs0 "
DEFAULT_GW="10.0.0.1 dev eth0"
ENABLE_PARP_BRIDGING="no"

Sorry for such a long message.  Is there any advice, or help you can provide?

Ray



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
leaf-wisp-dist mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist

Reply via email to