Arch Linux

toxic

Member

Registered: 2006-06-05

Posts: 117

Network routes

Hey, this is probably a question which could be answered quickly at irc, but I don't have access to a client atm.

After configuring my network (sk98lin module) I found that I can reach my own NIC as well as the others in the lan. However, it seems as I cannot reach the WAN side of the router.

I am using DHCP so all information should be exchanged (?) which is necessary to access the internet. Looking at 'route' it tells me that the default gateway is the network address (xx.0) rather than the routers interface (xx.1). I'm not sure if this is correct or not.

Settings from rc.conf
lo = "lo 127.0.0.1 "
eth0="dhcp"
INTERFACES=(lo eth0)
ROUTES=(!gateway)

I have tried changing the routes variable, adding a gateway, removing the (!) in from of gateway, but nothing seems to work. (Each time restarting the network). 

As a final note, the network is working for the other computers in the lan. It's a router acting as a 4-way switch internally, and each computer can access the internet but me. Which leads me to the conclusion that there's probably some error with my route settings.

Thanks

MaikelG

Member

From: Balingen, Germany

Registered: 2006-04-29

Posts: 46

Website

Re: Network routes

The correct default gateway must be an IP of a PC not the subnet itself.
If your IP is 192.168.1.2 and your Router is 192.168.1.1 then thats your default gateway, not the subnet 192.168.1.0!

Did you restart your netwaork after changing settings?
I would say, delete the "!" from the gateway and then

/etc/rc.d/betwork restart

should solve your problem.

---

Cheers, Maikel

toxic

Member

Registered: 2006-06-05

Posts: 117

Re: Network routes

gateway="default gw 192.168.0.1"
ROUTES=(gateway)

That's what I've changed to. I've restarted the network, the computer, run dhcp, but still I can't ping 192.168.0.1 which is the router interface, while everyone else in the LAN can. I can still reach everyone else in the lan.

I tried deleting all information from the available routingtable:
route del -net 192.168.0.0/24 gw 192.168.0.1
route del default gw 192.168.0.1

After that I rebooted my computer and this is what the routingtable contains now (netstat -rn):

DESTINATION | GATEWAY |   GENMASK         | FLAGS | IFACE
192.168.0.0  0.0.0.0    255.255.255.0      U        eth0
0.0.0.0     192.168.0.1   0.0.0.0          UG       eth0

Maximum segment size, window size, irtt are all set to zero.

Emptying the route list, or removing one of the values, restarting network just causes the same table to be rebuilt again despite that I entirely removed gateway, ROUTE variables in rc.conf.
A test ping to any network on the net results in an ICMP error message "Destination Host Uncreachable". This includes pinging my router, 192.168.0.1.

ralvez

Member

From: Canada

Registered: 2005-12-06

Posts: 1,718

Website

Re: Network routes

For your system to  use DHCP the settings in /etc/rc.conf should be:

eth0="dhcp"
INTERFACES=(lo eth0)
ROUTES=(gateway)

The last posting with your route seems correct, except for the part that says your Destination is 0.0.0.0 typicall that reads "default" (double check that out).

Use (as root) the following command:

mii-tool eth0

in the machine not connecting to make sure it is negotiating a connection, then use (as root again) arping 192.168.0.1 and let us know the results of those tests.

toxic

Member

Registered: 2006-06-05

Posts: 117

Re: Network routes

sudo mii-tool eth0
:: SIOCGMIIPHY on 'eth0' failed: Bad address

sudo arping 192.168.0.1
:: APRING 192.168.0.1 from 192.168.0.3 eth0
And then nothing happens for about 2 mins. (then still nothing happens ;).
Cancelling the request: "Sent 113 probes, received: 0 responces"

Performing "arp -a 192.168.0.1" from another windows computer in the same lan returns the router MAC address.
sudo arping that_win_comp returns it's MAC address as well.

ethtools isn't installed by default either.
Like you said, my rc.confs looks like

eth0="dhcp"
INTERFACES=(lo eth0)
ROUTES=(gateway)

toxic

Member

Registered: 2006-06-05

Posts: 117

Re: Network routes

Case solved.

Thanks for the help all. What came to my attention was that my mate just the other day introduced a MAC filter in the router, natually mistyping my MAC address.

Now it works like a charm, thanks for your help.