Feature #1831

Captive portal IPv6 support

Added by Chris Buechler about 7 years ago. Updated 3 months ago.

Captive Portal
Target version:
Start date:
Due date:
% Done:


Estimated time:


Captive portal needs IPv6 support. ipfw fwd doesn't function with IPv6 last I heard, amongst other things that need work here for v6. (42.3 KB) Cyrill B, 12/31/2012 08:59 AM (46.3 KB) Cyrill B, 12/31/2012 09:24 AM


#1 Updated by Thomas NOEL about 7 years ago


I'm very interrested by this topic (IPv6 for CP). Do you have any plan or any schedule for this development ? If your team is ready to work on this, is a targeted donation is possible (and does it help) ?

#2 Updated by Chris Buechler about 7 years ago

this is, like everything with IPv6, targeted for 2.1. This is likely the single most complex and time consuming piece (actually several pieces directly related to this) of anything outstanding with IPv6. We're seeking donations for IPv6 work in general, and specifically if you could put something towards this that would be very helpful. Please email me to discuss details - cmb at pfsense dot org.

#3 Updated by Ermal Luçi about 7 years ago

For CP on IPv6 to work ipfw tables need to be tought about v6 addresses and
ipfw forward at layer2 needs to be coded for v6.

#4 Updated by Chris Buechler over 6 years ago

  • Target version changed from 2.1 to 2.2

there is a lot involved here, people will expect to auth both v4 and v6 IPs in a single shot which complicates everything. Our HSIA customers have indicated it's not an important feature in the immediate (or even foreseeable in some cases) future, and we're on too tight a schedule for 2.1 to get this done by then, so pushing to 2.2.

#5 Updated by Cyrill B almost 6 years ago

  • File 0001-MFC-r232865-r232868-and-r233478.patch added

MFC r232865, r232868 and r233478 added ipfw support for IPv6 tables in stable. To apply the changes the CaptivePortal multi instance patch (CP_multi_instance_ipfw.diff) may also require a few changes.

#6 Updated by Cyrill B almost 6 years ago

... and CP_speedup.diff also.

#7 Updated by Ermal Luçi almost 6 years ago

I think ipv6 fwd support on ipfw is not on 8.3, though i might be wrong!
And you forgot to attach as well.

As usual github pull requests are better in general :)

#8 Updated by Cyrill B almost 6 years ago

  • File CP_speedup.diff added

Yes, I believe there are only partial patches available for ipv6 fwd support for stable/8 such as
I didn't yet put any patches on github as they cannot be applied individually and they would break the current implementation.

So those modifications / patches are just tiny steps until full support. For now I have also modified and attached the CP_speedup.diff to support IPv6. The patch applies after the above 0001-MFC-r232865-r232868-and-r233478.patch (IPv6 tables support) which by the way applies to 8.3 release.

Before any of those patches can be included at least the context switching (CP_multi_instance_ipfw.diff) will have to be migrated and there are also changes required to the pfSense php module (or the ipfw binary will have to be used again). And of course to make everything work ipv6 fwd support will be needed.

#9 Updated by Cyrill B almost 6 years ago

I'll just add this here so that it doesn't get lost:
Add IPv6 support to 'pfSense_ip_to_mac' function

#10 Updated by Cyrill B almost 6 years ago

  • File php53-pfSense-module.patch added
  • File filterdns.patch added

Those patches make the required changes to the php53-pfSense-module and the filterdns ports.

#11 Updated by Cyrill B almost 6 years ago

  • File cp_ipv6.png added

IPv6 here we are! There's still some cleanup to be done but other than that it is working.

Still todo:
- add ipv6 to the default ipfw rules
- captiveportal php code needs some adjustments (e.g. 32bit netmask)

#12 Updated by Cyrill B almost 6 years ago

I assume there won't be any major changes anymore to 2.1 thus this feature will be integrated in 2.2? So I can either upload the patches here in a zip file or on github and create a pull request. What do you prefer?

I could also provide a working iso if someone wants to test it.
Maybe an admin can also cleanup my mess here and remove the files that I have previously attached, some of them required further modifications.

#13 Updated by Chris Buechler almost 6 years ago

Go ahead and attach it here for now, though that will almost certainly require some updating to merge cleanly post-2.1, we don't want any v6 CP in 2.1. This likely will require a lot of work to be usable in real world scenarios for a variety of reasons and that's not something we can support for 2.1. I'll remove the files attached to this point.

#14 Updated by Chris Buechler almost 6 years ago

  • File deleted (0001-MFC-r232865-r232868-and-r233478.patch)

#15 Updated by Chris Buechler almost 6 years ago

  • File deleted (CP_speedup.diff)

#16 Updated by Chris Buechler almost 6 years ago

  • File deleted (php53-pfSense-module.patch)

#17 Updated by Chris Buechler almost 6 years ago

  • File deleted (filterdns.patch)

#18 Updated by Chris Buechler almost 6 years ago

  • File deleted (cp_ipv6.png)

#19 Updated by Cyrill B almost 6 years ago

Attached is the zip file with the required patches. All files except for the patch, which applies to the pfsense repository, are part of the pfsense-tools repository. Patches apply to the FreeBSD 8.3 sources and code in the master branch as of 2012-12-31.

If you just want to take a look at the code you can also do so on github on the ipv6_cp branch in my (pfsense) [1] and (pfsense-tools) [2] repositories. I also made an iso [3] for anyone that wants to do early testing of the IPv6 capability.

I only tested a few Captive Portal use cases (e.g no radius) which seemed to work quite nicely, however there are still a few remaining issues which include:
  • User needs to login / logout for IPv4 and IPv6 addresses
  • The ipfw filter rules allow communication between IPv6 link-local addresses
  • Captive Portal Settings GUI is not yet fully IPv6 compatible (e.g. only accepts IPv4 addresses under "Allowed IP Addresses")


#20 Updated by Cyrill B almost 6 years ago

The required pfPorts patches were missing in the above archive.

#21 Updated by Thomas B over 5 years ago

Great work, and Thanks Cyrill.

Unfortunately I found another bug in the code, while setting up the CP for v6 in my network.
Since I'm using a central RADIUS authentication, there is an error shown while going through the captive portal.

There is a response on from the pfsense appliance, which says "Fatal Error: Error in converting address in /etc/inc/ on line 210"

I'm running the setup with a virtual machine.

Hopefully we can fix that somehow?

Best wishes,

Thomas from Munich

#22 Updated by Chris Buechler over 4 years ago

  • Target version changed from 2.2 to Future

#23 Updated by Martin Gollowitzer about 3 years ago


I just stumbled over this ticket after trying to find the reason for IPv6 not working in my guest WiFi. Since IPv6 is becoming more and more important (my ISP has started to switch customers to DS-Lite already), I think this feature would really be a big step towards better IPv6 adoption. I am willing to even through a little bit of money towards anyone who gets this included in one of the upcoming versions. Unfortunately, I am not a developer myself, but I can of course help with testing (and reading code, which is by far easier than writing). Please let me know what else I can do.


#24 Updated by Klaus Steinberger about 2 years ago


I think this is an important issue, I would like to see it as early as possible in pfsense, as IPV6 is an important protocol at our site.

#25 Updated by James Webb 11 months ago

With the growing demand for IPv6 it is essential that this feature is implemented ASAP.
Do we have a timeline on when this would be completed?

#26 Updated by Brandon Jackson 3 months ago

Bump. Its 2018, how is this still a thing.

Also available in: Atom PDF