Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Ipv6 not working on comcast

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    36 Posts 9 Posters 19.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      priller
      last edited by

      @johnpoz:

      What would be nice a is clear post that says what regions of the country comcast has enabled native ipv6 and on what devices.  Is it only in certain markets, major?  Full transparency should should show you in an easy to read table or document if the area of the country your in as a comcast customer if you have ipv6 only for single device - they like to hand out those /128 addresses.. Or if you can get your /64 behind your router or not, etc.

      Want to know if Comcast has deployed IPv6 in your area?
      http://comcast6.net/index.php/8-ipv6-trial-news-and-information/108-want-to-know-if-comcast-ipv6-is-available

      Disregard the references to "IPv6 trial".

      1 Reply Last reply Reply Quote 0
      • C
        casoah
        last edited by

        After a kernel panic, ipv6 stopped working for me.

        in my logs it says

        Aug 26 18:51:52 	radvd[35678]: version 1.9.1 started
        Aug 26 18:51:52 	radvd[35678]: IPv6 forwarding setting is: 0, should be 1
        Aug 26 18:51:52 	radvd[35678]: IPv6 forwarding seems to be disabled, but continuing anyway.
        Aug 26 18:51:57 	radvd[35936]: attempting to reread config file
        Aug 26 18:51:57 	radvd[35936]: resuming normal operation
        

        if I ssh into pfsense and do ping6 google.com it works fine

        however on my computers if I try to connect to an ivp6 address it just times out, even though I am assigned ipv6 ips.

        Nothing has changed in the firewall rules.

        For a release candidate this feels a bit buggy ;x

        Also if I disable ipv6 on the  LAN interface and under advanced ->allow ipv6 is unchecked

        computers still get an ivp6 address and under status ->interfaces LAN still has an ipv6 addresss

        Only way to get rid of it is with a reboot

        1 Reply Last reply Reply Quote 0
        • M
          mikeisfly
          last edited by

          I was able to get IPv6 to work on a Arris EMTA  TM822G following the instructions by razzfazz. I just wanted to share some things that I have learned trying to wrap my head around this IPv6. If you connect your computer to a a Docsis 3 modem that supports IPv6 and it's available in your area you will get an IP with a /128 netmask however if you connect it to a router that supports prefix Designation then your WAN IP will be /128 and your LAN IP will be /64. If you have multiple subnets then your router will need to support IA_PD which is Identity Association for Prefix Designation which Comcast will allow you to have up to a /60 which would give you 32 subnets by my count (5 bits) according to this site http://forums.comcast.com/t5/Home-Networking-Router-WiFi/ipv6-64/td-p/1780034. which should make the IA_PD (which PfSense calls IPv6 Prefix ID) go from 0 - 1f but PfSense has it from 0-f which would indicate only 16 subnets. (If you only see 0-0 its because your prefix is 64 if you lower it your values will change) Have I counted wrong? I am currently testing IPv6 on multiple subnets and I will report back on my findings tomorrow, as of yet it is not working.

          I hope I have cleared somethings up for anyone that was confused like me. Not really sure how I feel about having all my devices having public IPs but I'm glad I have PfSense protecting me. Also something that I have noticed is that I'm missing /61 in my prefix drop down on WAN Interface. I am currently using 2.1-RC1 (amd64) built on Mon Aug 26 01:13:05 EDT 2013.

          On a side note I had installed tinc but never used it so I uninstalled it but it stilled remained on the menu. IPv6 didn't start working until I installed that package back. I do not have it enabled and not really sure why it would have affected IPv6. Could have been coincidental but just wanted to put that information out there.

          1 Reply Last reply Reply Quote 0
          • P
            phil.davis
            last edited by

            /60 is only 16 /64 subnets:
            /64 = 1 /64 subnet
            /63 = 2 /64 subnets
            /62 = 4 /64 subnets
            /61 = 8 /64 subnets
            /60 = 16 /64 subnets

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

            1 Reply Last reply Reply Quote 0
            • M
              mikeisfly
              last edited by

              Correct I'm borrowing 4 bits from the /64 which would only be 16 subnets (It was late last night when I was working on this). I am still missing the /61 subnet under WAN is anyone else seeing this? Is this by design? Also I have not been able to an IPv6 address working on more than one interface. Right now I am only trying to get a IPv6 working on my LAN and WiFi subnets but when I change the WAN PD to /63 and set the LAN prefix to 1 and the WiFi prefix to 0 I can not pull a IP on those interfaces. Has anyone else tried to get IPv6 working on more than one interface. Not sure if the problem is on the PfSense side or my ISP's side. I'm running 2.1-RC1 (amd64) built on Mon Aug 26 16:50:31 EDT 2013 FreeBSD 8.3-RELEASE-p10

              1 Reply Last reply Reply Quote 0
              • D
                doktornotor Banned
                last edited by

                @mikeisfly:

                Has anyone else tried to get IPv6 working on more than one interface.

                Works just fine, though never tried with any similar weird subnets… /48 on WAN, /64 on LAN, WLAN etc.

                1 Reply Last reply Reply Quote 0
                • M
                  mikeisfly
                  last edited by

                  Just checked with Engineering at Comcast and IA_PD is not supported in the NJ Philadelphia area yet. :'(  They hope to bring the larger prefixes in the up coming months. I will update everyone when I find out more. (I guess this only effects you if you have Comcast and live in the NJ / Eastern PA area).

                  1 Reply Last reply Reply Quote 0
                  • R
                    razzfazz
                    last edited by

                    @doktornotor:

                    Works just fine, though never tried with any similar weird subnets… /48 on WAN, /64 on LAN, WLAN etc.

                    With Comcast?

                    1 Reply Last reply Reply Quote 0
                    • R
                      razzfazz
                      last edited by

                      They had rolled out support for /60 prefixes a while back, then apparently ran into issues with some CMTSs and removed that support again, supposedly to be re-enabled after some testing. That is the last I've been able to find online about this, so I was assuming the testing was still ongoing and /64 is still all we get for now.

                      1 Reply Last reply Reply Quote 0
                      • D
                        doktornotor Banned
                        last edited by

                        @razzfazz:

                        @doktornotor:

                        Works just fine, though never tried with any similar weird subnets… /48 on WAN, /64 on LAN, WLAN etc.

                        With Comcast?

                        No, no Comcast… As suggested above, ISP issue most likely, nothing to do with pfsense.

                        1 Reply Last reply Reply Quote 0
                        • M
                          mikeisfly
                          last edited by

                          It looks like Comcast has support for /60 most areas except for two major one which I can't tell you what they are. Philadelphia / Eastern PA and New Jersey is one major area and not sure what the other is. You can follow http://forums.comcast.com/t5/Home-Networking-Router-WiFi/IPv6-prefix-size-and-home-routing/td-p/1495933 There is a engineer there if you post on the main forum he may be able to help you out if you want to see if there is support in your area. He/she is very quick with their responses.

                          1 Reply Last reply Reply Quote 0
                          • R
                            razzfazz
                            last edited by

                            I finally managed to get a /60 delegated from Comcast and delegate parts of it to different subnets. Out of the box, this currently does not work, as Comcast will delegate a /64 by default unless a shorter prefix is explicitly requested via a prefix hint, and pfSense currently does not send such a hint.

                            I've added a switch to enable such hints; see pull request 792.

                            1 Reply Last reply Reply Quote 0
                            • M
                              mikeisfly
                              last edited by

                              razzfazz what area of the Country do you live? I'm in the Northeast (Philly,NJ,NY). I would like to keep track of which areas are working for others who might be having issues.

                              Thanks,

                              1 Reply Last reply Reply Quote 0
                              • R
                                razzfazz
                                last edited by

                                SF Bay Area.

                                1 Reply Last reply Reply Quote 0
                                • R
                                  razzfazz
                                  last edited by

                                  Also, pull request has been accepted, so the switch should turn up in the next snapshot.

                                  1 Reply Last reply Reply Quote 0
                                  • First post
                                    Last post
                                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.