IPv6 testing

Supermule

No I only use the "official" releases….no gitsync :D

MrKoen

Well that explains it then :) I must say it's incredibly stable to use the github updates. Only every now and then there's a typo somewhere which kills your whole pfSense box. That sucks bigtime.. but that's the risk of using alpha software. If you grab the current release, its stable, correct and provides you with DHCPv6 reservations :)

ludditetechnologies

Nice work on 2 everyone, looking pretty flash :)

I cant get IPV6 traffic out, gateway says it is ok:

HE_NET 2001:470:c:2f5::1 2001:470:c:2f5::1 Online HE.net Gateway

get this in log

php: : Could not find IPv6 gateway for interface(wan).

this under routing

HE_NET (default) WANIPV6 2001:470:c:2f5::1 2001:470:c:2f5::1 HE.net Gateway

Anyone have a clue about this?

Thanks.

(edit:
Version info 2.0-RC2-IPv6 (i386)
built on Sat Feb 26 16:00:14 EST 2011)

databeestje

gateway support is not complete yet, the filter rules are not address family aware yet.

If you try to set a v4 gateway on a v6 rule that will result in a rules error.

If no gateway is defined it will try to lookup a gateway for "wan" which doesn't have a v6 gateway and is returning this result in logfile.

pfsense_fan009

Could you also make an rc3 4G nanobsd ipv6 release?

pfsense_fan009

@pfsense_fan009:

Could you also make an rc3 4G nanobsd ipv6 release?

any plans for the future ?

Cino

I gitsync this morning and after reboot, my packages dont auto-start. I get this error:

Parse error: syntax error, unexpected T_STRING in /etc/inc/pkg-utils.inc on line 550

currently running 2.0-RC3-IPv6 (i386) built on Fri Jul 8 19:24:31 EDT 2011. Do i need to update my snapshot?

cmb

@Cino:

I gitsync this morning and after reboot, my packages dont auto-start. I get this error:

Parse error: syntax error, unexpected T_STRING in /etc/inc/pkg-utils.inc on line 550

currently running 2.0-RC3-IPv6 (i386) built on Fri Jul 8 19:24:31 EDT 2011. Do i need to update my snapshot?

This is fixed.
https://github.com/bsdperimeter/pfsense/commit/0b07c7636f583ad39d9ea31ea7fc322554607496

if you're gitsyncing from master (which now has the IPv6 code merged and is now 2.1) and not Seth's branch, you'll have that if you gitsync again. Or can just manually fix that one line

singerie

what should we put in the repository url ?

currently it's git://github.com/smos/pfsense-ipv6.git

Cino

That is good news to hear!!

I went ahead and deleted the /root/pfsense folder so it would point me back to the main code, git://github.com/bsdperimeter/pfsense.git
. then gitsync

After the system reboot I noticed 2 new errors:

Warning: Unexpected character in input: "" (ASCII=92) state=1 in /etc/inc/pkg-utils.inc on line 556

Parse error: syntax error, unexpected '"' in etec/inc/pkg-utils.inc on line 556

tebeve

@singerie:

what should we put in the repository url ?

currently it's git://github.com/smos/pfsense-ipv6.git

oops, sorry, didn't see this when I posted HERE asking the same thing.

looks like the answer is yes tho, it should be:
git://github.com/bsdperimeter/pfsense.git
now

iFloris

@Cino:

After the system reboot I noticed 2 new errors:

Warning: Unexpected character in input: "" (ASCII=92) state=1 in /etc/inc/pkg-utils.inc on line 556

Parse error: syntax error, unexpected '"' in etec/inc/pkg-utils.inc on line 556

That's due to a missing " in line 556, you can fix that by adding a " before the \n" so that it looks like this:```
pkg_debug(gettext("ERROR! Unable to fetch package configuration file. Aborting installation.") . "\n");

Cino

@iFloris:

@Cino:

After the system reboot I noticed 2 new errors:

Warning: Unexpected character in input: "" (ASCII=92) state=1 in /etc/inc/pkg-utils.inc on line 556

Parse error: syntax error, unexpected '"' in etec/inc/pkg-utils.inc on line 556

That's due to a missing " in line 556, you can fix that by adding a " before the \n" so that it looks like this:```
pkg_debug(gettext("ERROR! Unable to fetch package configuration file. Aborting installation.") . "\n");

Thanks iFloris! I didn't have a chance to look at the file before I posted but wanted to let the devs now so it can be fix in the code.

johnpoz

Ok just to be clear, maybe the last commit fixed error on line 550? But 556 is still broke.

I just changed over the new branch, and change git sync url, etc.

Did an update too
2.1-DEVELOPMENT (i386)
built on Thu Jul 14 01:23:35 EDT 2011

Even ran a manual gitsync, and still was getting error had to manually go in and add the " on this line
pkg_debug(gettext("ERROR! Unable to fetch package configuration file. Aborting installation.") . "\n");

in /etc/inc/pkg-utils.inc

cmb

@johnpoz:

Ok just to be clear, maybe the last commit fixed error on line 550? But 556 is still broke.

I just changed over the new branch, and change git sync url, etc.

Did an update too
2.1-DEVELOPMENT (i386)
built on Thu Jul 14 01:23:35 EDT 2011

Even ran a manual gitsync, and still was getting error had to manually go in and add the " on this line
pkg_debug(gettext("ERROR! Unable to fetch package configuration file. Aborting installation.") . "\n");

in /etc/inc/pkg-utils.inc

Jim fixed that one today.

Cino

My HE tunnel wont up after a gitsync/reboot today.

Looking at the changes, I believe this change: https://github.com/bsdperimeter/pfsense/commit/87f0f42c3230ad7ad15b14a8a9d63c58f8b2e379 is the cause. When i hand-type the code back in that was removed and reboot; my interface comes up.

johnpoz

I just did a gitsync, and got the latest commits - the one your talking about, and rebooted and my HE tunnel came up no problems.

Now it was odd before the reboot after the gitsync I was seeing a crash error on the UI that would not seem to go away. Odd, it had no details in it, close it, send it and it would just pop back up.

But everything seems to be working currently

Cino

@johnpoz:

I just did a gitsync, and got the latest commits - the one your talking about, and rebooted and my HE tunnel came up no problems.

Now it was odd before the reboot after the gitsync I was seeing a crash error on the UI that would not seem to go away. Odd, it had no details in it, close it, send it and it would just pop back up.

But everything seems to be working currently

Is your subnet mask 64bits or 128bits for your tunnel? Mines 64-bit

I was able to get it to work after clicking save/apply under the interface configuration page. IPv6 code has had a similar issue a couple of months ago to where we had to manually add a route or click save/apply..

see post http://forum.pfsense.org/index.php/topic,32721.msg179781/topicseen.html#msg179781

JoelC707

I'm having to do the same save/apply business. To make matters worse my DSL was in and out all day yesterday and it was leaving the tunnel down every time the DSL came back up. Talk about annoying having to go in and do that every few minutes lol. I finally gave up on it and surfed from bed with my phone lol. Grrrr, seems to be doing it again. In any case my tunnel is a /64. IIRC the direction say to do /128 or /120 but my tunnel wouldn't come up with that config. Since HE's site says /64 for the tunnel I figured it should be /64 on my end as well (same logic as different subnets on a LAN, they won't always talk to each other).

johnpoz

Mine is /128 There was some issues with that a while back. You can bring it up /64 and then just change it to /128