Results 1 to 2 of 2

Thread: Upgrade to Tumbleweed = Networkmanager issues?

  1. #1

    Default Upgrade to Tumbleweed = Networkmanager issues?

    Went from Leap 15.0 to Tumbleweed. I had no issues with Leap on this machine

    However On tumbleweed, the networkmanager icon in the top right of the screen shows disconnected after I'm on a VPN for a while. Disconnecting from the VPN doesn't change this. But networking works. I can connect back to the vpn, browse websites etc.

    Second problem, seems to have intermittent issues with connectivity. Switching to wicked solves the issues, then I lose all of my configured vpns... because they're not there for wicked. So i switched back.

    If the computer is on long enough, network just doesn't work and I have to reboot. With leap i could leave it on and connected to a VPN for weeks and have no issues.

    NIC is Intel Corporation 82540EM Gigabit Ethernet Controller (rev 03), latest updates for Tumbleweed.

    Gnome Desktop.

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    24,120
    Blog Entries
    1

    Default Re: Upgrade to Tumbleweed = Networkmanager issues?

    Can you show us
    Code:
    /usr/sbin/hwinfo --netcard
    Code:
    /usr/sbin/ethtool eth0
    *Assuming eth0 is the relevant network device node.

    Also, you could monitor NetworkManager in a terminal window, and capture/post the output when next disconnected
    Code:
    sudo journalctl -fu NetworkManager
    openSUSE Leap 15.4; KDE Plasma 5

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •