Nest Wifi VLAN Connection issues

---

sjd201 wrote:

Had issues as someone else set up origianal account for some access points at work and I didnt realise I was only a user rather than admin.  All went awry when he tried to transfer it.  Got a support ticket in so hopefully they can fix it.

---

Is this on a Basic or Premium Insight subscription? Then only one account exists. All devices should be registered to the same account to keep things simple, e.g. for taking to support or claim hardware warranty.

If this is an Insight Pro environment, there is a more complex roles concept starting with the Pro Admin (a single technical role, held e.g. by your Insight supplier or installer, we use e.g. insightpro@supplier.abc), an Insight Organisation Owner (as there can be many organizations managed, also a technical role, like CIO@customer.xyz), multiple Insight Manager (personal roles, like yourname@customer.xyz and/or a shared role for the supplier like support@supplier.abc). All technical roles should point to email aliases and distribution lists - never to a single personal account. Trouble is that most businesses don't have any working policies on IT processes...so this is where problems are caused when people are doing any kind of registrations for a multi-user-business on personal business accounts or worse private accounts.

It's technically possible to include Insight devices registered to another owner account into the Insight environment, unless these are already insight managed under that other account.

That's enough on Insight excursions for now - convinced Netgear is able to assist for merging accounts or transferring ownerships to the same organisation.

---

sjd201 wrote:

So I have read your respose and understand it. The Google support page indicates that you have to plug the nest into the WAN port of the switch but as I see it all the ports are the same. Is that right?  Or can you configure one of the ports to act as a WAN?

---

Whatever you have read here. Depending on a switch config, a port could have some role based on the switch VLAN/port/routing/whatever config. Per se, a switch does not have a WAN port.

---

sjd201 wrote:

I have been onto Google support again and they said should only have Nest WAN plugged into switch.  This works for WiFi ... 

---

So this is just:

BT Business Hub (bridge mode) <-> Switch <-> Nest Router WAN <-> WiFi

Great, so your Nest router and WiFi system does work to this point as expected, isn't it?

So it's time to streamline things:

Confirm at this point there is no VLAN configuration for VLAN 110 with a dedicated port [T]agged to VLAN 110 (no other VLAN), and a dedicated [U]ntagged port for VLAN 110/PIVD 110 ... that's what users with direct Fiber/Ethernet connections have to do to connect any user-supplied router. You don't have to do this at all: The BT Business Hub does handle the BT Internet VLAN part for you also in Bridge mode.

Reduce your set-up by removing the switch from the Internet-side of things:   

BT Business Hub <-> Nest Router WAN <-> WiFi     

I'm convinced your WiFi will continue to work as expected.

---

sjd201 wrote:

 ... but devices plugged into switch have no internet so thats an issue.  Resolved that by plugging Nest WAN into modem and LAN into switch.

---

Here I begin to understand where your network issues are coming from. Why on earth is the idea coming from connecting different networks onto one (I assume non-configured!) switch, which out of the box has a plain L2 switch functionality?

If you would like to have TWO networks on your switch - these are the BT-side Internet and your LAN - the switch must be configured accordingly for handling two networks as indicated above, into two VLANs: Two ports for the WAN/Internet, one tagged, one untagged; and all others for your LAN.

But here again, I'm convinced this isn't required at all - because WiFi will run well (as long as you don't connect the BT Internet network and the LAN onto the same plain L2 switch....).

Connect your switch only to the router LAN port as it is. And it will serve you well....

And nothng else must be ever connected to that BT Hub...

---

sjd201 wrote:

So would you just plug the Nest router directly into the BT Hub via Wan and plug LAN from Nest into the switch as I described above?  PPPoE info is in the Nest device as you described other than password field which is BT not blank.

---

Yes, as explained several times now.

---

sjd201 wrote:

I cannot find anything in the config for MTU.  Did some google research and it does not appear to be an option.

---

Oh well, can't find anything, too - guess Google Nest WiFi does derive some MTU based on the connection type and/or testing.

---

sjd201 wrote:

Dont understand your last comment other than you think managed switch is not necessary with any VLAN settings?

---

Re-read this post from the top again.