Disable start up interface reassignment
-
@stephenw10 said in Disable start up interface reassignment:
A pfSense upgrade? A BIOS update?
Card firmware. As I already stated it is not happening in the wild, must be only me the lucky one
. I think it was zeroed MAC or even two ports got the same MAC address in the corrupted firmware update process. Nevermind, as I already said there is nothing to do with that on pf side.
But in case of disappeared port... Maybe there's something to improve. -
Urgh, that sucks! Were you able to recover? It could be generating a random MAC at each boot, a few drivers do that if they can't read the hardware MAC. However that still wouldn't affect the detection order so....
-
@stephenw10 said in Disable start up interface reassignment:
Urgh, that sucks! Were you able to recover?
No. After few attempts flash became a read-only.
@stephenw10 said in Disable start up interface reassignment:
a few drivers do that if they can't read the hardware MAC. However that still wouldn't affect the detection order so....
Reply Quote 0
41 out of 41I don't know what exactly happened... I threw away this card a few months ago.
-
I just had the assignment script headache hit again. I was expecting it as I moved a pfSense to another hypervisor and the WAN PCI pass-through nic had a different bus number. But the headache is the assignment script is asking me to assign ovpns and bridge interfaces to a hardware interface. This time it included an ovpns server and a ovpns client.
@stephenw10 What list do you want to see? Console or Gui?
-
@w0w For note. Intel I350's have been rock solid for me in all aspects; pci pass-through, hypervisor bridge and VF. All while using either e1000 or virtio emulation and with IPS enabled. Zero complaints.
-
@Justaguy-0 said in Disable start up interface reassignment:
What list do you want to see? Console or Gui?
The list from the console menu should be enough, like:
WAN (wan) -> em0 -> v4/DHCP4: 172.21.16.22/24 LAN (lan) -> vtnet0 -> v4: 192.168.22.1/24 v6: 2001:db8:1000::1/64 WEBSERVER (opt1) -> vtnet1 -> v4: 172.25.10.1/24 OPENVPN_SERVER (opt2) -> ovpns1 -> v4: 192.168.251.1/25 OPT3 (opt3) -> vtnet0.100 -> v4: 10.40.0.1/24Though we don't need to see the IPs.
The check there doesn't care what order the NICs are in or where they are on the bus. Mearly that they are present.
-
This is the console of the most recent one to ask me to assign ovpns and bridge interfaces. Also, moving hypervisors I'm not manually recreating the VM, it is a migration with no removal of NICs. The MAC address of the vtnet interfaces are moved with the VM and igb0 receives a new MAC as it is PCI pass-through.
-
Hmm, so the ovpns and bridge interfaces are not assigned in normal use?
You should not have to assign them if/when it stops at the interface check. If you are forced to do so I assume two of the interfaces shown there are not available at that point?
-
I'm not aware that I need to assign them in the GUI. They work as is. The 2 interfaces are shown in the assignment script.
-
Ok, so changing the bridge on LAN from vtnet to SR-IOV VF the assignment script strikes. Assigning WAN and LAN but now it asks for opt1 which I can't ignore without losing the rules for opt2 and opt3.
To not lose my rules I have to add 2 interfaces as it asks me to assign opt1 and opt4. And when it's done;
In the GUI there is nothing assigned to opt1 and opt4.
-
Ok, that would be expected because changing the NIC type means that the assigned vtnet2 interface no longer exists.
I'm not sure why it asks for OPT1 and OPT4 unless those were assigned as the bridge/ovpns interfaces.
