How to correct install a USB Network interface on PfSense 2.4.5

[kiokoman]

@sscleber
it's Realtek not realtek
case sensitive

[sscleber]

@kiokoman
yes, did both of option..

[kiokoman]

@sscleber
uhm pretty much you are screwed

but past here the output of
usbconfig dump_device_desc

maybe remove that device and do a

dmesg

attach it again and do a dmesg again, copy/past here the output if something new is reported from dmesg
if nothing is reported than the type-c port is not recognized by pfsense

[bingo600]

@kiokoman said in How to correct install a USB Network interface on PfSense 2.4.5:

@sscleber
it's Realtek not realtek
case sensitive

grep -i

/Bingo

[sscleber]

@kiokoman

[bingo600]

That seems to be one of the EL'cheapo adapters

https://github.com/bzapal/usb-2-10-100m-ethernet-adapter-rd9700

Seems to be in FreeBSD 11 Stable

http://fxr.watson.org/fxr/source/dev/usb/usbdevs?v=FREEBSD-11-STABLE;im=3
vendor KONTRON 0x0fe6 Kontron AG
product KONTRON JP1082 0x9700 USB Ethernet

Edit:
It seems like it gives you the info that @kiokoman mentions here
https://forum.netgate.com/post/951370

Try to do as he describes

/Bingo

[kiokoman]

@bingo600
maybe it's another usb adapter, it's not the ue300c he mentioned on the first post

[stephenw10]

Maybe it's TP-Link just using whatever chipset they fancy and marking it v2 in tiny tiny letters.

But that is in 2.4.5:
https://github.com/pfsense/FreeBSD-src/blob/RELENG_2_4_5/sys/dev/usb/usbdevs#L2637

Should be supported by udav(4):
https://github.com/pfsense/FreeBSD-src/blob/RELENG_2_4_5/sys/dev/usb/net/if_udav.c#L179

Which is included in 2.4.5:

[2.4.5-RELEASE][admin@t70.stevew.lan]/root: kldstat -vv | grep udav
		395 udav/miibus
		394 uhub/udav

So, yeah, plug it in then check dmesg and the system log.

Steve

[Gertjan]

This means :

what ?

I do not see "FreeBSD" in that list.

Questions related to this device and 'pfsense' can be found on amazon.
Even this : https://static.amazon.fr/ask/questions/TxX2AE7DBIDUXI/ref=ask_ql_ql_al_hza ( with a possible solution ? )

[stephenw10]

I think this line indicates it only has one config index:

bNumConfigurations = 0x0001

So not possible to set a different one as linked there.

But, I agree, this looks like it might be the cheaper device. The TP-Link NIC may well work by setting an alternate config index. @sscleber ?

Steve