At 10:59 PM 2/9/03 -0500, Camille King wrote:
I'm having some major problems with my Linkys 4-port/wireless cable/dsl router.This description is a bit sketchy, so let me fill in the blanks the way I understand them, so you can either confirm the missing details or correct them.
My regular wired connection works with no problems and I'm using the dhcpd.lrp
so that all my internal network connections are assigned addresses by dhcp. Even
my wireless network connection is assigned all the proper settings through dhcp.
The problem is that no matter what, I can't connect through my wireless.
I've disabled DHCP and I'm not using the WAN connection (as I've read) but this
problem I don't understand. When I try and ping the LEAF box I get request timed
out but I no problems pinging other machines on my internal network.
I'm stumped.
You have a Bering router that is the Internet gateway for your LAN. Attached to that LAN is a Linksys wireless router that acts as a WAP for the LAN. You have hosts on the wireline portion of the LAN, and other hosts on the wireless portion of the LAN. It is all one network (in the IP sense); the Linksys WAN port is not used.
All clients -- on both wireline and wireless portions -- successfully receive DHCP leases from the Bering router (NOT from the Linksys).
But ... if you ping the Bering router from a host on the wireline portion, the ping succeeds, while if you ping the Bering router from a host on the wireless portion pings get sent but no response arrives. But a host on the wireless portion *can* ping a host (other then the Bering router) on the wireline portion successfully (and vice versa? you didn't say, I think).
If any of the above is wrong, please post a followup correcting me, and include the usual diagnostics this time.
If all of it is right ... I don't yet understand why it is happening, but I can suggest the next things to check.
1. What LAN IP address is assigned to the Linksys, and is it different from the LAN IP address of the Bering? If not, fix it; that conflict is causing your problem. If this is OK, then go on.
2. Before you ping from a wireless host, check its arp table to see if there is an entry for the Bering's IP address. (Probably there is not.) After you ping, check again. See if there is an entry present, and see if it has the right MAC address. Also check the Bering's arp table before and after.
3. Try to ping a wireless host from the Bering. Check the arp tables the same way you did in item 2.
Steps 2 and 3 should let you figure out which direction of the connection is failing to complete. From that, you may see the solution yourself. If not, post a follow here with these results, along with the standard diagnostics (see the SR FAQ), plus the details of the Linksys' configuration. Your problem is most likely some piddly little detail (like item 1) that will be easy for fresh eyes to spot, but hard for you to see because you are too close to the problem, and impossible for us to guess without having the details to look at.
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [EMAIL PROTECTED]
-------------------------------------------------------------------------------
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
