Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 05 Feb 2024 17:30:10 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 276843] rtadvd stops workng after ifconfig down/up
Message-ID:  <bug-276843-227@https.bugs.freebsd.org/bugzilla/>

index | next in thread | raw e-mail

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276843

            Bug ID: 276843
           Summary: rtadvd stops workng after ifconfig down/up
           Product: Base System
           Version: 13.2-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: bugs@FreeBSD.org
          Reporter: pmc@citylink.dinoex.sub.org

One of my interfaces, type ng_eiface, frequently locks up with "No buffer
space".
(I am still searching for a way to increase the buffer space for that specific
interface, as there is no mbuf shortage - but that is a different issue).
The interface can only be recovered by doing ifconfig down/up.

After the interface works again, rtadvd does no longer send advertisements
through it, neither does it answer rtsold requests. Restarting rtadvd is
necessary.

This is shown by rtadvctl (nlan_1u has the issue):

nlan_1u: flags=<UP,TRANSITIVE,PERSIST> status=<RA_SEND> mtu 1500
        DefaultLifetime: 30m
        MinAdvInterval/MaxAdvInterval: 3m20s/10m
        AdvLinkMTU: <none>, Flags: <none>, Preference: medium
        ReachableTime: 0s, RetransTimer: 0s, CurHopLimit: 64
        AdvIfPrefixes: yes
        Next RA send: Mon Feb  5 18:12:40 2024
        Last RA send: Mon Feb  5 04:36:07 2024
nsvc_1u: flags=<UP,CONFIGURED,PERSIST> status=<RA_SEND> mtu 1500
        DefaultLifetime: 30m
        MinAdvInterval/MaxAdvInterval: 3m20s/10m
        AdvLinkMTU: <none>, Flags: <none>, Preference: medium
        ReachableTime: 0s, RetransTimer: 0s, CurHopLimit: 64
        AdvIfPrefixes: yes
        Next RA send: Mon Feb  5 18:13:01 2024
        Last RA send: Mon Feb  5 18:05:24 2024

And a little later:

nlan_1u: flags=<UP,TRANSITIVE,PERSIST> status=<RA_SEND> mtu 1500
        DefaultLifetime: 30m
        MinAdvInterval/MaxAdvInterval: 3m20s/10m
        AdvLinkMTU: <none>, Flags: <none>, Preference: medium
        ReachableTime: 0s, RetransTimer: 0s, CurHopLimit: 64
        AdvIfPrefixes: yes
        Next RA send: Mon Feb  5 18:25:28 2024
        Last RA send: Mon Feb  5 04:36:07 2024
nsvc_1u: flags=<UP,CONFIGURED,PERSIST> status=<RA_SEND> mtu 1500
        DefaultLifetime: 30m
        MinAdvInterval/MaxAdvInterval: 3m20s/10m
        AdvLinkMTU: <none>, Flags: <none>, Preference: medium
        ReachableTime: 0s, RetransTimer: 0s, CurHopLimit: 64
        AdvIfPrefixes: yes
        Next RA send: Mon Feb  5 18:27:49 2024
        Last RA send: Mon Feb  5 18:17:55 2024

There is apparently nothing special, except that it shows that nothing is done
on that interface.
I would think, since the interface is back in working order, rtadvd should
continue to work on it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276843-227>