IPv6 code merged to mainline!
-
johnpoz, did you also do a reboot after the gitsync? That's where things go wrong here. Everything seems to be working: tunnel is up and active, but each ping results in no route to destination found. When I just do a gitsync and not reboot, it remains working.
-
Normally I do not reboot after a gitsync, but to make you happy I just did after reading your response
And working just fine
[2.1-DEVELOPMENT][root@pfsense.local.lan]/root(9): uptime
7:06AM up 2 mins, 2 users, load averages: 0.58, 0.45, 0.19[2.1-DEVELOPMENT][root@pfsense.local.lan]/root(11): ping6 ipv6.google.com
PING6(56=40+8+8 bytes) 2001:470:1f10:b85::2 –> 2607:f8b0:4001:c01::69
16 bytes from 2607:f8b0:4001:c01::69, icmp_seq=0 hlim=56 time=45.867 ms
16 bytes from 2607:f8b0:4001:c01::69, icmp_seq=1 hlim=56 time=46.064 ms
^C
--- ipv6.l.google.com ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 45.867/45.965/46.064/0.098 msipv6 gateway shows up, booted without errors, etc. etc..
Now I have seen those weird crash errors now and then after a gitsync, and can not make the thing go away on the web gui -- everything seems to be working. After a reboot those errors are gone, but this just happens every now and then. For example this last gitsync it did not happen.
-
Thanks for taking the time to try it johnpoz. All seems to work fine indeed, even with the crash message being displayed. I only regret not being able to update anymore since that breaks my IPv6. But I guess since all functionality I need is currently in pfSense, I'll stick with the current version. Maybe it's because my installation has been done over a year ago and has been dragged through many SMOS ipv6 updates already that some rock has fallen now. Maybe I'll try a reinstall with a recent image someday to see if that solves it. Thanks again for your help.
-
Just update to the latest 2.1 that jim has out, and do a gitsync – you shouldn't be sync to git://github.com/smos/pfsense-ipv6.git
-
Just did a clean install with the 2.1 ISO released today and all works fine again after restoring my config file! Even IPv6 works. Thx guys :)
-
Hi guys,
So what's the trick to getting "git" and such installed once you have updated to the latest 2.1 AMD64 development version?
The system tries to install "git" but it looks like it's trying to get the files from the "packages-8.1-release" branch of the ftp site which seems to have been removed. Any suggestions for what I should install?
-Will
-
http://doc.pfsense.org/index.php/Updating_pfSense_code_between_snapshots
Near the bottom… :)
-
I'll probably forget to post about it, but you can always just keep an eye on http://files.pfsense.org/jimp/ipv6/
I was just ready to start and planned to download but they are not there any more?
(is this because of the 2.0.1 release and do i have to be patient) -
files.pfsense.org is down, should be back sometime very soon.
-
Downloaded and running on developer now.
up to the next steps. :P -
At this point in time it is probably a better idea to use the current 2.1 BETA snapshots from the snapshots server.
I can not think of a reason why people would want to keep running the older FreeBSD 8.1 images.
-
When building a new pfSense server I usually take a recent ISO from snapshots.pfsense.org as well, but it always seems to be a lucky shot whether or not the latest build is stable enough for production use. I'm missing a stable though recent beta image download location like we used to have in the past on Jimp or iserv.nl which includes all the IPv6 goodness. Is there still such a site out there somewhere?
-
The snapshots are always the most stable ones. There may be 1-2 that have some brokenness here and there, but anything else gets stale rather quick.
-
^ so your quoting
http://www.ipv6now.com.au/primers/benefits.php
Why?? Your other post is gibberish as well. Thinking your going to start spamming some sort of nonsense as soon as you can post links?
-
^ so your quoting
http://www.ipv6now.com.au/primers/benefits.php
Why?? Your other post is gibberish as well. Thinking your going to start spamming some sort of nonsense as soon as you can post links?
Better to use the option to notify moderators so we know about them.
