@kesawi If NON PoE , there is a lot of 24/28 port 1Gb switches that are fanless & w. sensible power consumption ~16..20W For fanless PoE+ i use 8-port that is limited to 64W PoE in total. /Bingo

It creates a crash dump for a kernel panic but not for a process crashing out like that. It does create a coredump though which can use significant space. The coredump is not really useful for solving that. Unfortunately ntop-ng seems to like to do that regularly. Steve

Your trying to connect to your pfsense while your remote, or you setup pfsense to be a vpn client to some service. That error normally is you couldn't talk to the IP of the vpn server. Port is blocked? IP is wrong, etc. Lets assume your trying to setup pfsense as the vpn server, and your client - lets say phone is remote and your trying to connect to what IP.. If pfsense is behind a nat, you would have to forward the traffic from that nat router in front of pfsense, to pfsense wan IP.. And you would have to set your client to use your actual public IP of the nat device infront of pfsense.

In this first round with 2.5 and 21.02 there is no issue from switching, my take is same as moving from CE to FE now.. As it evolves - maybe that changes? The code base is for sure going to diverge. What happens to the ability to easy switch between the two as that happens, not sure. I would think they would want to keep that ability.. Especially if used in some business setting where they wouldn't be able to use the free home/lab version. I would take it they would want to make it simple for the business to migrate from CE to + One of the things that is coming is easy management for business of multiple units, zero config sort of setups.. Where you plug it in and it gets its config, etc. So my guess would be moving from CE to + will be easy. As to moving from + to CE a few versions down the road.. Not sure. My take from the information I was given, this is more of announcement of change, when this happens next month.. I didn't get the impression that there is going to be really much different from CE and + in the first round. Just like there is isn't much different now between CE and FE other than a few extra tools, and some optimization stuff for their equipment, etc.

Thank You For all your help, got it working , thank you for all the support :) it was all about time . Its take around 10-15 min to get a ip from comcast with bounded connection in my case with MB8600, and yes definitely rebooting the modem/pfsense box after each change is helped . I tried everything , reinstalled pfsense , tried the dev version... finally almost give it up , installed back 2.4.5p1 , rebooted everything , created the bonded ports in pf sense , set everything to DHCP, had my dinner , when i got back to my system...whoa ... my setup is connected to the internet. Now its time to play with those firewall settings :) [image: 1611348515743-pfsense.jpeg]

Those are virtual interfaces, they do not have a link status.

Yeah, it's not expected to change in the GUI. That is a list of sysctls to set at boot. Not their current status. Steve

@ Bertjan Many Thanks. I deleted the user and that was it. The Pfsense started alone and no longer needed a password.

@jackgle Great question; however, I don't think anyone can give a clear answer until v.2.5 have been released.

@stephenw10 thanks Stephen, the solution of creating a gw using LAN and setting up a static route worked well. Thank you for the quick reply and support!

Yup, if you need 'hot plug' you generally need the active graphics drivers. But loading them brings in a bunch of other stuff that may or may not cause more problems then they solve. And they may not be available for that box. What is the PCI-ID of the vga device shown by pciconf -lv? Steve

@johnpoz said in outlook not downloading folders: Still not really understanding the exact issue. That's why I asked OP whether OP forgot to login! It appears not a pfSense issue.

@johnpoz already did, thanks :-)

To anyone else who might come across this post with Comcast. (or probably any ISP) I went to the logs searching the logs as @stephenw10 suggested and noticed some funny "XID Mismatch" logs. So, looking up this article: https://docs.netgate.com/pfsense/en/latest/troubleshooting/dhcpv6-xid-mismatch.html It said to basically do (arrow is for pointing out command): # ps uxawww | grep dhcp6c root xxxxx 0.0 0.0 5780 1488 ?? INs Sat09PM 0:00.90 /usr/local/sbin/dhcp6c -d -c /var/etc/dhcp6c_wan.conf -p /var/run/dhcp6c_re1.pid re1 root xxxxy 0.0 0.0 5780 1524 ?? Is Tue07AM 0:00.30 /usr/local/sbin/dhcp6c -d -c /var/etc/dhcp6c_wan.conf -p /var/run/dhcp6c_re1.pid re1 Then, i saw multiple instances of it like the output do: killall -9 dhcp6c Solved my problem, maybe yours too.

@viragomann thanks ! --> solved

DNSMasq is not enabled by default in pfSense. It's mostly included for backward compatibility. Those issues look to be mostly DNSSec related which is not used in DNSMasq in pfSense, you should use Unbound if you want DNSSec. Any updates will be in the upcoming 2.5 release though. Steve

@emammadov I don't know if anyone fixed this - but I'm just typing this for anyone who might need it as I did. I wrote a small bookmarklet in javascript that selects all days in the current month. It can be expanded to select the whole year at once. As far as I care - they can even integrate it in the main interface, for easier management of the schedule dates... Here it is: https://jsfiddle.net/lovetruth/bdLnhw3m/2/ and the code inside the js section can be transformed easily into a bookmarklet using this site: https://www.yourjs.com/bookmarklet/ And then you just drag and drop your converted blue bookmarklet into your bookmarks bar and use it whenever you have the calendar of the firewall schedules in front of you. Success!...