Search results

We all need to do what works for us. I am glad to have other ideas to look at from this thread should my solution fail me in the future. Thank you everyone for feedback!

I am nowhere near that system at the moment, and I am sorry but I don't really want to poke at something not broken. That said your theory does hold weight. If the modem really does only lock into the first DHCP request you may have found another solution to this problem.

The issue is definitely related to the modem locking into the mac address of the physical network card during reboot. Once the virtual mac takes over it refuses the connection. However it will allow a new mac address if the link is lost for a short time. This is what my workaround simulates and...

Try just unplugging the Ethernet cable then plugging it back in then rebooting the pfsense. If this works then my workaround should work assuming you have a network card that can be turned off then on by command line.

For clarity eth1 was the network card that was connected to my cable modem. It very well could be eth0 eth1 eth2.... Depending on your configuration.

It is entirely possible the network card you are using does not support or does not fully support being turned off then back on via command line. If this is the case you could try other network cards to see if any of them will support this function. Otherwise my workaround won't work, because it...

Are you certain you are using the correct eth* that is connected to your cable modem?

When you ifconfig eth down does the link light on the network card go out?

I am resetting them in the Linux host not the pfsense guest

Try manually entering the commands after rebooting your proxmox. The idea is that during the reboot of the system the modem forgets the lan mac. When the system boots the real mac of the network card is locked onto by the modem before the virtual mac of the pfsense VM takes over. We simulate...

In the spirit of helping future people who may one day google this thread with the same problem I am having. I have found a workaround that consistently resolves the problem. A simple sh script executed after the host boots up to reset the interface seems to do the trick. This must be done on...

I am trying to setup a small server with a NAS + pfSense for my home network. pfSense is in a VM with vmbr0 and vmbr1 assigned as virtio devices. vmbr0 is a bridge of eth0 that is connected to my cable modem vmbr1 is a bridge of eth1 that is connected to my switch vmbr2 is a bridge of eth2...