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 cr
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 reque
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
Am 16.03.2015 um 10:53 schrieb Tom Gundersen:
> On Mon, Mar 16, 2015 at 10:34 AM, Thomas Richter
> wrote:
>> The laptop in question had a ipw2200 card installed, which was
>> configured by udev as wlan0 (obviously). This card got replaced
>> (basically, due to another
Am 16.03.2015 um 09:54 schrieb Greg KH:
>>
>> It's regular PCI based prism2, thank you. I'm not expecting *you* to fix
>> things in prism2, for sure. This is not the hostap mailing list.
>
> Which exact kernel driver is this? I don't see a prism2 PCI driver in
> the latest kernel source tree, bu
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
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, ude
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: /sys/class/net/wl
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 h
