Lost my /64 from Comcast



  • tldr: lost my /64, realized snort was responsible, disabled it and profited.

    Hi Everyone,

    I downloaded 2.1-BETA0 a few days ago and was pleasantly surprised when I was assigned a /64 (2601:) from Comcast, and I had all my devices up and running on it. I had done the IPv6 tests and they were working without a hitch. A few days later, everything connected via IPv6 dropped, pfsense now had a /128 (2001:), and none of my devices were connecting over v6. I'm not super knowledgeable about v6 so I was hoping someone could help me troubleshoot whether it's a pfsense issue or a Comcast issue. I'm now currently using 2.1-BETA0 built today (Nov 9) with the following interface settings:

    WAN -> http://imgur.com/6Pr7L.png
    LAN -> http://imgur.com/TW5vF.png

    I'd be happy to provide any further information. Thanks in advance!



  • You might be facing the same issue that I have been facing. Let's see.

    1. Does the LAN interface on your pfsense box have an IPv6 address or is it just the WAN?
    2. What does Status->Services show?


  • Hi darkcrucible,

    1. Does the LAN interface on your pfsense box have an IPv6 address or is it just the WAN?

    Both my WAN and LAN have IPv6 addresses - http://i.imgur.com/I75bC.png

    1. What does Status->Services show?

    Everything seems to be running unless a service is missing - http://i.imgur.com/o7rBS.png

    Thanks!

    Edit:

    darkcrucible – I have to say thanks! Looking at the services page made me wonder if snort was causing me issues. Disabling it allowed my devices to start working on IPv6 and passing the IPv6 test. I'm still rocking the 2001: address however.

    Edit Again:

    I take back the last part, it looks like snort was entirely to blame. Everything is back to normal with a /64 now.


Log in to reply