I posted on the Debian board and so far only one person has responded and it didn't help. I had to change out routers cause my old one kept losing my internet connection. My old one's ip was 192.168.1.1. My new one is 192.168.0.1. When I try and start my wireless network it tries to connect to the old router ip. My /etc/resolv.conf is set to the new router ip. I've change my wep encryption key in /etc/network/interfaces and in the router I set my dhcp server to my gentoo boxes ip. I've never run into this before and I have no idea how to fix it. I'd really appreciate some suggestions.

Please post the contents of /etc/network/interfaces.

Also, suggest that you are most likely using the Network Manager by the clock in Gnome, so, check this and re-assign your access point, because it will remember the IP of the old access point for the wireless connection.

I already changed it in the network manager. After I plugged it in directly to the router it detected the new router but I still have no wireless.

Here's my /etc/network/interfaces


But I think it's having a problem with my wireless key which I copied and pasted directly from my router. I'm getting this message when I restart the network:


And when I fun ifconfig I get this:

If you think it's still trying to connect to the old router (though I'm not sure how you know - where are you seeing the old routers IP?) you could always change the IP address on the router itself to be 192.168.1.1 (all routers allow you to change their internal IP, I'm pretty sure).

As for the error about the '[', if you have that character in your key, try a key that doesn't have it (AFAIK, however, there aren't many characters that aren't allowed in a key, and sure '[' isn't one).

Oh, that was just a typo. It's invalid arguement without the [. And now that I've plugged it into the router eth0 shows connecting to 192.168.0.1. With eth1 it shows Listing on LPF/eth1/ and then my computers mac address. And in my router it shows the Laptop with my correct Mac address. So the router is detecting the wireless connection.

Run:And see if it gives you 192.168.1.1 (should be the first destination). If it is, do this:And then:And restart your networking.

Try a:



to see if it sees anything. Incidently, I get that Set problem on Fedora 7 and cannot connect to my access point. Not tried without a key as of yet, but both WEP/WPA haven't worked so far.

tyme, it's showing 192.168.0.1 for eth0 but it shows nothing for eth1.

ian, here it is.

Could you post the output of /sbin/route for me?

Seems you can't see your own network based on that scan output. Did you turn on MAC filtering at all? Is ESSID broadcasting turned off on your router?

ESSID is turned on. As far as MAC filtering I had to set up the wireless card using the mac address I got from ifconfig -a. I have it set so it will only connect from this mac address.
Here it is:

Did you double check the MAC in the router? If you're MAC is right in the router, you should at least be able to see it. Make sure MAC filtering is set to "allow only the clients listed" versus "block the clients listed" - some routers have this setting (I know, I've accidentally blocked out everyone on my wireless a few times). Also, check the Channel, and try something other than 11 - lastly, make sure you do in fact have your ESSID for the router set to barbara (I am concerned that NETGEAR is actually your router, if it is a netgear router, and the ESSID is still at it's default).

I copied and pasted the MAC address but I've triple checked it and it's correct. I also tried channels 1 through 11. And I reset my ESSID name to Barbara.

Ok, it's working now. I assigned an ip to it that I got from ifconfig.

Do you mean you set the router to always give it the same IP? Or did you set it static on your machine? The IP you got from ifconfig should have been given to it via DHCP by your router, I believe, so I'm a little unsure what you mean.

It was automatically assigning it for eth0 but apparantly not for wireless. So I logged into my router and did what it called an ip reservation and assigned it to my acer laptop. I know this isn't ideal but it got it to work.

I actually do that a lot for both wired and wireless clients, just the ones that are my own, because then I don't have to figure out what IP some other computer is, and any port forwarding I set up for games and torrents will always be going to the right system.

I just keep it simple and give the machine a static IP instead of using DHCP and reservations

I prefer to use DHCP so that all the values get passed down, say, if DNS servers change for my ISP (not likely) or if I mess with the IP settings for my network on the router. It takes a lot less time to do DHCP with reservations than to go to all my boxen and set up static IP's with proper DNS, etc. etc. - and any changes I make will get passed down.

The odd thing is that when I booted into windows to see if wireless worked it worked immediately. And I have wep encryption set so it shouldn't have worked until I changed the key. But it did.

must've been Gizmo...

I don't have this problem. My router gets all the IP info from the ISP. My firewall is between me and my desktops/laptops and my wireless access point is also connected to the firewall. I use proxy DNS on the firewall, so that the firewall gives the DNS to my machines. Of course, if the DNS does change, then I have to look at the router, and then modify the firewall accordingly, but it hasn't happened yet in the last two years. So for me, only one change to make.

Of course, I understand yours doesn't need any changes now, but took a bit more to get it all set up

I think in all it took checking one box for a each system I wanted to reserve an IP for and clicking a "Save Changes" button, all done via my browser on my firewall in about 2 minutes...vs. going to all of my computers and setting them separately, which would take more than 2 minutes considering all of my systems have more than 1 OS on them. I tend to try new OS's or do reinstalls on my systems on a regular basis, this way I don't have to configure each OS to do static, if I just let it with the default DHCP the router takes care of it. So, personally, I think it's saving me work

Probably

I don't change much often at home.