 plencnerbPremium
join:2000-09-25
Elgin, IL
kudos:2 | reply to graysonf
Re: [IPv6] Issues with IPv6 and pfsense
WAN Interface Configuration | 
LAN Interface Configuration |
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 |
|
 graysonfPremium,MVM
join:1999-07-16
Fort Lauderdale, FL | Glad you have it sorted out. You might want to change the Subject of the root post for this to include [SOLVED]. |
|
plencnerbPremium
join:2000-09-25
Elgin, IL
kudos:2 | 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 |
|
graysonfPremium,MVM
join:1999-07-16
Fort Lauderdale, FL | I doubt they will delete posts or threads, which is why I suggested editing the Subject to include [SOLVED]. |
|
 whfsdudePremium
join:2003-04-05
Washington, DC
 ·T-Mobile US
| reply to plencnerb
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 |
|
plencnerbPremium
join:2000-09-25
Elgin, IL
kudos:2 | reply to graysonf
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 |
|
graysonfPremium,MVM
join:1999-07-16
Fort Lauderdale, FL | FAQ, good idea. Feel free to get started anytime |
|
plencnerbPremium
join:2000-09-25
Elgin, IL
kudos:2 | 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 |
|
graysonfPremium,MVM
join:1999-07-16
Fort Lauderdale, FL | 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. |
|
 NetDogPremium,VIP
join:2002-03-04
Parker, CO
kudos:4
 ·Comcast
| reply to plencnerb
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. |
|
|
|
