@PiBa:

just fyi: pfBlockerNG 2.1.2_2 includes that patch.

Noted, and thank you!

i have the same issue, the "XHCI: Reset controller" loop only stopped after I disconnected the UPS.

I wanted to update this post by saying the traffic graph is now working!  :) Also the time has been corrected and have been able to use the actual drop down menu for my location. I have to gather this was fixed in the 2.4.2 release so that is two item off the list. Thank you to those hidden hero's who resolved this issue!

It would have been nice if someone would have chimed in as to what broke to cause these issues. I am working through the list to see if anything else is amiss.

Thank You!


Did a few things, but it seemed a combination of setting IPv4 as the preferred transport, and clearing out the pkg repository, finally did the trick.

Thank you !

I've upgraded to 2.4.2, as expected I had to reset pfsense again and recover a pre-2.4.1 config backup to get it booting.

FWIW, I switched from the Zotac C1327 to a Protectli E3845 Vault with Intel NICs and there's no problem with speed under 2.4.2. I think it's likely an issue with the Realtek driver used in the latest version of FreeBSD, though it could also have something to do with a crypto or BIOS incompatibility.

I appreciate your answer, great help!

fwiw: Your post was a really big deal for me when I happened across it.

That board is what Sophos uses for their SG 105/115 UTM's.

I have three of these that have been laying around for a couple of years, and I've never been able to get around that error.

With my near total lack of BSD knowledge (and it appears BSD specific) I went a ways down the rabbit hole and got nowhere.

Toggled that usb setting per your post and the install was uneventful after that.

As a result, I now have three small pf routers that I can use for small projects instead of giving up my good hardware.

I'm getting around 800mbps as a pure router, with a load around 10%, so it's a nic limitation.

I should see what I can pull both aggregating and under a more real world load of packages.

In any event, it's an order of magnitude more performant than Sophos ever was.

https://forum.pfsense.org/index.php?topic=140031.0

https://redmine.pfsense.org/issues/8098 fixed in next snapshot

I ran into the problem upgrading to 2.4 on some systems today. "upgrade failed" when trying to upgrade from the GUI. After enabling SSH and login as admin, I upgraded pfSense with```
pfSense-upgrade -d

Note per the releaes page about ZFS, "To use ZFS, a reinstall of the operating system is required. It is not possible to upgrade in-place from UFS to ZFS at this time." Ref [https://www.netgate.com/blog/pfsense-2-4-0-release-now-available.html](https://www.netgate.com/blog/pfsense-2-4-0-release-now-available.html)

Fixed in the next snapshot

@maverick_slo:

+1
But strange that I had no issues…

Maybe if the log messages weren't so vague, it would shed light on why the effects of this problem were different for different users.

Fixed.  Please try the next snapshot.

That functionality is there but I would not use it.

As far as I know if you edit the alias the routing table is not automatically updated to reflect the changes. You need to also go back and edit/save the static route.

Proper supernetting can reduce the number of static routes required.

dpinger will show in the pkg data in the shell, but it doesn't show the version in the GUI.

: pkg info -x dpinger dpinger-3.0 : pkg info dpinger-3.0 dpinger-3.0 Name          : dpinger Version        : 3.0 Installed on  : Fri Nov  3 15:58:03 2017 EDT Origin        : net/dpinger Architecture  : FreeBSD:11:amd64 Prefix        : /usr/local Categories    : net Licenses      : BSD2CLAUSE Maintainer    : garga@FreeBSD.org WWW            : https://github.com/dennypage/dpinger Comment        : IP device monitoring tool Annotations    :         repo_type      : binary         repository    : pfSense Flat size      : 24.3KiB Description    : IP device monitoring tool WWW: https://github.com/dennypage/dpinger

I changed the space to an underscore and it works great now.  No idea of why it didn't work the first time when i changed it to all letters, but it is working this round after changing out the space.

Thanks for the help.

Yeah, it's not putting a record of the package into config.xml like other packages do.

Looks like that was a byproduct of how the package was intentionally coded, though it does appear to be an unintended side effect.

https://redmine.pfsense.org/issues/8068