Internet Connection Sharing Failure when updating to 15.4 (from15.3)

pedroSMS · June 21, 2023, 6:27am

Hi,

I have just updated 15.3 to 15.4, and the internet sharing has stopped working. The Wicked network settings seem to look okay, as do the Firewall.

This PC has 2 ethernet connections - eth0 to the internet, eth1 to the local net.

I still have access to the samba server on the local net, but I can’t get either internet nor emails via eth1.

Can anyone help?

Kind regards
Pedro

Sauerland · June 21, 2023, 6:33am

Post:
ip a

Can you ping:
ping -c3 8.8.8.8
ping -c3 google.com

pedroSMS · June 21, 2023, 7:02am

Thank you for your reply @Sauerland.

Results from eth0:

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: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:00:5a:00:01:33 brd ff:ff:ff:ff:ff:ff
altname enp5s0
altname ens3
inet 192.168.175.1/24 brd 192.168.175.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::200:5aff:fe00:133/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:1f:16:2a:d0:31 brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 192.168.1.100/24 brd 192.168.1.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::21f:16ff:fe2a:d031/64 scope link
valid_lft forever preferred_lft forever
4: wlan1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:1e:65:eb:ef:c2 brd ff:ff:ff:ff:ff:ff
altname wlp3s0
altname wls1

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=58 time=9.84 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=58 time=10.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=58 time=9.63 ms

— 8.8.8.8 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 9.630/10.103/10.845/0.531 ms
PING google.com (142.250.70.174) 56(84) bytes of data.
64 bytes from mel04s02-in-f14.1e100.net (142.250.70.174): icmp_seq=1 ttl=58 time=10.6 ms
64 bytes from mel04s02-in-f14.1e100.net (142.250.70.174): icmp_seq=2 ttl=58 time=10.0 ms
64 bytes from mel04s02-in-f14.1e100.net (142.250.70.174): icmp_seq=3 ttl=58 time=10.7 ms

— google.com ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 10.025/10.466/10.739/0.314 ms

Results from eth1:

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: enp12s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 00:26:18:53:2c:f4 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:1e:65:29:20:84 brd ff:ff:ff:ff:ff:ff
inet 192.168.175.140/24 brd 192.168.175.255 scope global dynamic noprefixroute wlp2s0
valid_lft 11697sec preferred_lft 11697sec
inet6 fe80::83dc:4e54:d676:f876/64 scope link noprefixroute
valid_lft forever preferred_lft forever

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=13.0 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=13.5 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=13.2 ms

— 8.8.8.8 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 12.991/13.220/13.452/0.188 ms
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=13.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=13.4 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=15.6 ms

— 8.8.8.8 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 13.063/14.029/15.636/1.143 ms

ping: google.com: Temporary failure in name resolution

I hope that helps

Kind regards
Pedro

Sauerland · June 21, 2023, 7:05am

Maybe broken dns?

Post
cat /etc/resolv.conf

pedroSMS · June 21, 2023, 7:16am

Thanks again for your reply @Sauerland .

### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf
### autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
#     NETCONFIG_DNS_STATIC_SEARCHLIST
#     NETCONFIG_DNS_STATIC_SERVERS
#     NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
#     NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
### Call "netconfig update -f" to force adjusting of /etc/resolv.conf.
nameserver 127.0.0.1
nameserver 192.168.1.1
nameserver 0.0.0.0

Kind regards
Pedro

Sauerland · June 21, 2023, 7:28am

Have you running a private dns?

I would try to use some of the public dns.

pedroSMS · June 21, 2023, 7:37am

Thanks for your reply again @Sauerland .

I should have mentioned that 192.168.1.1 is the internet modem connected to eth0.

I have looked into dns settings via yast - I can’t find any reference to private or public dns. Do it go by a different name in yast?

Kind regards
Pedro

Sauerland · June 21, 2023, 7:44am

Why these entries?
127.0.0.1 is f.e. an entry for internal dns-server such as pdns or pdns-resolver…

Maybe change them to a public dns in:
Yast----System----Editor for sysconfig-----network------general—DNS Static Servers

pedroSMS · June 21, 2023, 7:50am

Thanks once more for your reply @Sauerland

nameserver 127.0.0.1
................
nameserver 0.0.0.0

I have no idea. I did not add these entries. If they have added, it would be the 15.4 updater that has done so…

Should I remove them?

Kind regards
Pedro

pedroSMS · June 21, 2023, 8:14am

Thanks again for your reply @Sauerland .

There was no entry for this. I did find -

Yast----System----Editor for sysconfig-----network------general—NETCONFIG DNS Static Servers

The value for this was empty. I entered the value of “public”, but didn’t make any difference.

Kind regards
Pedro

Sauerland · June 21, 2023, 8:19am

Here is my list, but read the commend:

Auswahl_193

pedroSMS · June 21, 2023, 8:27am

I have change mine to -

“1.1.1.1 9.9.9.9 192.168.1.254” , but still not working…

Kind regards
Pedro

pedroSMS · June 21, 2023, 8:48am

I have tried a number different settings, but nothing is working!

I note that ‘ip a’ gives -

nameserver 127.0.0.1
nameserver 1.1.1.1
nameserver 9.9.9.9

192.168.1.254 didn’t come up!?!?

Kind regards
Pedro

hcvv · June 21, 2023, 9:11am

Do not separate the command from the output. All should be copied/pasted in one go. Like here:

boven:~ # 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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether ec:8e:b5:da:0d:0d brd ff:ff:ff:ff:ff:ff
    altname enp1s0
    inet 10.0.0.154/24 brd 10.0.0.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2a02:a465:d34e:1:ee8e:b5ff:feda:d0d/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 7115sec preferred_lft 3515sec
    inet6 fe80::ee8e:b5ff:feda:d0d/64 scope link 
       valid_lft forever preferred_lft forever
boven:~ #

And it shows that ip a gives something completely different from what you say.

BTW. I would use YaST > System > Network Settings and then the tab Hostname/DNS.

pedroSMS · June 21, 2023, 9:28am

Thank you for your reply @hcvv.

Everything is VERY difficult here with this problem. The computer that I am using now is tethered to my phone. It’s VERY difficult to get data & test results between my 2 computers under these conditions.

I will try my best in the future…

Kind regards
Pedro

hcvv · June 21, 2023, 9:57am

What about my suggestion in using YaST > Systems > Network Settings?

Another question, are you using DHCP or fixed IP addresses, etc.

pedroSMS · June 21, 2023, 10:20am

Thank you for your reply @hcvv,

eth0 gets its IP Address from upstream (that part seems to be working).

eth1 is fixed, and uses DHCP to allocate IP Addresses downstream (that part seems to be working okay).

Kind regards
Pedro

hcvv · June 21, 2023, 10:36am

Sorry, but there seems to be a language barrier.

What do you mean by “gets its IP address from upstream”?
And the same “from downstream”?

I know of two ways to get an IP address for an NIC:

Using DHCP to get it (and the netmask and the default router and the DNS server(s)) from a DHCP server, which is most often on the modem/router in the same LAN as the NIC.
Configuring it “fixed”, that all these parameters are defined on the system itself (in configuration files using e.g. YaST > System > Network Settings) and those are used at boot.

hcvv · June 21, 2023, 10:43am

And forgotten:

There is also the possibility the use DHCP, but nevertheless always get the same IP address, that one also could call “fixed”. That then is to be configured in the DHCP server.

pedroSMS · June 21, 2023, 10:53am

Thank you for your reply @hcvv.

The computer with the problem behaves like a router - having a “wide area” port (eth0) and a “local area” port (eth1).

eth0 uses DHCP in a client mode.

eth1 uses DHCP in a server mode.

This computer has been configured this way, and working very well for years. It is only now, that I have upgraded to 15.4 it has stopped working…

Kind regards
Pedro