Modify

Opened 8 years ago

Closed 8 years ago

#6911 closed defect (wontfix)

wrt160nl possible switch issue with native vlan

Reported by: anonymous Owned by: juhosg
Priority: normal Milestone: Backfire 10.03
Component: packages Version: Backfire 10.03 Beta
Keywords: Cc: brandon@…

Description

I am having some problems with using native vlans and the wrt160nl.

My network has two vlans one is the native vlan sent from another openwrt box and a second tagged vlan2. My goal is to bridge vlan2 to wifi and bridge the default vlan to the physical ethernet ports (eth0).

Basically reducing the box to a fancy managed switch with wifi bridge.

But, I am having some problems:

# Start with my interfaces down

root@OpenWrt:/# /sbin/ifconfig
mon.wlan0 Link encap:UNSPEC HWaddr 00-23-69-EC-E8-0D-00-00-00-00-00-00-00-00-00-00

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:76 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6245 (6.0 KiB) TX bytes:0 (0.0 B)

root@OpenWrt:/# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface

# Bring the WAN up, then eth1.2 then wifi

root@OpenWrt:/# ifconfig eth1 up

eth1: link up (100Mbps/Full duplex)

root@OpenWrt:/# ifconfig eth1.2 up
root@OpenWrt:/# wifi
Configuration file: /var/run/hostapd-phy0.conf
device wlan0 entered promiscuous mode
Using interface wlan0 with hwaddr 00:23:69:ec:e8:0d and ssid 'bikini_top'
br-lan: port 1(wlan0) entering learning state
device wlan0 left promiscuous mode
br-lan: port 1(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 1(wlan0) entering learning state
root@OpenWrt:/# brctl addif br-lan eth1.2

# And I am connected via WIFI to vlan2 over wifi

However, if I try to bridge eth0 and eth1 together the wifi bridge to vlan2 no longer works from my laptop.

root@OpenWrt:/# brctl addbr br-slan
root@OpenWrt:/# brctl addif br-slan eth0
root@OpenWrt:/# brctl addif br-slan eth1

# Connection stops working here

root@OpenWrt:/# ifconfig br-slan up

# So I tear it down

root@OpenWrt:/# ifconfig br-slan down
root@OpenWrt:/# brctl delbr br-slan
root@OpenWrt:/# ifconfig eth1 up

And everything wifi to vlan2 works again.

Having eth1 up on its own with the wifi bridge running works fine:

root@OpenWrt:/# ifconfig eth1 192.168.2.44 up
root@OpenWrt:/# ping 192.168.2.2
64 bytes from 192.168.2.2: seq=0 ttl=60 time=9.706 ms

I "fixed" the issue by not using a default vlan and tagging both vlan0 and vlan2. Then bridging eth1.0 eth0 and eth1.2 and wlan0.

Willing to test and hack. Just no time today since I needed to get this working to proceed with paid work :)

Attachments (0)

Change History (3)

comment:1 Changed 8 years ago by Brandon Philips

Hrm, just noticed this posted anonymously. If you want to ping me find my details here: http://ifup.org/contact/.

comment:2 Changed 8 years ago by thepeople

  • Owner changed from developers to juhosg
  • Status changed from new to assigned

comment:3 Changed 8 years ago by nbd

  • Cc brandon@… added
  • Resolution set to wontfix
  • Status changed from assigned to closed

This is not a problem of the switch, this has to do with the order in which various parts of the Linux network stack process incoming frames.

If you have eth1 in a bridge, then the bridging layer grabs frames before they make it to the 802.1q subsystem.

You should simply stick to not mixing untagged and tagged interfaces of the same device when using bridging.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.