Feature #9393
closed
Improved support for USB interfaces that may not always be present
100%
Description
Currently if you have a USB 4g modem or any other removable interface you need to manually delete it or otherwise you get an interface mismatch upon reboot. Would be awesome to have the option to match that interface to that specific device, and if it is missing during boot delete/disable it. If it gets plugged in while booted, it will detect that specific device and create/enable the same interface again.
Updated by Steve Wheeler over 5 years ago
Updated by Viktor Gurov almost 3 years ago
Updated by Jim Pingle almost 3 years ago
- Status changed from New to Pull Request Review
- Target version set to CE-Next
- Plus Target Version set to 22.05
Updated by Viktor Gurov over 2 years ago
- Status changed from Pull Request Review to Feedback
- Target version changed from CE-Next to 2.7.0
Updated by Viktor Gurov over 2 years ago
- % Done changed from 0 to 100
Applied in changeset 085ff94b11a8f0f9eea7aaf0d1d2ff8347710d9c.
Updated by Jim Pingle over 2 years ago
- Subject changed from Better Support for Removable/Hot Plug Interfaces to Improved support for USB interfaces that may not always be present
Updating subject for release notes.
Updated by Jordan G over 2 years ago
Tested on 22.05.a.20220429.1807 by adding USB NIC, enabling it and setting a static IP. Rebooted system and removed USB interface before system posted. pfSense loaded and had assigned a different unused physical interface to the interface where the USB was previously associated. Upon plugging the USB back in the new interface now has changed back to using the USB for it's physical assignment.
Updated by Jim Pingle over 2 years ago
- Status changed from Feedback to New
Jordan Greene wrote in #note-8:
Tested on 22.05.a.20220429.1807 by adding USB NIC, enabling it and setting a static IP. Rebooted system and removed USB interface before system posted. pfSense loaded and had assigned a different unused physical interface to the interface where the USB was previously associated. Upon plugging the USB back in the new interface now has changed back to using the USB for it's physical assignment.
Did it really change the assignment (Check Status > Interfaces, for example) or was it just missing from the drop-down on Interfaces > Assignments? That would be two very different problems. If it's missing from the drop-down list then the GUI appearance of it being a different interface is only cosmetic. If the actual assignment changed that would be a deeper issue that would break a lot more things.
Updated by Viktor Gurov over 2 years ago
Jordan Greene wrote in #note-8:
Tested on 22.05.a.20220429.1807 by adding USB NIC, enabling it and setting a static IP. Rebooted system and removed USB interface before system posted. pfSense loaded and had assigned a different unused physical interface to the interface where the USB was previously associated. Upon plugging the USB back in the new interface now has changed back to using the USB for it's physical assignment.
This is correct behavior - you can see a different unused physical interface on the interface assignment page, but correct value in config.xml.
Same issue if assign WiFi interface, and remove it on reboot.
Updated by Jim Pingle over 2 years ago
- Status changed from New to Resolved
Seems to be working about as well as we can hope for here. Maybe in the future we can add dummy entries into the interface list for assignment for these kind of potentially-temporary interfaces.