Happy to consider new Mesh Hardware if the price is not prohibitive. ?
Is there any software approach method to having the WiFi Mesh serve two Access Points? Each Access Point serves a different subnet?
1) LAN + WAN (192.168.2.xxx)
2) WAN only? (192.168.50.xxx)
Detail
Organically grown LAN 192.168.2.xxx - DLNA, TV / Streaming, NAS File Server, App Servers (Laptops) Print Servers, tablets, laptops, Phones - where cabled ethernet facility is avaialble on the end point device then it is used.
Thick walls, bungalow, wide floor space
Unamanaged Switches connected via Ethernet in each room with Wi-FI Mesh dishes connected to said Unmanaged Switches - room roaming is seamless most of the time - though Sonos units get uppity.
Added WI-FI Mesh on same Subnet (BT Whole Home - is easy) to cover black spots - Uses DHCP provided by 192.168.2.xxx main router
Recently acquired 2nd FTTC line (slow speeds out here)
192.168.2.xxx Router not up to job of running LAN and Load Balancing (busy LAN performance hungry)
Added 2nd router - Load Balances 2x FTTC Connections - Accessible on 192.68.50.xxx (Dual WAN)
This second router is providing WAN service to 192.168.2.xxx (seen as a single WAN Connection for 192.168.2.xxx)
It has its Own Access Point - but is building wall thickness and area prohibits WiFi coverage
Want Home Residents to use WI-FI mesh for 192.168.2.xxx (LAN + WAN)
Want external contractors and guests to use 192.168.50.xxx (WAN Only) (MESHED with single Mesh Hardware if possible?)
Have only 1 Wi-Fi Mesh hardware set
Have only 1 Ethernet cabling set (built into the walls and not easy / would say impossible to add second ethernet cabling as behind plastering and some rooms are vaulted ceilings.
Side Note : I am noticing the Mesh on 192.168.2.xxx subnet is dropping connections - presumably because the jump from 2.xxx to 50.xxx requires clever NATting- it works - it just cuts a bit when wandering around the building
I thought about having all wifi userss on 192.168.50.xxx subnet and managing users to access LAN Devices - but being on my own managing ports and permissions is not worth the effort.
I don't want to get rid of 192.168.2.xxx subnet and the idea of LAN resources behind 2 firewalls (2.xxx and 50.xxx) would be a good security measure.
The alternative is migrating all devices from 192.168.2.xxx to 192.168.50.xxx and that will take probably a whole day (not a great use of weekends)
Is there any software approach method to having the WiFi Mesh serve two Access Points? Each Access Point serves a different subnet?
1) LAN + WAN (192.168.2.xxx)
2) WAN only? (192.168.50.xxx)
Detail
Organically grown LAN 192.168.2.xxx - DLNA, TV / Streaming, NAS File Server, App Servers (Laptops) Print Servers, tablets, laptops, Phones - where cabled ethernet facility is avaialble on the end point device then it is used.
Thick walls, bungalow, wide floor space
Unamanaged Switches connected via Ethernet in each room with Wi-FI Mesh dishes connected to said Unmanaged Switches - room roaming is seamless most of the time - though Sonos units get uppity.
Added WI-FI Mesh on same Subnet (BT Whole Home - is easy) to cover black spots - Uses DHCP provided by 192.168.2.xxx main router
Recently acquired 2nd FTTC line (slow speeds out here)
192.168.2.xxx Router not up to job of running LAN and Load Balancing (busy LAN performance hungry)
Added 2nd router - Load Balances 2x FTTC Connections - Accessible on 192.68.50.xxx (Dual WAN)
This second router is providing WAN service to 192.168.2.xxx (seen as a single WAN Connection for 192.168.2.xxx)
It has its Own Access Point - but is building wall thickness and area prohibits WiFi coverage
Want Home Residents to use WI-FI mesh for 192.168.2.xxx (LAN + WAN)
Want external contractors and guests to use 192.168.50.xxx (WAN Only) (MESHED with single Mesh Hardware if possible?)
Have only 1 Wi-Fi Mesh hardware set
Have only 1 Ethernet cabling set (built into the walls and not easy / would say impossible to add second ethernet cabling as behind plastering and some rooms are vaulted ceilings.
Side Note : I am noticing the Mesh on 192.168.2.xxx subnet is dropping connections - presumably because the jump from 2.xxx to 50.xxx requires clever NATting- it works - it just cuts a bit when wandering around the building
I thought about having all wifi userss on 192.168.50.xxx subnet and managing users to access LAN Devices - but being on my own managing ports and permissions is not worth the effort.
I don't want to get rid of 192.168.2.xxx subnet and the idea of LAN resources behind 2 firewalls (2.xxx and 50.xxx) would be a good security measure.
The alternative is migrating all devices from 192.168.2.xxx to 192.168.50.xxx and that will take probably a whole day (not a great use of weekends)