Network interface stops working

[CM350]

Hi All,

We are on pfsense 2.3.4-RELEASE (amd64).

Virtualized trough KVM (Proxmox v5.1).

We changed our firewall setup from 5 firewall(s) to only 2 since this weekend  ;).

Our main firewall now has 8 network interfaces.

This morning round 11:00 AM GMT+1 1 of our interfaces stopped working. Could not ping to devices connected on that vlan. Devices could not ping firewall.

Disabled the interface, applied changes, enabled the interface again, applied changes and after that, it started working again.

We have this version running with a lot of customers and it never failed. So since we did a configuration-change I suppose we made a mistake. :)

Nothing to see in system log or firewall log.

Can you help us with this for future outage(s)? (We are hosting a few servers for our customers)

[CM350]

up?

Somebody?

[Gertjan]

@CM350:

We are on pfsense 2.3.4-RELEASE (amd64).

Not related, but : Old version.

@CM350:

Virtualized trough KVM (Proxmox v5.1).

So : probably wrong forum section. All your interface are 'virtual' - this might be an important factor.

@CM350:

We changed our firewall setup ….
Our main firewall now has 8 network interfaces.
This morning round 11:00 AM GMT+1 1 of our interfaces stopped working. Could not ping to devices connected on that vlan. Devices could not ping firewall.
Disabled the interface, applied changes, enabled the interface again, applied changes and after that, it started working again.
We have this version running with a lot of customers and it never failed. So since we did a configuration-change I suppose we made a mistake. :)

No way to go back ?
What I mean : when x (lower then 8) works well on your virtual host (VM) and 8 gives problems now, I exclude (I did not test)  pfSense, which is known to handle far more the 8 LAN's, VLAN, virtual LAN's using a VM.

Check also if there are enough resources available (CPU power) to handle all these vitual NIC's.

[CM350]

We had the same problem with our smaller pfsense (2nics) firewall (on the same server).

So we tried with virtio instead of e1000 and now everything looks running fine.

Has nothing todo with pfsense though :).

Just wanted to update this thread instead of someone has this problem too.