IPv6 changes in 2.2.5

HiddenWolf

@HiddenWolf:

I've tried applying your patch to see if I could get ipv6 on WAN, but it doesn't appear to work for my problem.

You have to wait until M_Devil chimes in. He has a 500/500 I understood.

Did you try my config in: https://forum.pfsense.org/index.php?topic=103990.msg579876#msg579876 on the vLAN in pfSense
or are you ?

And you know the "permanent" /48 you have, in order to config static LAN(s) ;)

I had not set dhcp6 advanced options. I've just tried it, and it does not appear to make a difference. IPv6 still comes up on LAN reliably, and local machines get assigned IP's as well, but no IPv6 route and no IP for the WAN.

Note: my WAN is set up as PPPOE(igb0,igb0_vlan6). IP connectivity is on vlan6, IPTV is on vlan4 (which I haven't gotten to work just yet)

![Screen Shot 2016-01-06 at 20.40.17.png](/public/imported_attachments/1/Screen Shot 2016-01-06 at 20.40.17.png)
![Screen Shot 2016-01-06 at 20.40.17.png_thumb](/public/imported_attachments/1/Screen Shot 2016-01-06 at 20.40.17.png_thumb)

David_W

@HiddenWolf:

I just made a post inquiring about a not-getting-an-IPv6-on-pppoe problem before I found this thread.
My setup is described here: https://forum.pfsense.org/index.php?topic=104895.0

I've tried applying your patch to see if I could get ipv6 on WAN, but it doesn't appear to work for my problem.
If there's anything I can do to help, I'd be happy to.
Screenshot from first boot after applying the patch attached.

I've just replied in your other thread.

I urge you to give MTU 1500 operation a go using RFC 4638, as I described in that thread - it should work with your setup, assuming bhyve and your NIC is capable of using jumbo frames on your WAN interface.

HiddenWolf

@David_W:

@HiddenWolf:

I just made a post inquiring about a not-getting-an-IPv6-on-pppoe problem before I found this thread.
My setup is described here: https://forum.pfsense.org/index.php?topic=104895.0

I've tried applying your patch to see if I could get ipv6 on WAN, but it doesn't appear to work for my problem.
If there's anything I can do to help, I'd be happy to.
Screenshot from first boot after applying the patch attached.

I've just replied in your other thread.

I urge you to give MTU 1500 operation a go using RFC 4638, as I described in that thread - it should work with your setup, assuming bhyve and your NIC is capable of using jumbo frames on your WAN interface.

MTU 1500 works as advertised. But I'm not getting an IPv6 on WAN (yet)

hda

@David_W:

…Bother...

Thanks. All OK and after the 1hr lease renewal. I approve of this patch ! :)

M_Devil

Steps
revert previous patch, delete it
update to newest built:
2.3-BETA (amd64)
built on Wed Jan 06 07:53:18 CST 2016
FreeBSD 10.2-STABLE

create newest patch (from your description), fetch it

After fetch, test it, but…

Apply = clean
Reverted = not clean

/usr/bin/patch --directory=/ -f -p2 -i /var/patches/568d8e2e969e1.patch --check --reverse --ignore-whitespace

Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/etc/inc/interfaces.inc b/src/etc/inc/interfaces.inc
|index 49fd2ca..73879ce 100644
|--- a/src/etc/inc/interfaces.inc
|+++ b/src/etc/inc/interfaces.inc
--------------------------
Patching file etc/inc/interfaces.inc using Plan A...
Hunk #1 failed at 1998.
Hunk #2 failed at 2020.
Hunk #3 failed at 3349.
Hunk #4 failed at 3958.
4 out of 4 hunks failed while patching etc/inc/interfaces.inc
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/etc/rc.newwanip b/src/etc/rc.newwanip
|index 45cef96..5bc6a61 100755
|--- a/src/etc/rc.newwanip
|+++ b/src/etc/rc.newwanip
--------------------------
Patching file etc/rc.newwanip using Plan A...
Hunk #1 failed at 170.
1 out of 1 hunks failed while patching etc/rc.newwanip
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff --git a/src/usr/local/sbin/ppp-ipv6 b/src/usr/local/sbin/ppp-ipv6
|index aa0536c..4d47de2 100755
|--- a/src/usr/local/sbin/ppp-ipv6
|+++ b/src/usr/local/sbin/ppp-ipv6
--------------------------
Patching file usr/local/sbin/ppp-ipv6 using Plan A...
Hunk #1 failed at 23.
Hunk #2 failed at 63.
2 out of 2 hunks failed while patching usr/local/sbin/ppp-ipv6
done

Apply patch
reboot

Test 1
after reboot no IPv6 traffic
Multiple Interface disconnect-connects, still no IPv6

Test 2
Same after several reboots:

IPv6 Link Local
IPv6 Address
Gateway IPv6

Leaving me in a non operationel IPv6 state now.
If you like, I can do more tests

Edit: If I find the time, I will reinstall 2.3.b and recover the configuration to make sure the problem has nothing to do with all the updates I performed.

M_Devil

After uninstalling patch, again updated to newest (2.3.b 7-jan 2:26) version of pfSense refetch, apply en reboot IPv6 is working again. Also after several reboots

Don't have a clue why it did't work te last attempt, maybe I made an configuration mistake (It was late on the evening…)

David_W

@M_Devil:

After uninstalling patch, again updated to newest (2.3.b 7-jan 2:26) version of pfSense refetch, apply en reboot IPv6 is working again. Also after several reboots

Don't have a clue why it did't work te last attempt, maybe I made an configuration mistake (It was late on the evening…)

It's good news that things are now stable with your IPv6 connectivity.

It would be useful if you'd try the patch again. It hasn't changed since you last tried it.

Please also give outline details of the connection - especially the settings for "IPv4 Configuration Type", "IPv6 Configuration Type" and "Use IPv4 connectivity as parent interface" (in the "DHCP6 Client Configuration" section).

I hope to reach a point of having confidence in this patch so that I can submit a pull request. I'm confident in the work-round used for Issue 2 (a proper fix needs changes in mpd5). Though I now believe I understand Issue 1 well, I would like some additional user experience of the fix for Issue 1 before submitting a pull request because of the complexity of the underlying issues.

David_W

I've posted a link to this thread in the 2.3-BETA forum, in the hope of further feedback on these issues.

maverick_slo

Well thats odd…

On 2.3 with or without patch pfsense can communicate via IPv6 with outside world but LAN clients cannot.

What?

hda

@maverick_slo:

What?

Your config & data could make it interesting ;)

maverick_slo

Upgraded from 2.2.6 to 2.3 rebooted 2 times all was working.
Then I just saved pppoe iface and now only pfsense can talk ipv6 hosts not.

maverick_slo

Some screens of my config

snip1.JPG_thumb

snip2.JPG_thumb

snip3.JPG_thumb

David_W

@maverick_slo:

Upgraded from 2.2.6 to 2.3 rebooted 2 times all was working.
Then I just saved pppoe iface and now only pfsense can talk ipv6 hosts not.

Your PPPoE configuration looks correct, assuming your ISP uses a similar configuration to mine (WAN IPv6 address allocated via SLAAC, static address allocation for local networks but you have to delegate the prefix from the ISP to install a route to that prefix) and you are allocating static IPv6 prefixes to your local networks from the correct prefix.

If this is what you are trying to do, you will need to enable Router Advertisements on your local networks unless you are installing a static route on each machine.

What is unclear is whether dhcp6c is running and, if so, what it is doing.

Can you run the four shell commands I introduced and explained earlier in this thread (either using SSH or Diagnostics -> Command Prompt), copying and pasting the results (as text) into a private message to me. These commands are:
clog /var/log/ppp.log | grep -A 1 -E -e 'IPV6CP: LayerUp' | tail -n 2
ifconfig pppoe0 inet6 | grep -E -e '( fe80::|nd6)'
ps -auwwx | grep -E -e '(dhcp6c|rtsold)'
clog /var/log/dhcpd.log | grep dhcp6c | tail -n 40

If you get no output from the second command, the interface might be called pppoe rather than pppoe0.

It would also help if you save your configuration, open it in a text editor and include the section between <interfaces>and</interfaces> in your private message. This section will be fairly near the top of the file. That's the most concise and accurate way to let me see your full interface settings. The <dhcpdv6>to</dhcpdv6> section would also be useful - this contains the DHCPv6 server and Router Advertisement settings.

maverick_slo

I found the bug and it`s actually old one :) But upgraded :)

This is it: https://forum.pfsense.org/index.php?topic=90699.msg501975#msg501975

GUI generates WRONG .conf file.

I used this:

interface pppoe0 {
 send ia-pd 0; # request prefix delegation
 request domain-name-servers;
 request domain-name;
 script "/var/etc/dhcp6c_opt2_script.sh"; # we'd like some nameservers please
};
id-assoc pd 0 {
};

And it`s working great now.

Gui generated this (WHICH IS GREAT BUT SEE BELOW)

interface pppoe0 {
 send ia-pd 0; # request prefix delegation
 request domain-name-servers;
 request domain-name;
 script "/var/etc/dhcp6c_opt2_script.sh"; # we'd like some nameservers please
};
id-assoc pd 0 {
};

After I click APPLY CHANGES on pppoe interface this OK conf dissapears and few seconds later newly generated config appears (below one).


interface pppoe0 {
	request domain-name-servers;
	request domain-name;
	script "/var/etc/dhcp6c_opt2_script.sh"; # we'd like some nameservers please
};

So GUI generates good config but apply button messes it up completley.
Just a heads up guys!

jimp

Can you try this in 2.3 and see if it happens there?

maverick_slo

It happens only on 2.3

David_W

@maverick_slo:

I found the bug and it`s actually old one :) But upgraded :)

This is it: https://forum.pfsense.org/index.php?topic=90699.msg501975#msg501975

GUI generates WRONG .conf file.

Good catch!

It would be worth comparing the entries in the relevant part of the <interfaces>to</interfaces> block of your configuration between the broken and working scenarios.

I'm unclear whether this was ever fixed in 2.2.x.

jimp

Ah, OK. My fault for not looking back more in the thread – the thread title is still 2.2.5.

Start a fresh thread in the 2.3 board for this, and open a ticket on redmine.pfsense.org

maverick_slo

Already started it, Redmine later…

David_W

@jimp:

Ah, OK. My fault for not looking back more in the thread – the thread title is still 2.2.5.

As I noted in the 2.3 board earlier today, the issues discussed in this thread relate to both 2.2.5/2.2.6 and 2.3. I'm not the original poster, so I can't change the thread title.

@jimp:

Start a fresh thread in the 2.3 board for this, and open a ticket on redmine.pfsense.org

I'll leave that to maverick_slo - though there is already a post in the 2.3 board.

Hopefully fixing the bug maverick_slo has found will help in the process of validating my fixes for the two issues discussed in this thread, so that I can get on with submitting redmine bugs for those issues and pull requests for the fixes.