Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
 ·Colbanet
·TekSavvy Solutions..
| Tomato/MLPPP v2 FINAL released!
We are proud to announce that v2 of Tomato/MLPPP has been released. This is a major update to Tomato/MLPPP that vastly improves stability and reliability.
Today also marks the official launch of »fixppp.org, the new official home of the Tomato/MLPPP firmware. We've got a lot more planned for the site, but for now we're just launching it with the basic functionality. The new release can be downloaded from there. We've also made the source code for this release available as promised.
Here's a changelog for this release (versus v1, not the latest betas):
* Fixed a bug where the router would not properly handle the primary link going down
* Fixed a bug where if the primary link was down permanently, the secondary link would never connect. The previous two items sparked a complete re-architecting of how the router manages PPP sessions.
* Added better status reporting on the status overview page
* Fixed the issue where occasional IPCP conf request timeouts on connect caused PPPd to hang
* Fixed frequent disconnects under moderate to high packetloss conditions
* Fixed a bug where 3 or more links locked up the router 100% of the time
* Added a whole bunch of additional options (MTU/MSS/MRU/MRRU/etc) to the advanced option page, and moved MTU there.
* Fixed issues with OpenVPN, Slingbox, and other devices/apps that couldn't connect through Tomato/MLPPP. This should also help with sluggish web browsing performance reported in v1.
* Added support for Acanac and other ISPs that only support MLPPP on some (but not all) of their gateways.
* Changed official name in webui to Tomato/MLPPP to reflect what we're calling it everywhere else.
* A few UI label changes to improve consistency and correctness.
And here's our planned changes for the upcoming v3:
* Merge in changes from Tomato 1.19 --> 1.20
* Improve behaviour of MSS/MTU as it relates to UDP applications that don't properly detect the MTU
* Fisx the issue where the router stops trying to connect after suffering many (100+) consecutive connection failures
In case you missed it before:
DOWNLOAD: »fixppp.org |
|
the cerberus
join:2007-10-16
Richmond Hill, ON | Really nice work! I know you guys worked hard on this, but I cant help but notice several references to visit fixppp.org for 3(or more) line support, but no documentation is there, it would be nice if that was added. Very very cool nonetheless! |
|
shopkins
join:2008-05-23
Nepean, ON | reply to Guspaz
Excellent work, congrats and thanks for everything. Once I get home and install it tonite I am sure that I will be amazed and impressed with the product. |
|
ealskriptik
join:2004-08-29
Cookstown, ON | reply to Guspaz
Good work! Now to pray that Big Bad Bell doesn't decide to turn on the option on the DSLAM software that will only allow one PPPoE connection per port. |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
·Colbanet
·TekSavvy Solutions..
| Single-link MLPPP theoretically doesn't require more than one connection per port. It's really just adds a 6-byte header that confuses DPI (and sequence numbers make it harder to throttle).
That said, the current implementation of Tomato/MLPPP briefly holds two connections for single-link setups. That's only to establish a control session (to manage the PPP device/bundle) and a child session (to manage the actual connection).
As soon as a child connection is established, the control connection is terminated, leaving the control session running in the background.
This is actually part of the connection logic for multi-link setups (one control, multiple children, and the ppp bundle isn't affected by children going up/down), but it's far simpler for the router to just use the exact same logic for single-link and multi-link.
That's not to say that this couldn't be changed if Bell decided to do as you say. |
|
HiVolt
Premium
join:2000-12-28
Toronto, ON
clubs: | reply to Guspaz
Very nice! Cool webpage also! 
--
,,!,,('-'),,!,, |
|
hkazmi
join:2004-07-12
Mississauga, ON | reply to Guspaz
excellent work guys. |
|
GIGABIT
join:2008-01-20
Etobicoke, ON
edit:
July 18th, @11:59AM
| reply to Guspaz
Looks nice! Can't wait to update tonight. |
|
matt_m
Premium
join:2007-04-07
Ottawa, ON | reply to Guspaz
Nice, but where is the "Donate" link? You guys have done a seriously good thing for lots of us.
Thanks. |
|
HiVolt
Premium
join:2000-12-28
Toronto, ON
clubs:
·TekSavvy Solutions..
·Bell Sympatico
| said by matt_m  :Nice, but where is the "Donate" link? You guys have done a seriously good thing for lots of us. Thanks. Yeah, for real... I'd have no issue donating by paypal.
--
,,!,,('-'),,!,, |
|
shopkins
join:2008-05-23
Nepean, ON
·TekSavvy Solutions..
·Bell Sympatico
| said by HiVolt :said by matt_m :Nice, but where is the "Donate" link? You guys have done a seriously good thing for lots of us. Thanks. Yeah, for real... I'd have no issue donating by paypal. Ditto. As long as I get a receipt to call it a business (network) related expense from PayPal  |
|
GearHead360
join:2002-12-14 | reply to Guspaz
Great work  |
|
waynezu
join:2008-06-21
Mississauga, ON | reply to Guspaz
good job, thanks |
|
distr0
join:2007-05-03
St George Brant, ON | reply to Guspaz
argh, I just installed the beta version last night! oh well, thanks for this! |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
·Colbanet
·TekSavvy Solutions..
| reply to HiVolt
Much props go to Jonathan Zarate (author of the Tomato firmware upon which this is based) for allowing us to use the Cyan stylesheet from Tomato itself. I'm completely useless at from-scratch web design, but given a base, I can usually pump out something at least usable. |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
·Colbanet
·TekSavvy Solutions..
| reply to GIGABIT
Assuming you're upgrading from either Tomato or Tomato/MLPPP, we do recommend this, yes. Instructions are included in the readme if you don't want to.
If you're updating from any other firmware (OpenWRT, linksys, dd-wrt, etc.), yes, it's pretty much required (much as it is with Tomato itself). |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
·Colbanet
·TekSavvy Solutions..
| reply to shopkins
(and other donation requests): We haven't really been interested in taking donations. If we did, it would be strictly towards paying for secondary DSL lines for DSL_Ricer and myself (we've done all testing on Jay Man's network remotely). And to be frank, the desire to get a second DSL line is entirely self-serving (Mmm... Speed...) as it would be useful for testing, but not required. I'm extremely uncomfortable accepting general monetary donations, but a second DSL line is something else.
I'll discuss the issue with DSL_Ricer; if anything, donations would go towards getting him a second line before me.
Oh, and if TekSavvy considered that we're responsible for a decent chunk of additional business as people order additional DSL lines from TekSavvy to use with Tomato/MLPPP, and that we're not getting referrals for those lines, and that we might be interested in ordering secondary DSL lines... |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC
·Colbanet
·TekSavvy Solutions..
| reply to distr0
If I recall correctly, the following items are changes from beta 2 (don't quote me on this):
* Added better status reporting on the status overview page (added in beta 1, revamped in beta 3 (unreleased, became final after some additional changes))
* Added support for Acanac and other ISPs that only support MLPPP on some (but not all) of their gateways.
* Changed official name in webui to Tomato/MLPPP to reflect what we're calling it everywhere else.
* A few UI label changes to improve consistency and correctness.
So other than the Acanac support (the checkbox to require MLPPP, which can be useful in other circumstances, and Acanac doesn't even support MLPPP quite yet), we're talking mostly about spit and polish. I do quite like the new status reporting in beta3/final, though. No actual additional information is really provided, but it's in a much easier to understand format.
I think that all but that last change made it into beta 3. That was never released, as we did some internal testing and decided that it was close enough to final that we should just do a bit of polish (the last item) and release it as final.
To be honest, we're at a bit of a loss about what else to add to the firmware. What you see in the plans for v3 is pretty much everything we could think of that should be added. If people have suggestions (or find any verifiable reproducible bugs), we're all ears. Keep in mind that Tomato/MLPPP is somewhat targeted; this isn't exactly a general purpose mod, and while we're willing to do stuff that isn't strictly MLPPP related, we probably aren't going to start adding stuff completely out of the blue.
On a random note, I should also mention that the source package for v2 final is enormous; it takes a rather long time to build up the nice and small patchset like we did for v1, so for now we've opted to just zip up the whole darned source tree (includes Linksys, Tomato, and Tomato/MLPPP stuff all together) and shove that up there. Eventually we'll get around to doing actual patches, but everything you need is still technically there. |
|
DSL_Ricer
Premium
join:2007-07-22
| said by Guspaz :If I recall correctly, the following items are changes from beta 2 (don't quote me on this): It also fixes a bug where if a secondary connection didn't reach an MLPPP capable endpoint, it'd restart the whole link, instead of just retrying that connection. |
|
Guspaz
Guspaz
Premium,MVM
join:2001-11-05
Montreal, QC | beta 2 didn't, strictly speaking, support operating on networks that don't have MLPPP on all connections. So the bug was sort of introduced and fixed between beta 2 and final. |
|
