its listed below in the lsusb command, it would be the same one the raspi comes with not like I can add a different NIC.


On Sun, Sep 30, 2018 at 11:55 PM Peter Robinson <pbrobinson@gmail.com> wrote:
Hi,

> Hi, I used to be able to do with back around the F25 days and previous.  Now I can't do vlans at all anymore.  As you can see from the commands below the vlan id gets set to id 3068862004, and seems to keep auto incrementing itself, and the kernel module gets loaded but not used.  Does anyone have any ideas?

It should work, it would help if you mentioned the hardware you are
using as well as the NIC type/model.

> $ ip link add link eth0 name eth0.1 type vlan id 1
>
> $ ip -d addr show eth0.1
> 3: eth0.1@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
>     link/ether b8:27:eb:20:25:16 brd ff:ff:ff:ff:ff:ff promiscuity 3068862004
>     vlan protocol 802.1Q id 3068862004 <REORDER_HDR> numtxqueues 3068862004 numrxqueues 3068862004 gso_max_size 3068862004 gso_max_segs 3068862004
>
> $ lsmod | grep q
> Module                  Size  Used by
> 8021q                  28672  0
> garp                   16384  1 8021q
> mrp                    16384  1 8021q
>
> $ lsusb
> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
>
>
> _______________________________________________
> arm mailing list -- arm@lists.fedoraproject.org
> To unsubscribe send an email to arm-leave@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org