cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

Nest Wifi PPPoE with ISP using VLAN 20

hubbobubbo
Community Member

I have just switched ISP and I would like to replace completely the ISP ZTE router with my Nest Router (i.e. not put the ISP router in bridge mode).

I have received the PPPoE credentials but the Nest Router still flashed yellow after changing from DHCP to PPPoE.

Then I also saw in the email from the ISP that it had a third parameter after user and password:

VLAN 802.1Q = 20

and this info https://support.google.com/googlenest/answer/9798157?hl=en 

indicates that 20 is not supported by Google Nest Router. I guess this is the reason for it not connecting.

Is there any workaround for this? It just seems surprising that Google does not offer a way to use another VLAN value than the three indicated in the post if there are 4096 values allowed?

Any ideas?

1 Recommended Answer

Dan_A
Community Specialist
Community Specialist

Hi hubbobubbo,

 

I understand your situation and the limitations you're facing with VLAN 20 on your Nest Router. Here are the options and potential ways for connecting to your ISP:

 

1. Contact ISP for Alternative Setups:

  • Reach out to your ISP and explain your desire to use your own router. They might offer alternative ways to connect, such as:
    • Bridge mode: Even though you prefer avoiding it, it's still a viable option that would allow your Nest Router to manage most network functions.
    • Removing VLAN tagging: In some cases, the ISP might be able to provision your internet connection without VLAN 20 tagging, making it compatible with your router.

 

2. Consider Third-Party Firmware (Advanced Users):

  • If you're comfortable with advanced networking, you could explore custom firmware like OpenWrt or DD-WRT. These firmwares often offer greater control over VLAN settings, potentially enabling VLAN 20 support. However, proceed with caution as custom firmware can void warranties and create stability issues.

 

3. Workaround with a Manageable Switch (If Available):

  • If you have a manageable switch that supports VLAN tagging, you could try:
    • Connect the ISP modem to the switch's WAN port.
    • Configure the switch to tag VLAN 20 on the WAN port.
    • Connect the Nest Router to a LAN port on the switch.
    • Configure the Nest Router for PPPoE with the provided credentials (without VLAN tagging).
    • This setup might allow the switch to handle VLAN 20 while the Nest Router manages the rest of your network.

 

4. Use ISP Router in Bridge Mode (Last Resort):

  • If none of the above options work, using the ISP router in bridge mode remains a fallback solution.

 

Our Nest Wifi routers rely on the credentials of your ISP for them to communicate with each other. Especially when credentials are changed, like the DHCP, OpenWRT supports Google Wifi routers; Nest Wifi itself is not officially supported by OpenWRT due to Google's locked bootloader and limited hardware access. Please remember that a Google/Nest Wifi router's function is, first and foremost, as a router and point. Doing otherwise is not recommended.

 

Limited Options and Challenges:

  • Unofficial Development: Despite the lack of official support, some enthusiasts have managed to install OpenWrt on Nest Wifi devices through unofficial methods. However, these methods can be complex, may void your warranty, and might not be stable or fully functional.
  • Limited Features: Even if you successfully install OpenWrt, some Nest Wifi features, like the Google Home app integration and mesh technology, might not work properly or require additional configuration.
  • Advanced Users Only: Due to the complexity and potential risks, installing third-party firmware on Nest Wifi is only recommended for experienced users with strong technical skills and a willingness to experiment.

 

Hope this helps.

 

Best,

Dan

View Recommended Answer in original post

3 REPLIES 3

Dan_A
Community Specialist
Community Specialist

Hi hubbobubbo,

 

I understand your situation and the limitations you're facing with VLAN 20 on your Nest Router. Here are the options and potential ways for connecting to your ISP:

 

1. Contact ISP for Alternative Setups:

  • Reach out to your ISP and explain your desire to use your own router. They might offer alternative ways to connect, such as:
    • Bridge mode: Even though you prefer avoiding it, it's still a viable option that would allow your Nest Router to manage most network functions.
    • Removing VLAN tagging: In some cases, the ISP might be able to provision your internet connection without VLAN 20 tagging, making it compatible with your router.

 

2. Consider Third-Party Firmware (Advanced Users):

  • If you're comfortable with advanced networking, you could explore custom firmware like OpenWrt or DD-WRT. These firmwares often offer greater control over VLAN settings, potentially enabling VLAN 20 support. However, proceed with caution as custom firmware can void warranties and create stability issues.

 

3. Workaround with a Manageable Switch (If Available):

  • If you have a manageable switch that supports VLAN tagging, you could try:
    • Connect the ISP modem to the switch's WAN port.
    • Configure the switch to tag VLAN 20 on the WAN port.
    • Connect the Nest Router to a LAN port on the switch.
    • Configure the Nest Router for PPPoE with the provided credentials (without VLAN tagging).
    • This setup might allow the switch to handle VLAN 20 while the Nest Router manages the rest of your network.

 

4. Use ISP Router in Bridge Mode (Last Resort):

  • If none of the above options work, using the ISP router in bridge mode remains a fallback solution.

 

Our Nest Wifi routers rely on the credentials of your ISP for them to communicate with each other. Especially when credentials are changed, like the DHCP, OpenWRT supports Google Wifi routers; Nest Wifi itself is not officially supported by OpenWRT due to Google's locked bootloader and limited hardware access. Please remember that a Google/Nest Wifi router's function is, first and foremost, as a router and point. Doing otherwise is not recommended.

 

Limited Options and Challenges:

  • Unofficial Development: Despite the lack of official support, some enthusiasts have managed to install OpenWrt on Nest Wifi devices through unofficial methods. However, these methods can be complex, may void your warranty, and might not be stable or fully functional.
  • Limited Features: Even if you successfully install OpenWrt, some Nest Wifi features, like the Google Home app integration and mesh technology, might not work properly or require additional configuration.
  • Advanced Users Only: Due to the complexity and potential risks, installing third-party firmware on Nest Wifi is only recommended for experienced users with strong technical skills and a willingness to experiment.

 

Hope this helps.

 

Best,

Dan

hubbobubbo
Community Member

Thanks for the very detailed answer. In the end the only thing I could make work was to keep the ISP router in bridge mode as you say. Using a managed switch would still mean having two devices which is simply what I was trying to avoid.

It would be so great if Google could just offer a way to set custom VLAN tags in the Nest Wifi app, that would allow for complete removal of the ISP router 🙂 

 

Dan_A
Community Specialist
Community Specialist

Hello there,

 

You're welcome! I understand your concern with the limited VLAN options on the Nest Wifi and the need for two devices in bridge mode. It's definitely a pain point for users with specific ISP configurations.

 

I agree that offering custom VLAN tag setting in the Nest Wifi app would be a great improvement. It would provide more flexibility and allow users like yourself to connect directly to their ISP without needing the additional hardware or limitations of bridge mode.

 

I'd suggest you submit feedback about it. If you have other questions or concerns, you know where to find us. We're here to help.

 

Best,

Dan