Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12

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

  1. #11
    Join Date
    Oct 2023
    Beans
    6

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

    I collected more logs in hopes it helps.

    This is with the default install from Ubuntu Server 23.10 -- No changes to any packages or configs after the installer completed. (only installed docker)


    systemd-networkd logs: https://pastebin.com/9H4m7ZM1
    dhclient -v logs: https://pastebin.com/jDAg9kn3
    ip addr: https://pastebin.com/5K1vrnc3
    dmesg: https://pastebin.com/YmfXs4mJ

    ping test:

    Code:
    PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
    From 192.168.1.165 icmp_seq=1 Destination Host Unreachable
    From 192.168.1.165 icmp_seq=2 Destination Host Unreachable
    From 192.168.1.165 icmp_seq=3 Destination Host Unreachable
    From 192.168.1.165 icmp_seq=5 Destination Host Unreachable
    From 192.168.1.165 icmp_seq=6 Destination Host Unreachable
    
    
    --- 1.1.1.1 ping statistics ---
    8 packets transmitted, 0 received, +5 errors, 100% packet loss, time 7162ms
    pipe 4

    networkctl
    Code:
    IDX LINK            TYPE     OPERATIONAL SETUP
      1 lo              loopback carrier     unmanaged
      2 enp2s0f0        ether    enslaved    configured
      3 enp2s0f1        ether    enslaved    configured
      4 bond0           bond     routable    configured
      5 docker0         bridge   no-carrier  unmanaged
      6 br-abb567d8b179 bridge   routable    unmanaged
      8 veth11789ae     ether    enslaved    unmanaged
     10 veth5032a5f     ether    enslaved    unmanaged
     12 veth7acf3a9     ether    enslaved    unmanaged
     14 vethec9903b     ether    enslaved    unmanaged
     16 veth43ce72c     ether    enslaved    unmanaged
     18 veth150e668     ether    enslaved    unmanaged
     20 veth7d9c3a8     ether    enslaved    unmanaged
    
    
    13 links listed.
    ip route:
    Code:
    default via 192.168.1.1 dev bond0 proto dhcp src 192.168.1.165 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-abb567d8b179 proto kernel scope link src 172.18.0.1 
    192.168.1.0/24 dev bond0 proto kernel scope link src 192.168.1.165 metric 100 
    192.168.1.1 dev bond0 proto dhcp scope link src 192.168.1.165 metric 100
    systemd-network status
    Code:
    ● systemd-networkd.service - Network Configuration
         Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled)
        Drop-In: /etc/systemd/system/systemd-networkd.service.d
                 └─10-debug.conf
         Active: active (running) since Fri 2023-10-13 16:30:24 UTC; 40min ago
    TriggeredBy: ● systemd-networkd.socket
           Docs: man:systemd-networkd.service(8)
                 man:org.freedesktop.network1(5)
       Main PID: 176448 (systemd-network)
         Status: "Processing requests..."
          Tasks: 1 (limit: 76890)
         Memory: 1.1M
            CPU: 72ms
         CGroup: /system.slice/systemd-networkd.service
                 └─176448 /lib/systemd/systemd-networkd
    
    
    Oct 13 16:45:28 ubuntu systemd-networkd[176448]: bond0: Requesting NDisc route (configuring,configured): dst: fd53:b5d0:dfb0::/64, src: n/a, gw: fe80::18ff:3bae:4525:4246, prefsrc: n/a, scope: global, table: main(254), proto: ra, type: unicast, nexthop: 0, priority: 100, flags: n/a
    Oct 13 16:45:28 ubuntu systemd-networkd[176448]: bond0: Setting SLAAC addresses and router.
    Oct 13 16:45:28 ubuntu systemd-networkd[176448]: bond0: Configuring NDisc route (requesting,configuring,configured): dst: fd53:b5d0:dfb0::/64, src: n/a, gw: fe80::18ff:3bae:4525:4246, prefsrc: n/a, scope: global, table: main(254), proto: ra, type: unicast, nexthop: 0, priority: 100, flags: n/a
    Oct 13 16:45:28 ubuntu systemd-networkd[176448]: bond0: SLAAC addresses and routes set.
    Oct 13 17:07:49 ubuntu systemd-networkd[176448]: Got message type=method_call sender=:1.88 destination=org.freedesktop.network1 path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=Get  cookie=2 reply_cookie=0 signature=ss error-name=n/a error-message=n/a
    Oct 13 17:07:49 ubuntu systemd-networkd[176448]: Sent message type=method_return sender=n/a destination=:1.88 path=n/a interface=n/a member=n/a cookie=57 reply_cookie=2 signature=v error-name=n/a error-message=n/a
    Oct 13 17:07:53 ubuntu systemd-networkd[176448]: Got message type=method_call sender=:1.89 destination=org.freedesktop.network1 path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=Get  cookie=2 reply_cookie=0 signature=ss error-name=n/a error-message=n/a
    Oct 13 17:07:53 ubuntu systemd-networkd[176448]: Sent message type=method_return sender=n/a destination=:1.89 path=n/a interface=n/a member=n/a cookie=58 reply_cookie=2 signature=v error-name=n/a error-message=n/a
    Oct 13 17:09:58 ubuntu systemd-networkd[176448]: bond0: Removing NDisc route (configuring,configured): dst: n/a, src: n/a, gw: fe80::68d7:9aff:fe5d:2726, prefsrc: n/a, scope: global, table: main(254), proto: ra, type: unicast, nexthop: 0, priority: 100, flags: n/a
    Oct 13 17:09:58 ubuntu systemd-networkd[176448]: bond0: Removed NDisc route (configuring): dst: n/a, src: n/a, gw: fe80::68d7:9aff:fe5d:2726, prefsrc: n/a, scope: global, table: main(254), proto: ra, type: unicast, nexthop: 0, priority: 100, flags: n/a

    ---------

    @TheFU

    I will test without a bond later today and let you know if that solves the issue.
    Last edited by jakesteele; October 13th, 2023 at 06:25 PM.

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

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

    Showing what is wrong assumes we didn't believe you. What is different compared to when it worked is more of what I'd be looking at. Is the kernel the same or different? Is the driver used the same or different? Are the NICs the same? Are the cables the same? Are the switch ports the same? Have the switches been reconfigured in any way?

    Version numbers for each part, not nebulous "23.04 v 23.10".

    Differences between what works and what doesn't - that's where to look, assuming this worked previously, as you say (which I believe).

    You do realize that for more advanced configurations, sticking with an LTS release would normally be strongly recommended, unless there's specific hardware that mandates newer drivers. The current LTS is 22.04 and I think it run the 5.15.x kernels.

Page 2 of 2 FirstFirst 12

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
  •