It was missing this:
https://github.com/bsdperimeter/pfsense/commit/9a03bc1905bfc124a3ada5cf55afc0a7ecd1c27c

I send the necessary information via PM, hope it arrived.

I have now tested to download the vpn.inc, ipsec.inc and diag_ipsec.php from github and replaced them in my pfSense.
So far it seems to have fixed both problems.  I will monitor this for a while to see that it keeps stable and report back
to you if I found any remaining problems related to this.  New faults will be opened in new threads for better visibility.

Thanks for fixing this.  This is still beta code so these kinds of things happens. :-)  (check my onelineer in my profile.  BEER  ;-)

//Danne

One of the two boxes doesn't have ANY IPv6 config or info so it wasn't that.

That said it is now working after updating to todays snap. Probably the default gateway issue. Even though I had a GW manually set it seems the updater was still broken until this was fixed :P

Found the missing "/" - https://github.com/bsdperimeter/pfsense/pull/401

Thanks, I guess I should have looked around before posting.  Would have saved me some time too.  Oh well, live and learn.

Yep, that did it.  I added the rows in the system.inc and rebooted and now the incoming seems to work.
It least for the incoming ICMPv6 Echos and replies.

I removed and snort-dev and installed snort but now I get /snort.rules(26) Undefined variable in the string: $EXTERNAL_NET.
Fatal Error, Quitting..

Looks better to me… merged it.

Thanks, I didn't want risk booting into a broken system, but it happily bootet back into the restored OS.

Agreedly the user feedback is not optimal at that point (none actually). It doesn't seem to be often used (which is a otherwise good sign of quality) ;-)
Lets see if someone remembers this or I'll make a ticket on redmine.

(I'll switch this over to the new thread I just started)

We had to make some emergency changes to files.pfsense.org recently and had to remove the AAAA in the process for complicated reasons, I'll get it back when time permits.

latest version should check all config files and startup on 2.1.

@ermal:

Which snapshot are you on?

this was one from 25th because the 30th had too much NAT problems for us.
I saw today that many fixes were done on last weekend… ;)

https://github.com/bsdperimeter/pfsense/commit/733829a9dbf5ea9d24cd9c3a42ee9fcc76051a2f
https://github.com/bsdperimeter/pfsense/commit/613a3cc56385481e65bba59850db01fa8d62d630
https://github.com/bsdperimeter/pfsense/commit/e017a46a994c693f9c05c8936c1a5585d7b3ae7c
https://github.com/bsdperimeter/pfsense/commit/18f338da58e4f98478bd4710b3f4907759cd9540

So I running now snapshot 7th Feb. 18:03 and the interface problems itself seems now solved. thx.

Thank you!

Thanks.  I will try to upgrade today…

I should have upgraded first  :)
The problem is fixed now:
2.1-BETA1 (i386) built on Thu Feb 7 18:00:57 EST 2013
by https://github.com/bsdperimeter/pfsense/commit/613a3cc56385481e65bba59850db01fa8d62d630

It will always stay up but as soon as there is traffic it will flow/re-establish.
Since there is gateway monitoring it mostly will stay even connected without disabling it.

It will be configured automagically behind the scenes.
For now it will stay like that.

With lots of changes it might flip somewhat and is not very managable but it is configured like this for now.