routing issues

jahrome · 2010-10-05 17:23:45

I have a webserver running here on arch. After an update, my rt73usb lost the route all the time and i had to wait some minutes for the route again. It made a productive working impossible. After posting a bugreport, none got assigned to it. Now i have switched to wired interface. Now the webserver can be accessed from local computers and from outside the local network, but cannot do a ping for example to www.google.de. It worked great before i did the update (in the last half year). Just another proof, not to change ever a running system.....

Sin.citadel · 2010-10-06 16:36:18

if you can access the webserver from outside the local network (internet), then your internet connection works, post route -n to show the current routes, also make sure that your firewall configuration is not the culprit, post iptables -L -n -v as well.

jahrome · 2010-10-06 22:03:38

route -n:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.2.0 0.0.0.0 255.255.255.0 U 303 0 0 wlan0
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 192.168.2.1 0.0.0.0 UG 303 0 0 wlan0

no iptabels installed. firewall on router.
I should mention, that when i plug in the wlan0 interface, i can ping, install updates etc. what's going on here? i don't know. when i look on other posts here, this really seems like poorly written drivers/firmware/routing/whatever..... dropping connection, loosing routes..... somehow no one of the developers figured out, that it worked before the updates.... which update? i have done the update 1 month ago. the server was down before the update for 3 or 4 months. at this time everything worked fine.

jahrome · 2010-10-08 22:38:06

maybe i should mention other hints regarding this whole routing problem:

my archserver is static 192.168.2.3 now. I have resetted my router and after reset i started my arch-server again. It was registered on the router as 192.168.2.8 (maybe an old dhcp ip). The old ip must be tranmitted somehow throug arch-server to the router. Maybe this is a good starting point to look for the problem. When i get other hints, i'll let you know.

best regards
Rome

pyther · 2010-10-09 12:24:36

Just so I get this straight: when connected via eth0 you can ping internal, but you can't ping outside web addresses?

Sin.citadel · 2010-10-09 20:05:19

i can see from your route, that both interfaces (eth0,wlan0) are inside the same subnet, this may be causing problems as the system sometimes uses eth0, and other times wlan0. Also, both wlan0 and eth0 are set as default routes, you should set only a single default route.

pyther · 2010-10-09 20:14:59

Sin.citadel wrote:

i can see from your route, that both interfaces (eth0,wlan0) are inside the same subnet, this may be causing problems as the system sometimes uses eth0, and other times wlan0. Also, both wlan0 and eth0 are set as default routes, you should set only a single default route.

That is wrong. The eth0 interface is being used because it has a better metric. 0 is better than 303!
Edit: you can have multiple default routes as long as they have different metrics

Last edited by pyther (2010-10-09 20:53:15)

jahrome · 2010-10-10 21:15:09

pyther wrote:

Just so I get this straight: when connected via eth0 you can ping internal, but you can't ping outside web addresses?

exactly. and i can connect to my dyndns-address.

Last edited by jahrome (2010-10-10 21:19:12)

pyther · 2010-10-11 00:54:09

Gez, I must have been out of it when I wrote that reply!

I am going to suspect you have a dns issue. Have you tried pinging a direct, outside ip address?

Try one of these

google.de.        296    IN    A    209.85.225.103
google.de.        296    IN    A    209.85.225.147
google.de.        296    IN    A    209.85.225.104
google.de.        296    IN    A    209.85.225.99
google.de.        296    IN    A    209.85.225.105
google.de.        296    IN    A    209.85.225.106

*I believe these resolv to google servers in the United States due to geodns (or something like that)

Example: ping 209.85.225.106

jahrome · 2010-10-15 22:50:22

pyther wrote:

ping 209.85.225.106

This works! When i do pacman -Syu before the ping, i get lots of errors, because of "Transient resolver error", but when i do it after the ping, it works as it should. What's wrong here?

Last edited by jahrome (2010-10-15 22:53:02)

pyther · 2010-10-16 01:57:17

It means that arch is not using the correct dns servers. Check /etc/resolv.conf and make sure you have valid dns entries.

Arch Linux

#1 2010-10-05 17:23:45

routing issues

#2 2010-10-06 16:36:18

Re: routing issues

#3 2010-10-06 22:03:38

Re: routing issues

#4 2010-10-08 22:38:06

Re: routing issues

#5 2010-10-09 12:24:36

Re: routing issues

#6 2010-10-09 20:05:19

Re: routing issues

#7 2010-10-09 20:14:59

Re: routing issues

#8 2010-10-10 21:15:09

Re: routing issues

#9 2010-10-11 00:54:09

Re: routing issues

#10 2010-10-15 22:50:22

Re: routing issues

#11 2010-10-16 01:57:17

Re: routing issues

Board footer