All packages are up to: pkg version -vL= Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. pfSense-upgrade >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. >>> Unlocking package pfSense-kernel-pfSense... done. >>> Setting vital flag on pkg... done. >>> Setting vital flag on pfSense... done. Your packages are up to date

Boot single user and run /sbin/fsck -y / until it comes back clean. Maybe 4 times.

@kb: Hm… But I'm able to use admin user for that. No you're not, it isn't working (or you wouldn't have started this thread) :-) It's pretty well documented around that admin@ is not to be used for scp or anything that needs ssh features. It's locked to the menu. Just add another non-admin account and use it for whatever you need/want.

You might want to read here: https://doc.pfsense.org/index.php/Multi-WAN

It is up to the client whether it uses IPv4 or IPv6 when it thinks it has IPv6 connectivity and both AAAA and A records to choose from. With IPv6 disabled on WAN I can't see anything else helping more.

I guess no one has attempted to set anything like this up before?  I have some time this week so I may attempt it, but I am not sure I'll have any idea what I'm doing.

So yeah, multiple layer 3s are normal with IPv6. That might be pertinent had OP mentioned IPv6.

Hello, I'm just wondering if anyone has experienced the same issue or if anyone has some insights that could point me in the right direction (i.e. what/where I should be looking). As far as I know, there is no setting (at least in the pfSense GUI) to disable EAP. Any hints would be greatly appreciated. Cheers

Hi, Yeah it looks very normal indeed, and the traffic came in thru one door & exited thru another just right as expected … until I realized that I should count how many left by counting those who exited ... not by counting those who came in. In other words, for me those marked as OUT in the graph should be labeled OUT in the list. This screen is traffic statistics for the LAN interface only, not combined WAN/LAN. It's just labelling anyway. Thanks. Edwin

@JKnott: Works fine for me. Check if your default gateway is setup correctly in System->Routing.

was looking at this one  LINKSYS SWITCH LGS318P 18-Port Smart Gigabit PoE+ Switch

System->Advanced->Misc Disable PowerD

Script works for 2.4 also!

my ISP is not dchp, we using static ip. then, i set my pfsense wan to static ip

@joelones: Any suggestion on how I could troubleshoot this? Better to ask at Asterisk forum as there is no evidence that pfSense is guilty. General advise - forget about generic Asterisk log and check your SIP signalling.

Does pfSense support a CNAME alias?  If so, he could create an alias for the Android-* name.  I do that with my firewall WAN address.  It's host name is dependent on the computer & modem MAC addresses.  So, I created an alias for it on my public DNS.

@fredfox_uk: Tried pfSense and VMWare ? No. I have no experience with VMWare. And it isn't the Virtualization in any case.