I think your remark is correct. I assume this is the situation after a reboot, meaning OpenWrt has read the config file.
I would be really unlikely that the script resposible to set the switch parses in the wrong way the config file. You may want to set port 1 via swconfig that enables you to change the settings of the ports on the fly. 2015-04-18 17:09 GMT+02:00 Brian J. Murrell <[email protected]>: > On Sun, 2015-04-12 at 17:51 -0400, Aaron Z wrote: > > Try setting the vlan and vid for the guest network to 3 or 4. > > I tried vlan 5. vlans 0-3 are already in use here on various routers > for wan ports, etc. > > But no change. The port is still tagging the packets that are > configured in the switch to be untagged. > > But here is something interesting. Despite the switch configuration of: > > config switch > option reset '1' > option enable_vlan '1' > option name 'switch0' > > config switch_vlan > option vlan '1' > option vid '1' > option device 'switch0' > option ports '0t 1 2 3 4' > > config switch_vlan > option device 'switch0' > option vlan '2' > option ports '0t 1t' > option vid '5' > > The switch is still being configured to tag vlan 1 on port 1: > > # swconfig dev switch0 show > ... > VLAN 1: > vid: 1 > ports: 0t 1t 2 3 4 > VLAN 2: > vid: 5 > ports: 0t 1t > > Am I barking up the wrong tree? Is it just impossible to have both > tagged and an untagged VLANs on the same physical port? > > Cheers, > b. > > > _______________________________________________ > openwrt-users mailing list > [email protected] > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users > >
_______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
