Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: 23.10 Upgrade - Internet failing every 1-2 hours

  1. #1
    Join Date
    Oct 2023
    Beans
    6

    Exclamation 23.10 Upgrade - Internet failing every 1-2 hours

    Hey,

    I upgraded to 23.10 today from 23.04, and I am having networking issues that I didn't have before. My networking works fine for an hour or two then it stops working completely. All I need to do to fix it is systemctl restart systemd-networkd and it works again for a few hours.

    I am scratching my head as to what's going on.

    systemd-networkd debug logs: https://pastebin.com/raw/Vp7BjUsH

    dmesg:
    Code:
    [ 1844.556199] bond0: now running without any active interface![ 1844.660220] bond0: (slave enp2s0f1): link status definitely up, 10000 Mbps full duplex
    [ 1844.660243] bond0: active interface up!
    [ 1844.764215] bond0: (slave enp2s0f0): link status definitely up, 10000 Mbps full duplex
    [ 1844.764228] bond0: (slave enp2s0f1): link status definitely down, disabling slave
    [ 1844.764230] bond0: active interface up!
    [ 1844.868200] bond0: (slave enp2s0f1): link status definitely up, 10000 Mbps full duplex
    [ 2334.684453] br-b77e9a781e16: port 7(vethbd3fb30) entered disabled state
    [ 2334.684523] veth7b45ba0: renamed from eth0
    [ 2334.760429] br-b77e9a781e16: port 7(vethbd3fb30) entered disabled state
    [ 2334.761211] vethbd3fb30 (unregistering): left allmulticast mode
    [ 2334.761213] vethbd3fb30 (unregistering): left promiscuous mode
    [ 2334.761215] br-b77e9a781e16: port 7(vethbd3fb30) entered disabled state
    [ 2334.908063] br-b77e9a781e16: port 5(vethc4914e1) entered blocking state
    [ 2334.908069] br-b77e9a781e16: port 5(vethc4914e1) entered disabled state
    [ 2334.908080] vethc4914e1: entered allmulticast mode
    [ 2334.908125] vethc4914e1: entered promiscuous mode
    [ 2334.908197] br-b77e9a781e16: port 5(vethc4914e1) entered blocking state
    [ 2334.908199] br-b77e9a781e16: port 5(vethc4914e1) entered forwarding state
    [ 2334.921779] br-b77e9a781e16: port 7(veth8d3e809) entered blocking state
    [ 2334.921783] br-b77e9a781e16: port 7(veth8d3e809) entered disabled state
    [ 2334.921793] veth8d3e809: entered allmulticast mode
    [ 2334.921829] veth8d3e809: entered promiscuous mode
    [ 2334.921901] br-b77e9a781e16: port 7(veth8d3e809) entered blocking state
    [ 2334.921903] br-b77e9a781e16: port 7(veth8d3e809) entered forwarding state
    [ 2335.161763] eth0: renamed from vetha989b79
    [ 2335.221721] br-b77e9a781e16: port 5(vethc4914e1) entered disabled state
    [ 2335.261915] eth0: renamed from veth47b419a
    [ 2335.281611] br-b77e9a781e16: port 5(vethc4914e1) entered blocking state
    [ 2335.281616] br-b77e9a781e16: port 5(vethc4914e1) entered forwarding state
    [ 2806.963265] bond0: (slave enp2s0f0): link status definitely down, disabling slave
    [ 2806.963296] bond0: (slave enp2s0f1): link status definitely down, disabling slave
    ip addr when its broken:
    Code:
    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: enp2s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
        link/ether 4e:dc:9b:39:43:85 brd ff:ff:ff:ff:ff:ff permaddr 80:61:5f:14:f7:73
    3: enp2s0f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
        link/ether 4e:dc:9b:39:43:85 brd ff:ff:ff:ff:ff:ff permaddr 80:61:5f:14:f7:74
    4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
        link/ether 4e:dc:9b:39:43:85 brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.179/24 metric 100 brd 192.168.1.255 scope global dynamic bond0
           valid_lft 85898sec preferred_lft 85898sec
    5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
        link/ether 02:42:b1:8f:46:8d brd ff:ff:ff:ff:ff:ff
        inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
           valid_lft forever preferred_lft forever
    6: br-b77e9a781e16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
        link/ether 02:42:da:eb:73:d6 brd ff:ff:ff:ff:ff:ff
        inet 172.18.0.1/16 brd 172.18.255.255 scope global br-b77e9a781e16
           valid_lft forever preferred_lft forever
    8: vethb7801bb@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-b77e9a781e16 state UP group default 
        link/ether b6:d7:44:5b:9e:50 brd ff:ff:ff:ff:ff:ff link-netnsid 1
    10: veth43236a0@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-b77e9a781e16 state UP group default 
        link/ether 2a:15:5a:d0:b9:57 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    12: veth2a2d4b2@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-b77e9a781e16 state UP group default 
        link/ether ce:8a:f3:16:e3:65 brd ff:ff:ff:ff:ff:ff link-netnsid 2
    14: veth2d6632a@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-b77e9a781e16 state UP group default 
        link/ether ba:67:32:64:42:57 brd ff:ff:ff:ff:ff:ff link-netnsid 3
    30: vethc4914e1@if29: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-b77e9a781e16 state UP group default 
        link/ether a2:36:43:3e:57:70 brd ff:ff:ff:ff:ff:ff link-netnsid 6
    32: veth8d3e809@if31: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-b77e9a781e16 state UP group default 
        link/ether 62:98:da:a6:5b:a3 brd ff:ff:ff:ff:ff:ff link-netnsid 4
    
    ip route when its broken:
    Code:
    default via 192.168.1.1 dev bond0 proto dhcp src 192.168.1.179 metric 100 
    172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
    172.18.0.0/16 dev br-b77e9a781e16 proto kernel scope link src 172.18.0.1 
    192.168.1.0/24 dev bond0 proto kernel scope link src 192.168.1.179 metric 100 
    192.168.1.1 dev bond0 proto dhcp scope link src 192.168.1.179 metric 100 
    Netplan:
    Code:
    network:
      bonds:
        bond0:
          dhcp4: true
          dhcp6: false
          interfaces:
          - enp2s0f0
          - enp2s0f1
          parameters:
            lacp-rate: slow
            mode: 802.3ad
            transmit-hash-policy: layer3+4
      ethernets:
        enp2s0f0: {}
        enp2s0f1: {}
      version: 2

    Can anyone help me out?

    Thanks,
    Jake
    Last edited by jakesteele; October 12th, 2023 at 11:54 PM. Reason: formatting and tags

  2. #2
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: 23.10 Upgrade - Internet failing every 1-2 hours

    code tags please, not quote tags. Columns need to line up, which is what code tags will do. Please make it easy to help you.

    23.10 is extremely new and it isn't an LTS. Thanks for being a tester.

    Code Tags: Https://ubuntuforums.org/misc.php?do=bbcode#code

  3. #3
    Join Date
    Oct 2023
    Beans
    6

    Re: 23.10 Upgrade - Internet failing every 1-2 hours

    Switched it to code tags.

  4. #4
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: 23.10 Upgrade - Internet failing every 1-2 hours

    The netplan file doesn't have correct YAML indentation. That means it is broken. I ran it through a YAML validator and it failed.

    Please use default fonts. Something is wrong with those used above.

  5. #5
    Join Date
    Oct 2023
    Beans
    6

    Re: 23.10 Upgrade - Internet failing every 1-2 hours

    Removed the color formatting and it fixed the indentation.

    The Netplan generates and applies fine. The internet works for a bit then stops.

  6. #6
    Join Date
    Aug 2016
    Location
    Wandering
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: 23.10 Upgrade - Internet failing every 1-2 hours

    I'm curious about "lacp-rate: slow"
    With realization of one's own potential and self-confidence in one's ability, one can build a better world.
    Dalai Lama>>
    Code Tags | System-info | Forum Guide lines | Arch Linux, Debian Unstable, FreeBSD

  7. #7
    Join Date
    Oct 2023
    Beans
    6

    Re: 23.10 Upgrade - Internet failing every 1-2 hours

    Quote Originally Posted by 1fallen View Post
    I'm curious about "lacp-rate: slow"
    tried fast as well, unfortunately wasn't a solution

  8. #8
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: 23.10 Upgrade - Internet failing every 1-2 hours

    The standard troubleshooting process is to simplify and test, repeat. How much have you simplified the setup and saw where it didn't have issues?

  9. #9
    Join Date
    Oct 2023
    Beans
    6

    Re: 23.10 Upgrade - Internet failing every 1-2 hours

    So I started with the install directly from the Ubuntu Server 23.10 Live CD, and it had the same issue. I've since then tried disabling / enabling DHCP, IPv6. I tried playing around with stopping certain services like resolvd. So far nothing has worked. Last night I reset the system back to the 23.10 defaults by re-installing the Ubuntu-Server Live CD.

    This was not an issue with the default 23.04 installer, but it happens with the same installation using 23.10. Something must have changed in the new installer / packages that is causing my internet to only work for an hour or so and then stop (sometimes as low as 10 mins).

    Jake

  10. #10
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: 23.10 Upgrade - Internet failing every 1-2 hours

    What about removing the bond? How else can we figure out which driver is causing the issue?

Page 1 of 2 12 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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