Messages

Orange published a list of connection requirements some time ago. If you stick to them (various send options in defined format etc), the connections are very stable.

TLDR

https://lafibre.info/remplacer-livebox/durcissement-du-controle-de-loption-9011-et-de-la-conformite-protocolaire/

That is why we don't speak often it's very rare you do

Oh and Orange France is behaving themselves now which makes life much easier.

changed the mirror to default in GUI then tried again from console

root@home:~ # uname -v
FreeBSD 14.1-RELEASE-p6 stable/24.7-n267981-8375762712f SMP

All is good again.

Thanks

sorry to be dumb how do I ensure its the default mirror from the shell

I saw the hot fix for Kernal panics which suggests the correct version
identifies itself as "stable/24.7-n267981-8375762712f" using uname - v

I get the following
root@home:~ # uname -v
FreeBSD 14.1-RELEASE-p6 stable/24.7-n267979-0d692990122 SMP

I have tried to issue the
opnsense-update -fk
and reboot but no change.

Am I miss reading the update notes

Currently in France can't connect via opnsense router using orange FTTP to opnsense.org forum. Switching to cellular or VPNing to my UK instance and all is well again. Orange recently allocated me a new IP which is when the issue started so I suspect a routing issue as other have indicated 

still no joy maybe just a slow connection or something !
tried two mirrors

I'll try later when it's quiet

PS: We had all the Orange FR fun we could get while you were away ;)

You love it

will try the suggestions

sorry yes 24.7 :-)

Fetching packages-22.7-OpenSSL-amd64.tar.......................

It seems to be just hanging forever. I tried turning off ipv6 no different

Any pointers?

EDIT : I tried again today all good. I assume just some sort of back-end mirror issue.

@zibloon

No set this option for both DHCP and DHCPv6 on the interface settings INTERFACES-->WAN

Just renewed on time no issues with the new patch.

19/20 score on https://ipv6-test.com/

I only have yesterday's log (updated yesterday) but the error was there then as well. Could have been there a while. BUT all seems to be working well.

Franco any clues about where to look at what address it's trying to assign?

new patch applied and changes were made to GUI removed the vlan-pcp option from the modifiers and defined the priority to 6

Like Skool, this caused a dhclient restart.

All looks good however in the logs for dhcp6c I noticed this error. Not sure if it was there before as I wasn't checking IPv6. I'm remote so I can't fully check but I'm getting a 19/20 on ipv6-test which is what I would expect.

Code Select Expand


2023-04-11T19:21:36 Notice dhcp6c dhcp6c REQUEST on igb0_vlan832 - running newipv6
2023-04-11T19:21:34 Notice dhcp6c RTSOLD script - Sending SIGHUP to dhcp6c
2023-04-10T12:04:53 Notice dhcp6c dhcp6c REQUEST on igb0_vlan832 - running newipv6
2023-04-10T12:04:51 Error dhcp6c transmit failed: Can't assign requested address
2023-04-10T12:04:50 Notice dhcp6c RTSOLD script - Starting dhcp6 client