Mmm, almost certainly a link negotiation issue then. On igc NICs the options there are limited because it can only link using auto-negotiation. You can set the available speeds it negotiates at which is what the speed setting in the gui does.

You may need to reboot twice to seen that set since it only gets; applied at boot.

However, yes, there is a bug on some systems where the default values are always used. It only happens on some filesystems where a race condition occurs. It's fixed in 25.03-Beta.

When using RAM Disks I usually start out at double the default values. 1G + 2G is very large. If you have hungry packages though you may need large drives, but not that big!

Yes, you can set it as a gateway. You don't have to route anything to it if there's no subnet behind that peer to route to,.

@Zeldar We believe one of our users is also experiencing the same behavior with their laptop reaching out to the FW and I just verified that the "Killer Performance Driver Suite UWD (3.1222.7103)" and "RivetNetworks.KillerControlCenter (3.1624.1026.0)" applications are installed. In your case, did you keep the driver and remove the intelligence center? or was there only the single app.

@Laxarus You show an IPv6 address on your WAN. You'd use that for the VPN. Also, it doesn't have to a OpenVPN. I assume Wireguard will work over IPv6. The question is whether VPN.AC supports it at the other end.

L2TP can only use Radius or local auth as far as I know. So you need to use NPS to interface it with AD (LDAP).

Unless you redeployed the VM it should not have changed. Simply changing the upstream device would not affect it.

Nice 👍

Many thanks John. In my situation I have one physical interface and one vpn. What I have found is that after a merge of two pcapngs that the term frame.interface_id is either 0 or 1 depending on whether frame is for physical or vpn respectively.

@stephenw10 Ohhhhh! I did remove one, but not one assigned. Is it possible an unused NIC being removed would cause this?

Is this the same problem with my non-Raid setup also?

Current NDI - as in non-RAID, single Hard drive: [NDI - removed]
I guess I can experiment and reinsert the NIC and try again.

Again, thank you for the information and time you are giving.

ok, further digging, looks like with the Kea DHCP; forwarding of hostnames is ignored: https://www.netgate.com/blog/netgate-adds-kea-dhcp-to-pfsense-plus-software-version-23.09-1

guess all my issues are solved then. thanks!

@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.