It is worth mentioning that the ONLY reason why this worked is because
the vendor has provided a serial number. Most vendors don't and it
would not have worked then.
devd NEEDS to be able to see device MAC addresses!
___
freebsd-net@freebsd.org mailing l
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
> ===
> I tried that as well, but $device-name is empty.
>
> If I do this:
>
> notify 1000 {
> match "system" "USB";
> match "subsystem" "INTERFACE";
> match "vendor" "0x0b95";
> match "product" "0x1790";
> match "sernum" "249B0DE00C";
> match "type" "ATTACH";
I am actually one step closer.
With the following I can get the device-name "axge0", but I don't know how to
create
a usable NIC interface name for that.
attach 1000 {
device-name "axge[0-9]+";
match "vendor" "0x0b95";
match "product" "0x1790";
match "sernum" "249B0DE00C";
>
> I would use three of these sections, one with the serial number of each
> interface. So:
>
> action "ifconfig $device-name name wan inet ..."
> action "ifconfig $device-name name dmz inet ..."
> action "ifconfig $device-name name lan inet ..."
>
> Then the interface names can be easily used in
>> This is what I got with the output of messages. I don't know how to either
>> give the device another unique name or somehow intercept what is happening
>> so that I can set the device name.
>>
>> notify 1000 {
>> match "system" "USB";
>> match "subsystem" "INTERFACE";
>> match "
> It might need a delay before the device is ready. Running devd in the
> foreground like that will show all the detected events.
Indeed that helped.
This is what I got with the output of messages. I don't know how to either give
the device another unique name or somehow intercept what is happe
I have tried setting this up in /usr/local/etc/devd/devd.conf and used "devd
-d" to re-read rules.
attach 100 {
device-name "ue0";
match "vendor" "0x0b95";
match "product" "0x1790";
match "sernum" "249b0de00c";
action "ifconfig $device-name inet
>> This is a major problem as the device *still* has the right name and the
>> right IP, but it is as though it has been physically removed from the
>> slot and changed place.
>>
>> Is it somehow possible to deal with this problem?
>>
>> pciconf doesn't display those devices.
>
> usbconfig wil
Hi
I got a small Intel Atom N280 box I wanted to use as a PF firewall.
It has one Intel NIC that gets registered as "bge0", then it has three
USB->NIC dongles with the ASIX AX88179 chipset which gets registered
as "ue0", "ue1" and "ue2".
I have set each device to a static IP during boot.
The pr
10 matches
Mail list logo
