you wrote that when you connect a PC instead a Mikrotik, its working. So i think your Mikrotik Config is wrong. Du you have a DHCP Client running in Mikrotik on that Interface which is connectet to pfSense? If YES, is the DHCP Client configured to add a Default Route?!

Maybe this post could help? I used the last suggestion to increase the screen size of my connection in Hyper-V. Add in /boot/loader.conf.local Maybe try juggling the X,Y numbers to fit? Post

I was able to resolve this issue while researching some of the error codes above. I cannot specifically comment on the exact solution.

Nice result!

@stephenw10 will do thanks

@bingo600 said in No packages installed/Unable to check for updates: @ramosel Yes - Bad url Fix is this (switch to the devel btanch , and immediately switch back) Gotcha, I thought reading that through they were talking about changing the actual version, but it was just the selection without choosing to commit the change and rewrites the config. Easy enough, Thanks. Seems to have cured all issues I saw this morning. The pkg-static runs fine and to completion now as well. Is there any thoughts as to how the URL is going bad? Every thing has been fine for weeks without any config changes. Rick Thanks Bingo, Thanks Stephen! (is that like Bingo Fuel, I'm outta here?)

It ends with @sotirone said in 1200 DynDNS Email Notifications Every Night: Sep 17 17:36:11 php-fpm 75704 /services_dyndns_edit.php: phpDynDNS (): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS so the file contains the same IP as the actual WAN IP and the file date is younger as 25 days from now. So there is nothing to do : all looks fine. Another look at : Sep 17 17:39:07 php 8219 notify_monitor.php: Message sent to email redacted OK The mail gets send, but some failure stops the mail from getting de-queued - and it will get send again. So not a dynsds issue, as no further dyndns log lines are shown, but a notification system issue.

@stephenw10 Got it. Thanks again! Switched monitoring IP to the Comcast primary DNS server: 75.75.75.75

If an IPSec P2 config is over-matching it will grab that traffic and send it across the tunnel so it never reaches the DMZ. That affect it whatever the NIC assignment though. It only applies to subnets. Steve

Ah, good catch. I was just going to suggest something must be blocking it upstream. Odd that you were able to ping 8.8.8.8 from a client on LAN though. Steve

@stephenw10 Thanks, it was good to get clarity as to why this is so, and that's OK. ;o)

Ah, good call!

Urgh, well bad news on the hardware but always good to hear support feedback. Steve

Thanks all for the advice. I have set it to 8.8.8.8 and increased the probe/alert intervals.

@bmeeks Thanks so much, adjusted accordingly. This being my first Pfsense setup I guess I am bit nervous, I'm use to working Sophos XG NG's and Junipers completely different animals and with this system going thousands of miles away just want to make sure I am providing them with a secure device.

Hi! Just to close this. Bought another unit and it is now working perfectly. So it was, indeed, faulty hardware. Thanks @stephenw10 and @Patch for the help. Manuel

For example the running firewall users are created from the config file at each boot. So whatever you have on there now is the result of the config that was present at the last boot.

@stephenw10 great, thanks! I will consider doing so. But you know what? The one employee using OpenVPN told me an hour ago that she doesn't even use it anymore! So I might not even need that setup anymore. For my own administrative purposes I can simply start from scratch or even use Wireguard instead. Thanks all for the feedback and help!