You are not logged in.

Pages: 1

#1 2008-03-29 19:13:53

nichos
Member
From: Florida
Registered: 2008-03-29
Posts: 5

Network troubles (goes in and out)

Hi all, I've been reading the wiki and believe I've followed everything correctly but I'm still having network issues.
Here's what's going on: I can stream audio and browse the web. Every few minutes a website won't resolve, but the music will continue to stream. I also noticed that conky, which is set to update every second will hang until networking comes back. (although it never really goes away as the music continues). Sometimes when i traceroute google.com I get host unknown, I'll immediately retype it and it goes through.
So I thought it was a DNS issue. I switched to openDNS, didn't help. No other systems on my network have this issue. I've disabled ipv6 as well.
My router is 192.168.100.1

My /etc/hosts file:

127.0.0.1               localhost.localdomain   localhost inertia

my /etc/rc.conf file (parts of interest):

HOSTNAME="inertia"
#
lo="lo 127.0.0.1"
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(lo eth0)
#
#gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
#NET_PROFILES=(main)

output from ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:1A:92:83:61:2C  
          inet addr:192.168.100.2  Bcast:192.168.100.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:60225 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44161 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:71170214 (67.8 Mb)  TX bytes:3384997 (3.2 Mb)
          Interrupt:18 Base address:0xa000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

output from route:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.100.0   *               255.255.255.0   U     0      0        0 eth0
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
default         192.168.100.1   0.0.0.0         UG    0      0        0 eth0

A few traceroutes outputs:

traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 72.14.207.99
traceroute to google.com (72.14.207.99), 30 hops max, 40 byte packets
 1  adsl-214-72-99.jax.bellsouth.net (68.214.72.99)  1.444 ms  1.418 ms  1.539 ms
 2  192.168.1.254 (192.168.1.254)  1.920 ms  1.878 ms  1.868 ms
 3  65.14.194.28 (65.14.194.28)  14.908 ms  14.729 ms  14.855 ms
 4  65.14.194.17 (65.14.194.17)  14.209 ms  14.926 ms  14.783 ms
 5  ixc01jax-ge-1-0-2.bellsouth.net (205.152.70.29)  15.584 ms  15.505 ms  15.623 ms
 6  65.83.239.166 (65.83.239.166)  23.986 ms  24.040 ms  24.191 ms
 7  axr01aep-so-0-0-0.bellsouth.net (65.83.239.70)  23.905 ms  23.566 ms  23.698 ms
 8  pxr00asm-so-3-0-0.bellsouth.net (65.83.236.6)  23.745 ms  23.397 ms  23.982 ms
 9  65.83.237.223 (65.83.237.223)  31.067 ms  32.185 ms  31.284 ms
10  64.233.174.84 (64.233.174.84)  30.767 ms  31.917 ms  31.293 ms
11  216.239.48.68 (216.239.48.68)  67.278 ms  46.563 ms  47.045 ms
12  209.85.252.167 (209.85.252.167)  54.667 ms 72.14.239.136 (72.14.239.136)  61.596 ms  70.469 ms
13  72.14.238.139 (72.14.238.139)  50.196 ms *  51.524 ms
14  * 66.249.94.234 (66.249.94.234)  62.820 ms 66.249.94.92 (66.249.94.92)  66.798 ms
15  66.249.94.50 (66.249.94.50)  71.805 ms 216.239.43.146 (216.239.43.146)  75.540 ms *
16  66.249.94.92 (66.249.94.92)  69.825 ms * *
17  72.14.207.99 (72.14.207.99)  69.016 ms  68.532 ms 66.249.94.50 (66.249.94.50)  87.144 ms

second traceroute:

traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 64.233.167.99
traceroute to google.com (64.233.167.99), 30 hops max, 40 byte packets
 1  adsl-214-72-99.jax.bellsouth.net (68.214.72.99)  1.448 ms  1.497 ms  1.498 ms
 2  192.168.1.254 (192.168.1.254)  1.877 ms  1.863 ms  1.879 ms
 3  65.14.194.28 (65.14.194.28)  14.566 ms  14.458 ms  14.559 ms
 4  65.14.194.17 (65.14.194.17)  13.863 ms  14.971 ms  14.294 ms
 5  ixc01jax-ge-1-0-2.bellsouth.net (205.152.70.29)  15.518 ms  15.209 ms  14.524 ms
 6  65.83.239.166 (65.83.239.166)  106.683 ms  143.453 ms  221.016 ms
 7  axr01aep-so-0-0-0.bellsouth.net (65.83.239.70)  23.809 ms  23.362 ms  23.638 ms
 8  pxr00asm-so-3-0-0.bellsouth.net (65.83.236.6)  24.319 ms  28.284 ms  23.677 ms
 9  65.83.237.223 (65.83.237.223)  31.843 ms  31.474 ms  31.047 ms
10  64.233.174.84 (64.233.174.84)  31.532 ms  31.456 ms 66.249.95.167 (66.249.95.167)  32.080 ms
11  66.249.95.148 (66.249.95.148)  46.971 ms 72.14.236.17 (72.14.236.17)  32.037 ms 72.14.236.27 (72.14.236.27)  50.438 ms
12  72.14.236.27 (72.14.236.27)  49.902 ms 72.14.238.90 (72.14.238.90)  52.778 ms 72.14.236.27 (72.14.236.27)  50.378 ms
13  64.233.175.42 (64.233.175.42)  50.653 ms 72.14.232.74 (72.14.232.74)  56.347 ms 72.14.238.90 (72.14.238.90)  50.897 ms
14  py-in-f99.google.com (64.233.167.99)  51.160 ms 64.233.175.42 (64.233.175.42)  58.049 ms 64.233.175.98 (64.233.175.98)  50.935 ms

third traceroute:

traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 72.14.207.99
traceroute to google.com (72.14.207.99), 30 hops max, 40 byte packets
 1  adsl-214-72-99.jax.bellsouth.net (68.214.72.99)  1.457 ms  1.441 ms  1.485 ms
 2  192.168.1.254 (192.168.1.254)  1.946 ms  1.882 ms  1.839 ms
 3  65.14.194.28 (65.14.194.28)  14.745 ms  14.818 ms  14.788 ms
 4  65.14.194.17 (65.14.194.17)  15.029 ms  14.335 ms  14.820 ms
 5  ixc01jax-ge-1-0-2.bellsouth.net (205.152.70.29)  15.325 ms  16.437 ms  15.026 ms
 6  65.83.239.166 (65.83.239.166)  142.906 ms  122.392 ms  199.999 ms
 7  axr01aep-so-0-0-0.bellsouth.net (65.83.239.70)  23.246 ms  24.415 ms  23.620 ms
 8  pxr00asm-so-3-0-0.bellsouth.net (65.83.236.6)  23.373 ms  23.321 ms  23.670 ms
 9  65.83.237.223 (65.83.237.223)  31.022 ms  31.502 ms  31.722 ms
10  64.233.174.84 (64.233.174.84)  31.835 ms  31.981 ms  50.937 ms
11  216.239.48.68 (216.239.48.68)  64.644 ms  48.028 ms  66.051 ms
12  209.85.252.167 (209.85.252.167)  52.212 ms 72.14.239.136 (72.14.239.136)  33.002 ms 209.85.252.167 (209.85.252.167)  51.658 ms
13  72.14.233.113 (72.14.233.113)  71.781 ms 72.14.238.139 (72.14.238.139)  50.525 ms 72.14.233.113 (72.14.233.113)  66.418 ms
14  66.249.94.234 (66.249.94.234)  53.960 ms 66.249.94.90 (66.249.94.90)  67.414 ms 66.249.94.234 (66.249.94.234)  55.564 ms
15  216.239.43.146 (216.239.43.146)  85.858 ms * *
16  66.249.94.90 (66.249.94.90)  73.660 ms 72.14.207.99 (72.14.207.99)  69.709 ms  72.513 ms

Any help/insight would be great! Thanks
Nick

Offline

#2 2008-03-30 01:45:58

nichos
Member
From: Florida
Registered: 2008-03-29
Posts: 5

Re: Network troubles (goes in and out)

I think I've narrowed it down - it's almost definitely a DNS issue. When I ping google.com on one xterm and it hangs, I can ping 208.69.32.230 (google's IP) and it goes through immediately.

Do this help anyone help me?:)

Thanks

Offline

#3 2008-03-30 20:43:59

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,150

Re: Network troubles (goes in and out)

Since you're using dhcp, you get DNS-settings from your router.

Several routers have their own built-in dns-server that doesn't work to well.

Try disabling the built-in dns of the router and configure it to use your isp/opendns servers directly.

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#4 2008-04-03 15:47:48

Barghest
Member
From: Hanau/Germany
Registered: 2008-01-03
Posts: 563

Re: Network troubles (goes in and out)

Lone_Wolf wrote:

Try disabling the built-in dns of the router and configure it to use your isp/opendns servers directly.

Hi,

how can I do this when dhcpcd overrides /etc/resolv.conf on every startup?

Thanks

Barghest

Offline

#5 2008-04-03 18:32:24

carlocci
Member
From: Padova - Italy
Registered: 2008-02-12
Posts: 368

Re: Network troubles (goes in and out)

Reading the wiki
http://wiki.archlinux.org/index.php/Net … _Static_IP

Offline

#6 2008-04-03 21:20:13

Barghest
Member
From: Hanau/Germany
Registered: 2008-01-03
Posts: 563

Re: Network troubles (goes in and out)

I know of 'static ip' but I'm in a network that uses dhcp sad

Offline

#7 2008-04-04 03:58:07

nichos
Member
From: Florida
Registered: 2008-03-29
Posts: 5

Re: Network troubles (goes in and out)

I think I've resolved my problem (kind of). I've removed the router and I'm going straight in to my DSL modem/router. I'm not sure why only this machine was having a problem with it. I'm going to hook up my router again but disable the DHCP server.

Offline

#8 2008-04-04 23:57:53

pyther
Member
Registered: 2008-01-21
Posts: 1,395
Website

Re: Network troubles (goes in and out)

You could set your dns servers in /etc/resolv.conf

You can still leave dhcp on the router, but just configure you ip address statically

For a typical home router you'd want the following settings (similar)

IP: 192.168.1.10
Subnet mask: 255.255.255.0
Broadcast: 192.168.1.255
Default Gateway: 192.168.1.1

Website - Blog - arch-home
Arch User since March 2005

Offline

#9 2008-04-05 04:58:08

nichos
Member
From: Florida
Registered: 2008-03-29
Posts: 5

Re: Network troubles (goes in and out)

FYI, it was a configuration issue between my DSL modem and my router. I have bellsouth. I followed the directions here:
http://www.dslreports.com/faq/6323
I'm not sure why only this computer had problems since I put arch on it (my macbook didnt have problems), but the above FAQ fixed it.

Offline

Pages: 1

Board footer

Powered by FluxBB