This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Setting up VLAN with Google Wifi. Switch "dissapears" on network.
Hi Everyone!
I have succesfully setup my Smart Switch to manage the VLAN tagging to a Google Nest Wifi Router.
The Wifi works fine, even the wired connection seems fine. However, when I go from the Nest Router, back into the switch the switch "dissapears" on the LAN. Even though i assigned it a static IP and correct gateway i just can't get in contact with it.
What also happens is that I can't get in touch with my NAS over the Wifi, only on a wired connection.
I am really trying to understand where in the network map it's going wrong, but It's difficult.
The only trunk port is from the modem, and I was thinking if also the port to the Google router needs to be trunk? Or the return connection from the router needs to be trunked? All advice is super welcome!
Re: Setting up VLAN with Google Wifi. Switch "dissapears" on network.
By rule of thumb you need two VLANs. First for the Internet WAN part:
#7 with the link towards the Telekom side VLAN 7, tagged, PVID whatever (I think, no need for handling non-tagged packets there) no other VLAN membership (!!!)
#7 with the link towards the Google WiFi VLAN 7, untagged, PVID 7 - no other VLAN membership (!!!)
When I understand you right, this does work.
Now it seems you intend to use the switch also for the LAN with a dedicated VLAN. You could use the default VLAN 1. Ensure this is VLAN not on the two ports where Internet/WAN VLAN 7 is. So configure all other ports to VLAN 1, untagged, PVID1 - and no other VLAN membership.
The static IP (on a LAN IP, like 192.168.1.x or whatever is in use there) is required because the Smart Managed Plus type switches (except some XS variants) don't allow to limit the controller to a single management VLAN. Said tht, there is some risk in this set-up with that switch class.
I have succesfully setup my Smart Switch to manage the VLAN tagging to a Google Nest Wifi Router.
The Wifi works fine, even the wired connection seems fine. However, when I go from the Nest Router, back into the switch the switch "dissapears" on the LAN. Even though i assigned it a static IP and correct gateway i just can't get in contact with it.
What also happens is that I can't get in touch with my NAS over the Wifi, only on a wired connection.
Does not read like a successful set-up to me ... leaving alone that the crystal ball here is out of service and my Transilvanian aunt is no longer appearing.
Or the return connection from the router needs to be trunked?
What is return connection? That's not a an fuel system.
Unlikely any Google Nest, including the WiFi router device does support VLAN trunking and tagging on the LAN side. Google WiFi does for my knowledge not even support a ISP/WAN-side VLAN tag support for e.g. the Internet VLAN, the IPTV VLAN, and the VoIP VLAN for configuring a VLAN bridge (being to an Ethernet port, other Google WiFi devices, or to a dedicated WiFi network.
Complete unclear to me what exactly you want to achive. Working on something like this? -> Set up a network that uses VLAN tagging stating "Some internet services providers (ISPs) require VLAN tagging in order for their modems to communicate with wireless routers. VLAN tagging is not supported by Google Nest Wifi or Google Wifi and can cause your set up to fail." Last sentence sounds familiar, isn't it?
In short: You can't easily replace a provider dual- or tripple-play router (making "everything" available on its Ethernet and WiFi) by a Google WiFi router and a smart managed siwtch.
In long: Your Google WiFi system can only serve one network - that's the Internet (plain IP or VLAN tagged), routed/NATed by the Google WiFi router. This is where e.g. your mobile, computers, NAS are connecting to. This Google WiFi served network can't carry IPTV or VoIP. The switch properly configured for handling the provider Internet and VLANs does allow the configuration of ports for serving e.g. IPTV on dedicated wired connection(s) or VoIP on dedicated wired connection - the port must be associated to the relevant VLAN ID, untagged, and have the PVID set to the same ID.
- Internet works on all devices. Wired, and wirelessly.
- I can wirelessly access my desktop computers.
What does not work: - In the moment i plug in the LAN cable from the Google Nest to the Netgear managed switch, the switch simply dissapears. I can't find it with the Netgear Utility, I can't ping it on the static IP i gave it and can't find it with Advanced IP Scanner. It's simply gone.
- I can't wirelessly access my server.
I made sure that the switch is not in DHCP mode and gave it a IP address on the same subnet, with an IP within the routers pool.
So I think it could be related to the VLAN tagging, but I am not sure!
Thanks for the patience.
However, something with DHCP or similar must fail. This is my what my unexperienced tummy tells me.
Re: Setting up VLAN with Google Wifi. Switch "dissapears" on network.
By rule of thumb you need two VLANs. First for the Internet WAN part:
#7 with the link towards the Telekom side VLAN 7, tagged, PVID whatever (I think, no need for handling non-tagged packets there) no other VLAN membership (!!!)
#7 with the link towards the Google WiFi VLAN 7, untagged, PVID 7 - no other VLAN membership (!!!)
When I understand you right, this does work.
Now it seems you intend to use the switch also for the LAN with a dedicated VLAN. You could use the default VLAN 1. Ensure this is VLAN not on the two ports where Internet/WAN VLAN 7 is. So configure all other ports to VLAN 1, untagged, PVID1 - and no other VLAN membership.
The static IP (on a LAN IP, like 192.168.1.x or whatever is in use there) is required because the Smart Managed Plus type switches (except some XS variants) don't allow to limit the controller to a single management VLAN. Said tht, there is some risk in this set-up with that switch class.
