Modify

Opened 7 years ago

Closed 5 years ago

Last modified 4 years ago

#8458 closed defect (invalid)

rtl8366s vlans broken

Reported by: openwrt@… Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: base system Version: Backfire 10.03.1 RC4
Keywords: rtl8366s vlan Cc:

Description

on a Buffalo WZR-HP-G300NH with Backfire 10.03 this configuration:

config switch
        option name     rtl8366s
        option reset    1
        option enable_vlan 1

config switch_vlan vlan2
        option device   rtl8366s
        option vlan     2
        option ports    "0 1 2 5*"
        
config switch_vlan vlan3
        option device   rtl8366s
        option vlan     3
        option ports    "3* 5t"

gives me 2 separate VLANs that seem to work (tested only ping so far).

with Backfire 10.03.1-rc4 r24045 and the same configuration I can't ping an ip i configure on the box on any of these 2 vlans.

Am I missing something or did something break?

I'd also prefer to have a Trunk uplink (both vlans) on a single port, but this doesn't seem to work in either Backfire version. In 10.03 adding 0t to the ports option for vlan3 will break vlan2 on port 0.

Tom

Attachments (0)

Change History (6)

comment:1 Changed 7 years ago by anonymous

I can verify that this same switch/model is broken in 10.03.1-rc4, r24045.

If you try to configure just about anything other than the default configuration it kills connectivity, especially if you attempt to do tagged traffic.

Merely doing a "swconfig dev rtl8366s vlan 10 ports "3t 5t" will kill it.

Moreover, if you run swconfig, you find that in addition to the default vlan 1 untagged on all ports, you have vlan 2 untagged on both 1 and 5, vlan 3 untagged on both 2 and 5, etc.

You can delete these unwanted vlans with swconfig without killing connectivity but they will reappear. If you put sections in /etc/config/network for them and leave out the ports line, or put in a ports value of you can boot and get in, but the vlans will still exist. If you try to put anything else (like "5" or "5t") in these vlans it will hose up after answering 3 or 4 pings.

Removing ports other than 5 from vlan 1 and placing them untagged in their own vlan without an uplink is the only configuration that seems not to wedge the entire stack.

As to whether it is crashing or just hosing the networking I cannot tell -- even the WAN port goes dark so I am guessing the former.

comment:2 Changed 7 years ago by anonymous

Followup on this: the WAN port was not hosing up, that was my error. So I was able to get in and play with this some more.

It seems you can indeed configure tagged ports with swconfig, but then after that you have to re-issue the untagged configuration for vlan 1. Not sure if there is anything special there about vlan 1, that's just what I was testing with.

From a fresh boot the vlan config is this:
VLAN 1:

info: VLAN 1: Ports: '012345', members=003f, untag=003f, fid=0
ports: 0 1 2 3 4 5

VLAN 2:

info: VLAN 2: Ports: '15', members=0022, untag=0022, fid=0
ports: 1 5

VLAN 3:

info: VLAN 3: Ports: '25', members=0024, untag=0024, fid=0
ports: 2 5

VLAN 4:

info: VLAN 4: Ports: '35', members=0028, untag=0028, fid=0
ports: 3 5

VLAN 5:

info: VLAN 5: Ports: '45', members=0030, untag=0030, fid=0
ports: 4 5

The device was attached to the LAN via port 0 on the switch.

# swconfig dev rtl8366s vlan 1 set ports "0 1 4 5"
... LAN address still pinging at this point ...

#swconfig dev rtl8366s vlan 10 set ports "2t 5t"
... LAN address no longer responding to pings

# swconfig dev rtl8366s vlan 1 set ports "0 1 4 5"
... LAN address now responding to pings again.

... also note Ticket #7795 which shows this switch driver has had some similar issues in the past.

comment:3 Changed 7 years ago by anonymous

A possible workaround (see #8501): Try moving the vlan 3 stanza before the other VLANs so it is first. You may also have to add a vlan with port 3 defined as native (and turn it down). Hopefully LUCI will preserve this order.

comment:4 Changed 6 years ago by leeand00

And by stanza you mean...

comment:5 Changed 5 years ago by nbd

  • Resolution set to invalid
  • Status changed from new to closed

wrong vlan config, if i remember correctly, the cpu port is 4 and it needs to be tagged to enable proper vlan config.

comment:6 Changed 4 years ago by jow

  • Milestone changed from Backfire 10.03.2 to Chaos Calmer (trunk)

Milestone Backfire 10.03.2 deleted

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.