udev and network devices

udev and network devices

[Michel Rode]

[-- Attachment #1: Type: text/plain, Size: 373 bytes --]

Hello,

i tried to rename my network device - this works, but the symlink are not exists.

This is my rule:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:6f:b5:8b:76", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0", SYMLINK+="eth1"

Now i have the idea, that it could not work because there are not such device in /dev - is it true ?

Thanks, Michel

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: udev and network devices

[Kay Sievers]

On Sat, Nov 15, 2008 at 11:02, Michel Rode <rmichel@devnu11.net> wrote:
> i tried to rename my network device - this works, but the symlink are not exists.
>
> This is my rule:
> SUBSYSTEM="net", ACTION="add", DRIVERS="?*", ATTR{address}="00:16:6f:b5:8b:76", ATTR{type}="1", KERNEL="eth*", NAME="wlan0", SYMLINK+="eth1"
>
> Now i have the idea, that it could not work because there are not such device in /dev - is it true ?

Right, network interfaces do not have any device nodes. The interface
names exist only in the kernel. There is only one name per interface
and nothing similar to the concept of symlinks.

Kay

Re: udev and network devices

[Matthew Dharm]

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

On Sat, Nov 15, 2008 at 02:19:25PM +0100, Kay Sievers wrote:
> On Sat, Nov 15, 2008 at 11:02, Michel Rode <rmichel@devnu11.net> wrote:
> > i tried to rename my network device - this works, but the symlink are not exists.
> >
> > This is my rule:
> > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:6f:b5:8b:76", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0", SYMLINK+="eth1"
> >
> > Now i have the idea, that it could not work because there are not such device in /dev - is it true ?
> 
> Right, network interfaces do not have any device nodes. The interface
> names exist only in the kernel. There is only one name per interface
> and nothing similar to the concept of symlinks.

What about aliased interfaces?  Or are those really considered separate
devices?

Matt

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

C:  Like the Furby?
DP: He gives me the creeps.  Think the SPCA will take him?
					-- Cobb and Dust Puppy
User Friendly, 1/2/1999

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: udev and network devices

[Kay Sievers]

On Sat, Nov 15, 2008 at 20:09, Matthew Dharm
<mdharm-usb@one-eyed-alien.net> wrote:
> On Sat, Nov 15, 2008 at 02:19:25PM +0100, Kay Sievers wrote:
>> On Sat, Nov 15, 2008 at 11:02, Michel Rode <rmichel@devnu11.net> wrote:
>> > i tried to rename my network device - this works, but the symlink are not exists.
>> >
>> > This is my rule:
>> > SUBSYSTEM="net", ACTION="add", DRIVERS="?*", ATTR{address}="00:16:6f:b5:8b:76", ATTR{type}="1", KERNEL="eth*", NAME="wlan0", SYMLINK+="eth1"
>> >
>> > Now i have the idea, that it could not work because there are not such device in /dev - is it true ?
>>
>> Right, network interfaces do not have any device nodes. The interface
>> names exist only in the kernel. There is only one name per interface
>> and nothing similar to the concept of symlinks.
>
> What about aliased interfaces?  Or are those really considered separate
> devices?

It's a bit different. Aliases carry their own information and state,
they are usually used to assign different IP addresses to an
interface. Symlinks to device nodes have no further meaning as their
name, and just point to the "real" device, without any own properties.

Kay