Messages

Ok this sounds workable... our best candidate for revert is https://github.com/opnsense/dhcp6c/commit/5676e78d87

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

Reboot and try again.

I was a bit suspicious of the patch but it's been in Debian too many years to give it a second thought. I don't know the code well enough but maybe the logic condition is wrong (|| vs. &&).


Cheers,
Franco

This fixed the issue for me as well. I'm on Comcast's DOCSIS network.

This is a bit weird:

vltime=34359741968

Otherwise it looks rather normal. Do you use the "prevent release" option?

A note on vltime (for Comcast not sure on others) Comcast states that IPv6 addresses received from DHCPv6 on their network are effectively static. Might be why they set the vltime to max.

Same issue here, updating from 22.7.8. Tried updating from console as well and the update process just stops suddenly.

I have not tested other values, but I can confirm that a decimal value of 16 does allow 2.5G negotiation on my X550 NIC.

Hello!

Comcast recently upgraded my internet service to 1.2Gb and I have attempted to configure LAGG via LACP to my MB8600 modem. I have successfully gotten this working and do in fact see the full 1.2Gb in a speedtest from the router! All outbound traffic seems to be functioning normally, no issues there. However, inbound traffic from the WAN side, such as trying to reach a web server I host, always times out on the client. I don't see any errors or collisions on the LAGG interface. When doing a packet capture I see a ton of TCP Retransmission packets coming from the client back into the router. What happens is, in this case my phone on data gets all of the packets out of order and sends a request for TCP Retransmission but continues getting the data out of order until it times out. This does not happen when I have the WAN as only one interface so I believe it is directly related to the LAGG splitting packets between the interfaces.

What would I go about doing to troubleshoot this issue? Is it even possible to fix this issue? I am worried that this might be an issue with the modem's implementation of LAGG, which obviously makes this only fixable by Motorola. At least then I could know it's not me! I fear my only solution would be to upgrade my equipment to faster interfaces and forget aggregation altogether.

Thanks for your help!

There is a small issue with updating a Namecheap DDNS if you need wildcard support. If you select the Namecheap option in the DDNS settings and enter all of the correct information it will only update the direct domain and not wildcards, even if Enable Wildcard is selected. The update link provided to me by Namecheap support is, https://dynamicdns.park-your-domain.com/update?host=[[host]&domain=[domain_name]&password=[ddns_password]&ip=[your_ip]. To be able to update your wildcard domains you need to specify "*" as your hostname assuming you already have Namecheap A records for wildcard DDNS. So for OPNSense to update your wildcard Namecheap IP select custom and use that link with the wildcard identifier instead of selecting the built in Namecheap settings.