I don't really get what went mad today on this configuration after 2.1.3 -> 2.1.4 upgrade but after a lot of suspicion on (too) many (correct) settings and finally re-assessing the initial configuration which worked fine on 2.1.3 *and* a final reboot (the clue?), it now is back alive and routing IPv6 as correctly as before.
So, G.B., as a synthesis: >> I am particularly interested in seeing if you have an IPv6 (other than link >> local) provided ? On its auto-configuration page EDPNET says these IPs are reserved for this fixed IP circuit: > IPv6 LAN prefix 2a02:578:XXXX::/48 > IPv6 WAN prefix 2a02:578:YYYY:ZZZZ::/64 Using the PPPOE for IPv4 WAN and DHCP6 for IPv6 WAN, I get: On the WAN interface status page: IPv6 Link Local fe80::f5a0:854e:1417:a510%pppoe0 IPv6 address fe80::215:17ff:fe16:18dc%em4 The gateway automatically defined is as this: WAN_DHCP6 (default) WAN fe80::207:7dff:fe56:5900 fe80::207:7dff:fe56:5900 Interface WAN_DHCP6 Gateway The start of the IPv6 routing table is like this: Destination Gateway Flags Refs Use Mtu Netif Expire default fe80::207:7dff:fe56:5900%pppoe0 UGS 0 3428 1492 pppoe0 ::1 ::1 UH 0 0 16384 lo0 2a02:578:XXXX:1::/64 link#1 U 0 319 1500 em0 2a02:578:XXXX:1::1 link#1 UHS 0 0 16384 lo0 2a02:578:XXXX:20::/64 link#2 U 0 0 1500 em1 2a02:578:XXXX:20::1 link#2 UHS 0 0 16384 lo0 2a02:578:YYYY:ZZZZ::/64 link#10 U 0 81 1492 pppoe0 2a02:578:YYYY:ZZZZ:f5a0:854e:1417:a510 link#10 UHS 0 0 16384 lo0 ... On the LAN interface, I use a /64 out of the /48 for LAN, and another one for OPT1. You can see that above. Yours, __ Olivier Mascia tipgroup.com/om > Le 9 juil. 2014 à 11:55, Olivier Mascia <o...@integral.be> a écrit : > > The NOT so funny thing is that following this discussion it came to my > attention that I was still running 2.1.3. > I upgraded to 2.1.4 this morning. > Nothing else changed in the configuration : packets do not route anymore > between IPv6 LAN and IPv6 WAN. > > pfsense can ping6 and traceroute6 anything else either WAN side or LAN side. > But LAN computers can not reach anything else outside (over IPv6). > > I will run some more tests and then will restore 2.1.3 to better check this. > >> I am particularly interested in seeing if you have an IPv6 (other than link >> local) provided ? > > You get a fe80: as WAN IP (I currently have fe80::215:17ff:fe16:18dc%em4) and > the gateway is currently fe80::207:7dff:fe56:5900%pppoe0. > This kind of setup has always worked until my 2.1.3->2.1.4 upgrade this > morning. > > :( > > __ > Olivier Mascia > tipgroup.com/om > >> Le 8 juil. 2014 à 19:49, b...@todoo.biz a écrit : >> >> One more question : >> >> Can you show me the output of your interface page ? >> I am particularly interested in seeing if you have an IPv6 (other than link >> local) provided ? >> >> And also can you show me the output of your routing table ? >> >> >> Sincerely yours. >> >> G.B. >> >> >> >> Le 7 juil. 2014 à 09:48, Olivier Mascia <o...@integral.be> a écrit : >> >>> I will assume your link is provided through VDSL2 as you mention Belgacom. >>> The next WAN setup works fine with a fixed-IP circuit provided by EDPNET, >>> who uses Belgacom VDSL2 network. >>> <PastedGraphic-1.png> >>> Assign (for instance) one /64 out of the /56 they provide you to the LAN (I >>> understand you did that). >>> >>> Regarding RA, I have to use these settings to best serve a LAN made of PCs >>> (mostly Windows, some Linux) and Macs. >>> In this configuration, neither pfsense DHCPv4 server nor pfsense DHCPv6 >>> server are used, those services are offered by other computers inside the >>> LAN. >>> I cut the print-screen before it, but don't forget to list your /64 LAN net >>> in the RA subnet(s) field (the third field). >>> >>> <PastedGraphic-2.png> >>> Hope it might help, >>> __ >>> Olivier Mascia >>> tipgroup.com/om >>> >>>> Le 6 juil. 2014 à 23:32, b...@todoo.biz a écrit : >>>> >>>> Hi, >>>> >>>> We are trying to debug an IPv6 link provided by Belgacom. >>>> >>>> >>>> We have our IPv6 through a PPPoE link, but instead of attributing our IPv6 >>>> to the default interface (WAN), the fixed IPv6 seems to end up on the lo0 >>>> interface ? >>>> >>>> I can ping6 google using the default route, but not through our LAN where >>>> I have configured one of the /64 block taken from the /56 provided by >>>> Belgacom. I have properly configured RA on the LAN with stateless >>>> autoconfig… still no luck ! >>>> >>>> >>>> Is there a bug somewhere or am I missing smthg ? >>>> >>>> >>>> Thanks. >>>> >>>> G.B. >>>> >>>> >>>> <Capture d’écran 2014-07-06 à 23.21.06.png> >>>> >>>> ________________________________________________ >>>> «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ >>>> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ >>>> BSD - BSD - BSD - BSD - BSD - BSD - BSD - BSD - >>>> ________________________________________________ >>>> «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ >>>> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ >>>> PGP ID --> 0x1BA3C2FD >>>> >>>> _______________________________________________ >>>> List mailing list >>>> List@lists.pfsense.org >>>> https://lists.pfsense.org/mailman/listinfo/list >>> >>> _______________________________________________ >>> List mailing list >>> List@lists.pfsense.org >>> https://lists.pfsense.org/mailman/listinfo/list >> >> ________________________________________________ >> «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ >> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ >> BSD - BSD - BSD - BSD - BSD - BSD - BSD - BSD - >> ________________________________________________ >> «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ >> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ >> PGP ID --> 0x1BA3C2FD >> >> _______________________________________________ >> List mailing list >> List@lists.pfsense.org >> https://lists.pfsense.org/mailman/listinfo/list > > > _______________________________________________ > List mailing list > List@lists.pfsense.org > https://lists.pfsense.org/mailman/listinfo/list _______________________________________________ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
