Accessing IOT devices in guest WiFi via "Main" WiFi not working

Technical Support for Routers
1

Hi there,

I have a Slate AX, using the following config (completely in GL.Inet UI, not Luci)

Physical
WAN > Connected to router/Modem (Telekom DE Speedport 4), Not in bridge Mode, all WiFi Networks turned off
LAN 1 > Ikea Smart Home Bridge
LAN 2 > Tado Bridge Wifis (each is 2.4 and 5 GHz)

Wireless
WiFi 1 > Main WiFi for "human" devices. Laptops, Tablets, Phones
Guest WiFi > Bunch If IOT devices Like light bulbs, thermostats, Google Home speakers

Now what's not working when the Main Phone is Connected to WiFi 1 is trying to Google cast music to speakers, steer temperature on the thermostats.

While the while Idea behind this Setup to have the IOT devices separates, its limiting if the phone cant steer stuff.

Is there any Stock solution to this and If not, what would I need to so in Luci to get IT working?

Thanks all, looking forward to learning something as I'm fairly new to this :slight_smile:

2

Interested here as well.

Thinking of getting a Flint 2 (or waiting for the 3) but want to allow one-way traffic from main LAN/Wifi TO the Guest WiFi (but not the other way around) for IoT access.

3

Question here is what the detailed design of this Slate AX is. There are many choices they had to make for setting this up.

In GL.inet my experience so far is that ...

  • wifi Home and wifi Guest both are allowed Internet access
  • wifi Guest has client isolation (guest devices cannot communicate with other guest devices)
  • wifi Home has no client isolation (devices can communicate within this SSID wifi, and with LAN ethernet devices, and are in the same subnet (broadcast/multicast domain))
  • wifi Guest devices cannot access wifi Home or LAN ethernet
  • wifi Guest devices have no access to the gL.inet admin page
  • wifi Home and LAN ethernet to wifi guest? not checked yet but is probably also denied (intra zone routing disabled)

Check "advanced /LUCI" for those parameters in interface settings and in Firewall, these settings can be changed or can have been changed before.

Google cast probably is using mDNS (or Bonjour, or DLNA) to find the speakers IP address. This requires the requestor to be in the same broadcast:multicast domain as the receiver. (Otherwise some extra reflector APP is needed , e.g. AVAHI , replacing the usual central DNS function)

1 Like