FS#1622 - DSA switch port vlan

Open
#8,499 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux
Domain
networking

Research direction

Start with the supplied network configuration and the DSA bridge path involving lan0, br-lan, and lan4.1, then reproduce the difference between traffic from lan0 and traffic from wlan0 or tun0. Done means a device connected to lan0 can communicate with the remote device through lan4.1 on the intended VLAN.

Written by the indexing model from the issue text.

Description

flyspray release/19.07

opotonil:

Device: Turris Omnia
Version: OpenWRT-18.06-rc1

Steps to reproduce:

Network configuration:

config interface 'lan'
option type 'bridge'
option ifname 'lan0 lan1 lan2 lan3 lan4.1'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'

config interface 'dmz'
option type 'bridge'
option ifname 'lan4.2'
option proto 'static'
option ipaddr '192.168.2.1'
option netmask '255.255.255.0'

From router, I have ping with the other device on both vlan:

ping -c 3 192.168.1.5

PING 192.168.1.5 (192.168.1.5): 56 data bytes
64 bytes from 192.168.1.5: seq=0 ttl=64 time=0.434 ms
64 bytes from 192.168.1.5: seq=1 ttl=64 time=0.335 ms
64 bytes from 192.168.1.5: seq=2 ttl=64 time=0.333 ms

--- 192.168.1.5 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.333/0.367/0.434 ms

ping -c 3 192.168.2.5

PING 192.168.2.5 (192.168.2.5): 56 data bytes
64 bytes from 192.168.2.5: seq=0 ttl=64 time=0.455 ms
64 bytes from 192.168.2.5: seq=1 ttl=64 time=0.341 ms
64 bytes from 192.168.2.5: seq=2 ttl=64 time=0.337 ms

--- 192.168.2.5 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.337/0.377/0.455 ms

But from other device connected to lan0 port I can't do ping. More exactly, the situation is the next:

  • All work as expected in the next cases:
    • movile -> tun0 (openvpn) -> br-lan -> lan4.1 (part of br-lan) -> remote device
    • tablet -> wlan0 (part of br-lan) -> lan4.1 (part of br-lan) -> remote device
  • It do not work as expected in the next case:
    • PC linux -> lan0 (part of br-lan) -> lan4.1 (part of br-lan) -> remote device
Dominant language
C
Stars
28.5k
Forks
13k
Avg merge
3d 1h
Merged PRs (30d)
160

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openwrt/openwrt

All issues in openwrt/openwrt

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.