Re: Access Point problem

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

 



On Tue, 2005-03-08 at 21:14 -0500, Claude Jones wrote:
> 
> I see that more explanation is necessary. I do know that in theory the 
> access point and my LAN are on two different networks. My Linux box is 
> both router and DHCP controller. In theory the Access Point is supposed 
> to be 192.168.0.50. My LAN is configured to 192.168.2.0/255.255.255.0. 
> Despite this, the laptop that is on the LAN is getting it's IP address 
> from the Linux box, and is getting out to the net. Somehow, this doesn't 
> make sense to me, but that's how it is. I did consider the possibility 
> that the Access Point got reprogrammed at some point, and is on the same 
> network as my Lan, but if it is, I can't see it - I have tried several 
> obvious addresses as Scot suggests in the next reply to my post, but it 
> doesn't respond. Is there some scan I can run to try to spot it? I have 
> also tried changing my Lan configuration to the 
> 192.168.0.0/255.255.255.0 range, but, I still wasn't able to see the 
> access point - however, I did something wrong when I made the change and 
> lost DHCP services to the laptop, so I left something out when trying 
> this, and maybe that's my problem. I changed the configuration of eth1 
> in the Network admin tool, and changed my settings in the dhcpd.conf, 
> when I tried that. Are there other settings somewhere else I missed?
> 
> While reconfigured, I did try to reset the access point with the pin in 
> the reset hole method, but that didn't change my results. Now, after the 
> supposed reset which puts the Access Point to 192.168.0.50, I've put my 
> lan back to the original settings of 192.168.2.0/255.255.255.0, and DHCP 
> to the laptop is working (it's got 192.168.2.254 assigned to it), and 
> I'm getting out to the net - this is baffling my imperfect understanding 
> of how this is supposed to work.
> 
> -- 

Claude,

With your eth0 interface aliased or set to 192.168.0.10, try pinging the
entire subnet ala:  ping -b 192.168.0.255 and see what is returned.

Also, is it possible that the AP is also getting an address from DHCP?
Check your logs.

Bob...


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux