Timeline for How do you unconfuse Raspbian when it has WLAN0 and WLAN1 reversed?
Current License: CC BY-SA 4.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 8, 2018 at 6:23 | history | edited | SDsolar | CC BY-SA 4.0 |
deleted 147 characters in body
|
Jul 8, 2018 at 6:03 | history | edited | SDsolar | CC BY-SA 4.0 |
Updated based on new information
|
Jun 26, 2017 at 4:22 | vote | accept | SDsolar | ||
May 25, 2017 at 22:29 | comment | added | SDsolar | I see a similar question with an answer: raspberrypi.stackexchange.com/questions/67499/… - I did it without using either blacklist or MAC addresses. | |
Mar 23, 2017 at 17:36 | answer | added | nickcrabtree | timeline score: 3 | |
Mar 22, 2017 at 13:58 | comment | added | bobstro | Dead end then. On debian systems, this is how I've resolved the problem. I'm not sure where raspbian is storing that information to make it persistent now. I suppose you could try creating the file /etc/udev/rules.d/70-persistent-net.rules, replacing the MAC address and desired interface name in my example. | |
Mar 22, 2017 at 6:18 | comment | added | SDsolar | Under /etc/udev/rules.d there is one file called 99-com.rules - and it has no SUBSYSTEM=="net" section. Just "input" and "i2c-dev" and "bcm-gpiomem" and "gpio then it goes to KERNEL=="ttyAMA[01}" and KERNEL="ttyS0" ---- I think I see what you are getting at, but am not proficient enough to handle this. | |
Mar 22, 2017 at 2:01 | comment | added | bobstro | Do you have the file /etc/udev/rules.d/70-persistent-net.rules on the misbehaving RPi? If so, look in there to see if udev has locked a name to the wrong MAC address. I use a customized version of that file to name one of my wifi adapters "mom" to be used as an AP if connected. SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="80:1f:02:86:f1:fc", KERNEL=="wlan*", NAME="mom0" See /usr/share/doc/udev/README.Debian for more details. | |
Mar 21, 2017 at 23:39 | history | asked | SDsolar | CC BY-SA 3.0 |