Guest Network DHCP broken on Archer VR1210v V2
I have an Archer VR1210v V2 set up with a VDSL connection for the WAN and the LAN set up with the router on 192.168.1.1 (default mask of 255.255.255.0 and DHCP IP pool 192.168.1.100-192.168.1.249). The 2.4GHz and 5GHz WiFi is set up with Band Steering enabled and everything works so far - WiFi clients can connect to the LAN and internet and are successfully given DHCP addresses from the pool.
However, I cannot get the Guest Network feature to work. When enabled, clients can see the corresponding guest SSID but when they attempt to connect to it, they successfully authenticate but are not given a DHCP address. They then either disconnect or remain connected with a 169.254.x.x address (i.e. no DHCP address available). Presumably they should be issued an address from a separate DHCP pool to that of the primary 192.168.1.x subnet but this doesn't happen.
I have noted that in the help page for the Guest Network, there are features referred to that are not displayed in the web UI of the VR1210v (tested on both Chrome and Safari):
- Allow Guests to Access My Local Network
- Allow Guests to Access My Local USB Storage
- QoS Settings
Only the "Allow Guests To Access Each Other" is shown and it makes no difference whether it's checked or not - clients are still not given an DHCP address when connecting to the guest network.
[As an aside, I have found that using the Developer Tools feature of Google Chrome, the missing settings are included in the rendered HTML, as divs with id="AccessLocal", "USBStorage", etc but given a CSS class of "nd" which causes them to not be displayed - this is presumably a separate bug]
As a workaround, I have found that the Multi-SSID feature of the VR1210v can be used to create a separate SSID for guests, instead of using the Guest Network feature. When enabled, guest clients are able to successfully join this network and are given a 192.168.33.x address via DHCP, i.e. from a different subnet to the primary 192.168.1.x LAN, and as far as I can tell are not addressable from the primary LAN and presumably cannot access other clients on the primary LAN. Isn't this what the Guest Network feature should do?
So my questions are:
1. Is it possible to fix the DHCP problem on the Guest Network feature, so clients are given IP addresses when they connect (presumably from a different pool to the primary LAN), without giving them access to clients on the primary LAN subnet?
2. In the meantime, does the Multi-SSID feature definitely provide the same kind of isolation from the primary LAN subnet as the Guest Network should, if it worked? (I don't want guest clients to have any access to any clients on the primary LAN, connected via WiFi or wired ports)
@terziyski thanks for your reply.
In this case the VR1210v was purchased directly from Amazon, rather than supplied by an ISP, and then configured with my ISP's VDSL settings to connect it to their network. However, I've made no other customisations to the configuration and the Guest Network feature is broken from the start, after factory resetting it.
I agree that the guest network should be straightforward and require no need for configuring DHCP (the VR1210v should do that automatically) but for whatever reason it isn't working, so I suspect a bug in this firmware, which could also be related to why the other settings are missing from the Guest Network configuration page, even in the Advanced section (see attached screenshot).
The guest network definitely gets created and clients can authenticate to it but, unlike if I create a second SSID via the Multi-SSID feature, they don't get assigned a DHCP address, so I suspect something isn't right in the configuration behind the scenes. The Multi-SSID feature works as it should and the DHCP server issues addresses from a separate pool starting with 192.168.33.100 (at least it does for the MSSID1 (I've not tried using MSSID2 but I suspect that also works).
Do you know if there is any later firmware available for the VR1210v V2 that might address this? (later than 0.12.0 2.0.0 v606e.0 Build 231113 Rel.47602n)
