@naiw the instructions from Vultr sound like targeted at Linux systems (ip a, /etc/sysconfig/ -> RedHat). You may ask them for FreeBSD instructions or better for pfSense.. But I don't think automatic config will work with pfSense at all.

They assign the second IP to your instance and you have to manually create an alias, as @stephenw10 mentioned.

More infos (although old, 2016): On this forum: Two totally separate IP's on WAN - how to configure on VULTR. The result was the same, create an alias.

Thank you both for the responses. This makes sense. I had not thought that ping might be disabled on the gateway. I took @JKnott suggestion to find the first upstream server using tracert. All is well again!

Any alerts/errors shown in the gui when you logged back in?

Anything in the system logs?

You don't need a leading dot for that.

@patient0
Hi,

Thanks for the your information.

Now we tested with intel NIC. Its working now.

Yup the 8200 does not have eMMC.

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.