lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 5 Jan 2014 01:13:53 +0100 (CET)
From:	Herbert Rosmanith <>
Subject: 3.11.10: rtl8192cu device name, kernel crash

hello list,

this afternoon I bought a new usb/wlan adapter, which identifies 
itself as:

    # lsusb
    Bus 001 Device 017: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter

the first thing I noticed is that the device name is renamed:

    [ 4444.688299] systemd-udevd[3090]: renamed network interface wlan1 to wlp0s29f7u4u4u2

Excellent! I always hated that userfriendly and easy to remember names like "wlan1".
Finally I have a more sophisticated name, "wlp0s29f7u4u4u2" that strictly follows
The Tao Of Terribly Silly Device Naming.

Additionally, iwconfig and ifconfig cannot decide upon the device name.
While iwconfig sees "wlp0s29f7u4u4u2", ifconfig is a bit short-sighted and 
only sees "wlp0s29f7".
The problem is that none of the two devicenames can be used for configuring it:

    # dhclient -d wlp0s29f7
    SIOCSIFADDR: No such device
    wlp0s29f7: ERROR while getting interface flags: No such device
    wlp0s29f7: ERROR while getting interface flags: No such device
    Bind socket to interface: No such device


     # dhclient -d wlp0s29f7u4u4u2
     Bind socket to interface: No such device

Renaming "wlp0s29f7u4u4u2" back to "wlan1" will make the adapter known to
dhclient/ifconfig (finally udev can do something useful), but not without
crashing the system in between: I added the mac-addr. to the
persistent-net udev-rules, did a /etc/init.d/udev restart,
and removed the adapter from the usb hub. Instantly, the system froze, I had to
push the power button to get it back. This was the 2nd time the system
crashed, the first time on the console: it was some kernel panic. As the system
didn't react anymore, I did not bother to write down the lengthy panic message.

By the way, kernel version is 3.11.10.
As the device is handled by the rtl8192cu module, which is not in the 
staging directory, it is considered stable, isn't it?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists