I read the guide for the /etc/config/network file, but seem to be missing something.
I learn best by taking an existing setup, deconstructing it, and making it fit my needs, but these guides give very crude examples and don't seem to fully explain the options available.
Is there a better manual for these? man network doesn't seem to work.
What do you want to achieve? Be as specific as possible and we can give you guidance.
FWIW, you are correct that there isn't a man page for network because that is a configuration file, not an executable/binary. All of the documentation for the various options and syntax is in the wiki, but since it's an extensible config file, there isn't a singular page that will tell you everything you can or "should" do with it... it's very much a question about the goals (and sometimes constraints) for a given person/network environment.
We do, however, have many tutorials in the wiki for different types of configs, ranging from guest networks to VLANs with DSA to VPNs. Many of those just tell you how to achieve the goals, but some have the "why" included, too... or we can help you dissect that if you still have questions.
All that said, tell us what you want to do with your router and we'll either directly help or provide some links to references.
Could you pin point specific issues whats crud with the current doc?.also, pleas link to the article so we could talk about the same topic...
I have a second linksys e7350 that I am using as a wireless access point to extend coverage to the far side of my house.
this e7350 connects via 1G copper to an 8 port managed switch on a trunk line carrying tagged VLANS 1, 2 and 3.
1 - OOB management
2 - Internet of Things (cameras, tvs, switches, etc.)
3 - Data (NAS, Computers, things to not be exposed to the IoT)
I also have two separate WiFi networks. IoTWiFi on the 2.4GHz radios to connect the wireless IoT devices, and mywifi that connects phones and computers to allow NAS access.
I currently seem to have the remote wireless access point working except for the OOB management. When I set up the VLANS I lost connectivity to Luci. Currently my only access is JTAG (the guts are out of the case. I'm also considering adding a DB9 connector so I can access the JTAG connection without disassembly).
I've found a couple of Wikis on the topic, but nothing with a full table of what can be done with a configuration file. I do have experience with the RHEL network-scripts and Cisco and Brocade configurations, but I have volumes of manuals and thorough examples to manipulate.
I'm not saying the examples I've found are bad, just sparse enough that I'm not learning what I'd like to know.
I've been working with https://openwrt.org/docs/guide-user/network/network_configuration
If I understand correctly, the specific device you're trying to setup is the secondary e7350 that will be used as an AP with VLANs. Is that correct?
And it sounds like you already have an e7350 setup as the primary router, again with VLANs. Am I still on the right track?
This should be pretty straightforward to implement...
Basically, you want to start with the bridged AP tutorial. You'll make a few minor modifications, using DSA syntax (bridge-VLANs) to setup the tagged VLANs on the trunk port(s) and then define the rest of your port-vlan memberships.
For VLANs 2 and 3, you'll just setup unmanaged interfaces (option proto 'none'). And that should do it. VLAN1 (oob management) is the only one that needs to have an address.
Yes, this is not uncommon when using LuCI due to sequencing. The key is that you need to setup bridge-VLANs and then change the lan interface (or whatever name you've given to the OOB management network) to use device br-lan.1. I like to directly edit the config files because I can guarantee the sequencing isn't an issue.
If you need specific help, post your configs and we can help you through the process.
I'm giving br0.1 a DHCP address, but cannot seem to reach the web gui or ssh.
the networks seem to be working as expected other than that.
/etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fdd4:ae5b:abb7::/48'
option packet_steering '1'
config device
option name 'br0'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
list ports 'wan'
config device
option name 'lan1'
option macaddr 'xx:xx:xx:xx:xx:xx'
config device
option name 'lan2'
option macaddr 'xx:xx:xx:xx:xx:xx'
config device
option name 'lan3'
option macaddr 'xx:xx:xx:xx:xx:xx'
config device
option name 'lan4'
option macaddr 'xx:xx:xx:xx:xx:xx'
config interface 'lan'
option device 'br0'
option proto 'dhcp'
config device
option name 'wan'
option macaddr 'yy:yy:yy:yy:yy:yy'
config device
option type '8021q'
option ifname 'br0'
option vid '1'
option name 'br0.1'
config device
option type '8021q'
option ifname 'br0'
option vid '2'
option name 'br0.2'
config device
option type '8021q'
option ifname 'br0'
option vid '3'
option name 'br0.3'
config interface 'OOB'
option proto 'dhcp'
option device 'br0.1'
config interface 'IoT'
option proto 'none'
option device 'br0.2'
config interface 'PRIV'
option proto 'none'
option device 'br0.3'
config bridge-vlan
option device 'br0'
option vlan '1'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
list ports 'wan:t'
config bridge-vlan
option device 'br0'
option vlan '2'
list ports 'wan:t'
config bridge-vlan
option device 'br0'
option vlan '3'
list ports 'wan:t'
This is likely because the OOB network is probably not assigned to a zone in the firewall that allows input. Try assigning that network to the lan firewall zone.