I have a PCSpecialist laptop, which I find great. Except that the
socket for the wired router cable is 'upside-down', and I once tried to
insert the plug in what I had forgotten was the incorrect orientation.
Since then, the wired connection doesn't seem to want to work, all
indications are that it is working and communicating with the router,
but it won't load any webpages. Pings work fine. The manufacturer, who
does not support Linux, naturally wants me to return the laptop so it
can fix the socket. Fair enough. I am using the Wifi instead until I can
find the opportunity to do without the machine for a week or so.
But are there any tests that I can do to try and find out what the
problem is? I wonder if one of the pins in the socket has got bent out
of shape or contact, and how does it appear as though there is
communication, but it doesn't actually work?

Any help welcome, out of curiosity.
--
Davey.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Am Sonntag, 30. Januar 2022, um 12:04:48 Uhr schrieb Davey:

I have a PCSpecialist laptop, which I find great. Except that the
socket for the wired router cable is 'upside-down', and I once tried
to insert the plug in what I had forgotten was the incorrect
orientation. Since then, the wired connection doesn't seem to want to
work, all indications are that it is working and communicating with
the router, but it won't load any webpages. Pings work fine. The manufacturer, who does not support Linux, naturally wants me to
return the laptop so it can fix the socket. Fair enough. I am using
the Wifi instead until I can find the opportunity to do without the
machine for a week or so. But are there any tests that I can do to
try and find out what the problem is? I wonder if one of the pins in
the socket has got bent out of shape or contact, and how does it
appear as though there is communication, but it doesn't actually work?

Any help welcome, out of curiosity.

Show the output of
ip a
ip route show
ip -6 route show
cat /etc/resolv.conf
systemd-resolve --status --no-pager

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Davey <davey@example.invalid> wrote:

I have a PCSpecialist laptop, which I find great. Except that the
socket for the wired router cable is 'upside-down', and I once tried to insert the plug in what I had forgotten was the incorrect orientation.
Since then, the wired connection doesn't seem to want to work, all indications are that it is working and communicating with the router,
but it won't load any webpages. Pings work fine. The manufacturer, who
does not support Linux, naturally wants me to return the laptop so it
can fix the socket. Fair enough. I am using the Wifi instead until I can
find the opportunity to do without the machine for a week or so.
But are there any tests that I can do to try and find out what the
problem is? I wonder if one of the pins in the socket has got bent out
of shape or contact, and how does it appear as though there is
communication, but it doesn't actually work?

If pings work fine then I can't see how there can be anything wrong
with the hardware. It sounds more like a DNS problem to me, i.e. the
WiFi connection has proper DNS whereas the wired connection, for
whatever reason, has no DNS.

Simple thing to try, get the IP address of some web site ('host <name
of website>' at the command line), then turn off WiFi and try
connecting to that numeric IP address in the browser address bar.

By the way you have turned off the WiFi when you try the wired
connection have you? It often confuses things if you have both at the
same time. To do a thorough check turn off the WiFi, then reboot the
laptop, then try the wired connection.

--
Chris Green
·

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Davey wrote:

it won't load any webpages. Pings work fine.

Then it's not physical problem caused by inserting the plug badly.

Static or dynamic IP address?
default gateway not pointing to router?
firewall rules?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 30 Jan 2022 12:32:01 +0000
Chris Green <cl@isbd.net> wrote:

Davey <davey@example.invalid> wrote:

I have a PCSpecialist laptop, which I find great. Except that the
socket for the wired router cable is 'upside-down', and I once
tried to insert the plug in what I had forgotten was the incorrect orientation. Since then, the wired connection doesn't seem to want
to work, all indications are that it is working and communicating
with the router, but it won't load any webpages. Pings work fine.
The manufacturer, who does not support Linux, naturally wants me to
return the laptop so it can fix the socket. Fair enough. I am using
the Wifi instead until I can find the opportunity to do without the
machine for a week or so. But are there any tests that I can do to
try and find out what the problem is? I wonder if one of the pins
in the socket has got bent out of shape or contact, and how does it
appear as though there is communication, but it doesn't actually
work?

If pings work fine then I can't see how there can be anything wrong
with the hardware. It sounds more like a DNS problem to me, i.e. the
WiFi connection has proper DNS whereas the wired connection, for
whatever reason, has no DNS.

Simple thing to try, get the IP address of some web site ('host <name
of website>' at the command line), then turn off WiFi and try
connecting to that numeric IP address in the browser address bar.

By the way you have turned off the WiFi when you try the wired
connection have you? It often confuses things if you have both at the
same time. To do a thorough check turn off the WiFi, then reboot the
laptop, then try the wired connection.

Well, that was a surprise. Ping now does not work, so either it didn't
before (last month) and I mis-interpreted something, or it has degraded. Whichever, the Connection Info. box still says 'Connected', but that is
as far as it goes.
All other settings look correct, to me, and I tried connecting both Automatically and Manually.
So a trip back to base is after all in order.
Thanks, All, for the info, though.
--
Davey.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 30 Jan 2022 13:55:47 +0000
Andy Burns <usenet@andyburns.uk> wrote:

Davey wrote:

it won't load any webpages. Pings work fine.

Then it's not physical problem caused by inserting the plug badly.

Static or dynamic IP address?
default gateway not pointing to router?
firewall rules?

Thanks, folks, I'll do the tests prescribed and report back.
That sounds encouraging.

--
Davey.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Davey <davey@example.invalid> wrote:

By the way you have turned off the WiFi when you try the wired
connection have you? It often confuses things if you have both at the
same time. To do a thorough check turn off the WiFi, then reboot the laptop, then try the wired connection.

Well, that was a surprise. Ping now does not work, so either it didn't
before (last month) and I mis-interpreted something, or it has degraded. Whichever, the Connection Info. box still says 'Connected', but that is
as far as it goes.
All other settings look correct, to me, and I tried connecting both Automatically and Manually.
So a trip back to base is after all in order.
Thanks, All, for the info, though.

I'm still a bit confused as to what's going on.

Where are you trying to connect "Automatically and Manually"? ... and
my Connection Info. box doesn't say 'connected' or not, it has lots of information about the connectio like the IP address, MAC address, speed
and so on.

--
Chris Green
·

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Davey wrote:

So a trip back to base is after all in order.

Might as well give the replies to Marco's questions, could save it a wasted journey?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 30 Jan 2022 18:22:21 +0000
Chris Green <cl@isbd.net> wrote:

Davey <davey@example.invalid> wrote:

By the way you have turned off the WiFi when you try the wired
connection have you? It often confuses things if you have both
at the same time. To do a thorough check turn off the WiFi, then
reboot the laptop, then try the wired connection.

Well, that was a surprise. Ping now does not work, so either it
didn't before (last month) and I mis-interpreted something, or it
has degraded. Whichever, the Connection Info. box still says
'Connected', but that is as far as it goes.
All other settings look correct, to me, and I tried connecting both Automatically and Manually.
So a trip back to base is after all in order.
Thanks, All, for the info, though.

I'm still a bit confused as to what's going on.

Where are you trying to connect "Automatically and Manually"? ... and
my Connection Info. box doesn't say 'connected' or not, it has lots of information about the connectio like the IP address, MAC address,
speed and so on.

Briefly, if I click on the Connection Info. box, it says 'Connected'.
This is Ubuntu 18.04.
The Auto and Manual refers to the DHCP or not connection.
More tomorrow, it's bed-time.
--
Davey.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 31 Jan 2022 02:11:22 +0000
Davey <davey@example.invalid> wrote:

On Sun, 30 Jan 2022 18:22:21 +0000
Chris Green <cl@isbd.net> wrote:

Davey <davey@example.invalid> wrote:

By the way you have turned off the WiFi when you try the wired connection have you? It often confuses things if you have both
at the same time. To do a thorough check turn off the WiFi,
then reboot the laptop, then try the wired connection.

Well, that was a surprise. Ping now does not work, so either it
didn't before (last month) and I mis-interpreted something, or it
has degraded. Whichever, the Connection Info. box still says
'Connected', but that is as far as it goes.
All other settings look correct, to me, and I tried connecting
both Automatically and Manually.
So a trip back to base is after all in order.
Thanks, All, for the info, though.

I'm still a bit confused as to what's going on.

Where are you trying to connect "Automatically and Manually"? ...
and my Connection Info. box doesn't say 'connected' or not, it has
lots of information about the connectio like the IP address, MAC
address, speed and so on.

Briefly, if I click on the Connection Info. box, it says 'Connected'.
This is Ubuntu 18.04.
The Auto and Manual refers to the DHCP or not connection.
More tomorrow, it's bed-time.

To confirm, I shut down the Wifi, inserted the network cable, and
rebooted the PC.
The setup was set to DHCP, with Auto DNS and Routes. The Connections box
again showed the Wired connection to be Connected, at 1000 Mb/s.
But all attempts to actually connect to another PC failed, ping
requests going on for ages with no response. However, removing the
cable from the PC's socket did result in the Connection indicator
disappearing, so there is some communication there, but certainly not
enough for it to work.
--
Davey.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

In article <st8df2$9e0$1@dont-email.me>, Davey <davey@example.invalid> wrote:

To confirm, I shut down the Wifi, inserted the network cable, and
rebooted the PC.
The setup was set to DHCP, with Auto DNS and Routes. The Connections box again showed the Wired connection to be Connected, at 1000 Mb/s.
But all attempts to actually connect to another PC failed, ping
requests going on for ages with no response. However, removing the
cable from the PC's socket did result in the Connection indicator disappearing, so there is some communication there, but certainly not
enough for it to work.

This suggests that the problem is probably not with the PC's network interface, but it may take a bit of methodical diagnosis.

Can you go into a shell and post the output of the following two commands?

ifconfig -a
netstat -rn

You could also use tcpdump to see if the PC is hearing anything on the network:

sudo tcpdump -n -i any -c 10

(The -c 10 makes it stop after 10 packets - use control-C if you don't see any)

Obviously, all the above should be done while wifi is still switched off.
You may need to capture the outputs in files if you need to re-enable wifi before you can post the results.

Cheers
Tony

--
Tony Mountifield
Work: tony@softins.co.uk - http://www.softins.co.uk
Play: tony@mountifield.org - http://tony.mountifield.org

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 31 Jan 2022 11:35:12 +0000
Andy Burns <usenet@andyburns.uk> wrote:

Davey wrote:

there is some communication there, but certainly not
enough for it to work.

The output of the commands requested will be more useful for people
to see what's actually happening than your description ... just
saying ...

Answered inline to Marco's post. I hope you can make more sense of it
than I can!
To confirm, pings and ssh requests to a local PC on the same network
just hang forever with no result.
--
Davey.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 30 Jan 2022 13:41:05 +0100
Marco Moock <mo01@posteo.de> wrote:

Show the output of
ip a

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 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000 link/ether 80:fa:5b:94:d5:65 brd ff:ff:ff:ff:ff:ff inet 192.168.179.2/24 brd 192.168.179.255 scope
global dynamic noprefixroute enp1s0f1 valid_lft 21578sec preferred_lft
21578sec inet6 fe80::26a4:47a1:73f3:1275/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN
group default qlen 1000 link/ether 38:fc:98:5b:6c:7e brd
ff:ff:ff:ff:ff:ff

ip route show

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 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000 link/ether 80:fa:5b:94:d5:65 brd ff:ff:ff:ff:ff:ff inet 192.168.179.2/24 brd 192.168.179.255 scope
global dynamic noprefixroute enp1s0f1 valid_lft 21578sec preferred_lft
21578sec inet6 fe80::26a4:47a1:73f3:1275/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN
group default qlen 1000 link/ether 38:fc:98:5b:6c:7e brd
ff:ff:ff:ff:ff:ff

ip -6 route show

::1 dev lo proto kernel metric 256 pref medium
fe80::/64 dev enp1s0f1 proto kernel metric 100 pref medium
fe80::/64 dev enp1s0f1 proto kernel metric 256 pref medium

cat /etc/resolv.conf

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS
servers # currently in use.
#
# Third party programs must not access this file directly, but only
through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5)
in a different way, # replace this symlink by a static file or a
different symlink. #
# See man:systemd-resolved.service(8) for details about the supported
modes of # operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0

systemd-resolve --status --no-pager

Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 3 (wlp6s0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 2 (enp1s0f1)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.179.1
DNS Domain: ~.



--
Davey.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Davey wrote:

there is some communication there, but certainly not
enough for it to work.

The output of the commands requested will be more useful for people to see what's actually happening than your description ... just saying ...

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 31/01/2022 10:25, Davey wrote:

To confirm, I shut down the Wifi, inserted the network cable, and
rebooted the PC.
The setup was set to DHCP, with Auto DNS and Routes. The Connections box again showed the Wired connection to be Connected, at 1000 Mb/s.
But all attempts to actually connect to another PC failed, ping
requests going on for ages with no response. However, removing the
cable from the PC's socket did result in the Connection indicator disappearing, so there is some communication there, but certainly not
enough for it to work.

First thing to try is the simplest one, a different cable.

--

Fake news kills!

I may be contacted via the contact address given on my website:
www.macfh.co.uk

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 31 Jan 2022 12:36:08 +0000
Java Jive <java@evij.com.invalid> wrote:

On 31/01/2022 10:25, Davey wrote:

To confirm, I shut down the Wifi, inserted the network cable, and
rebooted the PC.
The setup was set to DHCP, with Auto DNS and Routes. The
Connections box again showed the Wired connection to be Connected,
at 1000 Mb/s. But all attempts to actually connect to another PC
failed, ping requests going on for ages with no response. However,
removing the cable from the PC's socket did result in the
Connection indicator disappearing, so there is some communication
there, but certainly not enough for it to work.

First thing to try is the simplest one, a different cable.

Well, that led to an interesting discovery.
I knew that I had tried that before, but it was worth doing it
again, to be sure.
I had a spare cable handy, already plugged into the router, so I
switched them at the PC. And it worked! To confirm that the cable
itself was faulty, I then switched the cables at the router, and the
failure stayed with the router socket, not the cable. I was not
expecting that. A couple of back-and-forth changes confirms this.
So the problem is the socket at the router, rather than the PC or the
cable. My attention now shifts to the router. Maybe the socket is set
up differently from the others. I don't remember it having any problem
when I last used it in that socket, for a different laptop, so maybe the
router setup for that socket has changed.
Thanks for the suggestion, even though it was not the problem, it led
to a new course of action.
Maybe the results of the tests I posted earlier might hint at the
problem in the router? I will dig into it's setup and see if I can find anything.
If this posting is successful, then it was transmitted via the Wired
router connection, at last.
--
Davey.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 31 Jan 2022 12:36:08 +0000
Java Jive <java@evij.com.invalid> wrote:

On 31/01/2022 10:25, Davey wrote:

To confirm, I shut down the Wifi, inserted the network cable, and
rebooted the PC.
The setup was set to DHCP, with Auto DNS and Routes. The
Connections box again showed the Wired connection to be Connected,
at 1000 Mb/s. But all attempts to actually connect to another PC
failed, ping requests going on for ages with no response. However,
removing the cable from the PC's socket did result in the
Connection indicator disappearing, so there is some communication
there, but certainly not enough for it to work.

First thing to try is the simplest one, a different cable.

Found it! The LAN socket on the router had guest access enabled,
although I have never had any guests using it. Problem solved. I am now
online using the wired connection of my laptop.

Thanks to everyone for working with me, it has led to the answer.

--
Davey.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Am Montag, 31. Januar 2022, um 12:01:26 Uhr schrieb Davey:

On Sun, 30 Jan 2022 13:41:05 +0100
Marco Moock <mo01@posteo.de> wrote:

Show the output of
ip a

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 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000 link/ether 80:fa:5b:94:d5:65 brd ff:ff:ff:ff:ff:ff inet 192.168.179.2/24 brd 192.168.179.255 scope
global dynamic noprefixroute enp1s0f1 valid_lft 21578sec preferred_lft 21578sec inet6 fe80::26a4:47a1:73f3:1275/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN
group default qlen 1000 link/ether 38:fc:98:5b:6c:7e brd
ff:ff:ff:ff:ff:ff

ip route show

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 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000 link/ether 80:fa:5b:94:d5:65 brd ff:ff:ff:ff:ff:ff inet 192.168.179.2/24 brd 192.168.179.255 scope
global dynamic noprefixroute enp1s0f1 valid_lft 21578sec preferred_lft 21578sec inet6 fe80::26a4:47a1:73f3:1275/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN
group default qlen 1000 link/ether 38:fc:98:5b:6c:7e brd
ff:ff:ff:ff:ff:ff

ip -6 route show

::1 dev lo proto kernel metric 256 pref medium
fe80::/64 dev enp1s0f1 proto kernel metric 100 pref medium
fe80::/64 dev enp1s0f1 proto kernel metric 256 pref medium

cat /etc/resolv.conf

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to
the # internal DNS stub resolver of systemd-resolved. This file lists
all # configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS
servers # currently in use.
#
# Third party programs must not access this file directly, but only
through the # symlink at /etc/resolv.conf. To manage
man:resolv.conf(5) in a different way, # replace this symlink by a
static file or a different symlink. #
# See man:systemd-resolved.service(8) for details about the supported
modes of # operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0

systemd-resolve --status --no-pager

Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 3 (wlp6s0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 2 (enp1s0f1)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.179.1
DNS Domain: ~.

You should be able to reach servers via IPv4, but not via IPv6.
Also check your DNS:

dig google.com

Then test a ping google.com

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 31 Jan 2022 20:36:51 +0100
Marco Moock <mo01@posteo.de> wrote:

Am Montag, 31. Januar 2022, um 12:01:26 Uhr schrieb Davey:

On Sun, 30 Jan 2022 13:41:05 +0100
Marco Moock <mo01@posteo.de> wrote:

Show the output of
ip a

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 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
fq_codel state UP group default qlen 1000 link/ether
80:fa:5b:94:d5:65 brd ff:ff:ff:ff:ff:ff inet 192.168.179.2/24 brd 192.168.179.255 scope global dynamic noprefixroute enp1s0f1
valid_lft 21578sec preferred_lft 21578sec inet6 fe80::26a4:47a1:73f3:1275/64 scope link noprefixroute valid_lft
forever preferred_lft forever 3: wlp6s0: <BROADCAST,MULTICAST> mtu
1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 38:fc:98:5b:6c:7e brd ff:ff:ff:ff:ff:ff

ip route show

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 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
fq_codel state UP group default qlen 1000 link/ether
80:fa:5b:94:d5:65 brd ff:ff:ff:ff:ff:ff inet 192.168.179.2/24 brd 192.168.179.255 scope global dynamic noprefixroute enp1s0f1
valid_lft 21578sec preferred_lft 21578sec inet6 fe80::26a4:47a1:73f3:1275/64 scope link noprefixroute valid_lft
forever preferred_lft forever 3: wlp6s0: <BROADCAST,MULTICAST> mtu
1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 38:fc:98:5b:6c:7e brd ff:ff:ff:ff:ff:ff

ip -6 route show

::1 dev lo proto kernel metric 256 pref medium
fe80::/64 dev enp1s0f1 proto kernel metric 100 pref medium
fe80::/64 dev enp1s0f1 proto kernel metric 256 pref medium

cat /etc/resolv.conf

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to
the # internal DNS stub resolver of systemd-resolved. This file
lists all # configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers # currently in use.
#
# Third party programs must not access this file directly, but only
through the # symlink at /etc/resolv.conf. To manage
man:resolv.conf(5) in a different way, # replace this symlink by a
static file or a different symlink. #
# See man:systemd-resolved.service(8) for details about the
supported modes of # operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0

systemd-resolve --status --no-pager

Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 3 (wlp6s0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 2 (enp1s0f1)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.179.1
DNS Domain: ~.

You should be able to reach servers via IPv4, but not via IPv6.
Also check your DNS:

dig google.com

Then test a ping google.com

Thanks, but it's all working now. See my other posts.
Much obliged for the help and attention.
--
Davey.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)