O Canada! > Canadian > TekSavvy > Tomato/MLPPP v2 beta 2 released

Tomato/MLPPP v2 beta 2 released

tomato-mlppp···2.7z.zip 2,798,730 bytes Tomato/MLPPP v2 beta 2

v2 beta 1:

- Fixed a bug where the router will not properly handle the primary link going down (unless the secondary link also goes down).
- Fixed a bug where if the primary link is down permanently, the secondary link will never connect. The previous two items sparked a complete re-architecting of how the router manages PPP sessions.
- Add some sort of status reporting for the multilink status
- Fix the issue where occasional IPCP conf request timeouts on connect cause PPPd to hang
- Fix frequent disconnects under moderate to high packetloss conditions
- Investigate PMTU clamping as it relates to reports of slow browsing speed
- Fixed a bug where 3 or more links lock up the router 100% of the time

v2 beta 2:

- Added a whole bunch of additional options (MTU/MSS/MRU/MRRU/etc) to the advanced option page, and moved MTU there. We moved MTU because too many people were messing with it when it should be left on "automatic" for the vast majority of cases.
- Hopefully fixed issues with OpenVPN, Slingbox, and other devices/apps that couldn't connect through Tomato/MLPPP. Tried to fix this by increasing the automatic MTU, MRU, and MRRU, while leaving the MSS settings at the lower settings. This should cause most apps to correctly use the optimal packets, while "dumb" apps that try to send oversized packets will at least succeed via fragmentation.
- Fixed the status page not updating properly when multilink was disabled

Changes currently scheduled for v2 beta 3:

- Change/improve status reporting to be more obvious ("1 of 1 links connected" instead of "Connected 1/1"), and always specify the MLPPP status rather than only when it fails.
- Add support for Acanac and other ISPs that only support MLPPP on some (but not all) of their gateways. This is not difficult to do, and we have a test account from Acanac to work with
- Change official name in webui to Tomato/MLPPP to reflect what we're calling it everywhere else.

Changes currently scheduled for v3:

- Add kernel support for faking a smaller MTU/MRU/etc. while actually allowing oversized (up to 1500b) packets. This will further improve on the previous changes in this area by informing non-TCP applications that do MTU detection of the optimal MTU, but still work with applications that don't or can't detect the MTU.
- Optimize QOS for ATM cell sizes rather than IP packet sizes.
- Add support for overriding user settings after upgrading to a new version. This will remove the requirements for NVRAM resets (or manually fixing broken settings) after flashing.

Cheers, Guspaz

reply to Guspaz

Administration\Configuration\Select --> Erase all.. NVRAM ...

reply to Guspaz
As a bit of an update on where we stand:

- We've got a nice short 6-letter .org domain name for the firmware website. Let me tell you, we were tempted to register mlpppoe.ca, just to poke fun at TSI

- I'm currently building out a website for that. It'll be a fairly simple deal, just need to put a few more hours work into it. It should nonetheless be a huge improvement over what we have now, with enormously long forum threads around here where we try to deal with all this stuff.

- I've finally notified the author of Tomato as to what we're doing, and to ask him for permission to use CSS/visual styles from the Tomato UI for the site. I'll hold back on posting the URL of our new site until I hear back from him (or if I don't hear back).

- We've got a test account from Acanac for the purpose of adding their style of network setup (many gateways, only one supports MLPPP) to the firmware. That will be in beta 3.

- DSL_Ricer is now working on Beta 3, which we hope will be out soon; it's not a huge set of changes from beta 2.

I'm really looking forward to where this is going. Beta 3 is going to open up the firmware to a whole new ISP (Acanac), and the website is going to be a huge bump up from what we've got now; hopefully we can eliminate a huge portion of the redundant questions and discussion that we're getting about here that could actually be handled by a FAQ.

We'll probably continue using this forum for release notifications and all discussions, it's just that we should really be able to cut down on the volume of discussions by centralizing a lot of the info on this stuff. Exciting!

Congrats on getting the beta out. I'm using the firmware with Velcom and will post any difficulty I have with it.

reply to Guspaz
I got the new version running now. Nothing to report so far.

reply to Guspaz
- Fix the issue where occasional IPCP conf request timeouts on connect cause PPPd to hang

The only problem I have with version 1 is that the connection goes dead from time to time and I must disconnect and reconnect so it work again. Is that fix this problem? I'm not sure and don't want to change it as I have many configuration as i have 2 audio server 2 web server, 1 ftp server and 1 video server on my network. don't want to restart the configuration unnecessarily.
--
Connection: Teksavvy 6016/800 fast path premium
www.Globaltuners.com Remotely controled Radio scanner

thanks for your reply I will give it a try.

reply to vitesse
Actually, that issue you're having is a combination of two things. First, the lack of disconnects, which was fixed when we redid how connections are managed. And second, v1 had an issue where not enough LCP echo failures were required to detect a disconnect; a bit of packetloss and the router would figure the connection was down (and then fail to reconnect).

That bug was fixed in beta 1. The relevant entry is "- Fix frequent disconnects under moderate to high packetloss conditions".

Of the two releases (beta 1 and beta 2), obviously beta 1 was the major release. It was the first new version of beta 1. Beta 2 only has some tweaks and bug fixes from there.

reply to Guspaz
Don't know if this will help but I have just installed the latest beta2 firmware on an ASUS WL500GP. As a newbie to Tomato I can say that it was very painless. Other than a panic when I may have restarted too soon (used the tftp method to install the firmware) it is up an working. I had actually been thinking of using an OS firmware but had an incompatible router (Linksys WRV200).

I am impressed with the work. Will try and report back if I can contribute. I like the device list that is on the status page. Probably basic but I had asked a tech buddy to tell me how to discover what wireless devices were using my network and he was not totally certain how with the old router. I do not need to bug him now !

MLPPP is enabled and speed tests are unchanged. I am using single link, getting 4500/600 or so - what I would expect. I am not downloading any torrents yet but I will try later.

reply to Guspaz
Can you guys add support for multiple modems on the wan port.

I have a switch I have hooked up to both modems and I would prefer to keep the modems just on the wan side.

Right now I have to connect a cable from LAN to wan then connect the modems switch to lan.

That's impossible to do with PPPoE. No device/software can do that.

You can just use a VLAN to create another WAN port. That's all the WAN port is, after all, one of the switch ports that is on a different VLAN.

reply to Guspaz
Nice speed tests with this build with everything on automatic. A big improvement over beta 1. Well done.
(using single link MLPPP).

reply to Guspaz
Is the MTU supposed to be set at 1500 now? Since previously it was set at 1442 for single link.

Or is that what MMS is doing now?

Yes.

reply to Guspaz
Just wonder if the "MLPPP interface" should stick with "vlan1" as the default value or change it?

You can technically change it to br0 if would rather plug your modem into your switch instead of the WAN port, but that's not advisable.

reply to Guspaz
will this work on the whr-g125?