Re: [Devil-linux-develop] Feature request - Enable "nameif" to associate MAC address with correct interface name.

[Dominic R. <dl...@ed...>]

Regarding udev, I found info at 
http://www.reactivated.net/writing_udev_rules.html#why about how it 
works which mentions some udev tools - udevinfo, udevtest, udevtrigger, 
udevcontrol - which are missing in DL, and might be worth adding.

udevtrigger seems to be the way to reprocess udev rules without 
rebooting. Altering (or deleting) 70-persistent-net.rules + udevtrigger 
+ /etc/init.d/network restart should be a way to fix a broken network 
connection after a hardware change. At the moment I think you have to 
save-config and reboot instead of udevtrigger.

If this worked, then a new option could be added for the network script, 
say '-redetect' which would stop the network, delete 
70-persistent-net.rules, then run udevtrigger before starting the 
network again. It should also post an advisory message that the change 
will not persist under DL unless configuration is saved.

Dominic

On 26/04/2010 07:32, Frank Weis wrote:
> Hi,
>
> being a complete ignorant about how udev works internally, I wonder if
> it would be possible to put multiple entries in 70-persistent-net.rules,
> eg.
>
> ma:cc:ad:dr:es:s1 is eth0
> ma:cc:ad:dr:es:s2 is eth0
>
> ma:cc:ad:dr:es:s3 is eth1
> ma:cc:ad:dr:es:s4 is eth1
>
>
> Plan B:
> If that doesn't work (or can be hacked to work easily) I'd favour a
> solution which handles multiple etc-mods.tar.bz2 entirely. This would
> probably be interesting for other people/problems too (someone wanted to
> be able to roll back to the previous config recently)
>
> We'd need the following:
>
> *) save-config would need to be able to attach a label (that would go
> into the filename) and maybe a description.
>
> *) a way to specify which config is 'hot': there used to be boot options
> that specified where the config-file is and what it is called. See if
> it's still there and if it works.
>
> *) a tool to manage config files
> 	list,
> 	delete,
> 	copy,
> 	specify 'hot' file at next boot.
>
> What do you think? I'd be willing to invest some time into this if this
> can make us all happy...
>
> Frank
>
>
> Heiko Zuerker wrote:
>    
>> I took a quick look at our network init script.
>> I'm not sure about a good place to put the nameif line, since we may
>> required the module to be loaded first.
>> Honestly I'd rather stick with just the udev solution for now, but I'm
>> open to suggestions.
>>
>> Heiko
>>