You are not logged in.
[edited for clarification] If my internet is not used for a few minutes it disconnects it, if say, I start downloading a large file it stays connected until it is done, then a few minutes after the download, it will disconnect. What's odd is that is stays connected to the network, just does not get an internet connection. I suspected a power management issue but power management is turned off. I'm just using an edimax wifi dongle, however it is one that I have confirmed works fine.
Last edited by kc3 (2015-09-11 07:26:10)
Offline
the internet just disconnects.
That is not descriptive enough for us to understand the problem.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
My apologies, I meant to be descriptive. If my internet is not used for a few minutes it disconnects it, if say, I start downloading a large file it stays connected until it is done, then a few minutes after the download completed, the internet will disconnect. What's odd is that is stays connected to the network, just does not get an internet connection. I suspected a power management issue but power management is turned off.
Last edited by kc3 (2015-09-11 05:57:42)
Offline
My apologies, I meant to be descriptive. If my internet is not used for a few minutes it disconnects it
Sorry, but you're still not explaining clear enough -- what does "disconnects" mean? Do you get an error? Is there something that says "Internet Disconnected"? How are you testing the connectivity of your internet? How are you testing the connectivity of your local network?
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
I still maintain an ip address with my network, I guess that itself I haven't tested well enough. Next time the issue comes up, probably very soon I'll ping an internal device. What I mean by disconnect is that it stops being connected to the internet, it drops. It appears to still be connected to the network however. I cannot ping anything outside of my network, I cannot browse the web, I cannot download anything. I will be able to for a short while when the computer first connects, and if I'm downloading something large it stays connected until it's done and again in a few minutes will have no internet connection.
Last edited by kc3 (2015-09-11 06:24:46)
Offline
I still maintain an ip address with my network, ................. I cannot ping anything outside of my network
OK, that's more useful information. What is the output of your ping command when it fails? What is the output of the following commands when everything is working, compared to when it's broken?
ip a s
ip r s
cat /etc/resolv.conf
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
ip a s when connected
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether d0:50:99:73:06:b7 brd ff:ff:ff:ff:ff:ff
3: wlp0s19f2u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 74:da:38:0f:a8:4a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.5/24 brd 192.168.1.255 scope global wlp0s19f2u3
valid_lft forever preferred_lft forever
inet6 fe80::76da:38ff:fe0f:a84a/64 scope link
valid_lft forever preferred_lft forever
ip a s when disconnected
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether d0:50:99:73:06:b7 brd ff:ff:ff:ff:ff:ff
3: wlp0s19f2u3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 74:da:38:0f:a8:4a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.5/24 brd 192.168.1.255 scope global wlp0s19f2u3
valid_lft forever preferred_lft forever
inet6 fe80::76da:38ff:fe0f:a84a/64 scope link
valid_lft forever preferred_lft forever
ip r s when connected
default via 192.168.1.1 dev wlp0s19f2u3 metric 303
192.168.1.0/24 dev wlp0s19f2u3 proto kernel scope link src 192.168.1.5 metric 303
ip r s when disconnected
default via 192.168.1.1 dev wlp0s19f2u3 metric 303
192.168.1.0/24 dev wlp0s19f2u3 proto kernel scope link src 192.168.1.5 metric 303
resolve.conf when connected
# Generated by resolvconf
nameserver 192.168.1.1
resolve.conf when disconnected
# Generated by resolvconf
nameserver 192.168.1.1
If I ping I get this output, assuming I ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.1.5 icmp_seq=1 Destination Host Unreachable
From 192.168.1.5 icmp_seq=2 Destination Host Unreachable
From 192.168.1.5 icmp_seq=3 Destination Host Unreachable
From 192.168.1.5 icmp_seq=4 Destination Host Unreachable
From 192.168.1.5 icmp_seq=5 Destination Host Unreachable
From 192.168.1.5 icmp_seq=6 Destination Host Unreachable
From 192.168.1.5 icmp_seq=7 Destination Host Unreachable
From 192.168.1.5 icmp_seq=8 Destination Host Unreachable
From 192.168.1.5 icmp_seq=9 Destination Host Unreachable
From 192.168.1.5 icmp_seq=10 Destination Host Unreachable
And I need to correct myself, apparently despite having an ip address I cannot connect to anything internally either. That was my mistake, I should have known that wasn't working either when I was working on this earlier. If I ping say my gateway 192.168.1.1 it does the same thing.
Offline
Sounds like possibly an ARP issue. Next time it's broken, get the output of this tcpdump while trying to ping 192.168.1.1
tcpdump -lnn -i eth0 arp or host 192.168.1.1
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Just to make sure, I ran it with wlp0s19f2u3 as I'm not using eth0 and I ran it with eth0 anyway at first and that did not find the device, but when running 'tcpdump -lnn -i wlp0s19f2u3 arp or host 192.168.1.1' I get the following
00:48:18.943556 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:18.944553 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:19.147030 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:19.517845 ARP, Request who-has 192.168.1.1 tell 192.168.1.5, length 28
00:48:20.521175 ARP, Request who-has 192.168.1.1 tell 192.168.1.5, length 28
00:48:20.990297 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:21.195149 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:21.524509 ARP, Request who-has 192.168.1.1 tell 192.168.1.5, length 28
00:48:22.015542 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:22.019794 ARP, Request who-has 192.168.1.7 tell 192.168.1.1, length 46
00:48:23.038301 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:23.039293 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:24.882817 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:25.086291 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:25.087294 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:27.134416 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:27.135410 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:27.954812 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:28.491175 ARP, Request who-has 192.168.1.1 tell 192.168.1.5, length 28
00:48:29.182406 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:29.183411 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:29.494506 ARP, Request who-has 192.168.1.1 tell 192.168.1.5, length 28
00:48:30.497842 ARP, Request who-has 192.168.1.1 tell 192.168.1.5, length 28
00:48:31.026930 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:31.230405 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:31.231404 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:33.278525 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:33.279407 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:33.280274 ARP, Request who-has 192.168.1.14 tell 192.168.1.2, length 28
00:48:35.327523 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:37.170916 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:37.171924 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:37.374517 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:38.197044 ARP, Request who-has 192.168.1.7 tell 192.168.1.1, length 46
00:48:39.217790 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:39.422520 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:40.243037 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:41.265789 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:41.470635 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:43.313781 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:43.316036 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:43.317029 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:45.361903 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:45.362775 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:46.388896 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:47.227927 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:49.253046 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:49.459143 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:49.460150 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:50.277792 ARP, Request who-has 192.168.1.14 tell 192.168.1.2, length 28
00:48:51.304039 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:51.505896 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:52.532015 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:53.349163 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:53.557639 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:53.963461 IP 192.168.1.1 > 239.255.255.250: igmp v2 report 239.255.255.250
00:48:55.397157 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:55.603254 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:55.604261 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:57.445168 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:57.520273 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
00:48:58.675254 IP 192.168.1.1.53425 > 255.255.255.255.7423: UDP, length 173
00:48:59.493276 ARP, Request who-has 192.168.1.1 tell 192.168.1.10, length 46
00:48:59.494030 ARP, Request who-has 169.254.143.32 tell 192.168.1.8, length 28
00:48:59.698002 ARP, Request who-has 192.168.1.1 tell 192.168.1.20, length 46
Offline
Ah yes, my bad on the interface, sorry.
So it looks like the issue is your router isn't responding to ARP requests for some reason. Your network connection to the switch looks OK since you can see the ARP requests from .14 and .7 and .10 and .20 etc. For some reason either the router is not responding the ARP requests, or you're not seeing it's replies. I would go with the former since all the other hosts continue to ARP for the router which suggest they're not getting replies either.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Hm... That's odd, idk why, everything else on this network is working fine, including this same adapter when connected to a raspberry pi. I'm not very familiar with ARP, is there any suggestions? I can now simply try restarting the router as it's late and I can't image it's in use. [edit] restarting it didn't work
Last edited by kc3 (2015-09-11 07:08:55)
Offline
I don't have any real suggestions sorry. What is your router? Are you sure you can ping 192.168.1.1 from another device when it's broke?
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Very sure, I have several devices connected to it all functioning. The router is a Netgear R7000, I just did a firmware update, I really appreciate the help, I know if it's a router issue this kind of goes outside of the scope of these forums.
Oddly after the firmware update my internet speed on this computer went up a lot higher and the latency went down. I guess I'll wait and see what happens.
[update] Yeah I'm pretty sure this is a router issue, if for some reason it appears otherwise I'll respond. I was looking in my router attached devices and this is listed under a hostname of a device this adapter used to be connected to, I wonder if there's some sort of conflict idk after doing the update so far it seems fine. I'll post again if it turns out otherwise, I really appreciate the help.
Last edited by kc3 (2015-09-11 07:25:49)
Offline
Anyone report problems with the AC on the R7000 to the Netgear community forum? ( https://community.netgear.com/t5/All-Co … -p/English ) - maybe there is also a site for direct reporting of Netgear bugs? By the way do the R7000 disconnects ever happen with non-AC connections?
Last edited by mcloaked (2015-09-18 12:57:56)
Mike C
Offline