I suggest to use built-in Windows wireless client.
Ray Gwinn wrote:
It seems that you again try to get bridging functionality out of a routing setup.
Can you explain the above in more detail? If you point out the attempted bridge, I can/will alter the configuration to eliminate it.
The dhcp server is running on a redhat 9.0 box that is connected to the Soekris (Wisp-
Disp) box with an ethernet switch. The Soekris and redhat system are both connected using eth0. Eth0 on rehdat is 192.168.0.1/16. Eth0 on the Soekris is 192.168.0.2/16. There is nothing else on the 192.168.0.0 network. The redhad box has an eth1 with an internet routable IP. NAT is enabled on the redhat box.
I think the redhat setup is okay because it works layer 3 bridging is enabled on the Soekris, and SEEMS to work with layer 3 disabled.
I cannot do an "ipconfig /all" on the windows system. The Windows XP displays three messages. 1 - "Waiting to Associate". 2 - "Renewing IP Address". 3 - "Verifying Connection". The windows system terminates on the third "Verifying Connection" message, resulting in no setup.
The Orinoco docs does not explain what "Verifying Connection" is doing. I am speculating that this test fails because no route is setup by Wisp-Disp.
BTW, I can let you SSH into the redhat and soekris boxes if you want to look for yourself.
Ray
On 25 Feb 2004 at 1:14, Vladimir Ivashchenko wrote:
Hi Ray,
It seems that you again try to get bridging functionality out of a routing setup.
Where is the DHCP server running? What is the output of "ipconfig /all" on the Windows notebook?
Ray Gwinn wrote about "Re: [leaf-wisp] Routing problem":
The client is a Windows XP notebook with an Orinoco gold pcmcia card, configured to use dhcp for IP and DNS.
Perhaps I chose my words "cannot connect" poorly. The client DOES seem
associate with the Soekris (Wisp-Disp) box, and dhcp seems to complete. However, the client cannot access anything because Wisp-Disp has not setup
any routes to support the connection.
Ray
On 24 Feb 2004 at 23:24, Vladimir Ivashchenko wrote:
What is the client configuration?
Ray Gwinn wrote about "Re: [leaf-wisp] Routing problem":
Vladimir, I eliminated the overlapping networks, and the same routing symptoms persist.
I have reduced the setup to as minimal as I can. The hardware is a Soekris 4521, but with only one pcmcia card installed and enabled.
If I enable layer 3 bridging, all works well. There is only one device in the layer 3 bridge, netcs0. The "ip route" output with layer 3 enabled, and just after boot is as follows:
192.168.0.1 dev eth0 scope link metric 50 10.0.0.0/16 dev netcs0 proto kernel scope link src 10.0.1.3 192.168.0.0/16 dev eth0 proto kernel scope link src 192.168.0.2 default via 192.168.0.1 dev eth0
The output of "ip route" after a wireless client connects is as follows:
192.168.0.1 dev eth0 scope link metric 50 10.0.5.243 dev netcs0 scope link metric 50 10.0.0.0/16 dev netcs0 proto kernel scope link src 10.0.1.3 192.168.0.0/16 dev eth0 proto kernel scope link src 192.168.0.2 default via 192.168.0.1 dev eth0
The above setup works!
-----------------------------------------------
If I turn off lawyer 3 bridging, and make NO OTHER changes, "ip route" just after boot shows the following:
10.0.0.0/16 dev netcs0 proto kernel scope link src 10.0.1.3
192.168.0.0/16 dev eth0 proto kernel scope link src 192.168.0.2
default via 192.168.0.1 dev eth0
And with the above routes, wireless clients cannot connect. And again, it seems that routes are not being set correctly when parprouted is not in the picture. The missing static (I think) route to 192.168.0.1 seems to be the problem.
The if.config file follows:
DEFAULT_GW="192.168.0.1 dev eth0"
eth0_IPADDR="192.168.0.2/16"
BR_IFACES="netcs0 "
IFACES="eth0 netcs0 "
br0_IPADDR="10.0.1.3/16"
ENABLE_L2_BRIDGING="no"
netcs0_IPADDR="10.0.1.3/16"
NAT_IFACE="eth0"
ENABLE_PARP_BRIDGING="no"
And as before, the only difference between failure and success is
setting ENABLE_PARP_BRIDGING="yes".
Any advice is appreciated. If I get this figured out, I will write a mini HowTo which may prevent these types of questions by others in the future.
Ray
On 24 Feb 2004 at 15:57, Vladimir Ivaschenko wrote:
You can have overlapping networks with interfaces only when layer 3 bridging is enabled; that's actually what layer 3 bridging is for. :)
In normal life, each interface has it's own, unique subnet. For a nice TCP/IP introduction, see this link: http://www.faqs.org/docs/linux_network/
Ray Gwinn wrote:
It will take me awhile to get back to where I can get the "ip route" outputs. I will send those later today.
I'm a bit confused as it seems that you have overlapping networks on the interfaces.
I am very NEW to this whole thing so I probably have some really dumb mistakes in my setup. I assume you mean the 10.0.0.0/16 networks on both eth0 and netcs0. I have wondered about that also.
Those routes are setup by Wisp-Dist (not me) based on the if.config file at the end of my original message (also quoted below). Can you suggest changes?
However, even with the network overlaps, all works okay when layer 3 bridging is enabled. I think it works because of the static host route to 10.0.0.1, added by parprouted (I think).
When layer 3 bridging is turned off, the static route to 10.0.0.1 is missing, and routes to wireless clients are not added to the routing table.
Ray
On 24 Feb 2004 at 12:10, Vladimir Ivaschenko wrote:
Ray,
I suggest you to use "ip route" command to get a list of routes, netstat -nr doesn't show everything. Can you send me it's output?
I'm a bit confused as it seems that you have overlapping networks on the interfaces.
Ray Gwinn wrote:
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
-- Best Regards, Vladimir Ivashchenko ThunderWorx - www.thunderworx.com Senior Systems Designer/Engineer
------------------------------------------------------- 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
-- Best Regards, Vladimir Ivashchenko ThunderWorx - www.thunderworx.com Senior Systems Designer/Engineer
-- Best Regards, Vladimir Ivashchenko ThunderWorx - www.thunderworx.com Senior Systems Designer/Engineer
-- Best Regards, Vladimir Ivashchenko ThunderWorx - www.thunderworx.com Senior Systems Designer/Engineer
------------------------------------------------------- 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
-- Best Regards, Vladimir Ivashchenko ThunderWorx - www.thunderworx.com Senior Systems Designer/Engineer
------------------------------------------------------- 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
