Print

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

[j0hn]

AAISP have actively worked with ZyXEL to get it added to every ZyXEL device they have shipped.
They haven't succeeded once.

https://support.aa.net.uk/VMG1312-B10A:_Bugs

Code: [Select]

Bridging 1508 bytes ethernet
Issue Description
Bridging does work, but we'd very much like the router to support baby jumbo frames bridging to VDSL and ADSL, to support *at least* 1508 bytes to allow RFC4638 PPPoE to a connected device.

Date Reported
2015-02-19

Updates
2015-02-19 ZyXEL development team aware, and are looking in to whether they can support this feature.
2015-03-28 Still ZyXEL HQ are still evaluating the effort to make this change.
2015-04-14 ZyXEL are working on supporting larger Ethernet frame sizes as part of the 'BT Lab modem conformity tests' (SIN 498). No ETA though.
2015-06-02 This has been chased with ZyXEL, we expect some form of update in the next couple of days
2015-06-03 Software Patch 6 is nearing release but we don't have details of which open issues are solved in this.
2015-06-09 We are chasing for further updates
2015-06-10 ZyXEL R&D resource is tied up and focus is on getting BT testing completed/passed, this feature is required to pass BT testing anyway, so we need to wait for the testing to complete and pass and then we should expect new software
2015-06-25 ZyXEL UK have been reminded again, and in turn they will be chasing up ZyXEL HQ. We're still waiting for the router to pass BT conformance testing
2016-10-24 Sadly (even though the hardware can support it) ZyXEL have told us that they will not be adding support for baby jumbo frames.
Resolution
Not going to be supported. (sorry)
The VMG1312-B10D has an extremely poorly performing chipset. I've not looked up the other device mentioned. Unless it has a BCM63168 or BCM63138 I wouldn't go near it.

[highpriest]

AAISP have actively worked with ZyXEL to get it added to every ZyXEL device they have shipped.
They haven't succeeded once.

Given that they are still hounding ZyXEL (as of March 2018), they haven't quite given up

The VMG1312-B10D has an extremely poorly performing chipset. I've not looked up the other device mentioned. Unless it has a BCM63168 or BCM63138 I wouldn't go near it.

The 3925 is BCM63168 equipped. It is well liked by Kitz users, as far as I can tell.

[j0hn]

It's a shame it shares the same horrible shape/style as many of the other Zyxels.

I love how the vmg1313-b10a wall mounts like the HG612, with the ports underneath.

AAISP spent over 18 months trying to get Zyxel to add support for Baby Jumbo Frames, only for them to discontinue the device and replace it with the vmg1312-b10D. Which also doesn't support Baby Jumbo Frames.
Doesn't seem like a high priority for Zyxel.

[highpriest]

Spotted this: https://github.com/Olipro/VMG1312-B10A

Anyone brave enough to try it?

This is the commit:

https://github.com/Olipro/VMG1312-B10A/commit/101a09d1c515fce95e987255e5d0cf66a828a1f5

[johnson]

Oh snap!

Guess I'm going to brick my 1312 this weekend.

[burakkucat]

Guess I'm going to brick my 1312 this weekend.

But not if you feel confident enough to recover it via the console serial port . . . the header pins are already present on the PCB. 

[johnson]

But not if you feel confident enough to recover it via the console serial port . . . the header pins are already present on the PCB. 

Indeed! Have a usb serial converter lying around somewhere.

[johnson]

Spotted this: https://github.com/Olipro/VMG1312-B10A

Anyone brave enough to try it?

This is the commit:

https://github.com/Olipro/VMG1312-B10A/commit/101a09d1c515fce95e987255e5d0cf66a828a1f5

Can anyone make sense of the two changes this chap has made? They seem sane but I'm far from a kernel hacker.

The first change in "bcmxtmrt_atm_ioctl" seems to be something you could set later i.e with "ifconfig ptm0 mtu 1508"?

I guess the second in "DoCreateDeviceReq" seems more fundamental as its set as the ppp session is brought up.

 

[burakkucat]

Can anyone make sense of the two changes this chap has made? They seem sane but I'm far from a kernel hacker.

I neither get a sensation that someone has "tweaked my tail"    nor a "warm and fuzzy" feeling    when viewing those few lines out of context. Overall, the changes look perfectly reasonable. But somebody needs to try the experiment. I wonder who that might be . . . 

[johnson]

It boots!

Guess that CFLAG is magic because all the interfaces now have an MTU of 2048.

Not attached it to my line yet, will report back.

[burakkucat]

It boots!

   

Guess that CFLAG is magic . . .

It is just defining a global parameter to be used when "make" is invoked.

. . . all the interfaces now have an MTU of 2048.

I'm not sure from whence it obtained that value!

But, certainly, progress has been made. 

[johnson]

It is just defining a global parameter to be used when "make" is invoked.

Indeed, but one that means the driver now supports an MTU over 1500 - "DCONFIG_BCM_ETH_JUMBO_FRAME", no idea where 2048 comes from, jumbo frames are up to 9000 right?

Anyway:

Code: [Select]

ifconfig eth1 mtu 1508
ifconfig: SIOCSIFMTU: Invalid argument

becomes pleasant silence now.

[burakkucat]

. . . jumbo frames are up to 9000 right?

Yes, that is my understanding.

[Alex Atkin UK]

What has baffled me is how the HG612 handles it.  All the interfaces show an MTU of 1500 yet it works fine.

[johnson]

Well the electrical storm this evening had other ideas about me trying out the modem.

What has baffled me is how the HG612 handles it.  All the interfaces show an MTU of 1500 yet it works fine.

Yeah it doesnt make sense, still haven't gotten around to trying an old HG612 but I was assuming its interfaces MTUs would change in accordance.