I’m experiencing a weird issue with a PC with Leap 42.1 xfce (please note that I’ve prepared a new HDD with the OS in a separate PC - working smoothly - then I moved the HDD in the concerning PC).
It has the AsRock G31M-S mobo with Realtek 8102EL ethernet device.
The fact is that, while I can connect the pc to my small office LAN, I’m unable to connect it to the internet.
I’ve tried several solution:
both changing configuration with yast (trying various network setup method) and with the xfce network manager;
both with auto- and manual setup;
resetting, reconnecting, etc. etc.
Booting with windows7, All is working smoothly.
At last, I have tried to install 42.2 with no results. No way to configure the network card during the installation.
I’m stuck here. Any advice to help me solving that problem? Thanks
I assume that you mean that you think that your system can not connect to systems on the internet. The internet is working IMHO, I am using it at the moment.
There are several steps to check when people think they have no access to internet systems. They should be done one after the other and there is no use in going for the next one if one fails.
Check if your network card is configured with an IP address and a netmask and if those are correct for the network you are in. I assume that is OK in your situation because you report access to other systems on the LAN. Could be done with
su -l -c 'ifconfig -a'
(asks for the root password)
You say the system connects to the LAN it is in, but you did not tell why you think this, nor did you post any prove of it. This is normally checked by doing a ping to a system on the LAN, preferable the router. So please check with
ping -c1 <IP-address-of-the-router>
When you can connect to the router, you have to check if you have a default route to the internet through that router.
su -l -c 'route -n'
(it will ask for the root password)
It should have a line starting with 0.0.0.0 in the Destination column and with the IP address of your router in the Gateway column.
When you have a route to the internet, you can check if you can connect to a system there. E.g.
ping -c1 8.8.8.8
When that works, you have connection to the internet.
One more step. You do not really want t o use IP addresses, but host/domain names. For that you should check if you have a working DNS sever configured. E.g.
nslookup forums.opesuse.org
Please report back here with the results, specialy if you got stuck at a test. Then we might be able to help you.
BTW, I see you are new here (Welcome!). Please use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.
your system has IP address 169.254.100.3 and the network is 169.254.0.0/16.
(there is also an IPv6 address, but we will not handle that now).
you can ping 169.254.100.254, which is supposed to be your router.
the default route points to 169.254.100.254, which is supposed to be your router.
no ping to 8.8.8.8 (a Google DNS server btw) possible.
Thus it looks as if the router does not route :(.
Why?
No connection from the router to the rest of the world?
The router filters your IP address (firewall functionality)?
This 169.254.100.254 is not a router at all?
As you mention that a Windows system has no problems, what are the parameters like net address, default router in that system?
These things are of course better investigated by you locally.
Rests the question of you telling that you tried all sorts of configuring without any details. It could be interesting to know e.g. if you try to use DHCP or configure static (IP addresses and the rest).
I did not detect that the addresses are in the Link-local address range 169.254.0.0/16. Those will not be routed by any router at all, let alone to the internet.
If your router is doing IPv4 NAT, then even link local addresses might access Internet resources.
But,
Machines should not ordinarily be configured with IPv4 link local addresses, it’s bad practice (although acceptable in IPv6) because it means that an important indication whether your network is healthy or not isn’t going to work.
Whatever networking you use, the Default Gateway address must be functional and known to access anything outside your LAN. Is that address in your “route” command correct or not?
Although the Default Gateway may be functional, that by itself only means that remote IP addresses outside your LAN can be accessed. Unless you have functional nameservers, you won’t likely be able to access many Internet sites by name. You need to run “nslookup”
The following launches nslookup
nslookup
You can point to any DNS server in your LAN or your ISP or the Internet by specifying “server” followed by the machine’s IP address. If you don’t specify, then any queries will be made to whatever is currently configured, likely by DHCP. The following example and your DNS server to be a Google DNS server, and will remain that way until you either restart your network services or manually specify again.
server 8.8.8.8
You can now query the configured or specified DNS server for anything you wish. The following queries for the IP address of “www.opensuse.org”
Hallo,
I’m using 169.254.100.x in my lan since I’ve bought a centronics-to-lan adapter already configured with 169.254.100.201, which I was unable to modify.
All my machines were configured on this range 12 years ago.
All seems to be ok, e.g., I was writing on a adjacent PC running Mint with 169.254.100.2.
Anyway I could readdress everything in 30’.
I am afraid there is some problem with the driver - or maybe I’ve missed something on the config side (except addresses).
If you are able to communicate with other machines in your network, then there is nothing wrong with your driver.
You should focus your attention on the two things I wrote about… your Default Gateway (You can test this by pinging something on the Internet like the following)
ping 8.8.8.8
If you return a successful series of results, then good. If you return “network unreachable” then you have a Default Gateway and/or local IP address problem.
and you can test your name resolution similarly by pinging a name and/or analyzing using nslookup as I described in my prior post.
Re: configuring non-link local addresses, you should do so. You probably know more about networking today than 12 years ago, so should be able to configure that network adapter properly instead of using the link local address.
Well, guys, I’m not fully aware of what happened, I’m feeling like a clever monkey.
I’ve changed all my lan addresses and routing - it took a while, mainly on finding the way to enter the printing devices - and magically the PC has been connected to the Internet.
Thank you all for your help!
I’ll be here around, I still have tons of configurations to do. Ciao.
You better inspect what your configs are now and take notes. And try to understand why it works now. As long as you think that there is magic involved, you will not be able to manage your systems/network properly.
Henk, for the time being I have to give up. It works.
Since I know little about networking, in my view the issue could have been related to the improper use of link-local addresses or to a some config restriction built in opensuse. I’ve read a wiki about link-local, but I’ve understood little.
I note that you said that you installed the system on another machine and then moved the drive to the current. But that is likely to be different hardware requiring different configurations. But systemd is set for the first machine. Run initrd to rescan and set things for the second machine.
Hi gogalthorp,
I’m not sure what I did. could you please check this output of /sbin/mkinitrd? I did not notice serious warnings, but It is far beyond my knowledge.
Creating initrd: /boot/initrd-4.1.12-1-default
Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.1.12-1-default 4.1.12-1-default
dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
*** Including module: bash ***
*** Including module: warpclock ***
*** Including module: i18n ***
*** Including module: ifcfg ***
*** Including module: drm ***
*** Including module: plymouth ***
*** Including module: kernel-modules ***
Omitting driver i2o_scsi
*** Including module: resume ***
*** Including module: rootfs-block ***
*** Including module: terminfo ***
*** Including module: udev-rules ***
Skipping udev rule: 91-permissions.rules
Skipping udev rule: 80-drivers-modprobe.rules
*** Including module: haveged ***
*** Including module: systemd ***
*** Including module: usrmount ***
*** Including module: base ***
*** Including module: fs-lib ***
*** Including module: shutdown ***
*** Including module: suse ***
*** Including modules done ***
*** Installing kernel module dependencies and firmware ***
*** Installing kernel module dependencies and firmware done ***
*** Resolving executable dependencies ***
*** Resolving executable dependencies done***
*** Hardlinking files ***
*** Hardlinking files done ***
*** Stripping files ***
*** Stripping files done ***
*** Generating early-microcode cpio image ***
*** Constructing GenuineIntel.bin ****
*** Store current command line parameters ***
Stored kernel commandline:
resume=UUID=...
root=UUID=... rootflags=rw,relatime,data=ordered rootfstype=ext4
*** Creating image file ***
*** Creating image file done ***
Some kernel modules could not be included
This is not necessarily an error:
swap
Creating initrd: /boot/initrd-4.1.31-30-default
Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.1.31-30-default 4.1.31-30-default
dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
dracut module 'multipath' will not be installed, because command 'multipath' could not be found!
*** Including module: bash ***
*** Including module: warpclock ***
*** Including module: i18n ***
*** Including module: ifcfg ***
*** Including module: drm ***
*** Including module: plymouth ***
*** Including module: kernel-modules ***
Omitting driver i2o_scsi
*** Including module: resume ***
*** Including module: rootfs-block ***
*** Including module: terminfo ***
*** Including module: udev-rules ***
Skipping udev rule: 91-permissions.rules
Skipping udev rule: 80-drivers-modprobe.rules
*** Including module: haveged ***
*** Including module: systemd ***
*** Including module: usrmount ***
*** Including module: base ***
*** Including module: fs-lib ***
*** Including module: shutdown ***
*** Including module: suse ***
*** Including modules done ***
*** Installing kernel module dependencies and firmware ***
*** Installing kernel module dependencies and firmware done ***
*** Resolving executable dependencies ***
*** Resolving executable dependencies done***
*** Hardlinking files ***
*** Hardlinking files done ***
*** Stripping files ***
*** Stripping files done ***
*** Generating early-microcode cpio image ***
*** Constructing GenuineIntel.bin ****
*** Store current command line parameters ***
Stored kernel commandline:
resume=UUID=...
root=UUID=... rootflags=rw,relatime,data=ordered rootfstype=ext4
*** Creating image file ***
*** Creating image file done ***
Some kernel modules could not be included
This is not necessarily an error:
swap
Update bootloader...
