Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[burakkucat]

Got a call from the installers on Thursday saying they'd be with me first-thing Friday.  And they were!

That's encouraging.

I took a look outside afterwards, as I thought I heard drilling.  Saw that they'd also replaced the CSP box.  Instead of a rounded-top one, it was rectangular -- and fitted much better to the wall.

Hmm . . . I can't mentally picture the two CSPs you have described. If you can make an image of the new CSP available to view, it would be appreciated, please.

So, new CSP box, new fibre to the ONT and new splice.  All sorted.

Excellent.

Now, just to figure out how they do IPv6.  With a straightforward pfSense DHCP6 config on the WAN, I'm seeing SOLICITs work, but REQUESTs go unanswered.  The Eero works fine, so clearly I need to have a tinker.  Will stick an ethernet switch with port mirroring between the Eero and the ONT so I can spy on what it's doing with Wireshark so I can try to hit pfSense until it does the same thing.

Agreed. That's the way to do it! 

[displaced]

Still working well!  And attached is a photo of the new CSP.  I'm reasonably sure the previous one had a curved top, possibly with the hinge on the side. 

I did as I said and spied on the eero.  It requests a prefix (a /56), but not an IP for itself.  Plus, DHCP's happening before any router advertisements are received.  So I configured pfSense appropriately and... it worked.  Turned on Router Advertisements and DHCPv6 on my LAN, which was set to 'Track Interface'... and it's all working.

Devices on my LAN pick up globally-routable IPs within my prefix alongside their link-local addresses.  Superb!

[displaced]

Ok -- small correction to the above, re: ipv6.

I noticed that the pfSense box itself couldn't ping out to public ipv6 addresses.  It just hangs.

For example:

Code: [Select]

[2.6.0-RELEASE][admin@heimdall.home]/root: ping6 google.com
PING6(56=40+8+8 bytes) 2a0e:xxxx:0:xx::299 --> 2a00:1450:400e:801::200e

So I unticked Only request an IPv6 prefix, do not request an IPv6 address to no ill effect on my clients' v6 connectivity.  But no joy.  Hmm.  Gonna go off and do some more reading.  I'd like the pfSense box to have ipv6 connectivity itself if only because it's stalling pkg updates whilst it tries and fails to use v6 before falling back to v4.

[burakkucat]

. . . attached is a photo of the new CSP.

Thank you. (Not one that I have seen before.) A simple query: I am assuming that the incoming fibre is contained within the black cable that comes from the right and the internal fibre exits the CSP through the back?

I did as I said and spied on the eero.  It requests a prefix (a /56), but not an IP for itself.  Plus, DHCP's happening before any router advertisements are received.  So I configured pfSense appropriately and... it worked.  Turned on Router Advertisements and DHCPv6 on my LAN, which was set to 'Track Interface'... and it's all working.

Devices on my LAN pick up globally-routable IPs within my prefix alongside their link-local addresses.  Superb!

<b*cat smiles enigmatically> 

I noticed that the pfSense box itself couldn't ping out to public ipv6 addresses.  It just hangs.

Hopefully that last niggle will not prove to be too difficult to resolve.

[Mark07]

Just for anyone else reading this, it's a /56 that's advertised and is what you need to configure on your WAN interface

[burakkucat]

All subsequent posts have now been split off into a new topic: "Calling any YouFibre End Users"