[gobolinux-users] weird network behaviour

Jonas Karlsson jonka750 at student.liu.se
Fri Jun 29 20:42:35 UTC 2007

On Fri, 29 Jun 2007 21:53:46 +0200, kenneth marken <k-marken at online.no> wrote:

> On Friday 29 June 2007 21:23:40 kenneth marken wrote:
>> On Friday 29 June 2007 21:22:04 demian florentin wrote:
>> > I guess your mac address is also constantly changing, therefore ethN also
>> > changes, if that's the case you should make an udev rule telling udev to
>> > keep a mac address for that card.
>> > I've never done it in gobolinux but i assume you should add a rule to
>> > /System/Settings/udev/rules.d.
>> > this link might help:
>> > http://reactivated.net/writing_udev_rules.html
>> hmm, weird that i should keep changing...
>> ill have to look into it, thanks. i just didnt expect it to be issued a new
>> eth each time.
> yep, its udev thats acting up allright. seems one of its scripts keep adding
> to one of the others.
> a quick hack for me would be to nuke the one that keeps setting the eth*
> entries as i have no idea how the udev script works.
> as in, both card have the same mac maintained, but each time the driver is
> modprobed in the script triggers and writes out a new line in the script
> thats supposed to maintain the eth across reboots. funny thing is that while
> firewire kept getting eth0 (even if it had as many entries in the script file
> as my true ethernet card) the ethernet card got a new eth each time.
What scripts are you talking about? Is it any of our scripts or is it udev?

> ugh, udev scripts are deep waters for me :(

If it's scripts it might not be udev, as udev is mostly rules.


Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

More information about the gobolinux-users mailing list