You are not logged in.
Just today I started have problems with my internet. It's probably best demonstrated with a ping:
[root@lappy ryantr]# ping www.google.com
PING www.l.google.com (74.125.71.103) 56(84) bytes of data.
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=1 ttl=48 time=142 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=2 ttl=48 time=129 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=3 ttl=48 time=141 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=4 ttl=48 time=147 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=5 ttl=48 time=126 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=6 ttl=48 time=141 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=7 ttl=48 time=141 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=8 ttl=48 time=150 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=9 ttl=48 time=138 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=10 ttl=48 time=149 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=11 ttl=48 time=141 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=12 ttl=48 time=139 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=13 ttl=48 time=132 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=14 ttl=48 time=138 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=15 ttl=48 time=123 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=16 ttl=48 time=153 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=17 ttl=48 time=147 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=18 ttl=48 time=155 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=19 ttl=48 time=136 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=20 ttl=48 time=138 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=21 ttl=48 time=147 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=22 ttl=48 time=135 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=23 ttl=48 time=129 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=24 ttl=48 time=145 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=25 ttl=48 time=118 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=26 ttl=48 time=125 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=27 ttl=48 time=139 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=28 ttl=48 time=149 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=29 ttl=48 time=127 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=30 ttl=48 time=135 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=31 ttl=48 time=144 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=32 ttl=48 time=143 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=33 ttl=48 time=133 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=34 ttl=48 time=138 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=35 ttl=48 time=137 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=36 ttl=48 time=136 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=37 ttl=48 time=128 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=38 ttl=48 time=144 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=39 ttl=48 time=129 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=40 ttl=48 time=133 ms
64 bytes from hx-in-f103.1e100.net (74.125.71.103): icmp_req=41 ttl=48 time=153 ms
^C
--- www.l.google.com ping statistics ---
82 packets transmitted, 41 received, 50% packet loss, time 81016ms
rtt min/avg/max/mdev = 118.905/138.889/155.945/8.647 msNotice the "time" field in the summary at the end. I am connected for a few seconds and then nothing. If I do a /etc/rc.d/network restart I'll eventually get another few seconds of internet connection before it craps out again. I did confirm that the connection works as expected in Windows so I assume it's something on the Linux side of things. I really have no idea where to look, though.
Potentially relevant info:
HP Pavilion dv6 laptop
Wired connection with static IP on a university network
Relevant results from lspci:
02:00.0 Network controller: Broadcom Corporation BCM43225 802.11b/g/n (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)Relevant sections of /etc/rc.conf
HOSTNAME="lappy"
# new network stuffs, I think
interface=eth0
address=147.46.213.197
netmask=255.255.255.0
gateway=147.46.213.1
...
DAEMONS=(syslog-ng netfs crond alsa @ntpd !pcspkr !snd_pcm_oss dbus)(I did have network in the DAEMONS too but tried taking that out to manual start while testing ... no difference)
And finally:
[root@lappy ryantr]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
inet 147.46.213.197 netmask 255.255.255.0 broadcast 147.46.213.255
inet6 fe80::226:9eff:feec:d95f prefixlen 64 scopeid 0x20<link>
ether 00:26:9e:ec:d9:5f txqueuelen 1000 (Ethernet)
RX packets 17874 bytes 1634032 (1.5 MiB)
RX errors 0 dropped 41 overruns 0 frame 0
TX packets 2064 bytes 250498 (244.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 46 base 0xa000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 metric 1
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 120 bytes 11225 (10.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 120 bytes 11225 (10.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0Any ideas?
Last edited by ryan0270 (2011-10-21 12:19:15)
Offline
I noticed you have !pcspkr and !snd_pcm_oss in your daemons array. I believe they are modules, not daemons, and blacklisting (!) has been deprecated. Check the wiki for kernel modules on how to blacklist them. I don't think that has anything to do with your connection though. Purely a guess, but maybe try putting dbus before network? Maybe worth a try? Did it start happening after an update?
Last edited by stlarch (2011-10-20 16:48:27)
Offline
Well today the problem just disappeared. I didn't do anything that I can think of ... certainly no updates or even config changes since I posted the problems yesterday. I guess I'll just file this one under drunk laptop gnomes.
Offline