> Subject: RE: Wireless Networking, no gateway, no DNS. > From: Dave Sherman <dsherman@real-time.com> > To: "RedHat 8.0" <psyche-list@redhat.com> > Date: 30 Jan 2003 13:59:26 -0600 > Reply-To: psyche-list@redhat.com > > > 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: > >=20 > > The diagram you drew is 100% accurate in Windows XP. > >=20 > > In WINDOWS XP: When the Laptop was configured to obtain IP > from the Luce= > nt > > AP, It GETS 169.254.93.100 (but no GW or DNS) That is why I > had to hard c= > ode > > it. (one test should be to find out what the internal IP > of the WAP) > >=20 > >=20 > > On my Red Hat Linux 8.0 (Dual Boot) using the above config, > it doesnt wan= > t > > 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=3D=3D=3D(ethernet)=3D=3DLinksys rou= > ter > > 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) > > --=20 > Dave Sherman > MCSE, MCSA, CCNA > "If we wanted you to understand it, we wouldn't call it code." 169.254.x.x is autoassigned by Windows to signify that the machine is set for DHCP but it was unable to get an address assigned from a dhcp server.... hence, DHCP services are not working properly on the network. Linksys => 192.168.1.1/255.255.255.0 Lucent AP => 192.168.1.150/255.255.255.0 (as you stated... I would recommend 192.168.1.2) The laptop should receive an address in the range 192.168.1.100 - 150 (default DHCP scope from Linksys) This could of course be a problem if the AP is 'hard-coded' with an IP that is in the DHCP scope from the Linksys. Is there an option in the Lucent AP configuration to turn on DHCP relay? You don't necessarily want the AP to be a DHCP server (since you already have one) and you definitely don't want it to be a client if you are manually entering the address. The key to this is the 169.254.x.x address... DHCP isn't getting an address assigned in Windows and more than likely won't in Linux either. Christopher W. Griffin MCP, part-time Linux user ;-) -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
