RE: Wireless Networking, no gateway, no DNS.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dave,
	First I would like to say thank you so much for your time and
dedication, I truly appreciate it.

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.


Let me know your thoughts,

Eyal




Let's draw this out in a diagram:

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)

Does this make sense? I had to go back and look over your comments again
to put this together. It sounds/looks like the Lucent gets its IP via
DHCP from the Linksys, and your laptop gets its IP via DHCP from the
Lucent WAP. Apparently, however, this is not happening. Instead, you
have to hard-code your IP and DNS entries in your laptop to make it
work. Is this correct?

Do you know the inside ("left" in the diagram) IP address of your Lucent
WAP? Given that your subnet is 255.255.0.0 (16 bits, thus my /16
notation), the IP should follow the pattern I show in the diagram,
169.254.x.x.

It sounds like DHCP is not working in the Lucent. This would explain why
you had to hard-code your IP address, subnet mask, and DNS entries in
WinXP. If you can get it working, you should be ok. In truth, it doesn't
make any sense to me that WinXP shows the 169.254.x.x address, because
that address space is only supposed to be used for APIPA (a different
kind of automatic IP addressing), not DHCP.

If my diagram is incorrect, then please correct it (including IP
addresses) so we have a better understanding of how things are laid out.

-- 
Dave Sherman
MCSE, MCSA, CCNA
"If we wanted you to understand it, we wouldn't call it code."

-----Original Message-----
From: Dave Sherman [mailto:dsherman@real-time.com]
Sent: Thursday, January 30, 2003 1:54 PM
To: RedHat 8.0
Subject: RE: Wireless Networking, no gateway, no DNS.


On Thu, 2003-01-30 at 11:56, Levinshtein, Eyal wrote:
> Dave,
> 	Thanks for your reply,  here is the scoop about the IP addressing.
> Let me know what you think.
> 
> 
> My external IP is 24.x.x.x
> 
> The default Gateway is the Linksys router 192.168.1.1
> 
> LinkSys is configured for DHCP (Obtain IP, and DHCP Enabled.)
> 
> The Lucent gets an IP 192.168.1.150  (Hard Coded)
> 
> The Windows XP client was setup to obtain IP from the (Lucent AP-500) and
it
> was assigned as follow:
> 
>    IP Address. . . . . . . . . . . . : 169.254.93.100
>    Subnet Mask . . . . . . . . . . . : 255.255.0.0
>    Default Gateway . . . . . . . . . : 192.168.1.1
>    DNS Servers . . . . . . . . . . . : 167.206.3.207
>                                        167.206.7.4
> 
> When the access point was configured to obtain an IP (from the linksys
> router),  the gateway and DSN were not supplied to the wireless client (in
> Windows XP).   So, In windows, I had to hard code the IP, Gateway, DNS.
> 
> 
> I used the same setings in Linux as above but it doesnt want to work.
> 
> Question:  Should the Laptop be at 192.168.1.xx  / 255.255.255.0   ?



-- 
Psyche-list mailing list
Psyche-list@redhat.com
https://listman.redhat.com/mailman/listinfo/psyche-list

[Index of Archives]     [Fedora General Discussion]     [Red Hat General Discussion]     [Centos]     [Kernel]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat 9]     [Gimp]     [Yosemite News]

  Powered by Linux