Using NetworkManager unable to set fixed IP and connect to WAN

English Network/Internet
#1

I am in unfamiliar territory again and trying leap 15.3 and NetworkManager. Previously I had been using TW and Wicked.

From a network installation and with a copper connection everything has been ok with a default dhcp connection using NetworkManager.

Before putting the new system into service I changed the network configuration to a fixed IP and promptly lost my connection to the wan.

In order to post this I have had to change the configuration back to dhcp.

Here are the network addresses with a fixed IP:-

alastair@localhost:~> ip address
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 mq state UP group default qlen 1000
    link/ether 34:40:b5:92:a0:54 brd ff:ff:ff:ff:ff:ff
    altname eno1
    altname enp11s0f0
    inet 192.168.169.135/25 brd 192.168.169.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::8a90:fe0f:f97a:e545/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 34:40:b5:92:a0:55 brd ff:ff:ff:ff:ff:ff
    altname eno2
    altname enp11s0f1
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 36:40:b5:92:a0:59 brd ff:ff:ff:ff:ff:ff
    altname enp0s26f1u2
alastair@localhost:~>

I also ran the commands suggested in an earlier thread with the DHCP

The latter is rather long so I have put it on susepaste:

Pasted as:
https://susepaste.org/54618896
https://paste.opensuse.org/54618896

What trouble me is the lines in the Fixed result:-

4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 36:40:b5:92:a0:59 brd ff:ff:ff:ff:ff:ff
    altname enp0s26f1u2
alastair@localhost:~>

What is this and why is it there. Have I screwed up again?

Also why are the old names being used for devices? Is this only changed in TW?

All help, comments and advice gratefully received.
Budge

#2

What exactly does it mean? You won’t believe how many different interpretations of this I have seen. Show actual command that fails and its output. Full.

Educated guess - either default route or DNS are missing.

#3

To add to @avidjaar. Here is a set of commands to check from bottom to top what works and what not. Maybe you can prove us with them that you really have no connection to the internet:

You check from bottom to top:

  1. Is the NIC up with an IP address?

ip addr

  1. Can you connect to another system on your LAN?

ping -c1 <IP-address of your router>

(I hope you know that address)

  1. Do you have a default route to the Internet?

ip route

  1. Can you connect to a system on the internet?

ping -c1 195.135.221.161

and/or

ping -c1 2001:67c:2178:8::161

  1. Can you resolve host/domain names?

ping -c1 forums.opensuse.org

Take care. As soon a one step fails, that must be resolved first. It is useless to go to the next step before it is resolved.

So start with 1. and do not hesitate to post the output here to get help on the interpretation.

#4

I have it now. When changing to fixed IP (using yast) in the wired tab I hadn’t set the device and for some reason this defaulted to usb0. Restricting the device to eth0 solved the issue. Sorry I hadn’t picked this up but the clue was there in my original post.

That brings me to how on earth can I have a usb0 device and how did it get the address? Here is what I have:-

alastair@localhost:~> ip address
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 mq state UP group default qlen 1000
    link/ether 34:40:b5:92:a0:54 brd ff:ff:ff:ff:ff:ff
    altname eno1
    altname enp11s0f0
    inet 192.168.169.135/24 brd 192.168.169.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::8a90:fe0f:f97a:e545/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 34:40:b5:92:a0:55 brd ff:ff:ff:ff:ff:ff
    altname eno2
    altname enp11s0f1
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 36:40:b5:92:a0:59 brd ff:ff:ff:ff:ff:ff
    altname enp0s26f1u2
    inet 169.254.95.120/24 brd 169.254.95.255 scope link dynamic noprefixroute usb0
       valid_lft 673sec preferred_lft 673sec
    inet6 fe80::41c8:b3ba:1556:6f09/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
alastair@localhost:~>

Could it from an IBM/Lenovo IBM UpdateXpress System Pack Installer which I tried but became doubtful when looking for BIOS updates which might have enabled booting from NVMe?
Whatever it is I think I should remove this connection but have a look at startup settings.

Thanks for the help once more.

#5

Show us output from

dmesg|grep usb0

/usr/sbin/hwinfo --netcard
#6

Hi Deano,
Here are the results of the commands:-

alastair@localhost:~> sudo dmesg|grep usb0
[sudo] password for root: 
    8.840112] cdc_ether 4-2:1.0 usb0: register 'cdc_ether' at usb-0000:00:1a.1-2, CDC Ethernet Device, 36:40:b5:92:a0:59
alastair@localhost:~> 
alastair@localhost:~> sudo /usr/sbin/hwinfo --netcard
25: PCI b00.0: 0200 Ethernet controller                         
  [Created at pci.386]
  Unique ID: rBUF.UiIC1YKJsA9
  Parent ID: vSkL.IhM5noxxQ+3
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:0b:00.0
  SysFS BusID: 0000:0b:00.0
  Hardware Class: network
  Device Name: "Ethernet 1 BroadCom 5709C Ethernet Controller"
  Model: "Broadcom NetXtreme II BCM5716 Gigabit Ethernet"
  Vendor: pci 0x14e4 "Broadcom"
  Device: pci 0x163b "NetXtreme II BCM5716 Gigabit Ethernet"
  SubVendor: pci 0x1014 "IBM"
  SubDevice: pci 0x03e0 
  Revision: 0x20
  Driver: "bnx2"
  Driver Modules: "bnx2"
  Device File: eth0
  Memory Range: 0x92000000-0x93ffffff (rw,non-prefetchable)
  IRQ: 24 (no events)
  HW Address: 34:40:b5:92:a0:54
  Permanent HW Address: 34:40:b5:92:a0:54
  Link detected: yes
  Module Alias: "pci:v000014E4d0000163Bsv00001014sd000003E0bc02sc00i00"
  Driver Info #0:
    Driver Status: bnx2 is active
    Driver Activation Cmd: "modprobe bnx2"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #23 (PCI bridge)

68: PCI b00.1: 0200 Ethernet controller
  [Created at pci.386]
  Unique ID: JNkJ.UiIC1YKJsA9
  Parent ID: vSkL.IhM5noxxQ+3
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:0b:00.1
  SysFS BusID: 0000:0b:00.1
  Hardware Class: network
  Device Name: "Ethernet 2 BroadCom 5709C Ethernet Controller"
  Model: "Broadcom NetXtreme II BCM5716 Gigabit Ethernet"
  Vendor: pci 0x14e4 "Broadcom"
  Device: pci 0x163b "NetXtreme II BCM5716 Gigabit Ethernet"
  SubVendor: pci 0x1014 "IBM"
  SubDevice: pci 0x03e0 
  Revision: 0x20
  Driver: "bnx2"
  Driver Modules: "bnx2"
  Device File: eth1
  Memory Range: 0x94000000-0x95ffffff (rw,non-prefetchable)
  IRQ: 48 (no events)
  HW Address: 34:40:b5:92:a0:55
  Permanent HW Address: 34:40:b5:92:a0:55
  Link detected: no
  Module Alias: "pci:v000014E4d0000163Bsv00001014sd000003E0bc02sc00i00"
  Driver Info #0:
    Driver Status: bnx2 is active
    Driver Activation Cmd: "modprobe bnx2"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #23 (PCI bridge)

100: USB 00.0: 0291 USB Host-to-Host link
  [Created at usb.122]
  Unique ID: rg_L.W3Bp+6TvMh5
  Parent ID: zPk0.7gZT0a5zLs5
  SysFS ID: /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0
  SysFS BusID: 4-2:1.0
  Hardware Class: network
  Model: "IBM RNDIS/CDC ETHER"
  Hotplug: USB
  Vendor: usb 0x04b3 "IBM Corp."
  Device: usb 0x4010 "RNDIS/CDC ETHER"
  Revision: "2.15"
  Driver: "cdc_ether"
  Driver Modules: "cdc_ether"
  Device File: usb0
  Speed: 12 Mbps
  HW Address: 36:40:b5:92:a0:59
  Permanent HW Address: 36:40:b5:92:a0:59
  Link detected: yes
  Module Alias: "usb:v04B3p4010d0215dc02dsc00dp00ic02isc06ip00in00"
  Driver Info #0:
    Driver Status: cdc_ether is active
    Driver Activation Cmd: "modprobe cdc_ether"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #106 (Hub)
alastair@localhost:~>
#7

YaST can only be used to configure wicked.**

NetworkManager** cannot be configured via YaST! You have to use command-line-tools like nmtui or nmcli or - depending on your DE - some GUI-tool like plasma-nm5 from KDE

NetworkManager stores connection-related configurations in connection profiles (simple text files) in /etc/NetworkManager/system-connections, one file per connection-setup. So another way is to create such a connection profile manually (see here for more information)

Regards

susejunky

#8

What I wrote was wrong. I had been using NetworkManager so my actions were correct, my post wrong. Sorry about that and thanks for keeping watch and for the further info re profile.

#9

I should have explained there is a usb stick on board which is used for uefi and booting but the rest of my system is in NVMe. Clearly the usb stick has become involved but it is only there because it is needed because my hardware system cannot boot from NVMe. Too old!

#10

Ok, well at least you should understand that it is an ethernet device connected to the USB subsystem. As it is not explicitly configured by you (as the system administrator) you can ignore it.

#11

Hi Deano,
I have difficulty ignoring it when it seems to be able to find and use an address which I don’t want or AFAIK need.
Do you know what is going on?
I have another problem which may need me to do a new installation so perhaps I should do that.

#12

I have difficulties parsing this sentence (it is rather hard to properly interpret post in the middle of long conversation and without any reference to what you are replying to) but assuming you are talking about USB LAN interface you have two options

  1. Disable it in your BMC/iLO/iDRAC or whatever it is called by vendor of your server. And to answer followup question - I do not know how to do it. Read documentation.
  2. Set it as unmanaged in NetworkManager so it is ignored and does not get automatic connection (with well known IPv4 link-local address). Read man NetworkManager.conf, search for “device section”.
#13

Interfaces can be ignored (unamanged) by NetworkManager as required…

sudo nmcli device set <interface_name> managed no
#14

FWIW, another old thread asking similar…
https://forums.opensuse.org/showthread.php/538248-how-to-disable-interface-in-Networkmanager

#15

This is not persistent to my best knowledge. To persistently ignore device you need to edit NetworkManager.conf.

#16

Hi and thanks for picking up on my earlier posts.
I have two network devices in my machine, only one of which has any plugged in connection.
I expressed my concern and ignorance of how and why a usb device can be seen as having a pingable IP address. To save time here is what I have in my machine now after a new installation of the OS.

alastair@localhost:~> ip address
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 mq state UP group default qlen 1000
    link/ether 34:40:b5:92:a0:54 brd ff:ff:ff:ff:ff:ff
    altname eno1
    altname enp11s0f0
    inet 192.168.169.222/25 brd 192.168.169.255 scope global dynamic noprefixroute eth0
       valid_lft 75265sec preferred_lft 75265sec
    inet6 fe80::3640:b5ff:fe92:a054/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 34:40:b5:92:a0:55 brd ff:ff:ff:ff:ff:ff
    altname eno2
    altname enp11s0f1
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
    link/ether 36:40:b5:92:a0:59 brd ff:ff:ff:ff:ff:ff
    altname enp0s26f1u2
    inet 169.254.95.120/24 brd 169.254.95.255 scope link dynamic noprefixroute usb0
       valid_lft 1055sec preferred_lft 1055sec
    inet6 fe80::4f9f:ee2d:faee:4b40/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
alastair@localhost:~>

I asked as I would like to understand what is going on and what or who is connected to the above IP address. Not, I hope, important, but in these days of internet snooping I am concerned.

#17

Yes, as I linked to in post #14. :wink:

#18

That is fine, but I assume that you’ve made an effort to read what has been posted already?

From man NetworkManager.conf…

KEYFILE SECTION
This section contains keyfile-plugin-specific options, and is normally only used when you are not using any other distro-specific plugin.

   hostname
       This key is deprecated and has no effect since the hostname is now stored in /etc/hostname or other system configuration files according to build options.

   path
       The location where keyfiles are read and stored. This defaults to "/etc/NetworkManager/system-connections".

   unmanaged-devices
       Set devices that should be ignored by NetworkManager.

       See the section called “Device List Format” for the syntax how to specify a device.

       Example:

           unmanaged-devices=interface-name:em4
           unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth2

Any changes made to NetworkManager.conf will take effect the next time NetworkManager is restarted.

#19

According to

which implies you are using some unknown IBM/Lenovo system (Notebook? Desktopt? Server? You did not say, but UpdateXpress is for servers only to my best knowledge) and

this sounds like IMM LAN-over-USB internal connection. In which case you should be able to disable it in IMM as I already told you.

#20

https://www.ibm.com/support/pages/qradar-how-determine-status-lan-over-usb-systemx®-and-thinksystem™-appliances

Appliance firmware updates require that administrators have Ethernet Over USB enabled before a firmware update can be applied. When Ethernet Over USB is not enabled, any firmware update the administrator attempts to apply using the Bootable Media Creator or ToolsCenter utility will fail to update the UEFI. Ethernet/LAN Over USB is required for remote firmware updates with an ISO file and local USB update packages that use an IMG file. The Ethernet over USB setting must be enabled before you update firmware. After the firmware update is complete, the administrator can disable Ethernet Over USB functionality.