On Thu, 2003-01-30 at 13:46, Levinshtein, Eyal wrote: > Dave, > First I would like to say thank you so much for your time and > dedication, I truly appreciate it. No problem. I have a similar wireless setup (different hardware) at home, so I understand the concepts. > Second, reply to your message: > > The diagram you drew is 100% accurate in Windows XP. > > In WINDOWS XP: When the Laptop was configured to obtain IP from the Lucent > AP, It GETS 169.254.93.100 (but no GW or DNS) That is why I had to hard code > it. (one test should be to find out what the internal IP of the WAP) > > > On my Red Hat Linux 8.0 (Dual Boot) using the above config, it doesnt want > to work. Does the Lucent have any sort of web-based configuration tool? That would help in determining it's IP address. It might even give you a way of setting up the DHCP server to provide DNS and gateway information. I am still assuming that the Lucent is doing some sort of NAT, translating your laptop's IP into its own external address (192.168.1.150) for all outgoing packets. If there is no web-based tool, then a reasonable starting assumption for it's IP address would be 169.254.1.1. It still seems pretty screwy to me that it is using this IP network, but if that is really what you are seeing in WinXP, and it works there, then I suppose we should just go with it. > Laptop---(wireless)--------Lucent WAP===(ethernet)==Linksys router > 169.254.93.100/16 (right) 169.254.x.x/16 (left) > 192.168.1.150/24 (right) 192.168.1.1/24 (left) > 24.x.x.x (right) -- Dave Sherman MCSE, MCSA, CCNA "If we wanted you to understand it, we wouldn't call it code."
Attachment:
signature.asc
Description: This is a digitally signed message part
