Yup this would be trivial via SSH and much more complex via any other method.

Try to determine if you actually need to reboot though. It may be sufficient to just renew the DHCP lease or to logically DOWN/UP the WAN interface.

You'd have to use the sudo package to add commands to the Zabbix user to allow that if you need it. I don't think I've ever had to do that.

@johnpoz Thanks.

I went one step ahead an filed a feature request for the things I asked earlier.
It is at https://redmine.pfsense.org/issues/14899

Your problem as described in your previous post is not a pfSense issue. It is something on your web server setup. Your domain.net I assume resolves to a single IP. The URLs have the domain name in them, but then also include a web path that only the web server (or a web proxy) can read and understand. DNS and pfSense stop at the end of net in your example. The trailing slash and everything after that is the responsibility of the web host the URL is directed towards.

No the recovery image will take you to 23.05.1. You can then restore your config into that and be back up on the current version.

Steve

@charry2014 said in pfSense 2.7.0 in a ProxMox VM not getting IP address from Deutsche Glasfaser:

IPv6 gateway shows connected and online but there is no DNS for internet

If you setup IPv6 correctly and there is no DNS, maybe you're suffering as I am discovering ISP gave static IPv6 that doesn't allow LAN to communicate with upstream DVCPv6 server. Please call your ISP.

@sTicKs23, exactly, thank you!

In my case, I was using Firefox and as always selected open downloaded files, but it still would not uncompressed in Ventura...so I grabbed my old MacBook pro 2011...solved that easily.

Check the other logs at that time. You can see in both those cases dpinger was restarted by something shortly after WAN was marked down due to packet loss.

@gessel I too have an alert from this China IP block 183.136.225.29

Screenshot 2023-10-18 at 8.24.51 AM.png

https://forum.netgate.com/topic/183488/et-scan-hid-vertx-and-edge-door-controllers-discover

Virus total shows it is an invasive actor.

183.136.225.31 also

Screenshot 2023-10-18 at 11.27.08 AM.png

Ok, seems like second reboot resolved the issue.

No updates I'm afraid. It still looks like harwdare, though clearly not RAM from that test.

Thanks everyone for your help and insights.

It was definitely ntop. I've disabled it and the messages stopped.

@stephenw10 I show the IP he connects to forum with from googlefiber on these 2 lists.

blocked.jpg

I'm not sure how much help a cloud based concentrator would provide here unless you also moved other resources to the cloud and the HQ becomes just another site. That way if the HQ connection goes down the other sites remain up.
Sure you can authenticate APs across one route whilst routing traffic from wifi clients over a different route.

Currently there is no official central management for pfSense so much of this would be manual setup. Though you can have each site pull alias lists from something central and use those is rules for common requirements.

Steve

@stephenw10 actually I'm an idiot, and am embarrassed to admit that I had forgotten to turn Outbound nat back to automatic!

Im now going to finish by following https://joshspicer.com/lte-failover-pfsense

Apologies for wasting your time, and many thanks for your response

@Gertjan okay, I will try to re run the test with multicore. Otherwise I am considering switching to a official netgate device and keep the protectli as a backup if the netgate device fails someday.

@stephenw10 Thank you...I have opened a ticket.

Depends on what you are trying to do. Mudwap supports pfSense CE only.