Network connection Problems (Hardware/Driver ? ) Opensuse Leap 15

pprkut1 · July 3, 2018, 11:27am

Hello,
i have Problems to connect my Opensuse Leap 15 Installation to a company network. I dont get a IP Adress via DHCP , when i assign a IP Adress manually, i get no connection. Other distributions (Ubuntu, Windows7) get a connection with the same configuration.


# ip addr
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 ####/8 scope host lo
       valid_lft forever preferred_lft forever
2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 98:90:96:b2:91:d5 brd ff:ff:ff:ff:ff:ff
    inet ####/24 brd #### scope global em1
       valid_lft forever preferred_lft forever


ping ####
PING #### (####) 56(84) bytes of data.
From #### icmp_seq=1 Destination Host Unreachable
From #### icmp_seq=2 Destination Host Unreachable
From #### icmp_seq=3 Destination Host Unreachable
^C
--- 10.49.120.177 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4098ms
pipe 4


# /usr/sbin/hwinfo --netcard
06: PCI 19.0: 0200 Ethernet controller                          
  [Created at pci.378]
  Unique ID: WZJ3.GFvflVjqaqC
  SysFS ID: /devices/pci0000:00/0000:00:19.0
  SysFS BusID: 0000:00:19.0
  Hardware Class: network
  Device Name: "Onboard LAN"
  Model: "Intel Ethernet Connection I217-LM"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x153a "Ethernet Connection I217-LM"
  SubVendor: pci 0x1028 "Dell"
  SubDevice: pci 0x05a4 
  Revision: 0x04
  Driver: "e1000e"
  Driver Modules: "e1000e"
  Device File: em1
  Memory Range: 0xf7c00000-0xf7c1ffff (rw,non-prefetchable)
  Memory Range: 0xf7c3d000-0xf7c3dfff (rw,non-prefetchable)
  I/O Ports: 0xf080-0xf09f (rw)
  IRQ: 30 (505 events)
  HW Address: 98:90:96:b2:91:d5
  Permanent HW Address: 98:90:96:b2:91:d5
  Link detected: yes
  Module Alias: "pci:v00008086d0000153Asv00001028sd000005A4bc02sc00i00"
  Driver Info #0:
    Driver Status: e1000e is active
    Driver Activation Cmd: "modprobe e1000e"
  Config Status: cfg=no, avail=yes, need=no, active=unknown


# ethtool em1
Settings for em1:
    Supported ports:  TP ]
    Supported link modes:   10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Supported pause frame use: No
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Advertised pause frame use: No
    Advertised auto-negotiation: Yes
    Speed: 1000Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 1
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: on (auto)
    Supports Wake-on: pumbg
    Wake-on: g
    Current message level: 0x00000007 (7)
                   drv probe link
    Link detected: yes




drv probe link

I tried to install a different driver for the intel e1000e, but it failed because of missing kernel headers.

Can you please help?

deano_ferrari · July 3, 2018, 1:31pm

Obscuring your private IP address is unnecessary. If you assign a static IP address, you also need to manually assign a default route to gain internet connectivity, and configure a valid name server as well for name resolution (via DNS) to work.

I tried to install a different driver for the intel e1000e, but it failed because of missing kernel headers.

Don’t do that. The existing kernel driver is all that is required.

You should post the output of the following…

ip a

ip r

You mention that DHCP didn’t work as expected. Are you using wicked (configured via YaST) or NetworkManager (configured with connection editor, but a DHCP ethernet connection should work out of the box)?

pprkut1 · July 3, 2018, 4:54pm

Hi,
my problem is not the internet connection. Even when i assign manual ip-adresses i can not ping the computers in the same subnet (10.49.120.177).

Still static ip config:


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
2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 98:90:96:b2:91:d5 brd ff:ff:ff:ff:ff:ff
    inet 10.49.120.169/24 brd 10.49.120.255 scope global em1
       valid_lft forever preferred_lft forever
ip r
10.49.120.0/24 dev em1 proto kernel scope link src 10.49.120.169

The not working dhcp seems not to be my problem as i can not ping or reach anything in my network with manual ip adress.
I tried both Network Manager and wicked , with dhcp as well as with static ip.

When i boot ubuntu and windows 7 on the same machine with same configuration, i am able to ping other computers or get a dhcp adress.

does anyone know what “drv probe link” means ?

deano_ferrari · July 4, 2018, 2:12am

I can only suggest that you have assigned an IP address (10.49.120.169/24) in the wrong subnet for your LAN then.

To check DHCP process manually…

Watch the journal (assuming /var/log/journal/ directory exists)…

sudo journalctl -f

or if using rsyslog/syslog-ng

tail -f /var/log/messages

then in another terminal run

sudo dhclient em1

and watch/capture the output generated.

pprkut1 · July 4, 2018, 10:43am

dhclient em1 did not work, the journal gave me following errors:

Jul 04 10:32:07 dhclient-script[9511]: dhclient conflicts with enabled wicked.service and disabledJul 04 10:32:07 dhclient[9505]: /sbin/dhclient-script: unable to pre-init requested interfaces -- see log messages
Jul 04 10:32:07 dhclient[9505]: 
Jul 04 10:32:07 dhclient[9505]: If you think you have received this message due to a bug rather
Jul 04 10:32:07 dhclient[9505]: than a configuration issue please read the section on submitting
Jul 04 10:32:07 dhclient[9505]: bugs on either our web page at www.isc.org or in the README file
Jul 04 10:32:07  dhclient[9505]: before submitting a bug.  These pages explain the proper
Jul 04 10:32:07 dhclient[9505]: process and the information we find helpful for debugging.
Jul 04 10:32:07 dhclient[9505]: 
Jul 04 10:32:07 dhclient[9505]: exiting.
Jul 04 10:32:07 sudo[9504]: pam_unix(sudo:session): session closed for user root

I found following entries for my dhcp reconfiguration:





Jul 04 10:30:02 YaST.desktop[2465]: Run command: /sbin/yast2 lan &
Jul 04 10:30:13 systemd-udevd[452]: Network interface NamePolicy= disabled by default.
Jul 04 10:30:13 systemd-udevd[9331]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 04 10:30:13 systemd-udevd[9330]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 04 10:30:13 systemd-udevd[9329]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 04 10:30:14 systemd[1]: Reloading wicked managed network interfaces.
Jul 04 10:30:14 avahi-daemon[653]: Withdrawing address record for 10.49.120.169 on em1.
Jul 04 10:30:14 avahi-daemon[653]: Leaving mDNS multicast group on interface em1.IPv4 with address 10.49.120.169.
Jul 04 10:30:14 avahi-daemon[653]: Interface em1.IPv4 no longer relevant for mDNS.
Jul 04 10:30:15 kernel: e1000e: em1 NIC Link is Down
Jul 04 10:30:18 kernel: e1000e: em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jul 04 10:30:18 wickedd-dhcp4[657]: em1: Request to acquire DHCPv4 lease with UUID 066e3c5b-3f6f-0900-b702-00001f000000


Jul 04 10:30:33 wickedd-dhcp4[657]: em1: defer timeout 15 reached (state SELECTING)
Jul 04 10:30:45 wicked[9346]: em1             device-ready
Jul 04 10:30:45 wicked[9346]: em1             setup-in-progress
Jul 04 10:30:45 systemd[1]: Reloaded wicked managed network interfaces.
Jul 04 10:30:45 gnome-shell[1518]: Object Meta.WindowActor (0x55e9471493f0), has been already finalized. Impossible to get any property from it.
Jul 04 10:30:45 /usr/lib/gdm/gdm-wayland-session[1454]: == Stack trace for context 0x55e9438e9000 ==
Jul 04 10:30:45 /usr/lib/gdm/gdm-wayland-session[1454]: #0 0x7ffcc728b4f0 I   resource:///org/gnome/shell/ui/tweener.js:73 (0x7fda438ddef0 @ 9)
Jul 04 10:30:45 /usr/lib/gdm/gdm-wayland-session[1454]: #1 0x7ffcc728b590 b   resource:///org/gnome/shell/ui/tweener.js:105 (0x7fda438df230 @ 36)
Jul 04 10:30:45 /usr/lib/gdm/gdm-wayland-session[1454]: #2 0x7ffcc728b5f0 I   resource:///org/gnome/shell/ui/tweener.js:92 (0x7fda438df098 @ 52)

and with manual ip adress following entries for re config:



Jul 04 10:22:07 systemd-udevd[452]: Network interface NamePolicy= disabled by default.
Jul 04 10:22:07 systemd-udevd[8671]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 04 10:22:07 systemd-udevd[8673]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 04 10:22:07 systemd-udevd[8672]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 04 10:22:08 nscd[677]: 677 monitored file `/etc/hosts` was written to
Jul 04 10:22:08 systemd[1]: Reloading wicked managed network interfaces.
Jul 04 10:22:08 kernel: e1000e: em1 NIC Link is Down
Jul 04 10:22:12 kernel: e1000e: em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jul 04 10:22:13 avahi-daemon[653]: Joining mDNS multicast group on interface em1.IPv4 with address 10.49.120.169.
Jul 04 10:22:13 avahi-daemon[653]: New relevant interface em1.IPv4 for mDNS.
Jul 04 10:22:13 avahi-daemon[653]: Registering new address record for 10.49.120.169 on em1.IPv4.
Jul 04 10:22:14 wicked[8691]: em1             device-ready
Jul 04 10:22:14 wicked[8691]: em1             setup-in-progress
Jul 04 10:22:14 systemd[1]: Reloaded wicked managed network interfaces.

deano_ferrari · July 4, 2018, 11:05am

pprkut1:

dhclient em1 did not work, the journal gave me following errors:

Jul 04 10:32:07 dhclient-script[9511]: dhclient conflicts with enabled wicked.service and disabledJul 04 10:32:07 dhclient[9505]: /sbin/dhclient-script: unable to pre-init requested interfaces -- see log messages

Sorry, forgot you’re using wicked. (It uses its own DHCP client of course.)

I found following entries for my dhcp reconfiguration:

Jul 04 10:30:02 YaST.desktop[2465]: Run command: /sbin/yast2 lan &
Jul 04 10:30:13 systemd-udevd[452]: Network interface NamePolicy= disabled by default.
Jul 04 10:30:13 systemd-udevd[9331]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 04 10:30:13 systemd-udevd[9330]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 04 10:30:13 systemd-udevd[9329]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jul 04 10:30:14 systemd[1]: Reloading wicked managed network interfaces.
Jul 04 10:30:14 avahi-daemon[653]: Withdrawing address record for 10.49.120.169 on em1.
Jul 04 10:30:14 avahi-daemon[653]: Leaving mDNS multicast group on interface em1.IPv4 with address 10.49.120.169.
Jul 04 10:30:14 avahi-daemon[653]: Interface em1.IPv4 no longer relevant for mDNS.
Jul 04 10:30:15 kernel: e1000e: em1 NIC Link is Down
Jul 04 10:30:18 kernel: e1000e: em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jul 04 10:30:18 wickedd-dhcp4[657]: em1: Request to acquire DHCPv4 lease with UUID 066e3c5b-3f6f-0900-b702-00001f000000

Jul 04 10:30:33 wickedd-dhcp4[657]: em1: defer timeout 15 reached (state SELECTING)
Jul 04 10:30:45 wicked[9346]: em1 device-ready
Jul 04 10:30:45 wicked[9346]: em1 setup-in-progress
Jul 04 10:30:45 systemd[1]: Reloaded wicked managed network interfaces.

What happens after the above? I feel like it’s not showing the whole picture.

It might be useful to watch the wicked logging for a longer period, or perhaps examine the wicked.service logging with

sudo systemctl -u wicked

Clearly though the static IP address gets assigned. What you haven’t demonstrated/verified is that it’s the correct subnet for the network you’re trying to connect to. Is it really /24 net for example?

deano_ferrari · July 4, 2018, 11:20am

With a DHCP configuration, open a terminal and do

# journalctl -f

In another terminal do

# ifdown em1;ifup em1

Post the complete output generated here.

pprkut1 · July 4, 2018, 11:48am

Jul 04 11:38:54  sudo[2647]: schordingt : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/systemctl -u wicked
Jul 04 11:38:54  sudo[2647]: pam_systemd(sudo:session): Cannot create session: Already occupied by a session
Jul 04 11:38:54  sudo[2647]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 04 11:38:54  sudo[2647]: pam_unix(sudo:session): session closed for user root
Jul 04 11:40:16  sudo[2672]: schordingt : TTY=pts/1 ; PWD=/home/schordingt ; USER=root ; COMMAND=/sbin/ifdown em1
Jul 04 11:40:16  sudo[2672]: pam_systemd(sudo:session): Cannot create session: Already occupied by a session
Jul 04 11:40:16  sudo[2672]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 04 11:40:16  wickedd-dhcp4[622]: ni_dhcp4_device_close: timer active for em1
Jul 04 11:40:17  kernel: e1000e: em1 NIC Link is Down
Jul 04 11:40:17  sudo[2672]: pam_unix(sudo:session): session closed for user root
Jul 04 11:40:51  sudo[2817]: schordingt : TTY=pts/1 ; PWD=/home/schordingt ; USER=root ; COMMAND=/usr/sbin/ifup em1
Jul 04 11:40:51  sudo[2817]: pam_systemd(sudo:session): Cannot create session: Already occupied by a session
Jul 04 11:40:51  sudo[2817]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jul 04 11:40:51  wickedd[666]: ni_process_reap: process 2825 has not exited yet; now doing a blocking waitpid()
Jul 04 11:40:54  kernel: e1000e: em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jul 04 11:40:54  wickedd-dhcp4[622]: em1: Request to acquire DHCPv4 lease with UUID dc933c5b-de61-0800-9a02-00000a000000
Jul 04 11:41:09  wickedd-dhcp4[622]: em1: defer timeout 15 reached (state SELECTING)
Jul 04 11:41:18  systemd[1]: Started Daily Cleanup of Snapper Snapshots.
Jul 04 11:41:18  dbus-daemon[607]: [system] Activating service name='org.opensuse.Snapper' requested by ':1.117' (uid=0 pid=2827 comm="/usr/lib/snapper/systemd-helper --cleanup ") (using servicehelper)
Jul 04 11:41:18  dbus-daemon[607]: [system] Successfully activated service 'org.opensuse.Snapper'
Jul 04 11:41:21  sudo[2817]: pam_unix(sudo:session): session closed for user root

as i told u before, i have on the exact same maschine ubuntu (18.04)running.
With the exact same configuration i get a valid adress via dhcp, can assign my adress with the same subnet manually and ping other maschines.

deano_ferrari · July 4, 2018, 12:13pm

I note from reading the openSUSE 15 release notes, there was some mention of changes relating to DHCP…
https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/#sec.technical.wicked-rfc4361
…but I’m not sure of the significance of this and whether you’re impacted by these changes perhaps…

RFC 4361 updates the client-id defined in RFC 2132, section 9.14 to be compatible with DHCP 6 client-id (duid). The use of an RFC 4361 is mandatory on Infiniband (RFC 4390) and is also required to perform DNS record updates in the same zone for DHCP 4 and DHCP 6 addresses a

You could try switching to NetworkManager as a test though.

pprkut1 · July 4, 2018, 12:17pm

I think there is any kernel/hardware/driver problem, as i can not ping to any pc directly connected.
With my usb-WLAN-stick everything works fine.

deano_ferrari · July 4, 2018, 12:22pm

I guess a bug report is one option. Another is try a newer kernel.

pprkut1 · July 5, 2018, 7:46am

How can i report a bug?

Has anyone else any suggestion i could try?

deano_ferrari · July 5, 2018, 7:53am

Bugzilla:
https://bugzilla.opensuse.org/index.cgi
Guide on submitting bug reports:
https://en.opensuse.org/openSUSE:Submitting_bug_reports

Has anyone else any suggestion i could try?

Only trying the current stable kernel perhaps…

zypper ar -f http://download.opensuse.org/repositories/Kernel:/stable/standard  Kernel:stable

zypper in --from Kernel:stable kernel-default

deano_ferrari · July 5, 2018, 7:59am

BTW, one the kernel is installed you’ll need to reboot, and at the grub prompt select ‘Advanced options for openSUSE Leap 15.0’, then choose the new kernel to boot from.

b_martin · January 3, 2019, 7:46pm

I think this is a little complicated. Since I have no broadband access, I can’t download things directly to the T430. I only have connectivity from my older Thinkpad running 13,2, so I can only download files and pass them to the T430

Sauerland · January 3, 2019, 8:25pm

I think, you have another problem, so open a new thread.

Please post also Infos…

Edit:
Your thread:
https://forums.opensuse.org/showthread.php/534381-No-broadband-access-on-Thinkpad-T430?p=2890138#post2890138

deano_ferrari · January 3, 2019, 8:31pm

Best to keep your posts in the same thread (otherwise it will get confusing)…

https://forums.opensuse.org/showthread.php/534381-No-broadband-access-on-Thinkpad-T430/page3