1. Home
  2. pfSense® Software
  3. IPv6
Log in to post
Load new posts
  • S

    ICMPv6 on tunnel interface gets blocked regardless of firewall rules

    10
    0 Votes
    10 Posts
    3k Views
    D
    Goes nowhere. From my POV, blocking ICMP is a pretty useless and as far as IPv6 goes, also completely broken idea. So, we'll agree to disagree.
  • I

    Question regarding NPT

    7
    0 Votes
    7 Posts
    4k Views
    I
    I talked to CMB a few weeks ago and he probably will consider NAT66… There really are use cases for NAT66. As i told earlier especiallay if you have to use ISP hardware that cannot be changed, doesn't get reconfigured, too small delegated prefix etc... Thanks for the bridging Firewall info, that could be of help. Didn't think of that :-) Allthough NAT is bad in general it wouldn't be too hard to implement it in pfSense; PF supports NAT66 and it would only require small change to the GUI. There has been even code for the pfSense GUI https://github.com/pfsense/pfsense/pull/427   <- even discussed on the forum here…
  • F

    Problems setting up native IPv6 on German Provider QSC

    4
    0 Votes
    4 Posts
    2k Views
    F
    We are in talks with QSC. They will setup correct Prefix Delegation, so that we hopefully have autoconfiguration pwith pfsense.
  • V

    V6 troubles

    4
    0 Votes
    4 Posts
    4k Views
    D
    +1 on that, need a tunnel iface for that with WAN as parent, not ethernet. The howto should get you started pretty quickly.
  • P

    IPv6 only for DMZ0 and DMZ1

    5
    0 Votes
    5 Posts
    2k Views
    T
    IPV6LAN Use the HE client IPv6 address as the interface IPv6 address IPV6DMZ You’re going to type your HE client IPv6 address into the IPv6 address box. And if not what kind of IPv6 adrdress I should use :) instead of the one in the manual? Kind regards Simon
  • ?

    Ipv6 2.1-RC0 (i386)

    6
    0 Votes
    6 Posts
    3k Views
    D
    I don't use snort for anything; not worth the myriad of false positives.
  • T

    IPv6 Problem

    2
    0 Votes
    2 Posts
    1k Views
    D
    No, you don't need any second range from another tunnel broker. Please, read the howto more carefully, it works perfectly fine.
  • M

    IPv6 setup without an tunnelbroker

    2
    0 Votes
    2 Posts
    2k Views
    D
    Use 2.1RC snapshots. P.S. You need at least /64 to get usable IPv6 on a router (one network); /56 or better for multiple subnets. /128 is definitely useless (very much doubt it's the case anyway).
  • F

    RFC 2136 DynDNS and IPv6

    Locked
    9
    0 Votes
    9 Posts
    5k Views
    jimpJ
    Resurrecting an old thread because I recently got around to setting up RFC2136 in bind and I can confirm that the IPv6 patch works, so I used a variant of it and it'll be in 2.1.
  • P

    DHCPv6 Leases need 100% CPU

    3
    0 Votes
    3 Posts
    2k Views
    P
    that's it: I deleted dhcpd6.leases  and dhcpd6.leases~ in /var/dhcpd/var/db solved
  • P

    PfSense LAN/WAN interface changes for DHCPv6-PD from 2.1 DEV to 2.1 RC0

    3
    0 Votes
    3 Posts
    7k Views
    R
    That said, there are still some issues being sorted out with DHCP-PD; see this thread in the 2.1 snapshot section.
  • F

    Help with native ipv6

    2
    0 Votes
    2 Posts
    2k Views
    F
    According to this article: http://www.zw3b.fr/linux/reseaux/ipv6-derriere-une-freebox-routeur-linux My ISP (Free), send a /64 prefix, which does not allow to have sub-networks. So one of the solution is to create a bridge between LAN and WAN. with: ebtables -t broute -A BROUTING -p ! ipv6 -j DROP brctl addbr br0 ifconfig br0 up brctl addif br0 eth0 brctl addif br0 eth1 I have created a bridge in >Interfaces > Bridge BRIDGE0 : WAN, LAN But what else now? what ipv6 should be assigned to OPT1 (BRIDGE0) and WAN?
  • O

    Pfsense edpnet (belgium) native ipv6

    Locked
    7
    0 Votes
    7 Posts
    4k Views
    O
    I'll give it a shot for sure. Thank you for your efforts.
  • V

    Native IPv6 on 2 interfaces

    Locked
    2
    0 Votes
    2 Posts
    2k Views
    D
    If you have native IPv6 on 2 wan interfaces you will have to resort to NPt for now. There is no real other solution yet, except getting BGP. Which I can recommend but is likely outside the budget.
  • D

    OpenBGPd IPv4 + IPv6

    Locked
    4
    0 Votes
    4 Posts
    5k Views
    D
    Yeah, it does work with both Protocols "as is"
  • D

    IPv6 link-local next-hop

    Locked
    12
    0 Votes
    12 Posts
    6k Views
    rbgargaR
    @Michael: And at the beginning of the string, not anywhere. if(! preg_match("/^fe80:/i", $_POST['gateway'])) { Fixed, thanks!
  • I

    Basic understanding question

    Locked
    4
    0 Votes
    4 Posts
    3k Views
    jimpJ
    Yes.
  • J

    Router Advertisement

    Locked
    6
    0 Votes
    6 Posts
    3k Views
    J
    Phew, the solution was hard to find. I have a MAC based VLAN membership configured on a switch port for the DMZ VLAN. This MAC based VLANs are built with untagged member ports. The advertisement was sent to ff02::1 over this port and reached all clients behind not only the VLAN members. Alex
  • B

    Stuck with IPv6 configuration

    Locked
    2
    0 Votes
    2 Posts
    2k Views
    jimpJ
    You should have been given two subnets. One, a /64 or smaller between you and your ISP for routing/interconnect. Second, your /48 should be routed to your WAN-side CARP VIP. Only then can you use addresses from any section of the /48 on your LAN.
  • D

    Track interface seems not to work

    Locked
    5
    0 Votes
    5 Posts
    5k Views
    D
    Runs fine, but clients do not get any ipv6 related setting. Even track interface seems not to work anymore since my LAN interface also has no ipv6 anymore, without changing anything on pfSense! Seems the whole ipv6 support is extremely buggy on Fritzbox or pfSense side. Even better as I just recognize: As long as mein LAN interface has a IPv6 adress, pfSense will hardcrash from time to time. I already sent 3 crash reports. The funny thing: if the interface does not get a IPv6 adress, there will be no crash. Hopefully some dev is able to trace that down with the debug logs uploaded… Dan
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.