Disable start up interface reassignment
-
I have 6 physical interfaces assigned. 1 PCI pass-through for WAN, 2 are VFs and 3 are bridges. All of the MACs are set in the VM config other than the PCI pass-through. For virtual interfaces there are 4, 3 ovpns and 1 bridge. The ovpns that is tied to the bridge that comes up in the assignment script along with the bridge. When I get a chance I'll redo that ovpns and bridge to see if it makes a difference.
-
Hmm, I wouldn't expect an issue there then. What does that actually look like in the interface list?
-
I have 2 issues. This pfSense won't boot without my intervention and that the assignment script asks me to assign a physical interface to the bridge and a opvns interface. If I don't give the a bridge and a opvns an interface I'm having to rebuild rules and routing.
-
Yes, that's a problem at the console because those sub-interface types don't exist yet when you are presented with the menu. However the fact it is shown at all means one of the assigned 'physical' interfaces is not present.
What interfaces do you see listed at the console menu after it has booted correctly? -
All physical interfaces are present, none have been removed.
-
Right but what does it show there? I can't guess what interface(s) are likely to be causing the problem without seeing that list. It doesn't have to include any IPs.
-
I've had another problem — when my 4-port Chinese card went crazy after a firmware update, it started to randomly change the ports order on startup. I did not see startup reassignment this time, but it was a total mess, I replugged the cables almost every time it booted. It is clear that this will almost never happen during normal use, and just because of this, there is definitely no need to redo anything there.
But… it would be good to store MAC instead of just interface name. The fun thing is that LAGG, for example, already shows the MAC address, when you configure it in GUI, but don't use it anywhere.Simple case — you have 4 physical ports, for example igc0 to igc3. You have assigned igc0, igc1 to LAGG0 and igc2, igc3 to LAGG1. What will be happening if igc1 is dead?
I think it will just shift igc2 to LAGG0, becoming igc1 and igc3 is still in LAGG1, is not it?
If it is configured just as failover it will work as expected, util for some reason there is no more link on the LAGG0 igc0 and when it's happening the LAGG0 will be connected to the LAGG1 network as igc1 became Master.If interfaces are assigned using those LAGGs so I am not sure that startup reassignment will be started even if there is no one interface is left in LAGG.
-
@w0w said in Disable start up interface reassignment:
my 4-port Chinese card went crazy after a firmware update
A pfSense upgrade? A BIOS update?
It would only be re-ordered in pfSense if the NICs appeared on the PCIe bus in a different order, which is hard to imagine. I'd guess only the PCIe bridge could do that, if it has one.
-
@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.
