My netgear mr814 router doesn't seem to work with mandrake 9.2. I had it running very well on redhat, and it runs fine on windows now, but whenever mandrake logs in, it kicks it off line, all zeros on the ip address. I obviously have settings wrong, if it works at all with mandrake. Anyone else have these probs?

It is connected by eth0 ethernet.

I just updated the firmware on the westell modem, and yesterday on the netgear router.

Is there some install program or some settings I should try?

I'm not sure, but I think the inside LAN works, because I can surf to the router, and change the settings, where I see all zeros on the ip address. I should be able to have my local network, but not internet access.

What is boot protocol option? I have tried static, and dhcp, but not bootp. I don't know what any of that is.


thanks
phil

I'll make a couple of assumptions here, and you change them to match your system:

First, open a terminal session and make yourself root (su, ENTER, root password, ENTER). Then type the following (substituting anything that is unique to your setup):

ifconfig eth0 192.168.0.3 broadcast 192.168.1.255 netmask 255.255.255.0

then type:

route add -net default gw 192.168.0.1 netmask 0.0.0.0 metric 1 eth0

In the first command line, replace 192.168.0.3 with the IP address of the computer you have installed Linux on. On the second command, if you have a different IP address for your router, use that instead of 192.168.0.1

That should work.

I tried both of those commands on two separate computers, and it took the commands without an error message, but it still won't let me access the internet.

thanks for the help, any other suggestions?

phil

What happens when you ping a site or an IP address? If you can ping an IP address outside your router but not a site name, then it is likely that you don't have a domain name server set up. Try both of these:

ping -c 3 www.google.com

ping -c 3 216.239.37.99

If you can do the second one but not the first, then you need to set up DNS. You do that by creating a file /etc/resolv.conf with the following 3 lines of text in it:

domain thenameofyourdomain.com
nameserver xxx.xxx.xxx.xxx (The IP address of your primary DNS server)
nameserver yyy.yyy.yyy.yyy (The same for your secondary DNS server)

You may still have a problem with your dynamic host control protocol (DHCP) setup, but my first suggestion should have fixed that it you used the right IP addresses for your setup (and not the ones I gave you). Most of the time people use their router as a DHCP host, which is one of the boot options you mentioned first off. If you have your router set up as a DHCP server and it still doesn't work, quite often all that is required to get that working is the following command:

dhcpcd eth0

but again, the stuff I asked you to try the first time should have worked. Have you tried the network setup script before? If not, try this:

net-setup eth0

If none of this works, I'm not sure I can help you - but I'm willing to try.

ok, tried them all, and no dice. I called the netgear customer service, and they are sending me a new router, after their diagnosis. is there a way the outbound is fried, and not the internal part? I know the cables are good, cuz the same one is being used now, directly into the computer.

thanks for the help.

phil

I fried my router once when I flashed it, so I'm guessing that will fix your problems. Hope the new one works. Otherwise, we'll keep working on it 'till it does :-)