| View previous topic :: View next topic |
| Author |
Message |
mikefot
l33t
Joined: 19 Nov 2014
Posts: 687
|
 Posted: Fri Oct 09, 2020 5:16 pm Post subject: ping at terminal and google not working on firefox; [SOLVED] |
 |
|
Dear All,
I am running gentoo stable on an FX 8350 box.
After some world updates my net connection is a bit wonky.
If I run I get | Code: | | network is unreachable |
as an error.
But if I run firefox I can run gmail on it successfully.
I also did and did a world update and installed the latest package updates.
But I can't load google or even the gentoo forums website on firefox.
Suggestions on some diagnostics I could run would be appreciated.
Regards
Michael Fothergill
Last edited by mikefot on Fri Oct 16, 2020 10:03 am; edited 1 time in total |
|
| Back to top |
|
 |
The Doctor
Moderator
Joined: 27 Jul 2010
Posts: 2644
|
| Posted: Fri Oct 09, 2020 10:23 pm Post subject: |
|
|
Okay, this is a total shot in the dark and probably shouldn't be a first response, but....
I think your DNS is messed up. The working stuff knows the IP address so it isn't a problem but if it has to resolve the IP address your SOL. To test my hypothesis try ping -c1 89.16.167.134 and let us know what that does.
If it works (or doesn't) try editing /etc/resolv.conf. Make the only uncommitted entry nameserver 8.8.8.8 See if google will solve your problem. It is easy to make this permanent if it works.
At the very least the above will narrow the problem space. If that doesn't doesn't yield any fruit please post what got updated. You can find the information in /var/log/emerge.log
[Moderator edit: added 1 to the ping command to make it valid, in case a future reader tries the advice. The edit came too late for the OP. -Hu]
_________________
First things first, but not necessarily in that order.
Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box. |
|
| Back to top |
|
|
Juippisi
Developer
Joined: 30 Sep 2005
Posts: 509
Location: /home
|
| Posted: Sat Oct 10, 2020 5:47 am Post subject: |
|
|
| IP4 vs. IP6? |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 687
|
| Posted: Sat Oct 10, 2020 12:35 pm Post subject: |
|
|
Many thanks for the response.
I ran | Code: | | ping -c 89.16.167.134 |
The response was | Code: | | ping: invalid argument: '89.16.167.134' |
I edited the file and commented out the two nameserver entries.
I then added an extra one: .
When I tried | Code: | | ping -c 89.16.167.134 |
again I got the same invalid argument error as before.
Comments appreciated.
PS How do I tell if I am using IP4 or IP6?
Cheers
MF
PPS I looked at the output. Nothing new seemed to appear in it that I could see from the last thing I did the other day. |
|
| Back to top |
|
|
freke
l33t
Joined: 23 Jan 2003
Posts: 603
Location: Somewhere in Denmark
|
| Posted: Sat Oct 10, 2020 2:00 pm Post subject: |
|
|
| mikefot wrote: | Many thanks for the response.
I ran | Code: | | ping -c 89.16.167.134 |
The response was | Code: | | ping: invalid argument: '89.16.167.134' |
I edited the file and commented out the two nameserver entries.
|
| Code: | | ping -c 10 89.16.167.134 |
| Code: | -c count
Stop after sending count ECHO_REQUEST packets. With deadline option, ping waits for count ECHO_REPLY packets, until the timeout expires. |
ie. the -c needs a number of pings you want to perform. |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 687
|
| Posted: Sat Oct 10, 2020 2:07 pm Post subject: |
|
|
Many thanks for your response and suggestion.
I tried adding in a count number but I still get the error | Code: | | ping: connect: Network is unreachable |
.
Comments appreciated.
Regards
MF |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 16494
|
| Posted: Sat Oct 10, 2020 4:00 pm Post subject: |
|
|
| Please show the output of dig www.google.co.uk ; ip route. |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 687
|
| Posted: Sat Oct 10, 2020 4:27 pm Post subject: |
|
|
Many thanks for your advice.
The output from dig is here:
| Code: | ➜ mikef dig www.google.co.uk ; ip route
; <<>> DiG 9.16.6 <<>> www.google.co.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10230
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.google.co.uk. IN A
;; ANSWER SECTION:
www.google.co.uk. 60 IN A 216.239.38.120
;; Query time: 22 msec
;; SERVER: fdee:615d:e88b:0:a2bd:cdff:fe72:2000#53(fdee:615d:e88b:0:a2bd:cdff:fe72:2000)
;; WHEN: Sat Oct 10 17:23:01 BST 2020
;; MSG SIZE rcvd: 50
➜ mikef |
Comments appreciated
Regards
MF |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 16494
|
| Posted: Sat Oct 10, 2020 5:46 pm Post subject: |
|
|
| I asked also for ip route. I see in your paste that you tried to run it, but somehow its output is not present. Please run it freestanding and post its output as well. |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 687
|
| Posted: Sat Oct 10, 2020 5:53 pm Post subject: |
|
|
Many thanks again.
I tried running and:
| Code: | ➜ mikef netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
➜ mikef ip route
➜ mikef |
I don't seem to get much output from either command.
Suggestions welcome.
Regards
MF
PS
I ran a few extra commands:
| Code: | ➜ mikef ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 54:a0:50:d5:11:f8 brd ff:ff:ff:ff:ff:ff
inet6 2a02:c7d:a18f:dc00:56a0:50ff:fed5:11f8/64 scope global dynamic mngtmpaddr
valid_lft 6113sec preferred_lft 2510sec
inet6 fdee:615d:e88b:0:56a0:50ff:fed5:11f8/64 scope global dynamic mngtmpaddr
valid_lft forever preferred_lft forever
inet6 fe80::56a0:50ff:fed5:11f8/64 scope link
valid_lft forever preferred_lft forever
3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
➜ mikef
➜ mikef ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::56a0:50ff:fed5:11f8 prefixlen 64 scopeid 0x20<link>
inet6 2a02:c7d:a18f:dc00:56a0:50ff:fed5:11f8 prefixlen 64 scopeid 0x0<global>
inet6 fdee:615d:e88b:0:56a0:50ff:fed5:11f8 prefixlen 64 scopeid 0x0<global>
ether 54:a0:50:d5:11:f8 txqueuelen 1000 (Ethernet)
RX packets 37565 bytes 11498260 (10.9 MiB)
RX errors 0 dropped 13366 overruns 0 frame 0
TX packets 14658 bytes 2377059 (2.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 2 bytes 78 (78.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2 bytes 78 (78.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sit0: flags=128<NOARP> mtu 1480
sit txqueuelen 1000 (IPv6-in-IPv4)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
➜ mikef
|
PS I am using |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 16494
|
| Posted: Sat Oct 10, 2020 7:36 pm Post subject: |
|
|
I see. You didn't drop the output the first time. There just was no output to show. I did not even consider that possibility, because it is extremely rare, especially in the presence of any working network resources. You should always have at least a few routes. If you don't, networking in general will not work well.
Based on your other output, you have no IPv4 address, which explains the lack of IPv4 routes. The resources that work are probably served over IPv6. So the question then becomes, why do you not have an IPv4 address? If your system were in working order, how would you expect it to get an IPv4 address? NetworkManager? DHCPCD? Something else? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 47101
Location: 56N 3W
|
| Posted: Sat Oct 10, 2020 8:33 pm Post subject: |
|
|
mikefot,
A few things.
That firefox works but ping www.google.co.uk fails shows that you have a nameserver issue.
Firefox uses its own DNSSec nameservers if it can reach them, not the ones you have in /etc/resolv.conf.
That may well be a privacy issue, since Mozilla knows all the websites you visit, rather than your ISP, or as well as your ISP.
Anyway that's a free extra.
| Code: | | ping -c 89.16.167.134 |
is incorrect. -c expects a value for the number of pings to send. If -cX is omitted, its ping forever.
The IP is not a valid argument to the -c option.
| Code: | nameserver 8.8.8.8
ping 89.16.167.134 |
are all using IPv4 addresses.
IPv6 addresses look like fe80::2e0:4cff:fe69:1509
All the public IPv6 addresses begin with a 2
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 687
|
| Posted: Sun Oct 11, 2020 9:32 am Post subject: |
|
|
Many thanks for your help again.
Firefox was working fine until I did a recent world update.
I read the updates and I think there was an instruction in there to run
an emerge command recommended to deal with the supposed retiring of if I recall it correctly.
I noticed during the most recent world update and run that some of the may still
be around plus some other deprecated stuff I need to get rid of.
Maybe that has got something to do with this problem appearing.
Regards
MF |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 47101
Location: 56N 3W
|
| Posted: Sun Oct 11, 2020 10:13 am Post subject: |
|
|
mikefot,
Pyton:2.7 will be around for a while yet. Some big packages need it for their build systems.
--depclean will remove python:2.7 when you don't need it unless you force keeing around with world file pollution or /etc/portage/* entries.
Your shows that you have an IPv6 public IP but no IPv4 address at all.
This means that IPv6 might work but that IPv4 cannot. Not everything on the internet supports IPv6 yet, so you have lost at least the IPv4 only internet.
The question now becomes how do you get your IPv4 setup?
If you didn't do anything special, it will be dhcp.
What does have to say?
When you get the prompt back, what does show?
IPv6 and IPv4 are almost completely separate, other than using the same wires.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 687
|
| Posted: Sun Oct 11, 2020 10:25 am Post subject: |
|
|
Many thanks for your advice.
I ran a couple of times. It doesn't generate much output.
I also ran as well:
| Code: | ➜ mikef dhcpcd eth0
sending commands to master dhcpcd process
➜ mikef dhcpcd eth0
sending commands to master dhcpcd process
➜ mikef ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fdee:615d:e88b:0:56a0:50ff:fed5:11f8 prefixlen 64 scopeid 0x0<global>
inet6 fe80::56a0:50ff:fed5:11f8 prefixlen 64 scopeid 0x20<link>
inet6 2a02:c7d:a18f:dc00:56a0:50ff:fed5:11f8 prefixlen 64 scopeid 0x0<global
ether 54:a0:50:d5:11:f8 txqueuelen 1000 (Ethernet)
RX packets 195 bytes 24989 (24.4 KiB)
RX errors 0 dropped 149 overruns 0 frame 0
TX packets 11 bytes 930 (930.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
➜ mikef |
Comments appreciated.
Regards
MF
PS Would this command help at all: | Code: | | touch /etc/udev/rules.d/80-net-name-slot.rules |
?
PPS I have googled around to look for other cases where people had this kind of problem.
Possible causes were incorrect system time. Releasing and reinstating the IP address was another remedial suggestion.
PPPS
Here is a bit more output:
| Code: | mikef ip -4 -c -o address
1: lo inet 127.0.0.1/8 brd 127.255.255.255 scope host lo\ valid_lft forever preferred_lft for
ever |
|
|
| Back to top |
|
|
mikefot
l33t
Joined: 19 Nov 2014
Posts: 687
|
| Posted: Fri Oct 16, 2020 10:02 am Post subject: |
|
|
The problem has cured itself somehow.
Regards
MF |
|
| Back to top |
|
|
|
Networking & Security
