Luci: unable to unconfigure device

Installing and Using OpenWrt
1

Hello all,

I have a situation in which I am unable to unconfigure a network device in Luci → Network → Interfaces → Devices. The button is simply disabled.

There are two of them and both are 802.1q devices. Both of these VLAN devices are working perfectly, though, and I really have no desire to unconfigure them, but I was just wondering under what circumstances will a network device become unconfigurable? Is there something wrong with my configuration?

I have other 802.1q devices also for which the unconfigure button is enabled.

So what might be causing this, is there something of concern here?

Thanks!

ps. This a WRT3200ACM if that matters.

2

I believe it has to exist as a device in /etc/config/network in order to be Unconfigurable. What’s in that file?

3

Hey, thanks! I’ll check that once I get an SSH access again to the router, but both of these devices are used as the device in their respective interfaces, and are indeed working perfectly, if that matters.

4

If the device is only virtual (i.e. not in the configuration file but understood to exist because e.g. an interface uses it) this would occur.

1 Like
5

Hello,

so here’s my network config (culled to remove irrelevant / sensitive parts like WG interfaces):

config interface 'lan'
	option proto 'static'
	option netmask '255.255.255.0'
	option ipaddr '192.168.1.254'
	option device 'br-lan.100'

config interface 'guest'
	option proto 'static'
	option netmask '255.255.255.0'
	option ipaddr '192.168.2.254'
	option device 'br-lan.200'

config interface 'IOT'
	option proto 'static'
	option device 'br-lan.300'
	option ipaddr '192.168.3.254'
	option netmask '255.255.255.0'

config interface 'mgmt'
	option proto 'static'
	option device 'br-lan.400'
	option ipaddr '192.168.4.254'
	option netmask '255.255.255.0'
	
config interface 'home'
	option proto 'static'
	option device 'br-lan.500'
	option ipaddr '192.168.5.254'
	option netmask '255.255.255.0'
	
config interface 'devices'
	option proto 'static'
	option device 'br-lan.600'
	option ipaddr '192.168.6.254'
	option netmask '255.255.255.0'
	
config interface 'games'
	option proto 'static'
	option device 'br-lan.700'
	option ipaddr '192.168.7.254'
	option netmask '255.255.255.0'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'lan1'
	list ports 'lan2'
	list ports 'lan3'
	list ports 'lan4'
	option ipv6 '0'

config bridge-vlan
	option device 'br-lan'
	option vlan '100'
	list ports 'lan1:u*'
	list ports 'lan2:t'
	list ports 'lan3:u*'
	list ports 'lan4:u*'

config bridge-vlan
	option device 'br-lan'
	option vlan '200'
	list ports 'lan2:t'

config bridge-vlan
	option device 'br-lan'
	option vlan '300'
	list ports 'lan2:t'

config bridge-vlan
	option device 'br-lan'
	option vlan '400'
	list ports 'lan2:t'

config bridge-vlan
	option device 'br-lan'
	option vlan '500'
	list ports 'lan2:t'

config bridge-vlan
	option device 'br-lan'
	option vlan '600'
	list ports 'lan2:t'

config bridge-vlan
	option device 'br-lan'
	option vlan '700'
	list ports 'lan2:t'

config device
	option name 'br-lan.100'
	option type '8021q'
	option ifname 'br-lan'
	option vid '100'
	option ipv6 '0'

config device
	option name 'br-lan.200'
	option type '8021q'
	option ifname 'br-lan'
	option vid '200'
	option ipv6 '0'

config device
	option name 'br-lan.300'
	option type '8021q'
	option ifname 'br-lan'
	option vid '300'
	option ipv6 '0'

config device
	option name 'br-lan.400'
	option type '8021q'
	option ifname 'br-lan'
	option vid '400'
	option ipv6 '0'

config device
	option name 'br-lan.700'
	option type '8021q'
	option ifname 'br-lan'
	option vid '700'

We can observe that there indeed are no device blocks for the two unconfigurable 802.1q devices:

image
image1248×154 33 KB

So, my question is now that are all those devices of type ‘8021q‘ completely unnecessary? Can I safely just remove them and expect everything to just work?

Thanks!

6

Yes, you can safely remove the explicit 802.1q stanzas. The .1q devices are created under the hood implicitly with the bridge-VLANs.

7

Okay, thanks! Just to make it explicit though, does this implicit device creation happen at boot automatically? This is my main router so would rather not break it if I can at all avoid it?

8

Yes. Those are the ones that can’t be “unconfgued”. I never create the explicit 802.1q stanzas and everything works properly. That is true for my own setups as well as the hundreds of vlan threads I’ve advised here.

9

Hi! Removing the excess devices worked perfectly ans this issue is thus resolved. Thank you!

10

Great!

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
Thanks! :slight_smile:

11

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.