no internet connection in opensuse 13.2, can't connet to router

Hello,

I have an opensuse 13.2 installation that has worked well for a while. Recently, I cloned the drive to a larger SSD so I would have more room for additional partitions. This caused some boot issues that have been more or less resolved.

Not that I am able to get back into the OS, I find that I no longer have an internet connection. It appears that the adapter is running, but it is like firefox can’t resolve the address. I don’t see anything in my router logs that is helpful. There are a few notations about ‘Out-of-order TCP reset’ but nothing that would indicate that all connections are being blocked.

Can anyone suggest where to start to get my connection back. Please let me know if there is additional information that I need to post.

Thanks,

LMHmedchem

What’s the output from

ls -l /etc/resolv.*

Here it is,

ls -l /etc/resolv.*
-rw-r--r-- 1 root root 199 Jul 11 14:35 /etc/resolv.conf
-rw-r--r-- 1 root root 846 Jul 12 01:17 /etc/resolv.conf.netconfig

In case it is helpful, this is the content of those files,

resolv.conf

nameserver 127.0.1.1
search hsd1.ma.comcast.net

resolv.conf.netconfig

search hsd1.ma.comcast.net
nameserver 192.168.10.1

Firefox simply reports that it can’t find the server for any page I try to display. My router is accessed through http://my.firewall/index2.html, and I get the same message from firefox about not finding it if I try to go there. I was able to access my router control panel from this opensuse install before, so I’m not sure what the issue is now.

LMHmedchem

What’s the “ifconfig” output?
For example from my 13.2 system it’s:


 # ifconfig 
enp2s0    Link encap:Ethernet  Hardware Adresse 14:DA:E9:EC:A0:4D  
          inet Adresse:192.168.178.22  Bcast:192.168.178.255  Maske:255.255.255.0
          inet6 Adresse: fe80::16da:e9ff:feec:a04d/64 Gültigkeitsbereich:Verbindung
          inet6 Adresse: 2003:65:ee40:ad00:8878:7172:68b5:39b/64 Gültigkeitsbereich:Global
          inet6 Adresse: 2003:65:ee40:ad00:16da:e9ff:feec:a04d/64 Gültigkeitsbereich:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10100 errors:0 dropped:6 overruns:0 frame:0
          TX packets:10473 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:1000 
          RX bytes:5089380 (4.8 Mb)  TX bytes:3777102 (3.6 Mb)

lo        Link encap:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 Sendewarteschlangenlänge:0 
          RX bytes:8596 (8.3 Kb)  TX bytes:8596 (8.3 Kb)

 # 

And, what’s “systemd” saying about the “network.service”?
For example, my 13.2 machine:


 # systemctl status network.service 
wicked.service - wicked managed network interfaces
   Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled)
   Active: active (exited) since Di 2016-07-12 08:09:35 CEST; 2h 48min ago
  Process: 963 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS)
 Main PID: 963 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/wicked.service

Jul 12 08:09:17 xxx systemd[1]: Starting wicked managed network interfaces...
Jul 12 08:09:35 xxx wicked[963]: lo              up
Jul 12 08:09:35 xxx wicked[963]: enp2s0          up
Jul 12 08:09:35 xxx systemd[1]: Started wicked managed network interfaces.
 # 

Try:

# mv resolv.conf.netconfig resolv.conf

I sometimes have that problem when I switch between “wicked” and “NetworkManager”.

That worked just fine, I now have my connection back.

I added,

# cp resolv.conf  resolv.conf.back

and did that first, just in case. I didn’t make a switch in the app that was controlling my network, so I’m not sure were the problem originated. I guess that’s nothing new for me in linux.

I am going to make a new image of the drive and then look at installing an additional OS, so thanks for the help.

LMHmedchem

I also have somewhat related issues, switching between network manager and wicked… I use either a wifi router/gateway on the ethernet port or a USB dongle. The former gets connected automatically by wicked (if it is running) while the latter gets sensed by Network Manager (if it is running).

  • When I use YAST to switch from Network Manager to wicked, the system hangs at 11% when writing the configuration and I have to re-boot.
  • Using Network Services to enable/disable, start/stop the services does help but success is not always guaranteed…Could this be a bug or just a bad installation?
  • I always get a notification, " Can’t find a usable proxy script …" on network start up. How do I fix this?
  • I don’t seem to have /etc/resolv.conf.netconfig on my system. The contents of /etc/resolv.conf include two nameserver ip addresses on the last two lines in the file and none of them is 127.0.0.1 as indicated by LMHmedchem.

I must quickly add that despite the above issues, either way I still get my internet connection eventually after some tweaking but it is frustrating. Is there a way I can get the OS to pick the correct network service based on the device in use?

I’m still learning Linux and can use all the help I can get! Thanks in advance.

Networkmanager should be able to deal with both of them, even at the same time ( for whatever reason ).

When you start the 13.2 YaST Network Settings module, it should prompt you with “Confirm Hardware detection” – “detecting Network Cards”: select “continue”.
On the “Overview” tab, check the detected hardware: the following example indicates properties which work:

RTL8111/8168 PCI Express Gigabit Ethernet controller
MAC : 14:da:e9:ec:a0:4d
BusID : 0000:02:00.0

  • Device Name: enp2s0
  • Started manually
  • IP address assigned using DHCP

Click the “Edit” button: check the “General”, “Address” and “Hardware” tabs:
“Activate Device”: “At boot time”; “Maximum Transfer Unit” (MTU): Mostly “Ethernet”; “Dynamic Address”: usually “DHCP”; “Module name”: should be the kernel module (driver) for your hardware (in my case: “r8169”.

Do the same for the “Hostname/DNS” and “Routing” tabs.

If everything has been detected correctly by the YaST Network Settings module then, the new configuration is normally written and activated within a minute or so.

Within the 13.2 YaST “Network Services” on this machine, I can find neither “Network Manager” nor “wicked”.
But:


 > systemctl list-unit-files | grep -iE 'network|wicked'
dbus-org.opensuse.Network.AUTO4.service enabled 
dbus-org.opensuse.Network.DHCP4.service enabled 
dbus-org.opensuse.Network.DHCP6.service enabled 
dbus-org.opensuse.Network.Nanny.service enabled 
network.service                         enabled 
NetworkManager-dispatcher.service       masked  
NetworkManager-wait-online.service      masked  
NetworkManager.service                  masked  
wicked.service                          enabled 
wickedd-auto4.service                   enabled 
wickedd-dhcp4.service                   enabled 
wickedd-dhcp6.service                   enabled 
wickedd-nanny.service                   enabled 
wickedd.service                         enabled 
network-online.target                   static  
network-pre.target                      static  
network.target                          static  
 > 

This could be related to a “Not using Network Manager, only using wicked” issue which was discussed here some time ago – it’s the reason why “NetworkManager-dispatcher.service”, “NetworkManager-wait-online.service” and “NetworkManager.service” are all ‘masked’ on this machine.

On this 13.2 machine the “resolv.conf” files in /etc/ produced by “YaST” and/or patches/updates, are as follows:


 > l /etc/resolv.con*
-rw-r--r-- 1 root root 874 28. Jul 08:01 /etc/resolv.conf
-rw-r--r-- 1 root root 812 13. Jun 09:26 /etc/resolv.conf.netconfig
 > 

Contents:


 > cat /etc/resolv.conf
### /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!
search fritz.box
nameserver fd00::5e49:79ff:fedc:e1aa
nameserver 192.168.178.1
 > 
 > cat /etc/resolv.conf.netconfig
### /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!
search fritz.box
 > 

If in your original post, you posted the <exact> error message you see, a lot of speculation and options could have been avoided.

Based on your original error description “no longer have an Internet connection” and “like firefox can’t resolve an address.”
The first generally speaks to fundamental network connectivity, and the second suggests basic networking is working but there might be a name resolution issue. This is where some basic knowledge of network troubleshooting is required, starting with PING and possibly TRACEROUTE.

Once you narrow down the problem to fundamental networking or a service running on top of networking, you can proceed to narrow down the problem further… If a networking problem, then physical connections and basic network configuration. drivers, etc. If a name resolution problem, then inspecting /etc/resolve.conf and using the nslookup utility.

You mentioned using Firefox, part of your early troubleshooting should have been to determine if your network connectivity problems were Firefox-specific or affects multiple or other apps.

With a lot of guessing, you also mentioned a possible proxy setting issue… But the way you described and didn’t post the exact message, it’s unknown if it was simply a warning or something critical to your connectivity.

If you do have some kind of proxy setting issue (and running a local proxy on localhost or 127.0.0.1 is common),
You should know that your system can have system proxy settings defined a number of different ways, typically in YAST/Wicked (Network Adapter settings), even some other way (command line? Locally installed proxy app?).

Web Browsers also contain their own application-specific proxy settings (would affect only that web browser and no other app), which can typically found in the general area… In FF,

Preferences > Advanced Settings > Network > Settings

FF is somewhat unique in that the default setting is “Use system settings” which for most browsers would be the same as “No Proxy” (By specifying no Web Browser proxy, the browser would normally still be subject to system settings). The default settings for most browsers is to automatically detect settings which might be provided over the network(eg WPAD). You can set this however you wish if you don’t want FF to use a proxy or even try to use a proxy.

So, unless you think you have resolved your problem already, I recommend you start this thread over with posting the <exact> errors you’re seeing. Don’t paraphrase, the exact wording is often associated with a specific problem.

@Tsu2; dcurtisfra …

Thanks so much for your prompt responses. Please find below the outputs from applicable utilities:

linux-s1jb:/etc # ls -l reso*
-rw-r–r-- 1 root root 838 Aug 2 21:26 resolv.conf

linux-s1jb:/etc # cat -n resolv.conf
1 ### /etc/resolv.conf file autogenerated by netconfig!
2 #
3 # Before you change this file manually, consider to define the
4 # static DNS configuration using the following variables in the
5 # /etc/sysconfig/network/config file:
6 # NETCONFIG_DNS_STATIC_SEARCHLIST
7 # NETCONFIG_DNS_STATIC_SERVERS
8 # NETCONFIG_DNS_FORWARDER
9 # or disable DNS configuration updates via netconfig by setting:
10 # NETCONFIG_DNS_POLICY=’’
11 #
12 # See also the netconfig(8) manual page and other documentation.
13 #
14 # Note: Manual change of this file disables netconfig too, but
15 # may get lost when this file contains comments or empty lines
16 # only, the netconfig settings are same with settings in this
17 # file and in case of a “netconfig update -f” call.
18 #
19 ### Please remove (at least) this line when you modify the file!
20 nameserver 41.72.99.141
21 nameserver 8.8.8.8

*As stated earlier you’ll notice the absence of resolv.conf.netconfig from /etc.
You’ll also notice the two additional lines (20, 21) above.
*
Next, the list-unit-files…

linux-s1jb:/etc # systemctl list-unit-files
UNIT FILE STATE
dbus-org.bluez.service enabled
dbus-org.freedesktop.Avahi.service enabled
dbus-org.freedesktop.hostname1.service static
dbus-org.freedesktop.locale1.service static
dbus-org.freedesktop.login1.service static
dbus-org.freedesktop.machine1.service static
dbus-org.freedesktop.ModemManager1.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
dbus-org.freedesktop.timedate1.service static
dbus.service static
network.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager-wait-online.service disabled
NetworkManager.service enabled
wicked.service disabled
wickedd-auto4.service disabled
wickedd-dhcp4.service disabled
wickedd-dhcp6.service disabled
wickedd-nanny.service disabled
wickedd.service static

Notice the following:

  1. Differences in the dbus-org services compared to yours. You have opensuse, I have freedesktop …

  2. Where your services are masked, mine are disabled.

linux-s1jb:/etc # ifconfig
enp0s25 Link encap:Ethernet HWaddr 00:19:99:37:21:17
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:23 Memory:f0180000-f01a0000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:14069 errors:0 dropped:0 overruns:0 frame:0
TX packets:14069 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1136468 (1.0 Mb) TX bytes:1136468 (1.0 Mb)

ppp0 Link encap:Point-to-Point Protocol
inet addr:10.61.163.83 P-t-P:10.64.64.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:22082 errors:0 dropped:0 overruns:0 frame:0
TX packets:21054 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:6865637 (6.5 Mb) TX bytes:2586954 (2.4 Mb)

The question is, given the above would editing resolv.conf and creating resolv.conf.netconfig (copy & paste from your post) help? what of the dbus-org services? Kindly advise.

P.S. The error message should have read “Could not find a usable proxy script.” instead stead of “Can’t find a …”.

@Tsu2, dcurtisfra …

I wish to report that my system is now behaving well in terms of detecting both the broadband modem and the wifi gateway automatically. However I still get the warning: “Could not find a usable proxy script” from Network Proxy Configuration, but I guess I can live with that until I figure out the cause or someone comes to my rescue. The important thing is being able to connect to the internet either way without having to reboot the system!

Unfortunately, I don’t know exactly what I changed to get it working 'cos, in my panic, I tried a lot of things including some of your suggestions and when I rebooted the system, Lo and behold! It worked. Thank you very much for your responses. I learnt a lot about the location of the relevant configuration files as well. Thanks.