Date: Thu, 04 Dec 2014 23:21:15 +0100 From: Martin Hanson <greencoppermine@yandex.com> To: Ian Smith <smithi@nimnet.asn.au> Cc: Warren Block <wblock@wonkity.com>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: NICs devices switches "pshycial" place on each boot (SOLVED) Message-ID: <151421417731675@web18h.yandex.ru> In-Reply-To: <20141204180007.Q85722@sola.nimnet.asn.au> References: <1511041417624247@web23g.yandex.ru> <alpine.BSF.2.11.1412031024340.32996@wonkity.com> <212351417642134@web20h.yandex.ru> <alpine.BSF.2.11.1412031601220.13301@wonkity.com> <2659291417665100@web17m.yandex.ru> <alpine.BSF.2.11.1412032119080.86447@wonkity.com> <2704971417669266@web25m.yandex.ru> <20141204180007.Q85722@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
I managed to get this working.
It is a dirty hack and I REALLY wish FreeBSD would make documentation
as high a priority as the guys at OpenBSD.
It is difficult to locate correct and updated documentation, especially
about devd. Yes, the man page has information about devd, and devd.conf
even come with examples, but those examples are too sparsome to be of
any real use when things get just a little bit complicated.
It is extremely frustration to spend hour of hours of wasted time
getting something to work, not because it doesn't work, but simply
because you're "throwing stones in the dark" in the hopes of hitting
the right target - because the correct and comprehensive documentation
is lacking.
A quality product HAS to have correct, updated and comprehensive
documentation. This is one point that really makes the OpenBSD guys
stand out deserving laud applause.
Now, the driver on OpenBSD didn't work, so I had to use FreeBSD because
that driver works, otherwise I would never had ventured into this
incredible time consuming task.
Warren Block, thank you a billion times for helping me with correct and
relevant information!
This is what I did to make it work. Like I said, it is a hack, but hey
it works.
attach 100 {
device-name "axge[0-9]+";
match "vendor" "0x0b95";
match "product" "0x1790";
match "sernum" "0000249B0DE00C";
# We need to wait a little for the interface to get up.
action "sleep 3";
# We don't know what number the interface has been assigned, but we know it is from axgeX,
# so we get the X, use it in "ueX" and then rename the interface which is then bound to the
# serialnumber, so the correct card will always get the right interface, ie. our own, not ueX.
action "ifconfig ue`echo $device-name | tr -dc '[0-9]'` name olan";
action "ifconfig olan inet 192.168.1.1 netmask 255.255.255.0";
};
I hope someone else might find this useful or perhaps even provide a cleaner approach.
Kind regards.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?151421417731675>