Handle all traffic from within virtual environment

KOM

You have your gateway set to the broadcast IP. Set it to the gateway as provided by your ISP, 192.99.198.150.

Hamclock

So I did. Whoops. Anyway, changing it to .150 hasn't changed the symptoms.

KOM

From the webGUI, can you go to Diagnostics - Ping and see if pfSense can ping the gateway?

Hamclock

@KOM:

From the webGUI, can you go to Diagnostics - Ping and see if pfSense can ping the gateway?

Nope. I get "ping: sendto: Host is down"

KOM

I'm starting to run out of ideas. I don't know KVM and I don't know Proxmox. Your ISP making you use one of your IP addresses as the gateway is strange from my perspective. Usually the gateway is outside your usable range. You can't even ping the gateway from another IP on the same subnet.

Hopefully someone else can chime in.

Hamclock

I agree it's strange. I'm still waiting to hear back from their support folks.

Hamclock

I heard back from the support folks, and they said that all 4 IPs should be usable, and gave me this link in relation to IPv4 settings..

It turns out the host requires you to use a MAC address they specify. I added that to pfSense and changed the gateway to .254 as they suggested, but I still can't get any connectivity. Here's my WAN settings now:

Also, when I try changing the address to .148/30 (to cover all 4 IPs), pfSense gives me the error "This IPv4 address is the network address and cannot be used". Does this mean the support person was incorrect when they said all 4 IPs are usable, or is this just a limitation of pfSense?

KOM

The MAC addy thing is not uncommon, but it would have been nice for them to let you in on the secret before you wasted hours trying to get it working.

OK, first off I would disable IP6 to reduce the complexity. From the WebGUI, can you once again go to Diagnostics - Ping and ping the gateway?

Hamclock

After much back-and-forth, it turns out the problem was… ARP tables in a router I don't control!

pfSense still wasn't happy with the fact that the gateway was outside my net range, but I was able to take care of that:

route add -net YOUR.DEDICATED.IP.254 -iface em0
route add default YOUR.DEDICATED.IP.254
route del -net YOUR.DEDICATED.IP.254 -iface em0

…and now other VMs can lease IPs via DHCP from pfSense and then access the Internet through it! Amazing how much better things work when they're not broken.

Anyway, thanks so much for all the help. The root of the problem may have been out of my control, but I still picked up a few handy things from this thread.

KOM

It seems to be common that network problems you can't seem to resolve end up having an external factor.