Bug #3171
closed
Network interface mismatch on next boot after adding usb-stick based WLAN
Added by dont care almost 11 years ago.
Updated almost 11 years ago.
Description
After adding a new interface where I selected run0 (an rt3070 based usb wlan stick, edimax EW-7711UMn) and not doing anything further (not enabling it, no wlan configuration...) except for rebooting, I get an network interface mismatch, so suddenly these settings are gone. I can reproduce this. Might has to do with https://redmine.pfsense.org/issues/3170, maybe the stick is recognized too late and this breaks everything? Note that I didn't any driver loading stuff to /boot/loader.conf.local, as the stick is recognized while pfsense runs. Does adding a driver load command in /boot/loader.conf.local load drivers earlier or is it just for drivers, that are else never loaded? Anyway it shouldn't happen that there is a network interface mismatch, screwing everything up.
tested on 2.0.3 x64.
- Status changed from New to Rejected
This was due to your wireless device not being present when it needed it to be there, so it's not a separate issue but a symptom of the other ticket.
Update: This can be fixed according to the solution in https://redmine.pfsense.org/issues/3170.
Yet I can't understand why my LAN, WAN etc. configuration is affected by a missing USB WLAN stick. I think this should be checked in detail, so the network config loading stuff can be made more reliable / not everything is screwed up just because the usb wlan stick is missing!
Jim P wrote:
This was due to your wireless device not being present when it needed it to be there, so it's not a separate issue but a symptom of the other ticket.
Yes. Yet I think my LAN, WAN etc. configuration shouldn't be gone just because my wireless usb stick is missing, which has nothing to do with my lan/wan configuration.
That has been discussed many times. If any interface is missing, it's best to stop and not try to assume it is safe to continue. Not a debate for this ticket, there are already others open for future features to maybe handle things differently in special circumstances. (For example, #410)
Also available in: Atom
PDF
Updated by 
Updated by