Re: name for wireless interface
>> What is the origin of the long name, wlxa0f3c10a28f7? * From: Kushal Kumaran * Date: Sat, 12 Aug 2017 22:45:44 -0700 > https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#new-interface-names OK, yes, just the MAC or Ethernet address prefixed with "wlx". root@dalton:/home/peter# ip addr show wlan1 4: wlan1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether a0:f3:c1:0a:28:f7 brd ff:ff:ff:ff:ff:ff Thanks Kushal, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 Tel: +1 360 639 0202 Pender Is.: +1 250 629 3757 http://easthope.ca/Peter.html Bcc: peter at easthope. ca
Re: name for wireless interface
On Sat 12 Aug 2017 at 18:38:05 (-0400), Fungi4All wrote: > > From: pe...@easthope.ca > > To: debian-user@lists.debian.org > > pe...@easthope.ca > > > > A TL-WN722N adapter connected to a stretch system gives these results. > > > > peter@imager:~$ lsusb | grep Ath > > Bus 002 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n > > > > root@imager:/home/peter# iwlist scan > > wlxa0f3c10a28f7 Interface doesn"t support scanning : Network is down > > > > lo Interface doesn"t support scanning. > > > > eth0 Interface doesn"t support scanning. > > > > What is the origin of the long name, wlxa0f3c10a28f7? > > Can a shorter name be assigned? > > I can not help much and I have given up worrying about this madness. > I have two debian installations, one has been on for years. The one is > testing the other unstable and previously have never had problems with > either one. Lately neither one has been able to maintain a wifi connection > for long and takes 2-3' to boot up. I took J.Johnson's recommendation > to play around with ifconfig -a and ifconfig wlan0 up from console. > The first time I run it the interface was listed as wlan0 > The second run it became wlan0mon > The third it became wlan0monmon > > I barely get enough time to run an update/upgrade on both installation > and then it is down hill from there. > > NOW > > I have 4 more installations on the same machine, as I keep debian for > sentimental reasons only. None of the four different installations have > had ANY connection problems, same machine, same wifi device, same > connection. The two are devuan-based the other two are Arch based. > NONE have systemd on them, only Debian does. > > You tell me what is wrong. Setup is about the same, wicd is on all of them. As usual, there's not much information to go on. I haven't seen "J.Johnson's recommendation to play around with ifconfig -a and ifconfig wlan0 up from console" but that sounds a great way to break a system, particularly if there are some scripts that are getting executed over and over. A while back I wrote to you in another thread, "I'm trying to explain what may have happened under the circumstances that you have presented us with. You are the one trying to apportion blame, and you've decided on fsck and grub." Getting a straight description of any problem from you seems to be very difficult, so I'm not really surprised that no one has yet taken the bait. Cheers, David.
RE: name for wireless interface
> From: jratl...@bluemarble.net > To: 'Dejan Jocic' , debian-user@lists.debian.org > > Create file /etc/udev/rules.d/70-persistent-net.rules > > Add line: > > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="[MAC_ADDRESS]", ATTR{dev_id}=="0x0", ATTR{type}=="1", > KERNEL=="wl*", NAME="wlan0" > > Replace [MAC_ADDRESS] with the MAC address of your wireless card. Reboot. > > This worked for me on a wired card with my MAC and changing KERNEL="wl*" to > KERNEL="en*" on a bhyve Debian 9 guest. > > -----Original Message- > From: Dejan Jocic [mailto:jode...@gmail.com] > Sent: Sunday, August 13, 2017 3:09 AM > To: debian-user@lists.debian.org > Subject: Re: name for wireless interface > > On 12-08-17, pe...@easthope.ca wrote: >> A TL-WN722N adapter connected to a stretch system gives these results. >> >> peter@imager:~$ lsusb | grep Ath >> Bus 002 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 >> 802.11n >> >> root@imager:/home/peter# iwlist scan >> wlxa0f3c10a28f7 Interface doesn"t support scanning : Network is down >> >> lo Interface doesn"t support scanning. >> >> eth0 Interface doesn"t support scanning. >> >> What is the origin of the long name, wlxa0f3c10a28f7? >> Can a shorter name be assigned? >> >> Thanks, ... Peter E. >> >> >> -- >> >> 123456789 123456789 123456789 123456789 123456789 123456789 123456789 >> Tel: +1 360 639 0202 Pender Is.: +1 250 629 3757 >> http://easthope.ca/Peter.html Bcc: peter at easthope. ca >> > > It was asked many times on this list, and all around generally. Best answer > would be to look here: > > https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfac > eNames/ > > It has full explanation of why those long names and what to do if you do not > like it. It is easy to assign shorter name, if you wish so and is explained > nicely, with 3 possible methods. Neither the document or any of you have explained to me why on a single session the same interface for a wireless connection would repeatedly change names. wlan0 wlan0mon wlan0monmon .. Because on a different distribution the interfaces are enp0s25 for wire wlp0s29f7u5 for wireless and never change or drop their connection like debian has been doing for a while. I go in Debian and try to do an update and upgrade in case the problem goes away on its own. When the connection gets dropped I leave and try again another day. Did I mention that none of my other systems have systemd! I have no idea whether it is related.
RE: name for wireless interface
Create file /etc/udev/rules.d/70-persistent-net.rules Add line: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="[MAC_ADDRESS]", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wl*", NAME="wlan0" Replace [MAC_ADDRESS] with the MAC address of your wireless card. Reboot. This worked for me on a wired card with my MAC and changing KERNEL="wl*" to KERNEL="en*" on a bhyve Debian 9 guest. -Original Message- From: Dejan Jocic [mailto:jode...@gmail.com] Sent: Sunday, August 13, 2017 3:09 AM To: debian-user@lists.debian.org Subject: Re: name for wireless interface On 12-08-17, pe...@easthope.ca wrote: > A TL-WN722N adapter connected to a stretch system gives these results. > > peter@imager:~$ lsusb | grep Ath > Bus 002 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 > 802.11n > > root@imager:/home/peter# iwlist scan > wlxa0f3c10a28f7 Interface doesn't support scanning : Network is down > > loInterface doesn't support scanning. > > eth0 Interface doesn't support scanning. > > What is the origin of the long name, wlxa0f3c10a28f7? > Can a shorter name be assigned? > > Thanks, ... Peter E. > > > -- > > 123456789 123456789 123456789 123456789 123456789 123456789 123456789 > Tel: +1 360 639 0202 Pender Is.: +1 250 629 3757 > http://easthope.ca/Peter.html Bcc: peter at easthope. ca > It was asked many times on this list, and all around generally. Best answer would be to look here: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfac eNames/ It has full explanation of why those long names and what to do if you do not like it. It is easy to assign shorter name, if you wish so and is explained nicely, with 3 possible methods.
Re: name for wireless interface
On 12-08-17, pe...@easthope.ca wrote: > A TL-WN722N adapter connected to a stretch system gives these results. > > peter@imager:~$ lsusb | grep Ath > Bus 002 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n > > root@imager:/home/peter# iwlist scan > wlxa0f3c10a28f7 Interface doesn't support scanning : Network is down > > loInterface doesn't support scanning. > > eth0 Interface doesn't support scanning. > > What is the origin of the long name, wlxa0f3c10a28f7? > Can a shorter name be assigned? > > Thanks, ... Peter E. > > > -- > > 123456789 123456789 123456789 123456789 123456789 123456789 123456789 > Tel: +1 360 639 0202 Pender Is.: +1 250 629 3757 > http://easthope.ca/Peter.html Bcc: peter at easthope. ca > It was asked many times on this list, and all around generally. Best answer would be to look here: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ It has full explanation of why those long names and what to do if you do not like it. It is easy to assign shorter name, if you wish so and is explained nicely, with 3 possible methods.
Re: name for wireless interface
pe...@easthope.ca writes: > A TL-WN722N adapter connected to a stretch system gives these results. > > peter@imager:~$ lsusb | grep Ath > Bus 002 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n > > root@imager:/home/peter# iwlist scan > wlxa0f3c10a28f7 Interface doesn't support scanning : Network is down > > loInterface doesn't support scanning. > > eth0 Interface doesn't support scanning. > > What is the origin of the long name, wlxa0f3c10a28f7? > Can a shorter name be assigned? > https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#new-interface-names -- regards, kushal
Re: name for wireless interface
* From: Fungi4All * Date: Sat, 12 Aug 2017 18:38:05 -0400 > ... given up worrying about this madness. > ... > You tell me what is wrong. Unfortunately I can't spare more time for work on it this week. If we're lucky, it will be solved before the next release. Thanks for replying. Now I know that this problem is not so unusual. Regards,... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 Tel: +1 360 639 0202 Pender Is.: +1 250 629 3757 http://easthope.ca/Peter.html Bcc: peter at easthope. ca
Re: name for wireless interface
> From: pe...@easthope.ca > To: debian-user@lists.debian.org > pe...@easthope.ca > > A TL-WN722N adapter connected to a stretch system gives these results. > > peter@imager:~$ lsusb | grep Ath > Bus 002 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n > > root@imager:/home/peter# iwlist scan > wlxa0f3c10a28f7 Interface doesn"t support scanning : Network is down > > lo Interface doesn"t support scanning. > > eth0 Interface doesn"t support scanning. > > What is the origin of the long name, wlxa0f3c10a28f7? > Can a shorter name be assigned? I can not help much and I have given up worrying about this madness. I have two debian installations, one has been on for years. The one is testing the other unstable and previously have never had problems with either one. Lately neither one has been able to maintain a wifi connection for long and takes 2-3' to boot up. I took J.Johnson's recommendation to play around with ifconfig -a and ifconfig wlan0 up from console. The first time I run it the interface was listed as wlan0 The second run it became wlan0mon The third it became wlan0monmon I barely get enough time to run an update/upgrade on both installation and then it is down hill from there. NOW I have 4 more installations on the same machine, as I keep debian for sentimental reasons only. None of the four different installations have had ANY connection problems, same machine, same wifi device, same connection. The two are devuan-based the other two are Arch based. NONE have systemd on them, only Debian does. You tell me what is wrong. Setup is about the same, wicd is on all of them.
name for wireless interface
A TL-WN722N adapter connected to a stretch system gives these results. peter@imager:~$ lsusb | grep Ath Bus 002 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n root@imager:/home/peter# iwlist scan wlxa0f3c10a28f7 Interface doesn't support scanning : Network is down loInterface doesn't support scanning. eth0 Interface doesn't support scanning. What is the origin of the long name, wlxa0f3c10a28f7? Can a shorter name be assigned? Thanks, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 Tel: +1 360 639 0202 Pender Is.: +1 250 629 3757 http://easthope.ca/Peter.html Bcc: peter at easthope. ca