Help please re Connection Issues after updating to Full Fibre with Open Reach UK

Started by Thorrrr, December 16, 2024, 04:28:39 PM

Previous topic - Next topic
HI Guys
Not sure if its my hardware or some settings i need to adjust to get my new Full Fibre Connection to work.
Been using Opnsesne for 24 months plus no issue. I have running on a Zimaboard

CPU: Intel Celeron N3450 at 1.10 GHz (Quad-core).
RAM: 8 GB (8380 MB).


Just had it fitted today after 3 months. After fitting it worked i was getting 356 download on Wifi 256 Upload engineer said it would settle down and speed increase.

But it was opposite i lost Wifi then lost  WLAN / LAN i have tried rebooting all the systems but nothing. I have had to add back the old connection and now it works fine.

My setup is described above is there anyway to see what the point of failure is?

My Opnsense modem did not look overloaded and i do not think it would just break the connection?
From Opnsense cable to switch from switch up-to Nighthawk Wifi Router?

Are there any logs i can check to see if its Opnsense or Hardware issues ?

Who is your ISP?
Is PPPoE configured and connected?
Do you need to use a VLAN for your ISP?


Plusnet and my PPPoE is already configured as i am just upgrading speed same user and same I.P address
VLAN not used

So your ISP is PlusNet (part of the BT group as I was last aware).

You look to have a gateway running. Some DHCP errors. Maybe sort those out next.

Then it might be helpful if you try a state what problem you are trying to solve.



OK soon as i connect my Zimaboard which runs Opnsense to the new Full Fibre Box i lose connection instantly.

But if i add it back to old connections it works instantly. 

But the FUll Fibre is working correctly according to Opnreasch Engineer as all 3 green lights are on.

He says its my Opnsense modem !!!

Problem 1:
2024-12-16T15:30:48     Error   dhcpd   uid lease 192.168.23.49 for client bc:24:11:00:5d:4c is duplicate on 192.168.23.0/24   
2024-12-16T15:30:48     Error   dhcpd   from the dynamic address pool for 192.168.23.0/24   
You seem to have IP addresses allocated for static leases on the same range as the dynamic pool. They need to be separate and not overlapping.

Problem 2:
2024-12-16T14:39:25     Error   opnsense        /usr/local/etc/rc.bootup: The command '/usr/sbin/arp -s '192.168.23.127' '48:b0:2d:f4:a9:e8'' returned exit code '1', the output was 'arp: set 192.168.23.127: Cannot allocate memory'
2024-12-16T14:33:38     Warning opnsense        /usr/local/etc/rc.bootup: ROUTING: refusing to set interface route on addressless wan(pppoe0) 
2024-12-16T14:33:35     Warning opnsense        /usr/local/etc/rc.bootup: interface_ppps_configure() waiting threshold exceeded - device pppoe0 is still not up
2024-12-16T14:33:13     Error   opnsense        /usr/local/etc/rc.bootup: The command '/usr/sbin/arp -s '192.168.23.127' '48:b0:2d:f4:a9:e8'' returned exit code '1', the output was 'arp: set 192.168.23.127: Cannot allocate memory'
2024-12-16T14:04:23     Error   opnsense        /usr/local/etc/rc.bootup: The command '/usr/sbin/arp -s '192.168.23.127' '48:b0:2d:f4:a9:e8'' returned exit code '1', the output was 'arp: set 192.168.23.127: Cannot allocate memory' 
It seems the PPPoE is not establishing a connection. That is the principal problem.
It can be bad username/password, MAC whitelisting on the ISP side, etc.

Please next time add these log entries as above, in text in code brackets.

HI

Sorry not used to the formatting on this site but that you for pointing it out

Problem 1 i have removed the entry from the DHCP Static Mappings for this interface. But for some reason it has also removed it from the Leases page?

Problem 2  i have the correct details as it is same provider same account same static ip and my details are correctly entered as my old account uses them and if i go back to old connection it works with my ISP.

Quote from: Thorrrr on December 16, 2024, 07:40:14 PMSorry not used to the formatting on this site but that you for pointing it out
At least it was in text :) not a screenshot

According to Plusnet's pages you might need VLANs https://www.plus.net/help/broadband/broadband-connection-settings/ depending on the service you are getting from them. So if you are going from ADSL to Full Fiber, it seems you need more than just the credentials.

From the Plusnet community they advice
The Openreach ONT can be seen as a modem, OPNsense is a router NO VLAN is required the ONT looks after that!

In that case you if the ONT is behaving like a modem, then you don't need to setup creds again in OPN, right? Why would you "dial" in both devices?
Try then to instead set WAN in OPN as DHCP.

OpenReach ONTs do NOT do PPPoE, but they do handle the VLAN tagging, so only PPPoE config should be needed in OPNsense, from what I understand.

I note that the OP's ZimaBoard thing has ReakTek NICs, which are known to be problematic with FreeBSD/OPNsense. I'm not sure if that could be preventing PPPoE from establishing a connection now (seems there's a lot of confusion, and likely some configuration issues), but it could have caused the instability observed after upgrading the internet service.

Good to know dseven. He might need to do a packet capture for clues too. I was surprised to hear the ONT would do PPPoE, never heard of that happening.

Quote from: dseven on December 17, 2024, 10:36:27 AMOpenReach ONTs do NOT do PPPoE, but they do handle the VLAN tagging, so only PPPoE config should be needed in OPNsense, from what I understand.

I note that the OP's ZimaBoard thing has ReakTek NICs, which are known to be problematic with FreeBSD/OPNsense. I'm not sure if that could be preventing PPPoE from establishing a connection now (seems there's a lot of confusion, and likely some configuration issues), but it could have caused the instability observed after upgrading the internet service.

HI on connection it works fine but soon as i add a file to Sabnzb this seems to break it during the download it breaks the connection.
But on ADSL connection i havr used it no issue but looks like the 900 Full Fibre might be overwhelming it but trying to find out what is doing it

interfaces are Realtek. No surprises there. You could try the os-realtek driver (os-realtek-re) but might not be much better.

p.s. this is a new problem now then ;)