Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mogsiewp]

I have recently connected Nest Wifi to the HG612 in the UK on a FTTC connection on a PPPoe connection.
Nest handles PPPoe with the HG612 bridged.
Unfortunately I am experiencing intermittent wireless dropouts on various devices at different times.
The internet connection stays solid in these periods.
A ping monitor on the nest router ip address shows it available periodically.
Google insist the instability is caused as my ISP is using VLAN tagging.
Reviewing the modem configuration I can see the WAN tag configured as 101, and what I thought meant LAN VLAN disabled.
ie. the LAN 802.1q setting is diabled

Can anyone confirm if this setting does indeed mean there is no VLAN tagging on the LAN side?
many thanks

[burakkucat]

Welcome to the kitz forum. 

Can anyone confirm if this setting does indeed mean there is no VLAN tagging on the LAN side?

You are correct. The two VLANs established from within the HG612 (out over the WAN interface) are tagged 101, which is essential for the service to operate, and 301, which is non-essential. The latter can be deleted as it was used in the early days of the UK's VDSL2 roll-out to monitor the VDSL2 link behaviour and remotely push updated firmware to the device.

[mogsiewp]

Dam. Nest WiFi just started dropping device connections again. Google insist there is vlan tagging but these setting say different. They say I have to put a managed switch between modem and router to strip tagging.

They concluded this because the default gateway doesn't configure to a .1 or .254 address mine is .120. none of this makes any sense?

[burakkucat]

none of this makes any sense?

Agreed. What you have been told is pure nonsense.

[Alex Atkin UK]

Dam. Nest WiFi just started dropping device connections again. Google insist there is vlan tagging but these setting say different. They say I have to put a managed switch between modem and router to strip tagging.

They concluded this because the default gateway doesn't configure to a .1 or .254 address mine is .120. none of this makes any sense?

What the heck are they on about?  I wouldn't EVER expect an actual WAN connection to end in .1 or .254, that's generally what the LAN gateway would use (though not mandatory).  I guess they're used to people incorrectly putting it behind an existing router in a double-NAT.

[mogsiewp]

They are talking about the wan default gateway IP address. They insist that due to the fact it ends in 172.xx.xx.120 that the connection (Lan) connection still has vlan tagging.

The 172 address is an internal one yes?

I know some of the early hg612s used 172 IPS. Coincidence?

What sets a wan default gateway IP? ISP?
If so how does it land up with 172.. internal IP?

I understand ip bridged and pppoe bridged mode are different.mine is former. Does it matter which?

Google support stinks!

All help really appreciated.

[mogsiewp]

Sorry quick addition.
Found this secret google status page which exposes more data.
Maybe useful?

[burakkucat]

They are talking about the wan default gateway IP address. They insist that due to the fact it ends in 172.xx.xx.120 that the connection (Lan) connection still has vlan tagging.

The 172 address is an internal one yes?

Not necessarily. 

The block 172.16.0.0 to 172.31.255.255 inclusive is one of the three private IPv4 address ranges. As you have shown 172.xx.xx.120, above, it is impossible to say whether the address in question is from the private RFC1918 block or is publicly routeable. The first "xx" holds the key. If it is less than 16 or greater than 31 then it is a publicly routeable IPv4 address.

[Edited to fix typo.]

[mogsiewp]

It's 172.16.12.120.
From what you just said to then it is private.

The full details are in attachment above.

[burakkucat]

I am baffled and at a total loss. 

Perhaps CarlT will offer an opinion?

[mogsiewp]

Me too.

Is the 172x the modems IP?
The router is on 192.168.86.x

So Google say this 172 gateway indicates vlan on the lan because it doesn't end in 1 or 254.

What would a routers default gateway normally be? A public ISP IP?

I've read about other settings like DHCP transparency and the pppoe bridge mode but feel i' m just guessing.

I wouldn't have bought a router that needs a modem and managed switch all seems ridiculous.

Hopefully someone will have some insight

[Alex Atkin UK]

The thing is in bridge mode its blindly forwarding traffic between the VLAN and the LAN1 ethernet port, no other traffic can be on that port so its confusing where this is coming from.  It certainly can't put anything on the PPP interface.

The HG612 LAN IP is in the 192.168 range, I can't remember specifically.

Its all very confusing.  I was going to ponder if it was CG-NAT by your ISP, but I don't think that is on the 172. range.  None of this should cause wireless drop outs anyway, the question would be if the PPP session is dropping.

[mogsiewp]

Also, why isn't the internet users from uk full of people complaining.

There are some with similar issues but not loads.

I've had a ping monitor on the router and seen intermittent dropouts, with the onhub stats (see above) showing wan uptime solids (it's in seconds)

[tubaman]

Perhaps I'm talking at cross purposes here but I get a 172.16.xx.xxx address as the hop after my router if I do a tracert on my BT VDSL service. Although a private address I'm assuming it's actually the gateway to the BT network? Is this what Goggle are going on about?

[mogsiewp]

Yes.

They say if the last set of digits isn't 1 or 254 that there is vlan tagging.

If this is a bt allocated gateway address ie. Wan based, that would be true as it's 101 there.

Given nearly all UK is bt backbone can't see it  will ever be 1 or 254

But there article on vlan connections says to put a managed switch or VDSL router between the modem the modem and nest router.

Google then say it will be stable.

But the modem has the lan vlan configured to disabled already but maybe that's not the point.
Maybe there Google specific features like cloud services which are integral part of it can't deal with tags being added. Who knows.

But a managed switch would just add them.
So why not the modem?
What would switch do that modem doesn't?

Can I test presence of tags on Lan?