Associate
If you can get past the normal helpdesk and in contact with the Network Team, ask them to try you with a static address temporarily to see if CGNAT is your problem. I assume your public IP starts with 100 at the moment?
Lit Fibre
- Thread starter bimbleuk
- Start date
Had to get tech to tell me what Mac they were seeing so I could spoof it on my dream machine. Seems their retention is nuts so even 30mins with the ONT Off I wasn't getting an IP on a different Mac.
Still seeing some intermittent lag spikes etc. support are not budging on giving me a static IP so I might just have to pay for one.
Still seeing some intermittent lag spikes etc. support are not budging on giving me a static IP so I might just have to pay for one.
I'm on a static IP using my UDM Pro with no MAC spoofing.
My Mac issue is because their DHCP server is retaining the Mac of the 2nd router I plugged in. Not the original/first lit OEM one, but the second Tapo deco X55 lol. Left it for hours and everything. They gave me the Mac they're seeing so I'm spoofing that just to be lazy.
Edit: oic what you mean -- maybe their DHCP is weird with Mac
Last edited:
Anyone else having problems getting logged-in to the PS4/PS5 Fortnite game on Lit Fibre today (Sunday 29th September). Very slow connecting and eventually comes up LOGIN TIMED OUT. Lit Fibre say it's an issue with a few online games, affecting a few ISPs, and they're aware and working on a resolution.
We haven't heard that any of my son's Fortnite friends are having issues on other ISPs. Have managed to get logged-in on the PS5 twice only today. It's very slow loading content in the menus, but once playing a game it seems ok. I've done the usual troubleshooting of rebooting the router, using Ethernet, changing DNS but nothing helps.
We haven't heard that any of my son's Fortnite friends are having issues on other ISPs. Have managed to get logged-in on the PS5 twice only today. It's very slow loading content in the menus, but once playing a game it seems ok. I've done the usual troubleshooting of rebooting the router, using Ethernet, changing DNS but nothing helps.
It seems overnight work in my area which forced a new static IPv4 and IPv6 to be assigned has broken IPv6 routing. A direct ping test from the WAN interface of my pfSense shows the following:
PING(56=40+8+8 bytes) xxxx:xxxx:xxxx:x::46 --> 2a04:4e42:400::81
ping: wrote bbc.co.uk 16 chars, ret=-1
ping: wrote bbc.co.uk 16 chars, ret=-1
ping: wrote bbc.co.uk 16 chars, ret=-1
--- bbc.co.uk ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
The DHCPv6 Prefix Delegation seems to be handing out a /48 which a huge difference from the previous /62. Not entirely sure if that's correct....
I've sent all the details over to Lit on their Twitter/X account via DM on their support account. Let's see how they respond when they wake up at 9am
PING(56=40+8+8 bytes) xxxx:xxxx:xxxx:x::46 --> 2a04:4e42:400::81
ping: wrote bbc.co.uk 16 chars, ret=-1
ping: wrote bbc.co.uk 16 chars, ret=-1
ping: wrote bbc.co.uk 16 chars, ret=-1
--- bbc.co.uk ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
The DHCPv6 Prefix Delegation seems to be handing out a /48 which a huge difference from the previous /62. Not entirely sure if that's correct....
I've sent all the details over to Lit on their Twitter/X account via DM on their support account. Let's see how they respond when they wake up at 9am
Last edited:
Associate
My dad's static IP address changed recently as part of the switch to CityFibre
Well this is certainly frustrating, plug Lit’s own router in and IPv6 routes perfectly fine. Switch back over to the pfSense and no matter what I do I can’t get it to work.
DHCP6 works, the /48 prefix gets picked from prefix delegation and /64 addresses are assigned to clients but nothing gets routed out.
I’m not really getting too much help from Lit’s Tech Support as their router is working. There’s obviously a change from Lit’s own IPv6 implementation to CityFibre’s but I’m dammed if I can work out what it is.
DHCP6 works, the /48 prefix gets picked from prefix delegation and /64 addresses are assigned to clients but nothing gets routed out.
I’m not really getting too much help from Lit’s Tech Support as their router is working. There’s obviously a change from Lit’s own IPv6 implementation to CityFibre’s but I’m dammed if I can work out what it is.
Last edited:
Associate
@pingloss have you managed to sort this out?
I'm having the exact issue after they also switched to CityFibre in my area. The only thing they could recommend was to change the prefix delegation to /48
I'm having the exact issue after they also switched to CityFibre in my area. The only thing they could recommend was to change the prefix delegation to /48
@erraticcommander Unfortunately not, Lit have washed their hands of the issue as their own router works ok.
I’ve sniffed the traffic on the WAN interface during startup on both my pfSense and their router. In both instances what I don’t see is a ICMPv6 router advertisement response from their side to the ICMPv6 router solicitation sent from the router. This response should tell the router what the default gateway is for IPv6 traffic.
As the Lit router somehow gets a default gateway it must be doing something different outside of the usual process. I’ve started to search on other instances where people of seen this but not found a fix as yet. I’ll keep on looking…..
I’ve sniffed the traffic on the WAN interface during startup on both my pfSense and their router. In both instances what I don’t see is a ICMPv6 router advertisement response from their side to the ICMPv6 router solicitation sent from the router. This response should tell the router what the default gateway is for IPv6 traffic.
As the Lit router somehow gets a default gateway it must be doing something different outside of the usual process. I’ve started to search on other instances where people of seen this but not found a fix as yet. I’ll keep on looking…..
Interesting news today
www.ispreview.co.uk
CityFibre Agrees to Sell UK Broadband ISP Lit Fibre to co-Founders
Network operator CityFibre, which earlier this year announced the acquisition of Lit Fibre's full fibre network (here), has today resolved the problem of what
www.ispreview.co.uk
Associate
Makes a lot of sense TBH...CF were never in it for the retail sideInteresting news today
CityFibre Agrees to Sell UK Broadband ISP Lit Fibre to co-Founders
Network operator CityFibre, which earlier this year announced the acquisition of Lit Fibre's full fibre network (here), has today resolved the problem of what
Lit Fibre were good because they were vertically integrated though. So the support will be friendly but helpless...
I've eventually worked out how to get IPv6 working on pfSense/OPNSense routers after the move over to the CityFibre network. First an observation and something I'll be sending to LitFibre, the new network doesn't seem to be following the industry standard ICMPv6 NDP method of discovering IPv6 default gateways as I linked to earlier. It's not just a 3rd party router thing as the same behaviour occurs when the LitFibre router is used.
It turns out that the IPv6 default gateway is the same fe80 link-local address that offers DHCPv6. By performing a network capture on the WAN interface while turning on the DHCPv6 option I was able to see the IPv6 link local address that was offering the DHCPv6 responses which I've highlighted.
By manually placing this IP address into the WAN DHCP6 gateway everything started working
Obviously, it really shouldn't take this amount of work to get IPv6 working. Their response to me of 'After checking with our technical team, we can confirm that if the the network works with our router then the issues might come from the configuration of your network/ 3rd party device.' isn't correct. I'm going to responding back to them asking why they seemingly aren't following RFC 4861 for IPv6 router discovery.
It turns out that the IPv6 default gateway is the same fe80 link-local address that offers DHCPv6. By performing a network capture on the WAN interface while turning on the DHCPv6 option I was able to see the IPv6 link local address that was offering the DHCPv6 responses which I've highlighted.
By manually placing this IP address into the WAN DHCP6 gateway everything started working
Obviously, it really shouldn't take this amount of work to get IPv6 working. Their response to me of 'After checking with our technical team, we can confirm that if the the network works with our router then the issues might come from the configuration of your network/ 3rd party device.' isn't correct. I'm going to responding back to them asking why they seemingly aren't following RFC 4861 for IPv6 router discovery.