Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

vlan tagged interfaces on ECW5211-L #31

Open
jmpolom opened this issue Jan 15, 2022 · 4 comments
Open

vlan tagged interfaces on ECW5211-L #31

jmpolom opened this issue Jan 15, 2022 · 4 comments
Assignees
@robimarko
Labels
question Further information is requested

Comments

@jmpolom
Copy link

jmpolom commented Jan 15, 2022 •
edited
Loading

Are VLAN tagged interfaces supported on the ECW5211-L?

After doing the following:

localhost ~ # ip l add link eth1 name vlan200 type vlan id 200
localhost ~ # ip l add link eth1 name vlan300 type vlan id 300
localhost ~ # ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br-lan qlen 1000
    link/ether 90:3c:b3:c6:98:08 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan qlen 1000
    link/ether 90:3c:b3:c6:98:09 brd ff:ff:ff:ff:ff:ff
4: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
    link/ether 90:3c:b3:c6:98:08 brd ff:ff:ff:ff:ff:ff
5: wl24g: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 90:3c:b3:c6:98:0a brd ff:ff:ff:ff:ff:ff
6: wl5g: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 90:3c:b3:c6:98:0b brd ff:ff:ff:ff:ff:ff
15: vlan200@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 90:3c:b3:c6:98:09 brd ff:ff:ff:ff:ff:ff
16: vlan300@eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 90:3c:b3:c6:98:09 brd ff:ff:ff:ff:ff:ff
localhost ~ # ip a add 10.40.50.60/24 dev vlan200
localhost ~ # ip a add 10.40.60.60/24 dev vlan300
localhost ~ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br-lan qlen 1000
    link/ether 90:3c:b3:c6:98:08 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan qlen 1000
    link/ether 90:3c:b3:c6:98:09 brd ff:ff:ff:ff:ff:ff
4: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
    link/ether 90:3c:b3:c6:98:08 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global br-lan
       valid_lft forever preferred_lft forever
    inet6 fe80::923c:b3ff:fec6:9808/64 scope link 
       valid_lft forever preferred_lft forever
5: wl24g: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 90:3c:b3:c6:98:0a brd ff:ff:ff:ff:ff:ff
6: wl5g: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 90:3c:b3:c6:98:0b brd ff:ff:ff:ff:ff:ff
15: vlan200@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
    link/ether 90:3c:b3:c6:98:09 brd ff:ff:ff:ff:ff:ff
    inet 10.40.50.60/24 scope global vlan200
       valid_lft forever preferred_lft forever
    inet6 fe80::923c:b3ff:fec6:9809/64 scope link 
       valid_lft forever preferred_lft forever
16: vlan300@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
    link/ether 90:3c:b3:c6:98:09 brd ff:ff:ff:ff:ff:ff
    inet 10.40.60.60/24 scope global vlan300
       valid_lft forever preferred_lft forever
    inet6 fe80::923c:b3ff:fec6:9809/64 scope link 
       valid_lft forever preferred_lft forever

Edit: Same results after ripping out default bridge br-lan:

localhost ~ # cat /etc/systemd/network/eth0.network 
[Match]
Name=eth0

[Network]
Address=192.168.1.1/24
VLAN=vlan200
localhost ~ # cat /etc/systemd/network/eth1.network 
[Match]
Name=eth1

[Network]
Address=192.168.2.1/24
localhost ~ # cat /etc/systemd/network/vlan200.netdev 
[NetDev]
Name=vlan200
Kind=vlan

[VLAN]
Id=200
localhost ~ # cat /etc/systemd/network/vlan200.network 
[Match]
Name=vlan200

[Network]
Address=10.40.50.60/24
localhost ~ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
    link/ether 90:3c:b3:c6:98:38 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::923c:b3ff:fec6:9838/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq qlen 1000
    link/ether 90:3c:b3:c6:98:39 brd ff:ff:ff:ff:ff:ff
4: vlan200@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue qlen 1000
    link/ether 90:3c:b3:c6:98:38 brd ff:ff:ff:ff:ff:ff
    inet 10.40.50.60/24 brd 10.40.50.255 scope global vlan200
       valid_lft forever preferred_lft forever
    inet6 fe80::923c:b3ff:fec6:9838/64 scope link 
       valid_lft forever preferred_lft forever
5: wl5g: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 90:3c:b3:c6:98:3b brd ff:ff:ff:ff:ff:ff
6: wl24g: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 90:3c:b3:c6:98:3a brd ff:ff:ff:ff:ff:ff

I'm unable to ping these addressed tagged interfaces from a connected system with a matching (verified working) configuration for 802.1q VLAN tagged interfaces on vlans 200 and 300. I also tried creating the tagged interfaces on the bridge br-lan but also was not successful pinging the tagged interfaces from the connected system. Seems like this does not work, at all.

Is this a known limitation of the current hardware support for the ECW5211-L?

cc: @storrgie
@robimarko
Copy link
Contributor

Hi Jon,
This is a limitation of the current driver, the DSA driver combo will remove those limits and allow normal HW offloaded VLAN filtering.
I plan to push the updated kernel with new drivers next week

@jmpolom
Copy link
Author

jmpolom commented Jan 15, 2022 •
edited
Loading

@robimarko thanks for the quick response! I will be watching for the new kernel to arrive here. I know the DSA driver was mentioned before, however I think I may have mistakenly thought it was already included in the builds.

@jpetrina jpetrina added the question Further information is requested label Jan 18, 2022
@robimarko
Copy link
Contributor

@jmpolom Updated kernel that contains DSA has been pushed.
CI has also already finished building:
https://drone.sartura.hr/artifacts/main/ecw5211-l-t/

@jmpolom
Copy link
Author

jmpolom commented Jan 19, 2022

@robimarko thanks for getting this out quickly. I will give this a try.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@robimarko robimarko

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jmpolom @robimarko @jpetrina