Client computers not get IPv6 from Pfsense, and not connect to Internet.



  • Hi every ones,

    I have pfsense 2.1, my WAN is IPv4 , i had following http://www.yourwarrantyisvoid.com/2011/12/01/networking-bringing-ipv6-into-your-network-using-pfsense/ to bring IPv6 into my network based on IPv4.
    I have successful creat tunnel Henet, and point to WAN. From pfsense i can ping another IPv6 as Ipv6.google.com sucssessful. 
    I also config DHCPv6&RA. and allow IPv6 rule from LAN throught  WAN.

    My problems is my computer as Win7, Win10 not get any IPv6 from on Pfsense, even i set static IP, cannot connect to internet.

    Please help me solved, i so appriciated. If you can, you teamviewer to my computer. Thanks
    You can contact to me on skype: huygau198288

    Best wish!



  • Hi,
    @huydq:

    I have pfsense 2.1, my WAN is IPv4 ,  …................

    STOP !
    2.1 has broken IPv6 support.
    => Problem solved ;)
    The solution has a name : upgrade.

    EDIT : Btw : a doc from 2011 ?
    What about an update one : https://doc.pfsense.org/index.php/Using_IPv6_with_a_Tunnel_Broker ?



  • There seams to be a bug with IPv6 in 2.3.4. After IP renewel clients won't get an IPv6 via RA. It works in  2.3.3 but also with some impacts to unbound starting every 15 min

    pfadmin



  • @pfadmin:

    …. After IP renewel clients won't get an IPv6 via RA.

    IP ? IPv4 or IPv6 (or both) ?

    Btw : my IPv4 is dynamic, but my IPv6 is a "he.net solution", so I consider it static.

    @pfadmin:

    It works in  2.3.3 but also with some impacts to unbound starting every 15 min

    unbound (local DNS resolver) restart is another issue.
    Much is said about that subject already - and one of the issues is that it restarts itself if a new DHCP lease comes in, and you instructed to "unbound" to include these in the "resolver table".
    Map all your fixed (LAN) devices as static DHCP leases and unbound will calm down.
    Leases from the DHCP pool shouldn't be handed over to unbound - because of their temporary presence (you don't need to access them anyway - they just visit to gain access to the net).



  • Both or IPv4 only. Deutsche Telekom breaks every 24h IPv4 Connection and gives a new IPv4 but not everytime a IPv6. In both situations IPv6 doesn't work after this event for lan Clients https://forum.pfsense.org/index.php?topic=130448.0  WAN seams to be ok.

    I turned of that DHCP devices register in unbound and it helps, but if IPv6 works, the renewel script lets start unbound at 00/15/30/45. But back to the topic, IPv6 doesn't work in 2.3.4 with Deutsche Telekom…

    know some patches for that?

    pfadmin