Beginning with 2.8.1, I am transitioning NUT support to a new thread, which can be found here.

Please continue to post issues related to 2.8.0_2 and below to this thread.

Also, I am actively seeking people to test the new 2.8.1 pfSense NUT package prior to general release. I would appreciate any help you can offer. Thanks!

@periko said in Unofficial E2guardian package for pfSense:

Hello marcelloc or other e2guardian users, does e2guardian is already support for pfsense 2.5.2?
Regards!!!

I've been using it on 2.5.2 for months now, no issues.

As I have mine in my living room next to where my computer is, I'm generally not even aware of it running. But one of the fans has started a bit of a wobble which caught my ear, though it seems to be gone now. This reminded me of the other day when the fans ramped up and were noticeably loud. I had checked the temps then and they were up around 68C. I went in and checked again after hearing this wobble tonight and I'm hovering around 48C. I don't remember what my average temps were previously. Maybe I've posted them in this thread before, I don't recall.

This all seems to have started after we had a power outage over Christmas while I was away. (Think the power was out for about 5 hours while the UPS probably only lasted about 3 or 4 hours at most.) I had thought I had it configured to auto power on when power was restored, but apparently not. I still need to get in there and set that one of these days. But in any case, when I turned it on after we got home, the fans screeched something terrible for a couple minutes while booting but then calmed down into a slightly louder volume than before, but low enough that you generally don't notice it unless you're listening for it.

So I don't know if the extended shutdown after constant running for so long did something to the fans, or if they're just old, or probably a combination of both. But now I'm thinking I should start looking for some replacement fans. Since I currently have this running and it's also in a slightly annoying spot to access it without having to shut it down and pull it all out, I'd like to ask a few questions that I don't recall having seen posted, though after all these years, it's hard to remember everything. (I tried searching but apparently don't remember how to correctly fine-tune the search results on this site and wasn't able to find anything helpful.)

Since this is on a 1U platform, I'm assuming pretty much any 40mm fan will fit, but does anyone know the depth of the stock fans or the max depth? I'm thinking if I'm going to buy a replacement fan, I'll just replace all 3 and maybe try and go for some quiet Noctua fans or something. Anyone have any suggestions on fans? Does anyone know the size of the fan in the power supply? As of right now, I'm not sure which fan it is that is dying and it could very well be the PS fan that's the culprit. I know these can be slightly more tricky to replace depending on how it's mounted, but I'm fairly sure I can manage without electrocuting myself inside. Any suggestions on a replacement fan for the PS? While my PS is apparently slightly different in that it had 2 SATA power cables instead of 1, I imagine the fan is still the same.

Anyway, thank you in advance for any help and suggestions. It will save me some time from having to find some time when everyone else isn't trying to use the internet to go in and diagnose which fans are dying and then getting the replacements and then bringing it down again to do the actual replacement.

@robnitro That sounds really good.

@gersonalves obrigado pelo retorno, já verifiquei se há conflito de porta por algum outro serviço, mas não há, inclusive quando para a navegação eu sempre vejo o netstat -an | grep -i listen e sempre a porta *.8081(ssl) deixa de listar, a porta 8080 continua listando, daí eu salvo a conf do e2guardian em seguida a porta 8081 começa a listar novamente e a navegação volta a fluir normalmente.

tcp4 0 0 *.8081 . LISTEN
tcp4 0 0 127.0.0.1.8080 . LISTEN
tcp4 0 0 192.168.0.254.8080 . LISTEN
tcp6 0 0 *.53 . LISTEN
tcp4 0 0 *.53 . LISTEN
tcp4 0 0 *.10050 . LISTEN
tcp6 0 0 *.80 . LISTEN
tcp4 0 0 *.80 . LISTEN
tcp6 0 0 *.xxxx . LISTEN
tcp4 0 0 *.xxxx . LISTEN
tcp4 0 0 *.xxxx . LISTEN
tcp6 0 0 *.xxxx . LISTEN

Já verifiquei no firewall e nat e não há algum impedimento com as portas de escuta do e2guardian.

@winsonfa

It should still work?

Those errors are just cosmetic, you can ignore.

On my machine, it gives that error but still works.

The link suggests no tweaks are required in 2.5 or 2.6 and I would expect the same in 2.7. Though I don't have an APU2 to test with.

Hi guys, I know this is a super old thread - but just wondering if anyone in here could share me the a copy of the last x32 bit via DD configured for the x700 - Please see here for the actual thread with the background as to why: https://forum.netgate.com/topic/133044/pfsense-image-for-firebox-x700

If you change pFSense / Services / Squid Proxy Server / GEneral tab Then check the SSL Man In The Middle Filtering area and change the SSL/MITM Mode from Splice WhiteList, Bumb OtherWise to the Splice ALL

the problem can be solve with a this shape.

OR

With a default value of the SSL/MITM Mode with Splice WhiteList, Bumb OtherWise you can goto ACLs atb and add desıred web site url to the WhiteList area ie: online.kktcmaliye.com

Hello Stephenw10

Thanks much for the message. I will check it, although the service can't start, not with that config.
Anyway, I am also trying to use parallel port configuration since it doesnt' need any interface in between. (I have another display hd44780 compatible with no USB interface)
Will post the results here after all.

Thanks
Fabricio.

Don't know if anyone else has tried yet (and I have no reason to think it wouldn't work but..) I successfully upgraded to Pfsense+ on my M400 today running an i5 processor..

More to support Netgate and Pfsense than anything.. but in case anyone else is holding back.. ;)

@jasonsansone I haven't tested the new pf versions yet. Will be starting my migration project in the next few weeks.

The details are fairly self explanatory I thought. Basically openssl disables certain weaker ciphers. The config file re-enables them for the wpa_supplicant session. Depending on which wpa_supplicant is in use, this is either done simply through the wpa_supplicant.conf file (example at the end of the file), or through a config file for openssl that's referenced in the command line launching wpa_supplicant.

@dreamdenizen Mac for wpa_supplicant doesn't have to be that of RG, or even RG where certs came from. What matters is the mac in wpa_supplicant.conf file match that of the wan interface mac requesting dhcp. Otherwise, you'll get eapol authentication, but never received an IP because of the mismatch.

@shred yup, I've been there, I also got confuse about that. but that rule is to block other interface to access management port. some of the link or pictures of this guide did not retrieve when netgate upgrade their forum.

02268e4d-4c47-4b6c-b5ed-0cdbe7ee2a20-image.png