Topic 'Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]' in forum 'Comcast HSI' - dslreports.com

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Sat, 19 Jan 2013 00:34:57 EDT

PGHammer posted : Glad to hear.

Oddly enough, the SAME settings work with some routers *known* to support IPv6 (WNR1000v2 and WNDR37xx v3 and later - this may apply to Netgear's WNDR4xxx as well), because of issues with Auto-Detect/Auto-Config vs. explicit DHCP; I don't know whether it's a bug on Netgear's end or possibly the router is, in fact, doing what it's supposed to.

I have a WNDR3700 v4 (which replaced a Comcast-supplied WNR3500v1) due to router timeouts (on the WIRED side - utterly inexcusable) which I initially setup with Auto-Detect (first for IPv4, then for IPv6) - for IPv6, I got the 6to4 tunnel that is the default for routers that don't support either DHCP6-PD or 6RD (neither of which is listed on the WNDR3700's spec sheet or documentation). However, there IS a setting for DHCP under Advanced Setup->IPv6 - just for grinz/lulz, I used it. *Bang.* I now have the *correct* IPv6 range, and I'm no longer using a tunnel.

Add this router to the explicit support list with the following note: DHCPv6 must be turned on via Advanced Setup->IPv6 - this is disabled by default.

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Sun, 06 Jan 2013 18:36:28 EDT

plencnerb posted : Good deal.

I also went ahead and added the two IPv6 DNS's under the General Setup so they now show up as well.

--Brian

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Sun, 06 Jan 2013 17:36:45 EDT

graysonf posted : This now agrees with what I have here on working m0n0wall 1.8b, including the /128 WAN netmask and having a local link address for the IPv6 gateway.

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Sun, 06 Jan 2013 16:48:51 EDT

whfsdude posted : There are some GUI issues with quickly back-porting to WIDE from ISC's DHCP6 client.

FWIW, I always shove the v6 DNS servers under System > General Setup.

2001:558:feed::1
2001:558:feed::2

I'd rather push v6 traffic over Comcast's network than v4 (but that's just me being a v6 nerd). :-)

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Sun, 06 Jan 2013 16:11:31 EDT

plencnerb posted : I went ahead and did a clean install of pfsense. The version information is below

2.1-BETA1 (i386)
built on Sun Jan 6 05:42:27 EST 2013
FreeBSD 8.3-RELEASE-p5

Good news is that everything is now working! :)

I also want to point out the difference in the WAN Interface screens. If you look at the one before the upgrade, the WAN Interface showed a Subnet mask IPv6 of "64". After moving to the new version, that value is now showing as "128", as indicated by the red arrows.

At this point, I have made ZERO changes to the configuration of pfSense (outside of changing the default admin password). Both IPv6 test sites now return 10/10, and the Comcast IPv6 Speed test site is working as well. I did some ping tests to known IPv6 sites, and they work. I also did a nslookup to that site, and returned both the IP and the name (depending on how I did the lookup) and that also worked without issue.

For reference, the changes that I made in the last version are below.

Add a WAN Rule for IPv6
Firewall --> Rules --> WAN
Action: Pass
Disabled: unchecked
Interface: WAN
TCP/IP Version: IPv6
Protocol: TCP
Source: No changes
Destination: No changes
Destination port range: No changes
Log: Unchecked
Description: Added to allow IPv6

Modify the IPv6 Configuration Type
Interfaces --> WAN
IPv6 Configuration Type: DHCP6

Again, I did not have to do either change. In regards to the IPv6 configuration type, it was already set as DHCP6. I also did not add the firewall rule on the WAN side as noted above, as things "appear" to be working without it.

If anyone has any questions, or needs to see any additional screens, let me know and I'll be happy to post them.

Interesting I just noticed that I "lost" the following two ISP DNS Servers
2001:558:feed::1
2001:558:feed::2

They were present under the WAN Interface prior to the install, and now they do not show up.

As I said, things "appear" to work without them, so I don't know if they are needed or not. However, I did want to point that out just in case I need to modify something to get them to show up again on the WAN Interface screen.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Dashboard Prior to upgrade
Interfaces Prior to upgrade
Dashboard After upgrade
Interfaces After upgrade

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Sun, 06 Jan 2013 09:58:38 EDT

plencnerb posted : Well, I went and downloaded the file indicated by the arrow in the above picture.

Later today I'll burn that to CD, and install clean and see how things go.

I do have my notes about what I changed before to get things working. I'll make any new notes if those same changes need to be made, or if they are already configured by default.

Once everything is working (crosses fingers! :) ), I'll post back here with all the information.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Sat, 05 Jan 2013 23:03:43 EDT

JoelC707 posted : Yeah that was my thought as well. I'm actually here with my system today (I actually moved on the 1st and haven't really had a chance to mess with this) and thought "great, I'll do an update while I'm here, wait what day is today, damn only the 5th?" I'm heading out of town in the morning so it'll be at least a week before I can get to it now. I'm liking what I'm seeing though, looks promising. :)

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Sat, 05 Jan 2013 13:24:07 EDT

plencnerb posted : Thanks!

Looks like I need to get a updated beta build of the 2.1 client.

I'll work on doing that this afternoon.

Once everything has been done, I'll test again and report back.

Edit: The post over there says to get one with a date of Jan 6th or later. Today is only the 5th! :) So, I have to wait a day I guess. No big deal. Now I have a project for tomorrow.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Sat, 05 Jan 2013 13:21:12 EDT

graysonf posted : See: »forum.pfsense.org/index.php/topi···sg306484

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Fri, 04 Jan 2013 08:49:10 EDT

plencnerb posted : Ok, so any thoughts on my issue? Should I reboot and see what happens?

Or, should I download and install the latest build, and see what that does?

Or, is there a setting that I need to modify?

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 21:28:47 EDT

whfsdude posted :

said by graysonf:

That's the way it came up here.

Oh awesome! Clearly there are some major code changes underway. Last time I tossed on a blank config was August.

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 18:02:53 EDT

graysonf posted : That's the way it came up here.

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 17:35:58 EDT

whfsdude posted :

I left it entirely in the default configuration which aligns with the configuration others have tried here. It would not assign an IPv6 address to my Windows 7 machine which is set for DHCPv6.

Huh? The default config won't do PD. You need to set a track int on the LAN.

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 17:08:34 EDT

graysonf posted : I flashed the latest pfsense snapshot (pfSense-2.1-BETA1-512mb-i386-nanobsd-20130103-0639) to CF and tried it.

I left it entirely in the default configuration which aligns with the configuration others have tried here. It would not assign an IPv6 address to my Windows 7 machine which is set for DHCPv6.

The only way I could get IPv6 working was to statically assign an IPv6 address, gateway, and DNS server to my Windows 7 machine.

I'm back on m0n0wall which works fine with Comcast IPv6 DHCP-PD. The only odd thing is that its system log is flooded with RAs on the WAN interface.

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 16:23:16 EDT

plencnerb posted : All,

Thanks for the clarification. As I'm still learning about IPv6, I got confused when I saw the note about /128. Seeing in pfsense I could only configure the size to be /64, I thought they were the same thing.

So, is it safe to assume that my configuration, as it was setup back in December, is still valid?

If it is, then how do we go about getting it to work again? I could reboot the modem, and my pfsense box, and that will probably fix things. However, how long will that fix last? Is there something else that is not configured correctly on my end that caused this? Or, is it something on Comcast's end that has broke, and someone who works for Comcast needs to fix something.

I'm willing to post any configuration, screen shot, or test anything I need to try to figure out what has stopped working. Just let me know what someone needs me to do, I'll do it.

Thanks in advance for any help that can be offered.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 14:09:16 EDT

whfsdude posted :

said by IPv6_NOT :

I don't know if the current beta release(s) of pfsense has a configuration option to specify a requested allocation size for the WAN interface, but if it receives a /64 allocation, I think that the problem the OP is seeing will continue (just as it continues to happen on my Netgear router which also receives a /64 allocation on its WAN interface). We are talking about the router's WAN interface, not its LAn interface which indeed should have a /64 allocation and subnet.

When set to DHCP6, pfsenses assumes asking for a /128 allocation. The question in the LAN thread (»[IPv6] Seeing two different LAN side ranges) was addressed that it is showing /64 for the WAN subnet, which is correct.

The PD size was asked again in this thread, but yes that should be set to /64 as well. In pfsense you specify the PD size on the WAN page. LAN interfaces are then set as track interfaces.

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 12:59:06 EDT

anon posted :

said by whfsdude:

said by IPv6_NOT :

http://www.dslreports.com/forum/r27782156-IPv6-Troubleshooting-Comcast-IPv6-Start-Here- he seems to agree that a router's WAN should get a /128 allocation

He's talking about allocation, not subnet. If you had a /128 subnet, you wouldn't be able to reach the gateway (it's just a single addressed network).

pfsense very clearly asks for the subnet which is why you give it a "/64."

If you do not believe that it's in a /64, pcap the RA.

fwiw, I ran pfsense on Comcast's network using '64' on-link and '64' for the PD prefix up until I had my new service installed (which is static).

You may want to find your reading glasses and look at my posts in this thread again. I don't think you will find that I have used the phrase "/128 subnet" in any of those posts. In fact the portion of my last post that you quoted clearly says "/128 allocation"

I don't know if the current beta release(s) of pfsense has a configuration option to specify a requested allocation size for the WAN interface, but if it receives a /64 allocation, I think that the problem the OP is seeing will continue (just as it continues to happen on my Netgear router which also receives a /64 allocation on its WAN interface). We are talking about the router's WAN interface, not its LAn interface which indeed should have a /64 allocation and subnet.

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 12:24:31 EDT

whfsdude posted :

said by IPv6_NOT :

http://www.dslreports.com/forum/r27782156-IPv6-Troubleshooting-Comcast-IPv6-Start-Here- he seems to agree that a router's WAN should get a /128 allocation

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 12:11:39 EDT

anon posted :

said by graysonf:

I suggested "None" because /128 is not a choice. I don't run pfsense here, I run m0n0wall instead. And I get a /128 on WAN and there is nothing to specify other than DHCP on WAN - there is no list of subnet mask choices.

I may flash a copy of pfsense to a spare CF and try it here to see what happens.

I do recall another thread along these lines and the way it turned out NetDog (I think) got involved and solved it. The cause was some type of misconfiguration by Comcast for that particular customer.

In NetDog's sticky thread: »[IPv6] Troubleshooting Comcast IPv6 (Start Here) he seems to agree that a router's WAN should get a /128 allocation:

[att=1]

Since NetDog does IPv6 support for Comcast, one would hope that his opinion is based on facts.

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 11:49:13 EDT

graysonf posted : I suggested "None" because /128 is not a choice. I don't run pfsense here, I run m0n0wall instead. And I get a /128 on WAN and there is nothing to specify other than DHCP on WAN - there is no list of subnet mask choices.

I may flash a copy of pfsense to a spare CF and try it here to see what happens.

I do recall another thread along these lines and the way it turned out NetDog (I think) got involved and solved it. The cause was some type of misconfiguration by Comcast for that particular customer.

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 11:43:47 EDT

plencnerb posted : I've seen that thread, but I do need to take the time to sit down and read it fully to see if I'm having the same issues.

The one thing I did see so far in that thread appears to be a disagreement on the WAN DHCPv6 Prefix Delegation size. whfsdude indicates that it should be set as /64 to work correctly. Which, for me that is what I had, and it did work.

However, you ( graysonf ) have a different view, in that the setting should be set to "None", which would imply that it will pull a /128 from Comcast. You have it set that way (I'm guessing) and it also appears to work. I have to step out for a few hours, but when I get home, I'll play with that and see if it makes a difference.

In the meantime, if I look at my dashboard, something has gone south, as the status of the gateway "WAN_DHCP6" is now showing "Unknown". I know when everything was working, it did show "Online", with a proper IPv6 IP in the gateway box.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 11:19:15 EDT

graysonf posted : Any relation with what is going on here to this thread?

»[IPv6] Seeing two different LAN side ranges

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 11:10:36 EDT

anon posted :

said by plencnerb:

I am not very familiar with pfsense, but everything I have seen in this and other forums discussing how Comcast assigns IPv6 addresses has implied that a standalone PC or a router WAN interface should receive a /128 IPv6 address beginning with 2001:558:xxxx:yy.

I don't have access to the hidden OpenWRT configuration in my Comcast supplied Netgear router and the only workable WAN options I have available are "Auto Detect" and "DHCP", and both give me a /64 IP address assignment. I know someone with a D-Link router, and that router does not explicitly have a selection choice for the WAN IP address allocation size either, but his router does get a /128 from Comcast, and his router's WAN IPv6 address is stable.

If you can't manually select a /128 preference for the WAN allocation size in pfsense, perhaps selecting "None" might work?

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 10:26:41 EDT

plencnerb posted :

said by IPv6_NOT :

I think that this is happening in my Netgear router because it is getting a /64 WAN assignment when it should be getting a /128, but there is no configuration setting that I can make to change that. I noticed that in one of your pfsense screen shots that you also were getting a /64 WAN assignment, so if you can change that in the pfsense config, you may be able to prevent this from happening again.

Are you talking about the section that I posted above in pic #1? That section is on the WAN interface configuration.

If so, the values that I can select there are shown in pic #2. Does not look like I have the option to set that to be /128, unless I'm looking in the wrong spot.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

#1
#2

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 10:03:57 EDT

anon posted :

said by plencnerb:

That is interesting.

I'm not seeing the dual WAN IPv6 IP's like you posted in your screen shot, but I did notice that the last part is different with my IPv6 IP.

I have no idea what you call each section, but the first 4 items are the same, but the last 4 are different.

Yet, my router, and cable modem have not been rebooted since I noted what my IPv6 IP address was.

Below is what I'm talking about.

My IPv6 IP, on 12/12/2012 around 12:30 PM
2001:558:6033:ad:7d1b:4b65:f6a7:4462

PFSense is now showing this
2001:558:6033:ad:149f:8627:2f1:9d33

The part after the :ad: is what has changed.

Is that what you are talking about?

It only takes a few minutes to reboot my router, so I may go ahead and do that this morning and report back.

--Brian

Yes, that is what I was talking about. I don't always see the dual WAN IPv6 assignments showing in the GUI status page either (but I suspect it is there but just not showing). Sometimes it also manifests itself as two LAN IPv6 addresses with the PD portion changed, but the DUID (the last part of the IPv6 address) not changed.

In either case I think what has happened is that the DHCP6 has assigned a new IP address, but the old IPv6 address is also still assigned. I think that this is happening in my Netgear router because it is getting a /64 WAN assignment when it should be getting a /128, but there is no configuration setting that I can make to change that. I noticed that in one of your pfsense screen shots that you also were getting a /64 WAN assignment, so if you can change that in the pfsense config, you may be able to prevent this from happening again.

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 09:28:15 EDT

plencnerb posted : That is interesting.

I'm not seeing the dual WAN IPv6 IP's like you posted in your screen shot, but I did notice that the last part is different with my IPv6 IP.

I have no idea what you call each section, but the first 4 items are the same, but the last 4 are different.

Yet, my router, and cable modem have not been rebooted since I noted what my IPv6 IP address was.

Below is what I'm talking about.

My IPv6 IP, on 12/12/2012 around 12:30 PM
2001:558:6033:ad:7d1b:4b65:f6a7:4462

PFSense is now showing this
2001:558:6033:ad:149f:8627:2f1:9d33

The part after the :ad: is what has changed.

Is that what you are talking about?

It only takes a few minutes to reboot my router, so I may go ahead and do that this morning and report back.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 06:15:38 EDT

anon posted : This is an update to the post I made ~20 minutes ago. That post is still in limbo, so I hope that both posts either are approved at the same time, or in the proper sequence so that this post makes sense.

The problem with my WNR1000v2-VC just occurred, so I will post some screen shots of what I see so that you can look at the similar status pages in pFsense to see if your problem is similar.

[att=1]

[att=2]

[att=3]

IPv6 status from several days ago
IPv6 status showing dual WAN IP addresses
IPv6 status after reboot

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Thu, 03 Jan 2013 06:15:20 EDT

anon posted : My Comcast supplied Netgear WNR1000v2-VC also randomly loses IPv6 connectivity. It sometimes will stay in sync for several weeks, and sometimes only for a few days. IPv6 connectivity always comes back if I reboot the router and remake the connections with the attached PCs.

The problem with the Netgear router seems to be that its WAN is randomly assigned a new IPv6 address (but the 2001:558:xxxx:xx: prefix does does not change, nor does the IPv4 address). That new IP address triggers a new PD prefix for the LAN, but the old PD prefix is also still active. The only fix I have found is to reboot the router.

Have you tried rebooting your pFsense box and reconnecting the attached PC(s)?

Re: [IPv6] Issues with IPv6 and pfsense [SOLVED]

Wed, 02 Jan 2013 18:12:23 EDT

plencnerb posted : Ok I don't get it.

Yes, I'm replying to my own thread.

Why would I do something?

Answer: Things are not working now with IPv6.

Both IPv6 test sites that used to return 10/10 now return 0/10. I cannot get to »ipv6.speedtest.comcast.net/ anymore.

System Uptime on my modem is 11 d: 8 h: 37 m.
System Update for PFSense is just behind that, at 11 Days 08 Hours 29 Minutes 21 Seconds.

The last configuration change that I made to PFsense was on Wed Dec 12 12:36:08 CST 2012, which, is just after the last edit I made to the first post of this thread to indicate that it was working.

So, my question is, What Broke! :) And, probably more important, how do I get it working again?

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Re: [IPv6] Issues with IPv6 and pfsense

Tue, 11 Dec 2012 13:07:20 EDT

NetDog posted :

said by plencnerb:

Now the next step I think is to work with the mods to modify NetDog 's thread to put a post that shows the configuration steps / changes that need to be made in this version of pfsense to get it to work. Once that is done, then delete all of the posts and troubleshooting steps from my case, as that configuration has now been confirmed to be working. Thoughts? Kind of like a cleanup / reset on the thread, and get it ready for the next user who comes along with configuration issues for a different piece of hardware.

--Brian

how about a thread that just has the how-to? I have been thinking about writing a How-to for each of the routers and devices that I know about.. Thinking and on paper are two different things :).. I have been working on a Juniper router\switch as of late so it has been taking my spare time.

Re: [IPv6] Issues with IPv6 and pfsense

Tue, 11 Dec 2012 11:26:57 EDT

graysonf posted : Go to the Comcast FAQ page here: »Comcast High Speed Internet FAQ

Contact one of the Editors on the upper right side via Instant Message. I'm sure they will point you in the right direction.

Re: [IPv6] Issues with IPv6 and pfsense

Tue, 11 Dec 2012 11:20:02 EDT

plencnerb posted : You know, I would if I knew how to start! :)

If anything, I would have no problems putting together the section on configuration for pfsense.

--Brian

Re: [IPv6] Issues with IPv6 and pfsense

Tue, 11 Dec 2012 11:02:47 EDT

graysonf posted : FAQ, good idea. Feel free to get started anytime :)

Re: [IPv6] Issues with IPv6 and pfsense

Tue, 11 Dec 2012 11:00:56 EDT

plencnerb posted : They probably won't, it was just a suggestion.

Maybe what I am thinking of is more along the lines of a FAQ for IPv6. NetDog's thread could be the "work area" so to speak for the FAQ. We take the first first post as kind of the starting point for the FAQ, and then as people post their different routers and configurations, and we all work together to get them up and running, the FAQ then is modified to include a section for a specific hardware.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Re: [IPv6] Issues with IPv6 and pfsense

Tue, 11 Dec 2012 10:59:13 EDT

whfsdude posted :

said by plencnerb:

I am curious though to hear whfsdude 's thoughts on this, as he is the one that said what he uses for that value, and apparently it is working fine for him.

Sorry I've been swamped since Monday and haven't had much time to look at threads. Glad you figured it out.

I was using DHCP6 w/track interface up until two weeks ago when I moved to all static configurations.

I wonder if it's a regression in their code. »lists.pfsense.org/pipermail/list···831.html

Re: [IPv6] Issues with IPv6 and pfsense

Tue, 11 Dec 2012 10:48:24 EDT

graysonf posted : I doubt they will delete posts or threads, which is why I suggested editing the Subject to include [SOLVED].

Re: [IPv6] Issues with IPv6 and pfsense

Tue, 11 Dec 2012 10:24:54 EDT

plencnerb posted :

said by graysonf:

Glad you have it sorted out. You might want to change the Subject of the root post for this to include [SOLVED].

Went ahead and did that, and modified my OP post as well to indicate what I had to do to fix it.

I am curious though to hear whfsdude 's thoughts on this, as he is the one that said what he uses for that value, and apparently it is working fine for him.

Now the next step I think is to work with the mods to modify NetDog 's thread to put a post that shows the configuration steps / changes that need to be made in this version of pfsense to get it to work. Once that is done, then delete all of the posts and troubleshooting steps from my case, as that configuration has now been confirmed to be working. Thoughts? Kind of like a cleanup / reset on the thread, and get it ready for the next user who comes along with configuration issues for a different piece of hardware.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Re: [IPv6] Issues with IPv6 and pfsense

Tue, 11 Dec 2012 09:56:57 EDT

graysonf posted : Glad you have it sorted out. You might want to change the Subject of the root post for this to include [SOLVED].

Re: [IPv6] Issues with IPv6 and pfsense

Tue, 11 Dec 2012 09:47:59 EDT

plencnerb posted :

said by graysonf:

Your WAN IPv6 netmask is 64 bits. Mine is 128 bits.

Your LAN IPv6 address looks more like it was statically assigned, not by DHCP-PD.

You still haven't said how you are configuring for IPv6. Post those screens as well.

Above are how I currently have things configured in regards to the LAN and WAN interfaces.

By default, when I installed pfsense, I did not need to make any changes to this, per what whfsdude said in the other post.

His comment is below

said by whfsdude:

Are you running the 2.1 branch?

1. Interfaces > WAN
2. For 'IPv6 Configuration Type' select 'DHCP6'
3. For 'DHCPv6 Prefix Delegation size' select '64', apply
4. Interfaces > LAN
5. For 'IPv6 Configuration Type' select 'Track Interface'
6. For 'IPv6 Interface' select WAN.
7. For 'IPv6 Prefix ID' enter '0', apply
8. Reboot!

What you are suggesting is a bit different then what he has said. But, since we are in troubleshooting mode, I'm willing to make any changes to see what I can do to figure this out.

So, on the LAN Interface configuration page, I modified the IPv6 Configuration Type from the value "Track Interface" to "DHCP6".

Once that was done, I did an ipconfig /release and then an ipconfig /renew.

The issue now is solved! :) The IPv6 Test pages now come back with a score of 10/10. On the Comcast IPv6 Speedtest side, it now loads, and shows my IPv6 IP at the top.

That was an easy fix!

Of course, it makes me wonder then, what is different between my setup and whfsdude 's, as he is also running pfsense, with that one value different then what I have, and he apparently does not have any issues.

Thoughts?

--Brian

--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

WAN Interface Configuration
LAN Interface Configuration

Re: [IPv6] Issues with IPv6 and pfsense

Tue, 11 Dec 2012 08:13:37 EDT

graysonf posted : Your WAN IPv6 netmask is 64 bits. Mine is 128 bits.

Your LAN IPv6 address looks more like it was statically assigned, not by DHCP-PD.

You still haven't said how you are configuring for IPv6. Post those screens as well.

Re: [IPv6] Issues with IPv6 and pfsense

Mon, 10 Dec 2012 23:27:43 EDT

plencnerb posted :

said by joako:

1) What is the version of pfsense (Status > Dashboard)
2) What IPv6 info do you see under Status > Interfaces?

said by PhReE5:

PFSense currently doesnt support ipv6. The next release (v2.1) will support ipv6. You can download and run a beta of it if you want, but the current release 2.0x versions do not support ipv6.

The answers to both of your questions should now be visible in the posts above. I have edited them all at this point.

If you need further information, just ask.

Thanks,

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Re: [IPv6] Issues with IPv6 and pfsense

Mon, 10 Dec 2012 22:15:37 EDT

PhReE5 posted : PFSense currently doesnt support ipv6. The next release (v2.1) will support ipv6. You can download and run a beta of it if you want, but the current release 2.0x versions do not support ipv6.

Re: [IPv6] Issues with IPv6 and pfsense

Mon, 10 Dec 2012 22:04:35 EDT

joako posted : 1) What is the version of pfsense (Status > Dashboard)
2) What IPv6 info do you see under Status > Interfaces?
--
PRescott7-2097

Re: [IPv6] Issues with IPv6 and pfsense

Mon, 10 Dec 2012 19:53:31 EDT

plencnerb posted : In this post, I'm going to document things in pfsense.

In Picture #1, I am showing the System Information. This should answer any questions about what version I'm running and all of that.

Picture #2 shows everything on the WAN side of things.

Picture #3 shows everything on the LAN side of things.

Finally, Picture #4 shows the only modification I have made. I added a WAN firewall rule to for IPv6. This was per the suggestion by whfsdude .

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Picture #1
Picture #2
Picture #3
Picture #4

Re: [IPv6] Issues with IPv6 and pfsense

Mon, 10 Dec 2012 19:51:17 EDT

plencnerb posted : In this post, I want to document how things work when I am behind my pfsense firewall.

So, I will run though the same set of tests I did above, and show you my results.

Below are the results of running the command "ipconfig/all"

Microsoft Windows [Version 6.1.7601]Copyright (c) 2009 Microsoft Corporation.  All rights reserved. C:\Users\Brian A. Plencner>ipconfig/all Windows IP Configuration    Host Name . . . . . . . . . . . . : BRIAN-DESKTOP   Primary Dns Suffix  . . . . . . . :   Node Type . . . . . . . . . . . . : Hybrid   IP Routing Enabled. . . . . . . . : No   WINS Proxy Enabled. . . . . . . . : No   DNS Suffix Search List. . . . . . : localdomain Ethernet adapter Local Area Connection:    Connection-specific DNS Suffix  . : localdomain   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller   Physical Address. . . . . . . . . : F4-6D-04-F0-32-43   DHCP Enabled. . . . . . . . . . . : Yes   Autoconfiguration Enabled . . . . : Yes   IPv6 Address. . . . . . . . . . . : 2601:d:4c00:67:34c8:339c:31d4:729b(Preferred)   Temporary IPv6 Address. . . . . . : 2601:d:4c00:67:1952:1b74:c511:8be4(Preferred)   Link-local IPv6 Address . . . . . : fe80::34c8:339c:31d4:729b%11(Preferred)   IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)   Subnet Mask . . . . . . . . . . . : 255.255.255.0   Lease Obtained. . . . . . . . . . : Monday, December 10, 2012 3:40:21 PM   Lease Expires . . . . . . . . . . : Monday, December 10, 2012 7:40:21 PM   Default Gateway . . . . . . . . . : fe80::250:4ff:fe21:713d%11                                       192.168.1.1   DHCP Server . . . . . . . . . . . : 192.168.1.1   DHCPv6 IAID . . . . . . . . . . . : 250899716   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-26-E4-53-F4-6D-04-F0-32-43   DNS Servers . . . . . . . . . . . : 2601:d:4c00:67::1                                       192.168.1.1   NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Teredo Tunneling Pseudo-Interface:    Connection-specific DNS Suffix  . :   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0   DHCP Enabled. . . . . . . . . . . : No   Autoconfiguration Enabled . . . . : Yes   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:2058:2218:e7f2:eed8(Preferred)   Link-local IPv6 Address . . . . . : fe80::2058:2218:e7f2:eed8%13(Preferred)   Default Gateway . . . . . . . . . :   NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter isatap.localdomain:    Media State . . . . . . . . . . . : Media disconnected   Connection-specific DNS Suffix  . : localdomain   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0   DHCP Enabled. . . . . . . . . . . : No   Autoconfiguration Enabled . . . . : Yes C:\Users\Brian A. Plencner>

Next, I ran the following command: "netsh int ipv6 show addr". I did this just to verify the information I was seeing from the ipconfig command.

 C:\Users\Brian A. Plencner>netsh int ipv6 show addr Interface 1: Loopback Pseudo-Interface 1 Addr Type  DAD State   Valid Life Pref. Life Address---------  ----------- ---------- ---------- ------------------------Other      Preferred     infinite   infinite ::1 Interface 13: Teredo Tunneling Pseudo-Interface Addr Type  DAD State   Valid Life Pref. Life Address---------  ----------- ---------- ---------- ------------------------Public     Preferred     infinite   infinite 2001:0:9d38:953c:2058:2218:e7f2:eed8Other      Preferred     infinite   infinite fe80::2058:2218:e7f2:eed8%13 Interface 11: Local Area Connection Addr Type  DAD State   Valid Life Pref. Life Address---------  ----------- ---------- ---------- ------------------------Temporary  Preferred    23h59m59s   3h59m59s 2601:d:4c00:67:1952:1b74:c511:8be4Public     Preferred    23h59m59s   3h59m59s 2601:d:4c00:67:34c8:339c:31d4:729bOther      Preferred     infinite   infinite fe80::34c8:339c:31d4:729b%11 Interface 14: isatap.localdomain Addr Type  DAD State   Valid Life Pref. Life Address---------  ----------- ---------- ---------- ------------------------Other      Deprecated    infinite   infinite fe80::5efe:192.168.1.100%14 C:\Users\Brian A. Plencner>

So far, things appear to be working, in regards to pfsense giving my desktop a "proper" IPv6 IP, as well as a "proper" IPv4" IP.

So, I then went ahead and tested the same three sites

• »test-ipv6.com/
• »test-ipv6.comcast.net/
• »ipv6.speedtest.comcast.net/

The results of these are shown above as Picture #1, #2, and #3, respectively.

Of note now is that my results went from 10/10 to 0/10 for both test sites, and the IPv6 speedtest site failed to load.

This tells me that something is not configured correctly in regards to pfsense.

To confirm this, I went ahead and ran the same commands from the command prompt.

nslookup commands

 C:\Users\Brian A. Plencner>nslookup www.comcast.netDNS request timed out.    timeout was 2 seconds.Server:  UnKnownAddress:  2601:d:4c00:67::1 DNS request timed out.    timeout was 2 seconds.DNS request timed out.    timeout was 2 seconds.DNS request timed out.    timeout was 2 seconds.DNS request timed out.    timeout was 2 seconds.*** Request to UnKnown timed-out C:\Users\Brian A. Plencner>nslookup -type=AAAA www.comcast.netDNS request timed out.    timeout was 2 seconds.Server:  UnKnownAddress:  2601:d:4c00:67::1 DNS request timed out.    timeout was 2 seconds.DNS request timed out.    timeout was 2 seconds.*** Request to UnKnown timed-out C:\Users\Brian A. Plencner>nslookup www.google.comDNS request timed out.    timeout was 2 seconds.Server:  UnKnownAddress:  2601:d:4c00:67::1 DNS request timed out.    timeout was 2 seconds.DNS request timed out.    timeout was 2 seconds.DNS request timed out.    timeout was 2 seconds.DNS request timed out.    timeout was 2 seconds.*** Request to UnKnown timed-out C:\Users\Brian A. Plencner>nslookup -type=AAAA www.google.comDNS request timed out.    timeout was 2 seconds.Server:  UnKnownAddress:  2601:d:4c00:67::1 DNS request timed out.    timeout was 2 seconds.DNS request timed out.    timeout was 2 seconds.*** Request to UnKnown timed-out C:\Users\Brian A. Plencner>

ping commands

 C:\Users\Brian A. Plencner>ping ipv6.dcsenterprises.net Pinging ipv6-dcs-srv.dyndns-ip.com [2601:5:c80:91:e291:f5ff:fe95:beac] with 32 bytes of data:Request timed out.Request timed out.Request timed out.Request timed out. Ping statistics for 2601:5:c80:91:e291:f5ff:fe95:beac:    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\Brian A. Plencner>ping 2601:5:c80:91:e291:f5ff:fe95:beac Pinging 2601:5:c80:91:e291:f5ff:fe95:beac with 32 bytes of data:Request timed out.Request timed out.Request timed out.Request timed out. Ping statistics for 2601:5:c80:91:e291:f5ff:fe95:beac:    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\Brian A. Plencner>

And then finally, a few trace commands. I did mix both IPv4 and IPv6 sites in this, just to be complete.

 C:\Users\Brian A. Plencner>tracert 2601:5:c80:91:e291:f5ff:fe95:beac Tracing route to 2601:5:c80:91:e291:f5ff:fe95:beac over a maximum of 30 hops   1     *        *        *     Request timed out.  2     *        *        *     Request timed out.  3     *        *        *     Request timed out.  4     *        *        *     Request timed out.  5     *        *        *     Request timed out.  6     *        *        *     Request timed out.  7     *        *        *     Request timed out.  8     *        *        *     Request timed out.  9     *        *        *     Request timed out. 10     *        *        *     Request timed out. 11     *        *        *     Request timed out. 12     *        *        *     Request timed out. 13     *        *        *     Request timed out. 14     *        *        *     Request timed out. 15     *        *        *     Request timed out. 16     *        *        *     Request timed out. 17     *        *        *     Request timed out. 18     *        *        *     Request timed out. 19     *        *        *     Request timed out. 20     *        *        *     Request timed out. 21     *        *        *     Request timed out. 22     *        *        *     Request timed out. 23     *        *        *     Request timed out. 24     *        *        *     Request timed out. 25     *        *        *     Request timed out. 26     *        *        *     Request timed out. 27     *        *        *     Request timed out. 28     *        *        *     Request timed out. 29     *        *        *     Request timed out. 30     *        *        *     Request timed out. Trace complete. C:\Users\Brian A. Plencner>tracert www.google.com Tracing route to www.google.com [74.125.225.211]over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  pfSense.localdomain [192.168.1.1]  2    30 ms    28 ms    19 ms  24.13.16.1  3    11 ms    14 ms    10 ms  te-9-1-ur04.algonquin.il.chicago.comcast.net [68.87.229.189]  4    16 ms    19 ms    15 ms  te-0-3-0-2-ar01.area4.il.chicago.comcast.net [68.86.189.229]  5    21 ms    23 ms    24 ms  he-3-11-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.13]  6    29 ms    13 ms    15 ms  pos-1-1-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.38]  7    37 ms    37 ms     *     66.208.228.202  8    14 ms    12 ms    14 ms  209.85.254.120  9    13 ms    13 ms    14 ms  72.14.237.133 10    25 ms    26 ms    39 ms  72.14.232.141 11    58 ms    34 ms    35 ms  72.14.239.51 12    40 ms    34 ms    38 ms  216.239.46.151 13    49 ms    50 ms    35 ms  209.85.251.111 14    36 ms    36 ms    35 ms  den03s06-in-f19.1e100.net [74.125.225.211] Trace complete. C:\Users\Brian A. Plencner>tracert www.dslreports.com Tracing route to www.dslreports.com [209.123.109.175]over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  pfSense.localdomain [192.168.1.1]  2    27 ms    29 ms    29 ms  24.13.16.1  3    10 ms    11 ms     9 ms  te-9-1-ur04.algonquin.il.chicago.comcast.net [68.87.229.189]  4    14 ms    15 ms    15 ms  te-0-3-0-2-ar01.area4.il.chicago.comcast.net [68.86.189.229]  5    18 ms    23 ms    24 ms  he-3-5-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.95.237]  6    39 ms    36 ms    35 ms  he-4-4-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.88.145]  7    36 ms    34 ms    33 ms  173.167.58.26  8    34 ms    36 ms    34 ms  0.e1-4.tbr1.oct.nac.net [209.123.10.122]  9    39 ms    34 ms    35 ms  vlan804.esd1.oct.nac.net [209.123.10.2] 10    36 ms    34 ms    36 ms  www.dslreports.com [209.123.109.175] Trace complete. C:\Users\Brian A. Plencner>

So, from what I can figure out, the issue appears to not be a DNS one, as I am able to resolve an IPv6 IP for its proper DNS name. However, I am not able to reach (or ping) to an IPv6 IP, or a IPv6 only site. So, there has to be something that is mis-configured inside of pfsense that is causing this. What I don't know.

--Brian

--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Picture #1
Picture #2
Picture #3

Re: [IPv6] Issues with IPv6 and pfsense

Mon, 10 Dec 2012 19:17:45 EDT

plencnerb posted : So for starters, I wanted to document my testing to show that IPv6 does work for me, when I connect my desktop directly to my cable modem.

For these tests, I connected my desktop directly to my cable modem, after doing a reset on both (desktop was powered off, cable modem was reset using the little pin hole in the back).

Once that was complete, I ran an "ipconfig/all". Those results are below

Microsoft Windows [Version 6.1.7601]Copyright (c) 2009 Microsoft Corporation.  All rights reserved.  C:\Users\Brian A. Plencner>ipconfig /all  Windows IP Configuration     Host Name . . . . . . . . . . . . : BRIAN-DESKTOP   Primary Dns Suffix  . . . . . . . :   Node Type . . . . . . . . . . . . : Hybrid   IP Routing Enabled. . . . . . . . : No   WINS Proxy Enabled. . . . . . . . : No   DNS Suffix Search List. . . . . . : hsd1.il.comcast.net.  Ethernet adapter Local Area Connection:     Connection-specific DNS Suffix  . : hsd1.il.comcast.net.   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller   Physical Address. . . . . . . . . : F4-6D-04-F0-32-43   DHCP Enabled. . . . . . . . . . . : Yes   Autoconfiguration Enabled . . . . : Yes   IPv6 Address. . . . . . . . . . . : 2001:558:6033:ad:18b2:dcdb:2418:a1ad(Preferred)   Lease Obtained. . . . . . . . . . : Monday, December 10, 2012 6:34:58 AM   Lease Expires . . . . . . . . . . : Friday, December 14, 2012 6:34:57 AM   Link-local IPv6 Address . . . . . : fe80::34c8:339c:31d4:729b%11(Preferred)   IPv4 Address. . . . . . . . . . . : 67.184.208.11(Preferred)   Subnet Mask . . . . . . . . . . . : 255.255.252.0   Lease Obtained. . . . . . . . . . : Monday, December 10, 2012 6:34:55 AM   Lease Expires . . . . . . . . . . : Monday, December 10, 2012 7:31:16 AM   Default Gateway . . . . . . . . . : fe80::201:5cff:fe3d:4e41%11                                       67.184.208.1   DHCP Server . . . . . . . . . . . : 69.252.202.7   DHCPv6 IAID . . . . . . . . . . . : 250899716   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-26-E4-53-F4-6D-04-F0-32-43   DNS Servers . . . . . . . . . . . : 2001:558:feed::1                                       2001:558:feed::2                                       75.75.75.75                                       75.75.76.76   NetBIOS over Tcpip. . . . . . . . : Enabled  Tunnel adapter isatap.hsd1.il.comcast.net.:     Media State . . . . . . . . . . . : Media disconnected   Connection-specific DNS Suffix  . : hsd1.il.comcast.net.   Description . . . . . . . . . . . : Microsoft ISATAP Adapter   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0   DHCP Enabled. . . . . . . . . . . : No   Autoconfiguration Enabled . . . . : Yes  Tunnel adapter Teredo Tunneling Pseudo-Interface:     Connection-specific DNS Suffix  . :   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0   DHCP Enabled. . . . . . . . . . . : No   Autoconfiguration Enabled . . . . : Yes   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:4b:3355:bc47:2ff4(Preferred)   Link-local IPv6 Address . . . . . : fe80::4b:3355:bc47:2ff4%13(Preferred)   Default Gateway . . . . . . . . . :   NetBIOS over Tcpip. . . . . . . . : Disabled  C:\Users\Brian A. Plencner>

Next, I ran the following command: "netsh int ipv6 show addr". I did this just to verify the information I was seeing from the ipconfig command.

C:\Users\Brian A. Plencner>netsh int ipv6 show addr  Interface 1: Loopback Pseudo-Interface 1  Addr Type  DAD State   Valid Life Pref. Life Address---------  ----------- ---------- ---------- ------------------------Other      Preferred     infinite   infinite ::1  Interface 12: isatap.hsd1.il.comcast.net.  Addr Type  DAD State   Valid Life Pref. Life Address---------  ----------- ---------- ---------- ------------------------Other      Deprecated    infinite   infinite fe80::200:5efe:67.184.208.11%12  Interface 13: Teredo Tunneling Pseudo-Interface  Addr Type  DAD State   Valid Life Pref. Life Address---------  ----------- ---------- ---------- ------------------------Public     Preferred     infinite   infinite 2001:0:9d38:953c:4b:3355:bc47:2ff4Other      Preferred     infinite   infinite fe80::4b:3355:bc47:2ff4%13  Interface 11: Local Area Connection  Addr Type  DAD State   Valid Life Pref. Life Address---------  ----------- ---------- ---------- ------------------------Dhcp       Preferred     3d23h59m   3d23h59m 2001:558:6033:ad:18b2:dcdb:2418:a1adOther      Preferred     infinite   infinite fe80::34c8:339c:31d4:729b%11  C:\Users\Brian A. Plencner>

So far, things were looking good.

Then, using Waterfox I went to the following three web pages

• »test-ipv6.com/
• »test-ipv6.comcast.net/
• »ipv6.speedtest.comcast.net/

The results of these are shown above as Picture #1, #2, and #3, respectively.

As a final verification, I ran some more tests from the command prompt.

nslookup commands

C:\Users\Brian A. Plencner>nslookup www.comcast.netServer:  cdns01.comcast.netAddress:  2001:558:feed::1  Non-authoritative answer:Name:    a1526.dscg.akamai.netAddresses:  2001:559:0:5d::1743:3d3b          2001:559:0:5d::1743:3d39          96.17.77.66          96.17.77.42Aliases:  www.comcast.net          www.comcast.net.edgesuite.net  C:\Users\Brian A. Plencner>nslookup -type=AAAA www.comcast.netServer:  cdns01.comcast.netAddress:  2001:558:feed::1  Non-authoritative answer:Name:    a1526.dscg.akamai.netAddresses:  2001:559:0:5d::1743:3d39          2001:559:0:5d::1743:3d3bAliases:  www.comcast.net          www.comcast.net.edgesuite.net  C:\Users\Brian A. Plencner>nslookup www.google.comServer:  cdns01.comcast.netAddress:  2001:558:feed::1  Non-authoritative answer:Name:    www.google.comAddresses:  2607:f8b0:400f:801::1011          74.125.225.208          74.125.225.211          74.125.225.209          74.125.225.210          74.125.225.212  C:\Users\Brian A. Plencner>nslookup -type=AAAA www.google.comServer:  cdns01.comcast.netAddress:  2001:558:feed::1  Non-authoritative answer:Name:    www.google.comAddress:  2607:f8b0:400f:801::1012  C:\Users\Brian A. Plencner>

ping commands

C:\Users\Brian A. Plencner>ping ipv6.dcsenterprises.net  Pinging ipv6-dcs-srv.dyndns-ip.com [2601:5:c80:91:e291:f5ff:fe95:beac] with 32 bytes of data:Reply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=41msReply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=37msReply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=35msReply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=36ms  Ping statistics for 2601:5:c80:91:e291:f5ff:fe95:beac:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 35ms, Maximum = 41ms, Average = 37ms  C:\Users\Brian A. Plencner>ping 2601:5:c80:91:e291:f5ff:fe95:beac  Pinging 2601:5:c80:91:e291:f5ff:fe95:beac with 32 bytes of data:Reply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=34msReply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=35msReply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=36msReply from 2601:5:c80:91:e291:f5ff:fe95:beac: time=36ms  Ping statistics for 2601:5:c80:91:e291:f5ff:fe95:beac:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 34ms, Maximum = 36ms, Average = 35ms

And then finally, a few trace commands. I did mix both IPv4 and IPv6 sites in this, just to be complete.

C:\Users\Brian A. Plencner>tracert 2601:5:c80:91:e291:f5ff:fe95:beac  Tracing route to 2601:5:c80:91:e291:f5ff:fe95:beac over a maximum of 30 hops    1    37 ms    30 ms    29 ms  2001:558:6033:ad::1  2     9 ms     8 ms     9 ms  te-9-1-ur04.algonquin.il.chicago.comcast.net [2001:558:322:26f::1]  3    15 ms    15 ms    15 ms  te-0-3-0-0-ar01.area4.il.chicago.comcast.net [2001:558:300:1e::1]  4    19 ms    23 ms    23 ms  he-3-5-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f7fb::1]  5    25 ms    25 ms    26 ms  so-7-1-0-0-ar03.nashville.tn.nash.comcast.net [2001:558:0:f7f4::2]  6    27 ms    26 ms    28 ms  xe-0-1-0-0-sur01.murfreesboro.tn.nash.comcast.net [2001:558:160:57::2]  7    39 ms    34 ms    27 ms  2001:558:162:32::2  8    36 ms    35 ms    37 ms  2001:558:6016:19:39d6:46d1:4004:e738  9    37 ms    35 ms    38 ms  2601:5:c80:91:e291:f5ff:fe95:beac  Trace complete.  C:\Users\Brian A. Plencner>tracert www.google.com  Tracing route to www.google.com [2607:f8b0:400f:801::1013]over a maximum of 30 hops:    1    27 ms    29 ms    29 ms  2001:558:6033:ad::1  2     9 ms     9 ms    10 ms  te-9-1-ur04.algonquin.il.chicago.comcast.net [2001:558:322:26f::1]  3    16 ms    16 ms    14 ms  te-0-3-0-3-ar01.area4.il.chicago.comcast.net [2001:558:300:286::1]  4    22 ms    23 ms    17 ms  he-3-7-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f68d::1]  5    14 ms    13 ms    13 ms  pos-1-2-0-0-pe01.350ecermak.il.ibone.comcast.net [2001:558:0:f593::2]  6    59 ms    13 ms    12 ms  2001:559::44a  7    13 ms    13 ms    13 ms  2001:4860::1:0:92e  8    14 ms    13 ms    13 ms  2001:4860::8:0:2fe9  9    35 ms    37 ms    36 ms  2001:4860::8:0:281d 10    36 ms    33 ms    33 ms  2001:4860::8:0:3426 11    34 ms    34 ms    43 ms  2001:4860::1:0:7a4 12    35 ms    38 ms    36 ms  2001:4860:0:1::593 13    34 ms    35 ms    35 ms  den03s06-in-x13.1e100.net [2607:f8b0:400f:801::1013]  Trace complete.  C:\Users\Brian A. Plencner>tracert www.dslreports.com  Tracing route to www.dslreports.com [209.123.109.175]over a maximum of 30 hops:    1    31 ms    22 ms    27 ms  67.184.208.1  2    29 ms    15 ms    16 ms  te-9-1-ur04.algonquin.il.chicago.comcast.net [68.87.229.189]  3    15 ms    15 ms    15 ms  te-0-3-0-2-ar01.area4.il.chicago.comcast.net [68.86.189.229]  4    14 ms    23 ms    11 ms  he-3-8-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.49]  5    40 ms    35 ms    35 ms  he-4-6-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.88.153]  6    41 ms    33 ms    40 ms  173.167.58.26  7    34 ms    33 ms    32 ms  0.e1-4.tbr1.oct.nac.net [209.123.10.122]  8    35 ms    34 ms    32 ms  vlan804.esd1.oct.nac.net [209.123.10.2]  9    34 ms    32 ms    32 ms  www.dslreports.com [209.123.109.175]  Trace complete.  C:\Users\Brian A. Plencner>

So, my final observation here is that IPv6 is working (as best as I can tell) exactly the way it should be when I am directly connected to my cable modem.

--Brian

--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

Picture #1
Picture #2
Picture #3

[IPv6] Issues with IPv6 and pfsense [SOLVED]

Mon, 10 Dec 2012 18:53:37 EDT

plencnerb posted : I figured it was time to start a new thread on the issues I'm having with getting pfsense configured to work with Comcast in regards to IPv6.

So, this post will be short, as it is just the introduction.

The next few posts will go into more detail. I've done it this way to help break up the different sections, and hopefully, help troubleshoot the issue at hand.

Basic information about my setup

1) Cable Modem:
Vendor: Arris
Model: TM722G/CT
Firmware Name: TS070463A_011312_MODEL_7_8_SIP_PC20
Firmware Build Time: Fri Jan 13 19:51:18 EST 2012

2) Computer
Self-Built desktop running Windows 7 x64 Enterprise

3) Location
Carpentersville, IL.

EDIT 12/11/2012 @ 9:19 AM
Turns out I had to modify the default WAN Configuration setting from for IPv6 Configuration Type from "Track Interface" to "DHCP6".

Everything is now working as it should be.

:)

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail