Am 16.03.2015 um 12:53 schrieb David Herrmann:
I don't see how we can fix that via name_assign_type. Sure, we could
set this to NET_NAME_PREDICTABLE and udev would no longer rename it.
But the name is *NOT* predictable, so it would be a hack.
The other fix would be to tell udev to never
Hi
On Mon, Mar 16, 2015 at 11:09 AM, Tom Gundersen t...@jklm.no wrote:
On Mon, Mar 16, 2015 at 11:01 AM, Thomas Richter t...@math.tu-berlin.de
wrote:
Am 16.03.2015 um 10:53 schrieb Tom Gundersen:
On Mon, Mar 16, 2015 at 10:34 AM, Thomas Richter t...@math.tu-berlin.de
wrote:
The laptop in
On Mon, Mar 16, 2015 at 8:26 AM, Thomas Richter t...@math.tu-berlin.de wrote:
Hi folks,
udev seems to create a problem here with the hostap (prism2) kernel
driver. Unlike many wifi devices, the hostap device driver always
creates paired interfaces, a raw interface (wifiX) and a network
Am 16.03.2015 um 16:28 schrieb David Herrmann:
However, it would be nice if you could describe your issues in more
detail. In particular, I cannot see any wifiX to wlanX issue. The
hostap driver exports a wlanX device as a base and multiple
sub-devices with a special suffix if requested by
Hi
On Mon, Mar 16, 2015 at 5:35 PM, Michael Biebl mbi...@gmail.com wrote:
2015-03-16 17:25 GMT+01:00 David Herrmann dh.herrm...@gmail.com:
Hi
On Mon, Mar 16, 2015 at 4:48 PM, Thomas Richter t...@math.tu-berlin.de
wrote:
If udev comes into play, it renames wlan0 to wlan1, because wlan0 was
2015-03-16 17:25 GMT+01:00 David Herrmann dh.herrm...@gmail.com:
Hi
On Mon, Mar 16, 2015 at 4:48 PM, Thomas Richter t...@math.tu-berlin.de
wrote:
If udev comes into play, it renames wlan0 to wlan1, because wlan0 was
already taken from a previously installed ipw2200 card that is no longer
Hi
On Mon, Mar 16, 2015 at 4:48 PM, Thomas Richter t...@math.tu-berlin.de wrote:
If udev comes into play, it renames wlan0 to wlan1, because wlan0 was
already taken from a previously installed ipw2200 card that is no longer
in the system. Hence, I have now the network interfaces wifi0 and
Am 16.03.2015 um 17:25 schrieb David Herrmann:
Ok, forget my previous mail, your issue is only related to the wext
driver, not the hostap extensions.
Up front, upstream udev never renames wlan0 to wlan1. This is a
downstream problem.
The problem is the following:
Kernel hostap creates
Hi
On Mon, Mar 16, 2015 at 1:04 PM, Thomas Richter t...@math.tu-berlin.de wrote:
Am 16.03.2015 um 12:53 schrieb David Herrmann:
I don't see how we can fix that via name_assign_type. Sure, we could
set this to NET_NAME_PREDICTABLE and udev would no longer rename it.
But the name is *NOT*
Hi folks,
udev seems to create a problem here with the hostap (prism2) kernel
driver. Unlike many wifi devices, the hostap device driver always
creates paired interfaces, a raw interface (wifiX) and a network
interface (wlanX) that represents the configured network.
Unfortunately, udev (or
On Mon, Mar 16, 2015 at 10:26 AM, Thomas Richter t...@math.tu-berlin.de wrote:
Hi folks,
udev seems to create a problem here with the hostap (prism2) kernel
driver. Unlike many wifi devices, the hostap device driver always
creates paired interfaces, a raw interface (wifiX) and a network
On Mon, Mar 16, 2015 at 08:26:00AM +0100, Thomas Richter wrote:
Hi folks,
udev seems to create a problem here with the hostap (prism2) kernel
driver. Unlike many wifi devices, the hostap device driver always
creates paired interfaces, a raw interface (wifiX) and a network
interface
Am 16.03.2015 um 09:04 schrieb Greg KH:
On Mon, Mar 16, 2015 at 08:26:00AM +0100, Thomas Richter wrote:
Hi folks,
udev seems to create a problem here with the hostap (prism2) kernel
driver. Unlike many wifi devices, the hostap device driver always
creates paired interfaces, a raw interface
On Mon, Mar 16, 2015 at 09:32:17AM +0100, Thomas Richter wrote:
Am 16.03.2015 um 09:04 schrieb Greg KH:
On Mon, Mar 16, 2015 at 08:26:00AM +0100, Thomas Richter wrote:
Hi folks,
udev seems to create a problem here with the hostap (prism2) kernel
driver. Unlike many wifi devices, the
On Sun, Mar 15, 2015 at 1:40 PM, Thomas Richter t...@math.tu-berlin.de wrote:
udev seems to create a problem here with the hostap (prism2) kernel driver.
Unlike many wifi devices, the hostap device driver always creates paired
interfaces, a raw interface (wifiX) and a network interface (wlanX)
Hi folks,
udev seems to create a problem here with the hostap (prism2) kernel
driver. Unlike many wifi devices, the hostap device driver always
creates paired interfaces, a raw interface (wifiX) and a network
interface (wlanX) that represents the configured network.
Unfortunately, udev (or
On 15.03.2015 15:38, Kay Sievers wrote:
Hi Kay,
grep ./sys/class/net/*/name_assign_type
grep: /sys/class/net/eth0/name_assign_type: Invalid argument
grep: /sys/class/net/lo/name_assign_type: Invalid argument
grep: /sys/class/net/wifi0/name_assign_type: Invalid argument
grep:
17 matches
Mail list logo
