On Sun, Oct 7, 2018 at 2:39 AM solarflow99 <[email protected]> wrote:
>
> I'll update and try, but I don't think it will help, I noticed this problem 
> since F25+ days.

Fedora 25 was the first release we supported the Raspberry Pi
officially and I know of numerous people using vlans with various RPi
since then. Also there's a lot of changes in general between most
major releases of the kernel so I don't necessarily agree with your
sentiment there, and in terms of support the 4.17 kernel is dead.

>> On Fri, Oct 5, 2018 at 8:24 PM solarflow99 <[email protected]> wrote:
>> >
>> > well i'll be, it works for you.  I wonder if it could be a hardware 
>> > problem then, this is really weird.
>> > 4.17.3-200.fc28.armv7hl
>>
>> Th 4.17.3 kernel is ancient, any reason not to move to 4.18.x (we're
>> currently at 4.18.11 as stable, and 4.18.12 in testing) as they have a
>> lot of CVEs fixed and other issues.
>>
>> > On Thu, Oct 4, 2018 at 1:07 AM Peter Robinson <[email protected]> wrote:
>> >>
>> >> On Thu, Oct 4, 2018 at 1:12 AM solarflow99 <[email protected]> wrote:
>> >> >
>> >> > Does anyone need any more info?  I suspect this is a bug.
>> >>
>> >> I've just run exactly the same commands as you on my network, I don't
>> >> have a trunk configured I could plug the RPi2 into to see if it worked
>> >> but the output looks sane to me:
>> >>
>> >> # ip link add link eth0 name eth0.1 type vlan id 1
>> >> # ip l
>> >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>> >> mode DEFAULT group default qlen 1000
>> >>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> >> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
>> >> state UP mode DEFAULT group default qlen 1000
>> >>     link/ether b8:27:eb:db:ff:1b brd ff:ff:ff:ff:ff:ff
>> >> 3: eth0.1@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
>> >> mode DEFAULT group default qlen 1000
>> >>     link/ether b8:27:eb:db:ff:1b brd ff:ff:ff:ff:ff:ff
>> >> # 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:db:ff:1b brd ff:ff:ff:ff:ff:ff promiscuity 0
>> >>     vlan protocol 802.1Q id 1 <REORDER_HDR> numtxqueues 1 numrxqueues
>> >> 1 gso_max_size 65536 gso_max_segs 65535
>> >>
>> >> # nmcli d
>> >> DEVICE  TYPE      STATE      CONNECTION
>> >> eth0    ethernet  connected  eth0
>> >> lo      loopback  unmanaged  --
>> >> eth0.1  vlan      unmanaged  --
>> >>
>> >> # lsmod | grep q
>> >> 8021q                  32768  0
>> >> garp                   16384  1 8021q
>> >> mrp                    20480  1 8021q
>> >>
>> >> This is Fedora 29 with 4.18.11-301.fc29 kernel, I don't see mention of
>> >> which Fedora/kernel you have.
>> >>
>> >> Peter
>> >>
>> >> > On Mon, Oct 1, 2018 at 4:06 PM solarflow99 <[email protected]> 
>> >> > wrote:
>> >> >>
>> >> >> oh sorry for making it sound like that, I didn't want to be rude at 
>> >> >> all.  I have a raspi 2 model B, it says Broadcom BCM2836, is there any 
>> >> >> other info you might still need?
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Mon, Oct 1, 2018 at 3:52 PM Peter Robinson <[email protected]> 
>> >> >> wrote:
>> >> >>>
>> >> >>> On Mon, Oct 1, 2018 at 11:36 PM solarflow99 <[email protected]> 
>> >> >>> wrote:
>> >> >>> >
>> >> >>> > 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.
>> >> >>>
>> >> >>> 1) you didn't mention anywhere that it was the raspberry pi
>> >> >>> 2) they don't just come on the Raspberry Pi
>> >> >>> 3) they can have different PHYs and other such things that can affect 
>> >> >>> details.
>> >> >>>
>> >> >>> I don't ask these questions for the sake of it, if you want assistance
>> >> >>> there's no need to be rude.
>> >> >>>
>> >> >>> Peter
>> >> >>>
>> >> >>> >
>> >> >>> > On Sun, Sep 30, 2018 at 11:55 PM Peter Robinson 
>> >> >>> > <[email protected]> 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 -- [email protected]
>> >> >>> >> > To unsubscribe send an email to [email protected]
>> >> >>> >> > 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/[email protected]
_______________________________________________
arm mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]

Reply via email to