@SteveITS said in Can't ping the same IP from multiple devices: I think you are right I tried it with both Senses and with FreshTomato, without any special OutboundNAT, the outcome was every time the same.

Yes, I'd like to see that. I'd also particularly like to see the configuration history after it fails. The only thing I can imagine so far is that is fails to detect ena1 and somehow assigns all interfaces to the only remaining NIC. But if that did happen it should drop to the interfaces assign prompt because the config contains interfaces no longer in the system. In the config you uploaded though both WAN and LAN are assigned as ena0 and that shouldn't be possible.

@stephenw10 I had to hold down the power button to turn it off. Then turn it on again I will remove the wireless card. The HP T730 only has DisplayPort connectors. When I connect DisplayPort during normal operation, I get an output. but during yesterday's crash, nothing. Im looking into getting some better kit to run pfsense on.

@josephchrzempiec So, to be clear, you don't have the central controller for these APs? You only have the options available in the APs directly?

@Cloudless-Smart-Home said in console - restore from recent configuration - disaster has struck: If you dig deeper ... and you right. Although I touch Mac devices every day (apple TV, phone, pad) I never had the courage to actually use an "mac pc" myself. I've been using Putty on MAC (not 'my mac', but the laptop of the company) and, yes, you're right, I recall now, it was also running Windows ^^ Anyway, a non issue, as mac is nix base, you already have the native ssh and serial comm client build in, something Microsoft based OSes (up until recent) lacks ... Added to that, SSH access isn't really needed. I'm using SSH - and also SFTP - access a lot because I do 'things' with my pfSense that aren't part of the normal maintenance cycle of a SOHO router firewall. Most of the pfSense users will rarely use the serial console access, and probably never use the SSH access. The ssh access is even, by default, deactivated.

@Cloudless-Smart-Home many, many threads regarding the home assistant not liking to be proxied, but I found the solution was to turn off the ssl checkbox that works in every other server, evidentially because they were already running https, unlike home assistant. also had to add a config.yaml entry to allow trusted proxies and uncheck forward for, but then it worked too, for the record, incase someone else stumbles into this conversation, they won't have to spend hours and hours to find a simple solution. sooo much to learn and such hard knocks when you do, lol.

@nimrod Hey Guys, Is it really that important to be right? You must both be steely eyed missle men to argue like you do.

Ok 6.0.19 is pretty old (2023?) That's still in Proxmox 7 I assume. You should upgrade that IMO. This is almost certainly that bug though which is not a pfSense issue.

If it ain't broke....

HAProxy is restarted? Does it log an error when it stops?

Did you set static source ports on the outbound rule? I would probably test a rule that just matches the one internal IP trying to connect and all ports to be sure. Then check what states it's opening when it fails. Or succeeds!

@RickyBaker I think it was the modem!!! [image: 1745282261191-680decb1-9933-4198-9eee-eb55e04c7910-image.png] I'm not convinced this isn't just temporary. Some of the settings of the Modem seem wrong. for one passthrough didn't seem to work and DHCP is enabled on the router. I'd like to enable the protocol in that link i posted above (https://docs.netgate.com/pfsense/en/latest/recipes/authbridge.html) but for the time being i'm happy to have snappy internet back! Thanks everyone! This seems......ok? not sure what I should expect over wifi with gigabit fiber: [image: 1745282459530-f8a26daf-94ec-416e-a4cc-bfab1911feec-image.png] It's def faster than it was though...

What does the console show pfSense has as a WAN address? If the upstream router/modem is passing it a 192.168.1.X address that would conflict with the default LAN subnet and one of them must be changed.

Hi all, Exchange Server working. Configured with Squid Reverse Proxy and a firewall rule, NAT rule not configured. Many Thanks! Matias

@madmaxpr FWIW for reference: https://docs.netgate.com/pfsense/en/latest/backup/restore-different-version.html

@kpa said in How can I install Midnight Commander on pfSense?: It's supposedly an easy to use file manager (for being an ncurses application) but since there are better ones like Filezilla, WinSCP and others that can use an SFTP connection and offer a proper GUI on your workstation I don't see why you would want to install it on pfSense. An upfist from the future!

Ha. Fair.

@stephenw10 Things looking good. Firewall survived multiple WAN/PPPoE down events with the new pppoe module. Though, It is still a mystery why this happened in the first place before with the old pppoe module or 24.03 more precisely.

@tinfoilmatt A domestic router, I guess, can be called a SOHO router that the average man in the street can but from their local computing shop - Linksys, TP-Link, D-Link, Draytek, Netgear etc or is supplied by your ISP. It excludes high end devices like some of the CIsco and Juniper devices and things like that. The warning is not good. It does not even point the user to the correct screen or give him any instructions. It did help me eventually narrow it down, but I consider myself way more advanced than your average user - I used work for Clearcenter providing support for ClearOS (which also resets the routing table when changing the external WAN settings).