Messages

Yes lots of people with this issue. I have been okay until yesterday when I lost my connection
It may not be the same issue as it's less than 24 hours since I rebooted the router. Time will tell

I think something has changed at Orange as like you I didn't  change anything

@franco which logs should we capture

@franco did these patches make it into today's patch release?

@franco
Renewal just requested and successful

All good on ipv6 and ipv4

Applied and rebooted for good measure
All seems well so far

Renewal would have been tonight but I suspect we will need to wait 24 hours now as reboot has requested wanip

NOTE: I only ever lost ipv4 not ipv6 here.

Ok will bae back home later

Will try then

renewal done

all seems well currently

I miscalculated

Renewal in 45 mins approx :-)

cool just issued the configd restart

I'll monitor and revert. I think it's due to renew in about 3 hours so I should have an update soon.

Long Time no speak @franco

I jumped ahead and already issued

opnsense-patch 26d26e2054

and then

opnsense-revert opnsense && opnsense-patch 90f1d1d766


I guess I just need to do a service configd restart. Any need to specifically reverse the first patch ?

Lost my Orange France FTTP connection a few weeks ago.
Arrived in France yesterday and rebooted rooter. All good for 24 hours until IPV4 went again.

Did I read correctly that I should do

opnsense-patch 26d26e2054

and then

opnsense-revert opnsense && opnsense-patch 90f1d1d766

For the DHCPv6 issue that users from Orange FR are having. This looks like a kernel problem and I have published a snapshot kernel for broader testing:

# opnsense-update -zkr 22.1-prio

(requires a reboot)


Cheers,
Franco

Being running for several days now without issue so I think we can safley say this fixed IPv6 thanks Franco 

Cheers yes that's allowing the credentials to be entered now.

Time to play now.

That's a bug in the validation routine in the Opnsense interface. I THINK it's already been taken care of, but not yet released. I manually patched mine to allow the API token I use for GoDaddy whilst I am playing with DDclient and Godaddy,

Cheers @marjohn

Whilst a few of us "me included" failed to understand/read the release notes. Once again I have to say the rapid response from the team was first rate. I wonder how that would have been handled on the other fork  :)

well, it is a least supposed to support google domains but will it accept the generated credential from my google domain accounts NO. Claims userid contains invalid characters

Anyone managed to get it to work with Google domains