You are not logged in.
Pages: 1
Hi,
I have a problem that I do not know how to solve it.
Here is what happens:
1. boot
2. ping www.google.com => ok
3. ip link show net0 => ok
4. pacman -Syyu
- after some data are downloaded connection stop working so I hit Ctrl+C
5. ip link show net0 => ok
6. ping www.google.com => nothing happens
To make connection working again I have to do
ip link set net0 down && ip link set net0 up
I have a dual boot on this machine and the other OS is just fine. So I do not think it is related to HW.
Regards,
Tomas
Offline
Compare the output of the following commands before and after step 4:
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
Before
# ip a s
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: net0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether e8:40:f2:eb:bb:55 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.104/24 brd 192.168.1.255 scope global net0
valid_lft forever preferred_lft forever
inet6 fe80::a93d:896c:ca75:1436/64 scope link
valid_lft forever preferred_lft forever
# ip r s
default via 192.168.1.1 dev net0 metric 202
192.168.1.0/24 dev net0 proto kernel scope link src 192.168.1.104 metric 202
# cat /etc/resolv.conf
# Generated by resolvconf
nameserver 192.168.1.1
After
# ip a s
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: net0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether e8:40:f2:eb:bb:55 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.104/24 brd 192.168.1.255 scope global net0
valid_lft forever preferred_lft forever
inet6 fe80::a93d:896c:ca75:1436/64 scope link
valid_lft forever preferred_lft forever
# ip r s
default via 192.168.1.1 dev net0 metric 202
192.168.1.0/24 dev net0 proto kernel scope link src 192.168.1.104 metric 202
# cat /etc/resolv.conf
# Generated by resolvconf
nameserver 192.168.1.1
I do not see any difference. Could it be something with configuration?
Offline
OK, so that's all good.
6. ping www.google.com => nothing happens
Can you elaborate on what "nothing happens" means? Something has to happen (terminal hangs, return to prompt with no output, error msg, etc?)
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
After some time it returns:
ping: unknown host www.google.com
But when I use IP address instead I get
From 192.168.1.104 icmp_seq=1 Destination Host Unreachable
Offline
This seems very similar to this issue from only a few days ago.
While it's broken, run this command and `ping 8.8.8.8`:
tcpdump -lnn -i net0 arp or host 192.168.1.1 or host 8.8.8.8
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Here is the output. It seems like my router suddenly becomes unreachable. But from other devices it is accessible.
07:17:43.230231 IP 192.168.1.1.2052 > 255.255.255.255.7437: UDP, length 173
07:17:46.236281 IP 192.168.1.1.2052 > 255.255.255.255.7437: UDP, length 173
07:17:47.948967 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 28
07:17:47.949350 ARP, Reply 192.168.1.1 is-at f8:d1:11:56:7f:4a, length 46
07:17:47.949361 IP 192.168.1.105.49964 > 192.168.1.1.53: 26263+ A? mirror.vpsfree.cz. (35)
07:17:47.949364 IP 192.168.1.105.49964 > 192.168.1.1.53: 59475+ AAAA? mirror.vpsfree.cz. (35)
07:17:47.950588 IP 192.168.1.1.53 > 192.168.1.105.49964: 26263 1/0/0 A 77.93.223.10 (51)
07:17:47.951125 IP 192.168.1.1.53 > 192.168.1.105.49964: 59475 1/0/0 AAAA 2a03:3b40:1::42 (63)
07:17:49.242812 IP 192.168.1.1.2052 > 255.255.255.255.7437: UDP, length 173
07:18:04.444757 IP 192.168.1.105.51557 > 192.168.1.1.53: 22700+ A? archlinux.mirror.dkm.cz. (41)
07:18:04.444763 IP 192.168.1.105.51557 > 192.168.1.1.53: 24179+ AAAA? archlinux.mirror.dkm.cz. (41)
07:18:09.449823 IP 192.168.1.105.51557 > 192.168.1.1.53: 22700+ A? archlinux.mirror.dkm.cz. (41)
07:18:09.449831 IP 192.168.1.105.51557 > 192.168.1.1.53: 24179+ AAAA? archlinux.mirror.dkm.cz. (41)
07:18:14.454932 IP 192.168.1.105.47258 > 192.168.1.1.53: 29196+ A? archlinux.mirror.dkm.cz. (41)
07:18:14.454938 IP 192.168.1.105.47258 > 192.168.1.1.53: 30398+ AAAA? archlinux.mirror.dkm.cz. (41)
07:18:14.964659 IP 192.168.1.105.55236 > 192.168.1.1.53: 46151+ A? mirror.us.leaseweb.net. (40)
07:18:14.964666 IP 192.168.1.105.55236 > 192.168.1.1.53: 60068+ AAAA? mirror.us.leaseweb.net. (40)
07:18:19.460003 IP 192.168.1.105.47258 > 192.168.1.1.53: 29196+ A? archlinux.mirror.dkm.cz. (41)
07:18:19.460011 IP 192.168.1.105.47258 > 192.168.1.1.53: 30398+ AAAA? archlinux.mirror.dkm.cz. (41)
07:18:19.969704 IP 192.168.1.105.55236 > 192.168.1.1.53: 46151+ A? mirror.us.leaseweb.net. (40)
07:18:19.969711 IP 192.168.1.105.55236 > 192.168.1.1.53: 60068+ AAAA? mirror.us.leaseweb.net. (40)
07:18:24.974776 IP 192.168.1.105.34645 > 192.168.1.1.53: 9865+ A? mirror.us.leaseweb.net. (40)
07:18:24.974783 IP 192.168.1.105.34645 > 192.168.1.1.53: 38534+ AAAA? mirror.us.leaseweb.net. (40)
07:18:25.484524 IP 192.168.1.105.51742 > 192.168.1.1.53: 62153+ A? mirror.nl.leaseweb.net. (40)
07:18:25.484530 IP 192.168.1.105.51742 > 192.168.1.1.53: 56488+ AAAA? mirror.nl.leaseweb.net. (40)
07:18:29.979849 IP 192.168.1.105.34645 > 192.168.1.1.53: 9865+ A? mirror.us.leaseweb.net. (40)
07:18:29.979857 IP 192.168.1.105.34645 > 192.168.1.1.53: 38534+ AAAA? mirror.us.leaseweb.net. (40)
07:18:29.980770 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 28
07:18:30.489591 IP 192.168.1.105.51742 > 192.168.1.1.53: 62153+ A? mirror.nl.leaseweb.net. (40)
07:18:30.489598 IP 192.168.1.105.51742 > 192.168.1.1.53: 56488+ AAAA? mirror.nl.leaseweb.net. (40)
07:18:30.984128 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 28
07:18:31.987470 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 28
07:18:35.494697 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 28
07:18:36.497470 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 28
...
Last edited by tomass (2015-09-18 05:27:33)
Offline
07:18:04.444757 IP 192.168.1.105.51557 > 192.168.1.1.53: 22700+ A? archlinux.mirror.dkm.cz. (41)
07:18:04.444763 IP 192.168.1.105.51557 > 192.168.1.1.53: 24179+ AAAA? archlinux.mirror.dkm.cz. (41)
07:18:09.449823 IP 192.168.1.105.51557 > 192.168.1.1.53: 22700+ A? archlinux.mirror.dkm.cz. (41)
07:18:09.449831 IP 192.168.1.105.51557 > 192.168.1.1.53: 24179+ AAAA? archlinux.mirror.dkm.cz. (41)
07:18:14.454932 IP 192.168.1.105.47258 > 192.168.1.1.53: 29196+ A? archlinux.mirror.dkm.cz. (41)
07:18:14.454938 IP 192.168.1.105.47258 > 192.168.1.1.53: 30398+ AAAA? archlinux.mirror.dkm.cz. (41)
07:18:14.964659 IP 192.168.1.105.55236 > 192.168.1.1.53: 46151+ A? mirror.us.leaseweb.net. (40)
07:18:14.964666 IP 192.168.1.105.55236 > 192.168.1.1.53: 60068+ AAAA? mirror.us.leaseweb.net. (40)
07:18:19.460003 IP 192.168.1.105.47258 > 192.168.1.1.53: 29196+ A? archlinux.mirror.dkm.cz. (41)
07:18:19.460011 IP 192.168.1.105.47258 > 192.168.1.1.53: 30398+ AAAA? archlinux.mirror.dkm.cz. (41)
07:18:19.969704 IP 192.168.1.105.55236 > 192.168.1.1.53: 46151+ A? mirror.us.leaseweb.net. (40)
07:18:19.969711 IP 192.168.1.105.55236 > 192.168.1.1.53: 60068+ AAAA? mirror.us.leaseweb.net. (40)
07:18:24.974776 IP 192.168.1.105.34645 > 192.168.1.1.53: 9865+ A? mirror.us.leaseweb.net. (40)
07:18:24.974783 IP 192.168.1.105.34645 > 192.168.1.1.53: 38534+ AAAA? mirror.us.leaseweb.net. (40)
07:18:25.484524 IP 192.168.1.105.51742 > 192.168.1.1.53: 62153+ A? mirror.nl.leaseweb.net. (40)
07:18:25.484530 IP 192.168.1.105.51742 > 192.168.1.1.53: 56488+ AAAA? mirror.nl.leaseweb.net. (40)
07:18:29.979849 IP 192.168.1.105.34645 > 192.168.1.1.53: 9865+ A? mirror.us.leaseweb.net. (40)
07:18:29.979857 IP 192.168.1.105.34645 > 192.168.1.1.53: 38534+ AAAA? mirror.us.leaseweb.net. (40)
07:18:29.980770 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 28
07:18:30.489591 IP 192.168.1.105.51742 > 192.168.1.1.53: 62153+ A? mirror.nl.leaseweb.net. (40)
07:18:30.489598 IP 192.168.1.105.51742 > 192.168.1.1.53: 56488+ AAAA? mirror.nl.leaseweb.net. (40)
07:18:30.984128 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 28
07:18:31.987470 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 28
07:18:35.494697 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 28
07:18:36.497470 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 28
That definitely suggests the router stops responding to your computer -- I don't have an explanation for that. Perhaps try changing your network cable and switchport? If you have a managed switch, see if there are any errors/logs on it that could explain it.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
I do not get it.
All other devices are fine. Even when I boot LIVE system on the same machine it works fine. Only this one installation has some problem. I think there must be something wrong with the configuration. Could there be some conflicting configuration in static vs. dynamic IP assignment?
Offline
What router do you have? The other thread was a Netgear R7000.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
I have a TL-WR1043ND
Offline
Alright. I finally found a solution.
https://bbs.archlinux.org/viewtopic.php?id=201459
setting mtu to 9000 helped
Offline
That's a strange bug. Glad you found a workaround
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
Pages: 1