well read the question asked if it was happing before the beta one tag someone has a roadmap not me, must be you know

@jimp:

How does "ifconfig" output look for that interface when it works vs when it doesn't?
How about "netstat -rn"?

I'll have to get back to you on that.  Currently have it working and don't want to break it right now.  Though being a VM would should be no big deal to recover from.  Maybe I'll do that tomorrow.

Looks good.

Seems that the recent change to class autoloading caused a couple of case sensitivity issues. Now corrected throughout hte project.

Thanks.

Fixed. Thanks Phil

Work in progress guys. Still refining the CSS to get the top padding perfect.

@jwt:

@Giuanìn:

@jwt:

https://github.com/pfsense/FreeBSD-src/commit/3353ee411e4b8bcb80c979f61c9dc03af09ba62f

https://github.com/pfsense/pfsense/commit/3eca6290447cb8c8853b4c03d232269f98fa834b

if you're on a Watchguard, WRAP, Alix, etc, sorry, but 64-bit only on both.

netmap? does it mean that snort and suricata can be used with an inline ips mode?

that's one of the uses, yes.

This is a great news!!!

@DougD:

8GB on bare metal.

Please file a bug.

2.3-ALPHA (amd64)
built on Fri Nov 20 05:28:06 CST 2015
FreeBSD 10.2-STABLE

Tested and woks… Thanks

@doktornotor:

Wow, it's finally updated?

Like it  ;)

P.S: Thanks to the posters on https://forum.pfsense.org/index.php?topic=93293.msg547128#msg547128

I have observed and fixed this previously with a misplaced in one of the widgets, but I see the problem now. Would you please provide a screenshot of your whole dashboard so I can exactly replicate you configuration?

lagg LACP with VLANs works fine on igb, I wouldn't be able to send this otherwise.

Guessing your switch isn't setup correctly for active mode LACP, or the VLAN tagging on the switch isn't right.  First look at the ifconfig output for lagg0 and verify NIC status. Check LACP status switch-side also.

There is now a Redmine issue for this: https://redmine.pfsense.org/issues/5483
so look there for discussion and progress.

gotcha ;)

but still, shouldn't be too much to ask for someone, who's working closely on the new pkg system to just answer my questions …. that'll get me going atleast ;)

They are back now, and I can see the various icons on rules once more.
If possible guys, leave the system in a consistent state at the end of the "USA" day. Then us others in opposite timezones around the world can play, test and report or fix stuff without being stuck because some general feature disappears.

looks like its trying to find a file that doesn't exist. all packages need to be adjusted to use the new pkg-system.

https://github.com/pfsense/FreeBSD-ports/blob/3f0729ef2e63f03132639fbfae6b3e0643e3ddad/www/pfSense-pkg-squidGuard/files/usr/local/pkg/squidguard_configurator.inc#L147

please file a bug report on https://redmine.pfsense.org/

sbeaver pointed out it's fine once you type in an IPv6 IP or network. Yeah, not an issue nor regression, I just trusted the report at a glance. You seeing any circumstance where the mask doesn't go to 128 with an IPv6 network configured?

That's a good thing to watch out for as you're going through 2.3 though. The Bootstrap conversion created a number of issues there, but I think they've all been fixed for some time.

Hi guys!

No comment on this one?
:)

BR,
M

Thanks.

1. & 3. have been fixed.

@cmb:

That a dual stack system that's more than roughly a week or so old? Could be getting hit by the IPv6 route-to bug, though I'd expect curl to pick v6 by default to Google as well in that case and fail.

It's a single stack system.  I'm just testing functionality and I had a hunch that the v6 related stuff would probably get less coverage.  I have v6 available at the ISP level on four FTTC connections with a pfSense 2.2.5 but haven't enabled it internally yet.  This box's WAN is on an internal LAN at the moment.

When 2.3 gets beta status then I'll run it up in a VM at home which has v6 as preferred and keep my 2.2.5 ready just in case (Wife Acceptance Factor).  I may even grow a pair in the meantime and get v6 available in the office, once I understand the full implications.

Also, thanks to you guys I now have a FreeBSD VM running on my laptop that I poke at a bit but I speak BSD with a dreadful Linux accent.

Anyway, I've just run "pkg install git" and it now works.  I'm learning …

@jimp:

IMHO allowing someone to delete more than one interface at a time is more likely to result in an accidental/unintended deletion.

Ok thank you Jimp.