Claude Jones wrote:
My FC3 computer with SELinux enabled in targetted mode is
accessing the internet just fine. On the LAN side, DHCP is working
and I have a wireless access point DLINK DWL-G700AP connected to
the LAN nic. It's passing traffic from a laptop to the Linux box
just fine, and I can access the internet from the laptop, so all
is well. I have one nagging issue. I can't access the DLINK. My
LAN is set to run as 192.168.2.0/255.255.255.0 and according to
the literature the DLINK is defaulted to IP address 192.168.0.50.
I have spent the better part of the afternoon trying to get around
this, but nothing is working. I changed the LAN addressing to
reflect the same range as the access point many times. I have
tried resetting the access point so that it's at its default
settings. I'm missing something - does anyone know something I
should be trying?
If I'm reading you correctly, your DHCP server (you don't say where it is) is giving you an address in the range 192.168.2.0 through .255. Your access point is on a totally different network, 192.168.0.50, so I don't see how you can use it to get through your network.
First, find out what your IP address actually is:
ifconfig eth0
If it's in the 192.168.2.x range, you can do one of two different things to access the AP. You can force a route:
route add net 192.168.0.0 netmask 255.255.255.0 dev eth0
or change the IP address on your NIC to the same as that of the AP:
ifconfig eth0 192.168.0.1 netmask 255.255.255.0
How about describing your network a bit more? What router are you using? Does it have wireless on it? What is acting as your DHCP server? Do you want the NIC on your machine to plug into the AP so your machine goes wireless? Just what are you trying to accomplish?
My access point is working too well - I can get internet access
from several rooms away in an industrial building with lots of
concrete and steel in the walls. It's not currently locked down in
any way, so I guess anyone else who tries can get in as well.
Set up a non-broadcasting ESSID and a WEP key, PRONTO!
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 Jones Bluemont, VA, USA
