Re: Consumer products with baked-in VLAN tagging

[Robert Seastrom <rs () seastrom com>]

On Apr 8, 2015, at 1:58 PM, Dave Taht <dave.taht () gmail com> wrote:

> I do wish they had bufferbloat-fighting queue managment on the ISP
> side, it is otherwise
> pretty good hardware.

As you're well aware since your name is in the acknowledgements, there's been some effort in this direction at CL.  If 
the problem gets solved in the CMTS and the CM, what the router does is kind of beside the point (unless we've 
progressed to wanting to do it on the wireless side too).

> Do they also supply that vlan to the ethernet?

You mean to the southbound ethernet when running as a router instead of to the northbound ethernet while running as a 
bridge?  No idea.  That's not my normal use case.

> How is their ipv6 with comcast?

Beats me.  No Comcast handy to test with.

 I *can* tell you that a freshly factory reset Airport Express 802.11n (2nd Generation) aka A1392 - the currently for 
sale $99 one - does pretty much exactly what you would hope when plugged into a freshly rebooted cablemodem on Another 
Pretty Darned Big MSO.  That is to say, it gets a PD /64 and you're off to the races with native IPv6 on the wireless 
side.  No warranties expressed or implied, but it seems to do what it says on the tin.

A similar test with a freshly factory reset Airport Extreme 802.11n (3rd Generation) aka A1301 is disappointing; 
default configuration is IPv6 link local only and although there is a knob to put it into "native/automatic" IPv6 
configuration it doesn't work as advertised.  But hey, it was discontinued five and a half years ago at this point so 
what do you want?  I figured that a test with an even older example I have sitting around in the junk box (A1143) would 
be similarly unsatisfying.

I'd really like to try these native IPv6 tests with my Verizon FIOS at home, but I think I already know the outcome...

-r