IPv6 testing

dreamslacker

I always felt that I live in a socialist republic anyway. Authoritarian Democracy would be more apt a term. All citizens here are equal, some more-so than others. ;)

I can only pull that off because the RSP is tiny enough. Their noc is less than 10 men strong and I do get contacted by them on and off for networking jobs anyway (infrastructure cabling, tracing and labelling network cables etc.).

I wouldn't quite say I get perks but they at least know I'm not an average network idiot so they can trust me. e.g. I can request for full access to the CPE they deploy or get PPTP access to their routing core with my own router. Stuff that most ISPs and RSPs wouldn't even allow a business customer to do, much less a residential user.

Alright, I think we've veered off the topic too much. In any case at all, I think the guys have done a good job on pfsense. cheers! If some form of ipv6 gets done by june next year, then I'll only need to deploy a single box.
If it doesn't, I'll try and convince the RSP to internally 1:1 NAT the ipv6 into a ipv4 subnet within their core routing and I'll PPTP in to get those ipv4 as my "wan" ip's block.

kronso

That's a cool thing to have.

Speaking in terms of economics, price is determined by supply and demand.

I notice that the supply of IPv4 addresses is running out.

Does anyone else think that the price of IPv4 addresses might go up next year? Am I way off on that?

Wondering if now is a good time to buy.

Thanks

databeestje

Nah, what you will see is that large internet providers will start taking back those public IP ranges for customers, which will break their skype etc by putting 100's of customers on a single IPv4 address via a large scale nat.

There will be premium customers which will get the advantage of a public ipv4 address, it's that or called a business subscription.

For the next 5 years we'll see more and different extortion schemes. I woulnd't even be surprised if they start billing extra for getting a ipv6 address which is just nonsense since tunnel services are already free.

A great example here is KPN in the Netherlands, the CPE is locked down, they have a few hundred thousand connections, the old devices don't support ipv6 and the new CPE devices still don't. Worse even the NAT in the current CPE they deploy is bad enough that even VPN software doesn't work (pptp and ipsec). As you can imagine, if the local NAT device doesn't even work, then the reason to believe that a LSN will work at all is futile.

One must not forget that the LSN does not start at the provider edge, but it already starts at the customer edge. We will no doubt see horrid rfc1918 address colissions with vpn connections. They will likely argue the requirements for a business connection.

The great thing of all this is that they still are not providing native or tunnel ipv6 access. The CPE currently does not have a way to forward protocol 41. And even then. You can't ask for port mapping on a LSN to your private WAN ip and then port forward that on the CPE to the box connected to your LAN.

The reason why NAT is less of a pain as it really should be is that things like uPNP exist. Not the brightest implementation, but atleast you get to punch holes through the NAT to effectively start communication. e.g. the end to end connectivity.
A LSN has no such controls, good luck.

Welcome to the world of nat444 or nat 464, we're &&(* either way.

In other news, static routing now works, I managed to add a carp vip and made some more fixes with regards to dhcpd and route advertising. Much work left, but atleast I can already internet without issue at home on dual stack.

sullrich

Impressive!

databeestje

I've made a short writeup of how you can get the IPv6 tunnel with HE.net configured on my experimental code branch.
http://iserv.nl/files/pfsense/ipv6/

This should help people get started.

m4rcu5

Nice writeup!

But i am unsure if i want to upgrade to a branch. This will make updating even harder.

Is there a way to do this with the normal 2.0Beta4 but maybe only from the console instead of the webinterface?
I am trying to get my sixxs tunnel to work for months now, and after modifying the script found here: http://tuts4tech.net/2010/07/18/ipv6-tunnel-on-pfsense/ i could ping the outside world from my pfsense machine. But the outside world could not ping me.
The first step i want to do is set up the tunnel and later on route a subnet over it.

-m4rcu5

databeestje

all the settings are saved in the config, I am also keeping my git branch uptodate with mainstream, except for the binary platform ofcourse.

If you do use the autoupdate from the UI you can then gitsync my branch over it and all the ipv6 access, addresses, tunnels and settings will be restored, possibly with a reboot. Not too sure on that.

With my branch you can add proper ipv6 rules on the WAN interface so that it can be reached from the internet. Welcome to the stateful firewall. For example add a icmp rule on the wan interface to allow icmp from any to the LAN subnet. Make sure to toggle the ipv6 protocol setting.

Accounts

databeestje, big thanks to the HE.net write up got me going fast and easy.

m4rcu5

@databeestje:

all the settings are saved in the config, I am also keeping my git branch uptodate with mainstream, except for the binary platform ofcourse.

If you do use the autoupdate from the UI you can then gitsync my branch over it and all the ipv6 access, addresses, tunnels and settings will be restored, possibly with a reboot. Not too sure on that.

With my branch you can add proper ipv6 rules on the WAN interface so that it can be reached from the internet. Welcome to the stateful firewall. For example add a icmp rule on the wan interface to allow icmp from any to the LAN subnet. Make sure to toggle the ipv6 protocol setting.

I just did a gitsync and followed you guide.

Unfortunately i only can get IPv6 traffic from the router itself to work.
I set up the gif tunnel IF, created a extra interface "WAN01_IPv6" and gave it my endpoint IPv6 ip /128. Now i was able to ping6 ipv6.google.com from the pfsense box.
But whatever rule i try, i cannot seem to be able to ping myself from the outside world. (tried form an ipv6 enabled machine at work and lg.he.net). Did i miss something?

I did add a ipv6 ip to the lan interface as i do not have a subnet yet.

Could you give me some pointers at what exact rules i would need to create? Adding allow ICMP IPv6 from any to any on WAN01 or WAN01_IPv6 did not work.

Thx!
-m4rcu5

EDIT: i must also note that the SixXS.net gateway does not show up green, but as gathering data on my homescreen.

databeestje

do note that the routed/64 of he.net has 1 character different. In my cas the use 1f14 for the tunnel network and 1f15 for the routed /64.

You can not just assign a random IP of the tunnel network on the lan side, that won't work.

That is one of the biggest mind set changes, it's routing now so the lan range needs to be routed your way. Previously with nat you always used that one external ip.

databeestje

Update:

It is possible to create a CARP ipv6 interface, carp syncing to the IPv6 address of the backup works too.
When using the easy firewall rule widget it will default to IPv4 protocol causing a filter rule error, editing the rule and setting the protocol to ipv6 fixes it.
The webUI can now listen on IPv6 too
It is currently not possible to configure the IPv6 interfaces from the cli.
The DHCP server still doesn't work properly, autoconfig for the LAN does work but nameservers need to be configured manually.
The DHCP server does not support failover pools with IPv6.

Be careful of creating any any rules on the WAN when using a routing config (e.g. IPv6)!

GrandmasterB

Great work!

@databeestje:

Update:

It is possible to create a CARP ipv6 interface, carp syncing to the IPv6 address of the backup works too.

When using the easy firewall rule widget it will default to IPv4 protocol causing a filter rule error, editing the rule and setting the protocol to ipv6 fixes it.

The webUI can now listen on IPv6 too

It is currently not possible to configure the IPv6 interfaces from the cli.

The DHCP server still doesn't work properly, autoconfig for the LAN does work but nameservers need to be configured manually.

The DHCP server does not support failover pools with IPv6.

Be careful of creating any any rules on the WAN when using a routing config (e.g. IPv6)!

wallabybob

I've been try to do some IPv6 testing. I upgraded firmware to```

[2.0-BETA4][admin@vb-pfsense.example.org]/root(3): uname -a
FreeBSD vb-pfsense.example.org 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #1: Wed Nov 17 10:32:05 EST 2010 sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 i386


I then attempted to work through the "gitsync" procedure described earlier in this topic. Then the webGUI refused  to start: (extract from _# clog /var/log/system.log _)

Nov 24 12:39:51 vb-pfsense php: : The command '/usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf' returned exit code '255', the output was '2010-11-24 12:39:27: (network.c.290) gethostbyname failed: 2 ::'


The gitsync procedure I attempted appeared to go wrong:

> Welcome to the pfSense php shell system
> Written by Scott Ullrich (sullrich@gmail.com)
> 
> Type "help" to show common usage scenarios.
> 
> Available playback commands:
>     disabledhcpd enableallowallwan enablesshd gitsync removepkgconfig restartdhcpd restartipsec
> 
> pfSense shell: playback gitsync
> 
> Playback of file gitsync started.
> 
> Current repository is http://gitweb.pfsense.org/pfsense/pfSense-smos.git
> 
> Please select which branch you would like to sync against:
> 
> master 2.0 development branch
> RELENG_1_2 1.2* release branch
> build_commit The commit originally used to build the image
> 
> Or alternatively you may enter a custom RCS branch URL (HTTP).
> 
> **> http://gitweb.pfsense.org/pfsense/pfSense-smos.git**
> 
> NOTE: http://gitweb.pfsense.org/pfsense/pfSense-smos.git was not found.
> 
> Is this a custom GIT URL? [y]?

The example at [http://iserv.nl/files/pfsense/ipv6/](http://iserv.nl/files/pfsense/ipv6/) goes only as far as the bold line above so I'm not sure what to answer to the following questions nor if _NOTE: http://gitweb.pfsense.org/pfsense/pfSense-smos.git was not found._ is a serious problem.

The failure of the web GUI after this point makes the configuration of the IPv6 tunnel something of a challenge.

Is there a quick patch I can make (to define an IPv6 local hostname?) or a particular snapshot build known to work?__

danne

@wallabybob:

The failure of the web GUI after this point makes the configuration of the IPv6 tunnel something of a challenge.

Is there a quick patch I can make (to define an IPv6 local hostname?) or a particular snapshot build known to work?

Theres some IPv6 stuff in /var/etc/lighty-webConfigurator.conf around line 128, if you remove that the web-UI will start.

danne

Is there anything I can do to help? Have you defined the tasks to complete for IPv6 support?

wallabybob

@danne:

@wallabybob:

The failure of the web GUI after this point makes the configuration of the IPv6 tunnel something of a challenge.

Is there a quick patch I can make (to define an IPv6 local hostname?) or a particular snapshot build known to work?

Theres some IPv6 stuff in /var/etc/lighty-webConfigurator.conf around line 128, if you remove that the web-UI will start.

For anyone else who might stumble upon this problem:
After changing /var/etc/lighty-webConfigurator.conf the web server needs to be restarted by /usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf

Restarting the system (or web configurator from the console menu) erases changes to /var/etc/lighty-webConfigurator.conf

ariel

What can be done to make those changes permanent ?

FisherKing

This solution might have some negative side effects, but you could set the file so that it is read-only.

chmod 444 /var/etc/lighty-webConfigurator.conf

I see the potential for this to prevent other (good/necessary) changes from pfSense though.

databeestje

it appears that both apinger and lighttpd are still not built with ipv6 support which is causing this issue.
I will investigate.

I will investigate the options

Inferno

Just a notice I got it all to work with my HE net tunnel

Excellent work! (Top gedaan ;) )