It doesn't exist at all in 2.2.

Anybody else, who can help here ?

@cmb:

Yeah it's still building, should be done within a few minutes from the time of this post.

It's getting hard to tell the difference between the "crashing" I was experiencing and the newish problem with IPSEC tunnels failing to start at all although I think that should be fixed now I have resaved the config using the button at the top of the IPSEC page which I suspect puts in the results of some changes in the code.

I see rather a lot of snaps have come out recently and I've been installing them so let's see how it goes. My CF card is getting a good writing to.  Let's call this solved for now and I'll start a new thread with a more useful set of diags if I still have issues.

Thanks for your comments and hard work, cmb and ermal.
Jon

[EDIT] Another crash.  I've managed to boot this box with a serial to USB converter (Prolific) without it hanging so that's an improvement over older versions.  I've passed that through to a Linux VM in VMware are connected it to "screen" with logging switched on.  I can then watch that via ssh and screen on my laptop downstairs as well.  With luck I'll have something better to report back with now I can see the console at last without having to sit in the attic!

The Unbound Resolver showed an up status in the service status window,. However, I could not resolve any domain names.
I have upgraded to the latest build and will see what happens.

@marcelloc:

0.2.3 package version is  out!  :)

https://github.com/pfsense/pfsense-packages/pull/786

Awesome!! You da the man!

I'm installing on a fresh amd64 install and will let you know if I run into any problems.

Nope, that didn't help.

Yes.  It's squid3 now as 3.1 version is no longer on freebsd ports and squid3-dev is pretty aread on gui functions from old squid3 version.

Thanks for the info but before we can use it on pfsense , we need it on freebsd ports.

This may or may not be related but I noticed the following error in a test update to 2.2 today.

It also appeared in previous update tests but I missed it.  It occurs right after re-install of Open VMware Tools.

Kernel.Critical 192.168.11.1 Jan 14 09:46:10 kernel: cp: /usr/local/lib/vmware-tools/modules/drivers/vmxnet.ko: No such file or directory

Updated the package to (0.8.0_2 pkg v1.0.2).

Seems to be working fine this morning and forwarding SIP traffic.

Many thanks jimp.

Wierd. So I deleted the GIF interface and all related config, and created it from scratch with the same values. Now it workes as expected.
Perfect! Thanks.

well that explains it. I guess I'll just watch for support in freebsd. hopefully backported to 10.1

The pfBlockerNG replacement is long overdue… no idea why it's still not available to 2.2 users.

Looks like that bug was fixed but not marked as such. The certs are indeed made properly, at least on 2.2.

Thanks to the devs for nailing this, and to meteotest for the heads up :)

Could you get us a packet capture of the Dlink's DHCPv6 traffic in a pcap file?

@dancwilliams:

Ah,

Don't mind me…I see what is happening now.  Mark me embarrassed  :-.

I do have Suricata installed and doing some testing.  I was unaware that Suricata used the snort2c list to block hosts.

Still in learning mode on all that.

Thanks for the help!

Dan

Yes, for expediency when Suricata blocking mode was released, it used the same pre-existing <snort2c>table.  That's why you don't want Snort and Suricata both installed and blocking on the same box.  It's OK to install both if you really want to, but only one of them should be configured for blocking.

Bill</snort2c>

Just to follow-up - After upgrading to the latest snapshot yesterday, this crash has not yet re-occurred.

Probably not. Free space was far beyong 90%. Much more seemed like filesystem failure caused by squid.

Thanks

That explains a lot (ie why I was having problems loading/installing packages)

I'll just add this HW to the boat anchor collection, though I'm not even sure it will work for that.