root@R4S:~# ubus call system board
{
"kernel": "5.15.137",
"hostname": "R4S",
"system": "ARMv8 Processor rev 4",
"model": "FriendlyElec NanoPi R4S",
"board_name": "friendlyarm,nanopi-r4s",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "23.05.2",
"revision": "r23630-842932a63d",
"target": "rockchip/armv8",
"description": "OpenWrt 23.05.2 r23630-842932a63d"
}
}
root@R4S:~# cat /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 'fd0a:bb4c:8eb9::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth1'
config device
option name 'eth1'
option macaddr 'REDACTED'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '10.0.0.1'
option netmask '255.255.255.0'
option ip6assign '60'
config device
option name 'eth0'
option macaddr 'REDACTED'
config interface 'wan'
option device 'eth0'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option gateway '192.168.1.254'
config interface 'wan6'
option device 'eth0'
option proto 'dhcpv6'
option reqaddress 'none'
option reqprefix 'auto'
root@R4S:~# cat /etc/config/wireless
cat: can't open '/etc/config/wireless': No such file or directory
root@R4S:~# cat /etc/config/dhcp
config dnsmasq
option domainneeded '1'
option localise_queries '1'
option rebind_protection '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option cachesize '1000'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option localservice '1'
option ednspacket_max '1232'
option port '54'
list server '10.0.0.1'
option rebind_localhost '1'
config dhcp 'lan'
option interface 'lan'
option start '10'
option limit '90'
option leasetime '12h'
option dhcpv4 'server'
option dhcpv6 'relay'
option ra 'relay'
option ndp 'relay'
list dhcp_option '6,10.0.0.1'
list dhcp_option '3,10.0.0.1'
config dhcp 'wan'
option interface 'wan'
option ignore '1'
option start '100'
option limit '150'
option leasetime '12h'
config odhcpd 'odhcpd'
option maindhcp '0'
option leasefile '/tmp/hosts/odhcpd'
option leasetrigger '/usr/sbin/odhcpd-update'
option loglevel '4'
config dhcp 'wan6'
option interface 'wan6'
option ignore '1'
option master '1'
option ra 'relay'
option dhcpv6 'relay'
option ndp 'relay'
config host
option name 'TL-SG108PE'
option mac 'REDACTED'
option ip '10.0.0.2'
config host
option name 'U6Lite'
option mac 'REDACTED'
option ip '10.0.0.3'
config host
option name 'ArcherC6'
option mac 'REDACTED'
option ip '10.0.0.4'
config host
option name 'rpi3-wired'
option mac 'REDACTED'
option ip '10.0.0.5'
config domain
option name 'REDACTED.nsupdate.info'
option ip '10.0.0.5'
I'd like to setup the guest network on the main router, and then use VLANs to run them out to the dumb APs. Is that possible, @psherman? If so, how to achieve this?
Will 802.11r be possible on the guest network using this setup?
Thanks for starting the new thread. Referencing your old thread, you were using the 10.0.1.0/24 subnet for the guest network. So we'll replicate that here.
Let's start with the network file. We're going to use device eth1.10 which will be tagged VLAN 10 on port eth1. Add the following
And then the firewall -- for now, we'll allow the guest network to reach the router itself, but we can tighten that down later (the goal here is to reduce any variables that could cause problems):
config zone
option name 'guest'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'REJECT'
list network 'guest'
config forwarding
option src 'guest'
option dest 'wan'
Next, you'll need to set your switch to handle VLAN 10. It needs to be tagged on 3 ports (I don't know the port numbers you're using, but these are the functional connections):
Uplink to the router
connection to the U6 Lite
connection to the C6.
And, I would also recommend making it untagged + PVID on any spare port that you have on your switch so that we can test to make sure the VLAN is working.
Now, restart your router and plug an ethernet connected device into the untagged + PVID port you setup above. It should get an address in the guest network and it should be able to reach the internet. Please confirm that and we can move onto the APs.
Does your guest network need to use the same dns, or is a public dns sufficient?
Answer: A public DNS is sufficient... I guess? Using AdGuard Home for the guest network would be cool, though.
config interface 'lan'
option device 'br-lan.1'
option proto 'static'
option ipaddr '10.0.0.3'
option netmask '255.255.255.0'
option ip6assign '60'
option gateway '10.0.0.1'
list dns '10.0.0.1'
And edit the guest network to use br-lan.10 and it should also be unmanaged:
config interface 'guest'
option proto 'none'
option device 'br-lan.10'
Restart the device and connect to the guest ssid. (You may want to temporarily unplug the other ap so that there is only one device broadcasting the ssid)
