Messages

1

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: October 02, 2024, 07:37:32 am »

I upgraded my N100 Box to 24.7.5 this morning and as for right now everything seems stable.

The packet loss i believed from 24.7.5 is in my case seems to be caused by MacOS 15 / Sequoia. Regardless of which ICMP target, i have 0.3 to 0.9% packet loss. Sometimes this happens only after 100+ packets, so it was a coincidence that i saw it on 24.7.5 and not on 24.7.4. Kindly ignore my previous report about it (but maybe keep in mind if more people complain about sudden loss, i could replicate this across 2 updated M1 Macs but my work laptop with Sonoma does not have this issue and neither none of my Win11 systems)

As for IPv6, this seems fine right now but it took much longer for the default route to show up, when looking into the logs what happens directly after the reboot it puzzles me a bit:

Reboot was around 06:55:42.

At 6:56:22 i see

Code: [Select]

<29>1 2024-10-02T06:56:18+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="166"] send request to ff02::1:2%igc0
<29>1 2024-10-02T06:56:18+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="167"] reset a timer on igc0, state=REQUEST, timeo=0, retrans=932
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="168"] Sending Request
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="169"] set client ID (len 14)
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="170"] set server ID (len 14)
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="171"] set IA address
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="172"] set identity association
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="173"] set elapsed time (len 2)
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="174"] set option request (len 4)
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="175"] set IA_PD prefix
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="176"] set IA_PD
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="177"] send request to ff02::1:2%igc0
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="178"] reset a timer on igc0, state=REQUEST, timeo=1, retrans=1786
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="179"] receive reply from fe80::ff:fe01:101%igc0 on igc0
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="180"] get DHCP option client ID, len 14
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="181"]   DUID: 00:01:00:01:2d:7a:03:f4:7c:83:34:be:41:a3
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="182"] get DHCP option server ID, len 14
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="183"]   DUID: 00:01:00:01:26:2c:40:77:00:50:56:b1:8a:d7
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="184"] get DHCP option identity association, len 40
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="185"]   IA_NA: ID=0, T1=1800, T2=2880
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="186"] get DHCP option IA address, len 24
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="187"]   IA_NA address: 2a00:6020:1000:40::518d pltime=3600 vltime=3600
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="188"] get DHCP option DNS, len 32
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="189"] get DHCP option IA_PD, len 41
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="190"]   IA_PD: ID=0, T1=1800, T2=2880
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="191"] get DHCP option IA_PD prefix, len 25
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="192"]   IA_PD prefix: 2a00:6020:5051:7d00::/56 pltime=3600 vltime=3600
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="193"] Received REPLY for REQUEST
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="194"] nameserver[0] 2a00:6020:100::1
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="195"] nameserver[1] 2a00:6020:200::1
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="196"] make an IA: PD-0
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="197"] create a prefix 2a00:6020:5051:7d00::/56 pltime=3600, vltime=3600
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="198"] add an address 2a00:6020:5051:7d00:7e83:34ff:febe:41a4/64 on igc1
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="199"] make an IA: NA-0
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="200"] create an address 2a00:6020:1000:40::518d pltime=3600, vltime=3600
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="201"] add an address 2a00:6020:1000:40::518d/128 on igc0
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="202"] removing an event on igc0, state=REQUEST
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="203"] removing server (ID: 00:01:00:01:26:2c:40:77:00:50:56:b1:8a:d7)
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="204"] executes /var/etc/dhcp6c_wan_script.sh
<13>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 60365 - [meta sequenceId="205"] dhcp6c_script: REQUEST on igc0 executing
<13>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 64486 - [meta sequenceId="206"] dhcp6c_script: REQUEST on igc0 renewal
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="207"] script "/var/etc/dhcp6c_wan_script.sh" terminated
<29>1 2024-10-02T06:56:19+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="208"] got an expected reply, sleeping.
this should also contain the RA but the def route via fe80::ff:fe01:101 never makes into the routing table.

It takes till 07:02 till the route shows up:
 

Code: [Select]

29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="108"] set client ID (len 14)
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="109"] set server ID (len 14)
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="110"] set IA address
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="111"] set identity association
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="112"] set elapsed time (len 2)
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="113"] set option request (len 4)
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="114"] set IA_PD prefix
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="115"] set IA_PD
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="116"] send request to ff02::1:2%igc0
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="117"] reset a timer on igc0, state=REQUEST, timeo=2, retrans=4304
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="118"] receive reply from fe80::ff:fe01:101%igc0 on igc0
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="119"] get DHCP option client ID, len 14
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="120"]   DUID: 00:01:00:01:2d:7a:03:f4:7c:83:34:be:41:a3
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="121"] get DHCP option server ID, len 14
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="122"]   DUID: 00:01:00:01:26:2c:40:77:00:50:56:b1:8a:d7
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="123"] get DHCP option identity association, len 40
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="124"]   IA_NA: ID=0, T1=1800, T2=2880
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="125"] get DHCP option IA address, len 24
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="126"]   IA_NA address: 2a00:6020:1000:40::518d pltime=3600 vltime=3600
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="127"] get DHCP option DNS, len 32
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="128"] get DHCP option IA_PD, len 41
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="129"]   IA_PD: ID=0, T1=1800, T2=2880
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="130"] get DHCP option IA_PD prefix, len 25
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="131"]   IA_PD prefix: 2a00:6020:5051:7d00::/56 pltime=3600 vltime=3600
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="132"] Received REPLY for REQUEST
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="133"] nameserver[0] 2a00:6020:100::1
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="134"] nameserver[1] 2a00:6020:200::1
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="135"] make an IA: PD-0
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="136"] create a prefix 2a00:6020:5051:7d00::/56 pltime=3600, vltime=3600
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="137"] add an address 2a00:6020:5051:7d00:7e83:34ff:febe:41a4/64 on igc1
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="138"] make an IA: NA-0
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="139"] create an address 2a00:6020:1000:40::518d pltime=3600, vltime=3600
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="140"] add an address 2a00:6020:1000:40::518d/128 on igc0
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="141"] removing an event on igc0, state=REQUEST
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="142"] removing server (ID: 00:01:00:01:26:2c:40:77:00:50:56:b1:8a:d7)
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="143"] executes /var/etc/dhcp6c_wan_script.sh
<13>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 74159 - [meta sequenceId="144"] dhcp6c_script: REQUEST on igc0 executing
<13>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 80208 - [meta sequenceId="145"] dhcp6c_script: REQUEST on igc0 renewal
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="146"] script "/var/etc/dhcp6c_wan_script.sh" terminated
<29>1 2024-10-02T07:02:52+02:00 opnframe.epp.home.arpa dhcp6c 69302 - [meta sequenceId="147"] got an expected reply, sleeping.
<13>1 2024-10-02T07:02:55+02:00 opnframe.epp.home.arpa opnsense 80564 - [meta sequenceId="148"] /usr/local/etc/rc.newwanipv6: IP renewal starting (address: 2a00:6020:1000:40::518d, interface: wan, device: igc0)
<13>1 2024-10-02T07:02:55+02:00 opnframe.epp.home.arpa opnsense 80564 - [meta sequenceId="149"] /usr/local/etc/rc.newwanipv6: plugins_configure dhcp (,inet6)
<13>1 2024-10-02T07:02:55+02:00 opnframe.epp.home.arpa opnsense 80564 - [meta sequenceId="150"] /usr/local/etc/rc.newwanipv6: plugins_configure dhcp (execute task : dhcpd_dhcp_configure(,inet6))
<11>1 2024-10-02T07:02:56+02:00 opnframe.epp.home.arpa opnsense 80564 - [meta sequenceId="151"] /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: 78043'
<13>1 2024-10-02T07:02:56+02:00 opnframe.epp.home.arpa opnsense 80564 - [meta sequenceId="152"] /usr/local/etc/rc.newwanipv6: ROUTING: entering configure using wan, lan
<13>1 2024-10-02T07:02:56+02:00 opnframe.epp.home.arpa opnsense 80564 - [meta sequenceId="153"] /usr/local/etc/rc.newwanipv6: ROUTING: configuring inet6 default gateway on wan
<13>1 2024-10-02T07:02:56+02:00 opnframe.epp.home.arpa opnsense 80564 - [meta sequenceId="154"] /usr/local/etc/rc.newwanipv6: ROUTING: keeping inet6 default route to fe80::ff:fe01:101%igc0
<13>1 2024-10-02T07:02:56+02:00 opnframe.epp.home.arpa opnsense 80564 - [meta sequenceId=


right now everything is fine, i dont know why the route is showing up today but did not during the last update.

full log in attachment

2

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 30, 2024, 08:07:45 am »

Thanks, Franco. I will try that as soon as i find some more time for it.
I wanted to spin up a fresh installation of 24.7.5 on another box for testing as well.

Will update asap.

3

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 30, 2024, 07:57:04 am »

should we start a new thread for 24.7.5 dhcp6c regression or move to github issues?
also not sure what to make out of the timeouts, i dont have time the next days to upgrade again to 24.7.5 trying to replicate it.

4

24.7 Production Series / Re: [24.7.4] Some UDP traffic causes packet loss

« on: September 27, 2024, 05:31:06 pm »

question, do you have timeouts against your lan gw as well?

i just upgraded to 24.7.5 and now i have sporadic timeouts (like 0.9%) pinging my lan def gw (192.168.2.1 on igc1)

other hosts on the same switch, with ping from same client do not show this behaviour.
Running opnsense on Baremetal (n100 mini pc; intel i226 nics)

EDIT: loss is gone reverting to 24.7.4_1

5

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 27, 2024, 05:00:16 pm »

just upgraded to 24.7.5 and the old problems are back
IA_PD is visible, IA_NA is there but the default route is never showing up (which in effect kills almost all clients as the PD is available and addresses are getting assigned, where all ipv6 lookups will fail)

downgraded to old dhcp6c and everything works again.

EDIT: would it be possible to keep back the allocated Prefix from radvd and dhcpd processes unless there is a RA received? that would at least not kill the whole network due to ipv6 having a higher priority on clients

EDIT2: reverted fully to 24.7.4_1 as there was additional packetloss not only pinging the lan interface but also transit i.e pinging 8.8.8.8 or 1.1.1.1 - packetloss is gone with 24.7.4_1 (and ipv6 is also still stable now)

6

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 09, 2024, 07:57:35 am »

the IPv6 should not be local with start fe80... or?

valid but not what you are looking for in this case.
FE80::/10 is link-local and not routed, you are missing a GUA out of 2000::/3

7

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 09, 2024, 07:53:16 am »

Good morning,

since I updated to OPNsense 24.7.3_1-amd64 I have the same issue on not running IPV6DHCP.

Reading through did not see clear the solution so far... do I need to return to older version or did any tweak help? I went through all 5 pages but maybe missed the key sentence, maybe also due to lack of coffee this morning....

to install the  new "fixed" version for testing:

pkg add -f https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/dhcp6c-20240907.pkg

OR

revert to previously known working from 24.7.1

opnsense-revert -r 24.7.1 dhcp6c

reboot afterwards

8

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 08, 2024, 09:41:44 am »

@CruxtheNinth so I think you making clear that the last one "somewhat" worked I reverted the other commit that seems to play a role here and this should be the final thing for 24.7.4:

# pkg add -f https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/dhcp6c-20240907.pkg

I'm actually glad that neither of the two fixes for operational issues we did caused this, but it's still a bit unfortunate there is something weird going on here with the random value generation.


Cheers,
Franco

thank you. dhcp6c-20240907.pkg running without any issues so far. still feels like 24.7.1 reconciles a bit faster but i think thats me and just caused by DGs general weird non-standard behaviour.

How come not more people were affected by this?

9

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 07, 2024, 10:19:06 am »

_5 seems "stable" so far. In quotation marks because: Had the funny situation where i had working IPv6 but no DHCPv4 for like 3 minutes but it recovered.

Rebooted twice for testing and it still seems fine but weirdly it (feels) all takes a bit longer to converge compared to 24.7.1, had few visual glitches in the UI where interfaces showed the prefix gone and after reload of the browser tab it was there again.

i am trying to replicate that behaviour but i cant anymore. trying not to chase ghosts, will do a few more tests, may have been a local/pebcak glitch

EDIT: 10:30 another reboot and the problems are back. took manual reload of igc0 to get a IA_NA and IA_PD, no RA yet (attached logs for this). 

EDIT2: 10:35 RA received but IA_NA and IA_PD are gone :/ - seems its not stable

EDIT3: All green again. it feels weird.

10

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 07, 2024, 08:32:22 am »

Ok, kind of expected that, so last one:

Bisecting: 0 revisions left to test after this (roughly 0 steps)
[fe3ed661a5fb97f9eb9f14d51e7dadcf7a9364bb] dhcp6c: use arc4random_uniform()

# pkg add -f https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/dhcp6c-20240820_4.pkg

And thanks a lot for your help so far!


Cheers,
Franco

you are welcome, happy to do some testing.

Behaviour is similar to _3

First reboot with _4 at 08:08:
- Everything fine directly after reboot, in fact it felt like it was never online this quickly. IA_NA/IA_PD and route there.

However, after a second reboot at 08:15, just for verification it started to act like _3.
- link-local fe80 only, no IA_NA or IA_PD BUT the RA was visible
- tried to recover with igc0 reload (log: <27>1 2024-09-07T08:20:26+02:00) which again did not help

its so odd to see the dhcp6c log to actually show that it received both IA_NA and PD but then just nothing happens.

will do another set of reboots. logs are attached

EDIT: 08:39 multiple reboots later, ipv6 staying down.

11

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 06, 2024, 08:38:35 am »

Bisecting: 1 revision left to test after this (roughly 1 step)
[4bd3f0c78be1683f0a1343af129d829e1a69f8f6] git: 21st century

# pkg add -f https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/dhcp6c-20240820_3.pkg

Now mayhem started (logs are attached)

Rebooted with _3 approx 08:05
- Directly after reboot IA_NA/IA_PD + ipv4 online but DNS was failing weirdly
- restarted unbound which fixed the issue for v4 resolution
- RA received approx 10 minutes later and it seemed ok

next i wanted to replicate the DNS problem and did another reboot with _3

reboot approx 08:23
- directly after reboot no IPv4, no IA_NA, no IA_PD
- ipv4 took a while but still no IA_NA or IA_PD
- few minutes late RA arrived (def route visible for v6) but still no IA_NA or IA_PD
(https://imgur.com/210CaAe)

still on _3 now and so far no working ipv6 in sight.

EDIT: 08:42 now, just did a manual restart of igc0/WAN (via reload button in the UI) and it instantly brought back IA_NA/IA_PD and its working now. (https://imgur.com/t1Hi43v)

EDIT: 08:49 its broken again. IA_NA/IA_PD are gone (added another latest.log zip (5) )

EDIT: 09:31 still broken


some weird race condition??


12

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 05, 2024, 01:03:48 pm »

good: v20240710, bad v20240820

Bisecting: 7 revisions left to test after this (roughly 3 steps)
[ba9cddfcb6e568a5c83775ed0c917a316acb64db] dhcp6c: fix prototype

# pkg add -f https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/dhcp6c-20240820_1.pkg

all green so far with this version
IA_NA directly after reboot, IA_PD a few moments later. RA also fine, route got few minutes after reboot
Will observe a bit longer

EDIT: logs attached; reboot was 10:46

Thanks a lot, here is the next one:

Bisecting: 3 revisions left to test after this (roughly 2 steps)
[6db1c1f5c07c0b53b3ab7671ab52598c4647a54d] common: simplify setloglevel()

# pkg add -f https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/dhcp6c-20240820_2.pkg

Reboot 12:50
Same as with _1;  but it took approx 10 minutes until the def route for ipv6 was available; probably just usual DG RA shenanigans. However all green since a minute.

13

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 05, 2024, 10:51:16 am »

@CruxtheNinth: It now seems obvious that DG has different PON setups in different areas. My 3 installations are all in Lower-Saxony and are based on Nokia equipment. Just for the fun of it: I have read that DG also uses Genexis ONTs, is that what you have?

South Hessen here, also on Nokia ONT

14

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 05, 2024, 10:50:42 am »

good: v20240710, bad v20240820

Bisecting: 7 revisions left to test after this (roughly 3 steps)
[ba9cddfcb6e568a5c83775ed0c917a316acb64db] dhcp6c: fix prototype

# pkg add -f https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/dhcp6c-20240820_1.pkg

all green so far with this version
IA_NA directly after reboot, IA_PD a few moments later. RA also fine, route got few minutes after reboot
Will observe a bit longer

EDIT: logs attached; reboot was 10:46

15

24.7 Production Series / Re: 24.7.2 IPv6 woes

« on: September 05, 2024, 07:40:37 am »

Quick reply for 24.7.3_1, all packages default, release kernel.

Updated System:

- Directly after reboot IA_NA almost instantly received; /128 shown on igc0 WAN
- few minutes later IA_PD received but no default route yet (as DG will not reply to RA Solicits) - /64 on igc1 LAN visible
- 10 minutes later, default route received but Prefix and Network Address are gone. tried restarting wan interface, no effect, same as above.
- > opnsense-revert -r 24.7.1 dhcp6c & reboot
- Directly after reboot  IA_NA & IA_PD visible, no gateway yet
- 10 minutes later, default route received, all green. Prefix and Network Address are still there.

i am staying with dhcp6c-20240710 for now



system latest.log attached. Upgrade reboot was approx 07:13 today, 2nd reboot was after downgrading
i took some pcaps during the problem, in case they are also needed.