-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ability to add an additional WiFi network #222
Comments
WiFi is really complicated, and it is even worse on the Gen 3, because on earlier generations both the WiFi and EasyMesh implementations were from Technicolor, but the Gen 3 has a third-party EasyMesh implementation. When I get some time, I will have a look. I use Guest for my IoT network, and I have a separate AdGuard Home instance for it. |
Ah I see! I didn't consider the easymesh integration! I might have another go at poking around the config. |
Have you considered running Guest 2.4 as wlan-IoT (as most IoT devices use 2.4) and then using guest 5ghz as wlan-guest? That along with your main network with band steering will be your 3 networks no? |
This won't work on a Gen 3. There is only one Guest network (unlike the Gen 2 and earlier that have separate networks for each Guest SSID). |
Ah I see, it's the way I'm running it with that set up on my Gen 2 so was ignorant of this change on the Gen 3. Thanks |
Just an update - I've tested this on a Gen 3 and you can have the guest network with two separate SSIDs. Just turn on "split" at the top of the wireless tab. Notably, this doesn't create a second VLAN like it does in the Gen 2 so technically Guest and Guest-5ghz are both still on the same network. |
Which is the problem, because the OP wants to create a different network with no access from Guest or IoT network to personal devices and home servers. I had considered what you have proposed, since as you say, if you split the SSIDs, you can have 3 SSIDs (5GHz/2.4GHz/2.4GHz) as the OP desires. However, even if you enable client isolation on the IoT 2.4GHz SSID that is attached to the LAN network (to get AdGuard protrection), it only stops Wi-Fi client-to-client access; it does not prevent Wi-Fi client access to the wired servers on that network. |
Been meaning to ask about this, as a request.
There's an option in the GUI to add an additional network under LAN interfaces. But there is no option to add a third network under WiFi. I previously tried to figure out how to do it in CLI but I was finding it pretty complicated (coming from a Cisco background.)
Would it be possible to implement this in the GUI?
Use case for this is as follows:
home (trusted network) - personal devices and home servers (adguard protection) - 5G
guest (untrusted network) guest internet - 2.4G (no advuard)
IoT devices (untrusted network) with adguard protection - 2.4G
I'm aware that an additional WiFi network / ssid will require more power and resources on devices that already are budgeting heavily. However on the cobra I've found it managing well in that respect. I know that these devices before de-telstra did have the telstra-air/fon network so this is why I assume this would be possible.
Happy to hear your thoughts.
The text was updated successfully, but these errors were encountered: