Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 2 3 [4]

Author Topic: HG612 and VLAN Tagging  (Read 3131 times)

stevebrass

  • Reg Member
  • ***
  • Posts: 261
Re: HG612 and VLAN Tagging
« Reply #45 on: June 12, 2021, 10:23:43 AM »

Its my understanding the HG612 is grossly underpowered to run NAT on VDSL, thus why its only found in modem/bridge mode.

Its also not really helpful as you're offsetting the PPPoE to the HG612 then so it probably will fix the problem as you're basically taking most of the work away from the Nest.

Having a system that works as long as you don't ACTUALLY use its functionality?  Yeah I wouldn't do that.

Bear in mind the issue here is loss of wifi connectivity not internet connection. The purpose of using the HG612 in router mode  is to see whether the NEST wifi behaves itself in this configuration. Which will add to the available information.
Logged
Netgear Orbi; BT FTTP with Smart Hub 2

RealAleMadrid

  • Reg Member
  • ***
  • Posts: 305
Re: HG612 and VLAN Tagging
« Reply #46 on: June 12, 2021, 07:34:59 PM »

@mogsiewp  I have been following this thread and cannot believe the stupidity and total lack of understanding of Google support. There is no VLAN tag on the LAN connection from the modem, so their obsession with VLAN tagging is just not a valid excuse for the problem. Also the nonsense about Gateway IP addresses is just beyond belief, a Private Gateway address is perfectly valid. As for adding a switch or router between the modem and Nest how can that achieve anything if there is no VLAN tag there, you can't remove something that isn't there!

The "Google Help Page" ???  about VLAN tagging confirms that it is not the problem.

Set up a network that uses VLAN tagging
**Some Internet Service Providers (ISP) require VLAN tagging in order for their modems to communicate with wireless routers.

Note: VLAN tagging is not supported by Google Nest Wifi or Google Wifi and can cause your setup to fail.

To confirm if your ISP uses VLAN tagging, or if you have IPTV or VoIP service through your ISP, check with your ISP.


There is no VLAN Tag going to the router so the sentence marked ** does not apply. The onhub file confirms you have a valid PPPoE connection and you are online. The vlanScan lines are somewhat ambiguous, it hasn't attempted to scan but the scan is complete. I don't see how that would confirm there is a VLAN tag. If there was a VLAN problem you would not get any connection.

VLAN tagging can be a problem if the ISP does uses it so the router can identify different services such as VOIP or IPTV but this does not apply to Openreach FTTC connections. (Seems to be on US and some Continental ISPs)

What I would like to clarify is when you see the WI-FI drops is the Internet still connected, is the PPPoE connection still up? Your earlier post suggested it was just the wi-fi dropping but could you confirm this?

There is nothing to be gained by trying to run the HG612 in Router  mode, as @Alex_Atkin states it probably doesn't have the processor power to run PPPoE which is quite demanding on high speed connections. I wouldn't even bother to try it and you will probably end up with a Double NAT situation.

My conclusion is that this is a Wi-Fi problem with the Google Nest but you are going to struggle to get them to accept this.
I don't think you will get a satisfactory result.

Logged
Pages: 1 2 3 [4]