Messages

Warning   radvd   sendmsg: No buffer space available

did you find any solution?
I have same effect when putting 100% load on traffic, e.g. downloading multiple ISO same time to bring the WAN to 30MB/s...
Without lower load no issues...

well, double DHCP6 I assume was killing the server. Now it runs as should !Many thanks!

thanks, yes found it now in NDP table!

Many thanks already - I think that already clarified two wrong items. Präfix ID was not different and disabled now DHCPv6 für LAN. Can imagine that cause double process and now all LAN/WAN/Wireguard has same prefix ...  Will report if issue remains...

Hello,
DG requires "DHCPv6-Mode stateful" if I read it correctly in the requirements doc.

Options SLAAC:
"Unmanaged" for SLAAC (A flag) - ISP did not give me IPv6 in SLAAC (request prefix only on/off both tried)

Options DHCP:
"Managed" for Stateful DHCPv6 (M+O flags) - currently used but failing
"Assisted" for Stateful DHCPv6 and SLAAC (M+O+A flags) - try again now
"Stateless" for Stateless DHCPv6 and SLAAC (O+A flags). - should not work as not "stateful" or?

By keeping focus on Interfaces: [WAN] - DHCPv6 + RA mode (Managed or Assisted) :

In the field Services: ISC DHCPv6: [LAN]:
- I still need to activate "Enable DHCPv6 server on LAN interface" or would that double vs setting in RA(Managed or Assisted) ?
- Do I have to write for Prefix Delegation Range also 56 (default was 64, just recognized)?
- Is the setting "request prefix only" only for SLAAC or also for DHCP reasonable?

[Configuration:]

Hello,

after frustrating weeks on trying to make Opnsense run again after upgrading to latest version, here my last try to get it resolved, otherwise I need to switch to alternative solutions... hope you can help and I try to better describe now. Opnsense has really great functionality but must be stable...

It was running fine for last year and problems startet out of sudden over last month with upgrades...

I'm getting IPv4 & IPv6 from ISP without issue, no error and all running fine. After sometimes 6/12/24h out of sudden below error appear in log, and 15-30min later, Opnsense has not more LAN -  reload services via shell does not help but only restart helps!

Configuration:

- Opnsense 27.7.7 (fresh install meanwhile + load minimum config - but also did not help)
- ISP - Deutsche Glasfaser (WAN DHCPv6, Prefix delegation size 56) all other default
- LAN (Track Interface WAN + manuell RA: Managed )
- no Vlans

DHCPv6 seems to work fine for ISP, and trying to use e.g. SLAAC was not successful.

LAN
192.168.0.1/24 - 2a00:6020:4347:xx01:2xx:2exx:fe96:7406/64
WAN
100.118.xx.250/16 - 2a00:6020:1000:xx::47x9/128

General Log:
2024-11-03T09:02:38   Error   opnsense   /usr/local/etc/rc.newwanipv6: The command '/usr/sbin/daemon -f -p '/var/run/dhcpleases6.pid' '/usr/local/opnsense/scripts/dhcp/prefixes.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 63828'
2024-11-03T08:50:54   Warning   radvd   exiting, 1 sigterm(s) received   
2024-11-03T08:50:54   Error   opnsense   /usr/local/etc/rc.newwanipv6: The command '/bin/kill -'TERM' '59777''(pid:/var/dhcpd/var/run/dhcpdv6.pid) returned exit code '1', the output was 'kill: 59777: No such process'   
2024-11-03T08:50:50   Warning   radvd   exiting, 1 sigterm(s) received   
2024-11-03T08:50:50   Warning   opnsense   /usr/local/etc/rc.linkup: dhcpd_radvd_configure(manual) found no suitable IPv6 address on lan(re0)   
2024-11-03T08:50:49   Warning   opnsense   /usr/local/etc/rc.linkup: dhcpd_dhcp6_configure() found no suitable IPv6 address on lan(re0)

After few minutes, the LAN hangs (but no further log) - only restart from shell can recover...

older topic but how can I find the device that is still using fe80: .... I see only proper configured device in my IPv6 leases list...

<7>cannot forward src fe80:1::d1f2:9d6a:4c2e:ef7, dst 2a03:2880:..., nxt 17, rcvif re0, outif re1

As I understand from here, it must bei in my LAN (re0) and want to reach there WAN (re1) right?

Hello, until now I saw no effect on "Prefer to use IPv4 even if IPv6 is available", but I recognized the relation, that having no devices on my VLANs, the system had no issue for a complete week (vs before min once per day), when I was traveling.

I now deleted both VLANs and also related networks in the Omada controller, lets see if it remains stable!

Thanks, I will try now your proposal, lets hope.
Did you select under DNS servers - Use gateway for the IPv4 or IPv6 WAN each for each DNS or kept it on "none"?

2024-10-20T18:57:03   Warning   radvd    sendmsg: No buffer space available
2024-10-20T18:57:03   Warning   radvd    sendmsg: No buffer space available
2024-10-20T18:57:03   Warning   radvd    exiting, 1 sigterm(s) received
2024-10-20T18:57:03   Error   opnsense    /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '50521''(pid:/var/dhcpd/var/run/dhcpdv6.pid)  returned exit code '1', the output was 'kill: 50521: No such process'
2024-10-20T18:57:00   Error   opnsense    /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '19286''(pid:/var/run/unbound.pid)  returned exit code '1', the output was 'kill: 19286: No such process'
2024-10-20T18:57:00   Warning   radvd    exiting, 1 sigterm(s) received
2024-10-20T18:57:00   Warning   opnsense    /usr/local/etc/rc.linkup: dhcpd_radvd_configure(manual) found no suitable IPv6 address on lan(re0)
2024-10-20T18:57:00   Error   opnsense    /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '50521''(pid:/var/dhcpd/var/run/dhcpdv6.pid)  returned exit code '1', the output was 'kill: 50521: No such process'

What can I do to investigate here further?
I tried to deactivate all other services, as DynDNS, Wireguard, VLANs, but not improvement yet - but need to find a solution as our home network cannot die now one a day....

radvd seems to run.

Code Select Expand

root@OPNsense:~ # pgrep radvd
4684

If my WAN IPv6 starts with:

WAN: 2a00:6020:101x:xxxx
LAN: 2a00:6020:434x:xxxx::/64

>Should the prefix of WAN not be re-used by DHCP of LAN for first 64 bit?

root@OPNsense:~ # cat /var/etc/radvd.conf
# Automatically generated, do not edit
# Generated RADVD config for manual assignment on lan
interface re0 {
        AdvSendAdvert on;
        MinRtrAdvInterval 200;
        MaxRtrAdvInterval 600;
        AdvLinkMTU 1500;
        AdvDefaultPreference high;
        AdvManagedFlag on;
        AdvOtherConfigFlag on;
        prefix 2a00:6020:434x:xxxx::/64 {
                DeprecatePrefix on;
                AdvOnLink on;
                AdvAutonomous off;
        };
        RDNSS 2a00:6020:434x:xxxx:201:2eff:fe96:7406 {
        };
        DNSSL localdomain {
        };
};

[restart]

Hello,

using now OPNsense 24.7.6-amd64, I have the issue that my network dies randomly after some hours.
Also also tried to find errors in my config, but not able to link it to the logged issue.
When the network is down and only restart via Shell helps to resolve.

WAN : IPv6 Configuration Type: DHCPv6
Prefix 56

Log:
Running OpnSense, there is no log at all on errors, notice,..., until this happens e.g. today 7:21, log starts getting filled and network died soon after. At 9:00 I did restarted and again log is remain empty until it happen again at 12:48:

2024-10-15T12:48:56 Error opnsense /usr/local/etc/rc.newwanipv6: The command '/usr/sbin/daemon -f -p '/var/run/dhcpleases6.pid' '/usr/local/opnsense/scripts/dhcp/prefixes.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 47755'

2024-10-15T12:48:45 Warning opnsense /usr/local/etc/rc.bootup: Skipping gateway WAN_DHCP6 due to empty 'gateway' property.

2024-10-15T12:48:45 Warning opnsense /usr/local/etc/rc.bootup: Skipping gateway WAN_DHCP6 due to empty 'monitor' property.

restart

2024-10-15T08:58:52   Warning   opnsense    /usr/local/etc/rc.newwanipv6: Skipping gateway WAN_DHCP6 due to empty 'gateway' property.
2024-10-15T08:58:52   Warning   opnsense    /usr/local/etc/rc.newwanipv6: Skipping gateway WAN_DHCP6 due to empty 'monitor' property.
2024-10-15T08:58:51   Error   opnsense    /usr/local/etc/rc.newwanipv6: The command '/usr/sbin/daemon -f -p '/var/run/dhcpleases6.pid' '/usr/local/opnsense/scripts/dhcp/prefixes.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 80564'
2024-10-15T08:58:39   Warning   opnsense    /usr/local/etc/rc.bootup: Skipping gateway WAN_DHCP6 due to empty 'gateway' property.
2024-10-15T08:58:39   Warning   opnsense    /usr/local/etc/rc.bootup: Skipping gateway WAN_DHCP6 due to empty 'monitor' property.
2024-10-15T08:57:12   Warning   radvd    exiting, 1 sigterm(s) received
2024-10-15T08:57:01   Error   opnsense    /usr/local/etc/rc.linkup: The command '/usr/sbin/daemon -f -p '/var/run/dhcpleases6.pid' '/usr/local/opnsense/scripts/dhcp/prefixes.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 57225'
2024-10-15T08:57:01   Warning   radvd    exiting, 1 sigterm(s) received
....
2024-10-15T07:39:03   Error   opnsense    /usr/local/etc/rc.linkup: The command '/usr/sbin/daemon -f -p '/var/run/dhcpleases6.pid' '/usr/local/opnsense/scripts/dhcp/prefixes.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 86503'
2024-10-15T07:39:01   Warning   radvd    exiting, 1 sigterm(s) received
2024-10-15T07:39:01   Error   opnsense    /usr/local/etc/rc.newwanipv6: The command '/bin/kill -'TERM' '10204''(pid:/var/dhcpd/var/run/dhcpdv6.pid)  returned exit code '1', the output was 'kill: 10204: No such process'
2024-10-15T07:38:56   Warning   radvd    sendmsg: No buffer space available
2024-10-15T07:38:56   Warning   radvd    sendmsg: No buffer space available
2024-10-15T07:38:56   Warning   radvd    exiting, 1 sigterm(s) received
2024-10-15T07:38:56   Warning   opnsense    /usr/local/etc/rc.linkup: dhcpd_radvd_configure(auto) found no suitable IPv6 address on lan(re0)
2024-10-15T07:38:55   Error   upsmon    Poll UPS [qnapups@192.168.0.7:3493] failed - Server disconnected
2024-10-15T07:21:14   Error   opnsense    /usr/local/etc/rc.linkup: The command '/usr/sbin/daemon -f -p '/var/run/dhcpleases6.pid' '/usr/local/opnsense/scripts/dhcp/prefixes.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 89310'
2024-10-15T07:21:14   Error   opnsense    /usr/local/etc/rc.linkup: The command '/bin/kill -'TERM' '89310''(pid:/var/run/dhcpleases6.pid)  returned exit code '1', the output was 'kill: 89310: No such process'
2024-10-15T07:21:07   Error   opnsense    /usr/local/etc/rc.linkup: The command '/usr/sbin/daemon -f -p '/var/run/dhcpleases6.pid' '/usr/local/opnsense/scripts/dhcp/prefixes.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 89310'
2024-10-15T07:21:06   Warning   radvd    exiting, 1 sigterm(s) received
2024-10-15T07:21:05   Error   opnsense    /usr/local/etc/rc.newwanipv6: The command '/bin/kill -'TERM' '62412''(pid:/var/dhcpd/var/run/dhcpdv6.pid)  returned exit code '1', the output was 'kill: 62412: No such process'
2024-10-15T07:21:01   Warning   radvd    exiting, 1 sigterm(s) received
2024-10-15T07:21:01   Warning   opnsense    /usr/local/etc/rc.linkup: dhcpd_radvd_configure(auto) found no suitable IPv6 address on lan(re0)

[hostname.spdns.de bei Token-Authentifizierung]

Edit: wer lesen kann ist klar im Vorteil, aber manchmal sie man den Wald vor Bäumen nicht  :-X
Bei der Hilfsseite zur Konfiguration für ne Fritz!Box hab ich den Konfigfehler entdeckt!

Benutzername:  Login für spDYN. oder hostname.spdns.de bei Token-Authentifizierung

DuckDns klappt seit heute auch ohne weitere Änderungen, was will man mehr!

ja das Thema will sich auch bei mir nicht lösen.

DynV6 & DuckDNS klappt die Übertragung der IPv6, da will Wireguard sich aber partu keine Verbindung per IPv6 aufbauen.

SPDNS akzeptiert Wireguard baut die Verbindung auf - aber hier will die der native ddclient weiter sich nicht anmelden.

[spdyn - spDNSService] failed to set new ip 2a00:xxxx:xxxx:xxx::xxxx [401 - badauth]

Zum Glück ändert sich die IPv6 bis dato selten & kann im Notfall bei DuckDNS die Daten unterwegs manuel zu SPDNS übertragen, aber macht nicht glücklich, das es nicht automatisch geht...
Hab schon viel gesucht, aber warum ich DynV6 & DuckDNS mit Wireguard nicht funktionieren wollen fehlen mir die Ideen, dann würde SPDNS in Rente schicken ;-)

Also ich glaub ich bin auf dem Irrweg mit dem Präfix holen für meinen DG Anschluss & das ganze lief ja auch wunderbar bis zum letzten upgrade von 24.7.1 dhcp6c.

Da es mit OPNsense 24.7.6 ja scheinbar wieder geht, würde ich gern besser verstehen, ob ich nicht doch ein Fehler in meiner Konfiguration habe, daher zunächst Verständnissfragen zu IPv6:

- WAN - 2a00:6030:3000:64::48e8/128
IPv6 Configuration Type: DHCPv6
Prefix 56

Standortpräfix : 2a00:6030:3000
Teilnetz-ID:  64
Schnittstellen-ID: ::48e8

LAN - 2a00:6030:5357:d900:201:2eff:fe96:7407/64
IPv6 Configuration Type: Track Interface
Parent interface: WAN
Prefix ID: 0

Sollte das LAN nicht 2a00:6030:3000:64: ..... ? bekommen?


Sofern ich dann anfange wieder VLANs zu betreiben, müsste ich dann bei der Prefix ID der IPv6 nicht jeweils 1,2, schreiben wie auch bei IPV4, um eine Trennung zu haben? Hier gibt es eine Fehlermeldung.

Meine Wireguard Adresse darf sich ja dann auch erst hinter dem Präfix ändern oder (bspw. aaab) ?

2a00:6030:3000:64:aaab::1/80