15.0 update trashes internet access

English Install/Boot/Login
1

I just updated to 15.0 from 42.3 All went well except for internet access. My server has 2 network cards: one for the LAN, the other for outside access. Both worked just fine under 42.3.

Now the LAN works but not the internet access. Also, when I try updating I get an error message that my proxy port isn’t open, which may be part of the problem. Pinging the external connection from a machine outside the network (this one) works but my web server is not accessible.

Any suggestions? I’ve gone through what I know.

2

Did you:

  • Check the change to the Red Hat Firewall daemon?
  • Execute “rpmconfigcheck” (check for stale configuration files)? – You’ll have to redirect the output to a file to be able to check all the changes which need to be worked through …

<https://en.opensuse.org/SDB:Offline_upgrade> <https://en.opensuse.org/SDB:System_upgrade>

3

in yast, go to network devices. On the last tab, make sure the correct interface is set as your gateway.

4

Meanwhile I have upgraded to LEAP 15.1 as long as it’s now out. I have stopped the proxy server, which now allows me to use the online upgrades. However, the other problems persist. In order of importance:

  1. I can ping all the machines on the network and vice versa, but I still don’t get internet access from the LAN machines via the LEAP 15.1 machine. Even though the network settings seem to be OK. External sources, such as offsite backup, seem to be working properly even though the LAN machines can’t get out.

  2. The websites are still offline. Access attempts simply produce blank pages and/or host not available notices.

I have printed out a long (34 items) list resulting from rpmconfigcheck but have not yet examined them in detail. All but the apache2 items don’t appear to address the internet access problem. I’m hoping to fix that problem without going through the whole list.

In any case, thanks for your help so far.

5

Unfortunately, yes, “rpmconfigcheck” usually generates quite a long list of “things which shall be worked through” but, this is exactly what’s happening during a system upgrade:

  • A system upgrade means that, the system’s packages have been upgraded and, therefore, they’ve been changed.
  • Therefore, the configuration of many packages, due to the fact that they’ve been upgraded, changes.
  • Yes, it’s tedious.
  • Yes, it’s time consuming.
  • But, it’s housekeeping which has to be performed after each and every upgrade.

[HR][/HR]The bad news is, this sometimes has to be done as a result of patches applied during the life of any given system version – “rpmconfigcheck” has to be occasionally run during the life of any given system version, to pick up any package configuration issues caused by patches …

6

Tumbleweed users should also do that from time to time.

7

That looks like a DNS problem - try the command “nslookup google.com”. I had the problem after upgrading from Leap15 to 15.1 and discovered that the file /etc/resolv.conf was missing. After creating it manually and restarting the network everything was OK.

8

I checked /etc/resolv.conf and it’s linked to /var/run/netconfig/resolv.conf. It lists the DNS servers, no problem. I am getting internet access for the server but the link between the LAN and the server is broken. The LAN computers all point to 192.168.2.1, which is the server’s internal address, as their gateway. The server also has an external address to the internet. This setup has worked for years until 15.* Now I can access both the internet and the LAN from the server and I can access the server, but not the internet from the LAN.

Meanwhile I’m working on sorting out the unresolved config files.

9

Have you checked the command “ip route” on the LAN computers? THis should show the default route to the internet. You could add that manually as well using the command

ip route add default via 192.168.1.1 dev eth0

where the address 192.168.1.1 is the gateway and eth0 (or in my case it would be eno1) the computer’s ethernet connection.

10

Huh??? !!! …
Not true on this Leap 15.0 system and ‘/var/run/netconfig/’ only contains two directories: etho/ and lo/ – both of which only contain the netconfig files generated by wicked at boot time.

What are you using to setup the network at boot (systemd) time?

  • Network Manager?
  • Wicked?
  • The systemd “networkd” service?
  • Something else?
11

That’s Leap 15.0. But check that on Leap 15.1 or on Tumbleweed, and you will see that “resolv.conf” is there.

12

That is interesting, nrickert, After upgrade from 15 to 15.1 I had IP addresses but no network. I manually added /etc/resolv.conf afterwards Internet was there again. In tumbleweed I have /etc/resolv.conf but no link to link to /var/run/netconfig. I have there NetworkManager.netconfig which contradicts /etc/resolv.conf. NetworkManager.netconfig lists the router’s IP addresses for DNS (which refers to the DNS servers of the ISP) and in resolv.conf I have those of openDNS. Could you please explain or send a link which explains more about this new set-up?

13

I don’t know the complete reasons for the change. But running

netconfig -f update

is supposed to fix any problems. It should create the needed symbolic link.

I did, at one time, run that command in Tumbleweed. I never needed to run it with 15.1. However, some people might still have problems.

14

Thank you, nrickert, I just die another update and again resolv.conf was gone - IP address but no internet. Again I added resolv.conf manually but after a reboot it was gone again. Again I created it manually and used this command

netconfig -f update

and it created that link. Hopefully the internet is up after another restart. However by now 2 out of 4 computers had this problem and it may be more common.

15

Keep us informed.

I have not heard a lot of complaints about this. However, people might be having problems logging into the forums, so maybe there are unheard problems.

16

So I rebooted and resolv.conf was gone again. To get to the internet I had again to recreate the file /etc/resolv.conf and restart the network. the command

netconfig -f update

created a link and resolv.conf could be read from /var/run/netconfig/ but after a reboot it must have been gone again.

17

Are you using “wicked” or “NetworkManager”?

18

I am using NetworkManager. I just tried renaming /var/run/netconfig/NetworkManager.netconfig into /var/run/netconfig/NetworkManager.netconfig.old and rebooted. The same result. resolv.conf gone (including the link to /var/run/netconfig and no internet access. Here is

cat NetworkManager.netconfig 
CREATETIME='10'
SERVICE='NetworkManager'
INTERFACE='NetworkManager'
DNSSEARCH='fritz.box'
DNSSERVERS='192.168.2.1 fd00::ca0e:14ff:fe12:ea9d'

The IP addresses are from the router (fritz.box) but in resolv.conf I use openDNS:

### /etc/resolv.conf file 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.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!
#
# IPv4 name servers OpenDNS:
nameserver 208.67.222.222
nameserver 208.67.220.220

# IPv6 name servers OpenDNS:
nameserver 2620:0:ccc::2
nameserver 2620:0:ccd::2

I will have a look into /etc/sysconfig/network/config if there is something obvious. You probably know more about this but I have to fix now two computer since they loose their internet access with a reboot.

BTW I have set in the /etc/sysconfig/network/config file NETCONFIG_DNS_POLICY=""

19

OK - I now changed /etc/sysconfig/network/config: I changed NETCONFIG_DNS_STATIC_SERVERS="" to NETCONFIG_DNS_STATIC_SERVERS=“208.67.222.222 208.67.220.220 2620:0:ccc::2” (the two IPv4 and one IPv6 address from openDNS. After a reboot the internet was up.

20

I’m glad you found that.

There’s actually a Yast setting for configuring DNS, but most people use what their router provides with DHCP so they don’t need that setting.