I have found this information for Tomato (see bottom of my post for the steps) I just not expeinced enough to know if something like this would be possible to do on DD WRT.
I know DD WRT is free but supporting MER I think would get more people using DD WRT as Sky router are rubbish and if there only one router out there currently that supports SKY MER if DD WRT were to support it would open it up to alot more routers and therefore huge number of users. Sky are now one of our fastest grown ISP(in the UK) due to great performance and price.
1) Convert your PPPusername|PPPpassword string into HEX - I used http://www.string-functions.com/string-hex.aspx
e.g. 1a2b3c4d5e6f@skydsl|zzc7Zovbt5Fpa7B turns into 31613262336334643565366640736b7964736c7c7a7a63375a6f766274354670613742
2) In 'Advanced->DHCP/DNS DHCPC options enter '-x 61:00' immediately followed by the converted string from above. e.g. '-x 61:0031613262336334643565366640736b7964736c7c7a7a63375a6f766274354670613742' & save.
3) In 'Basic->Network set your network type to DHCP, default MTU & save
The above works in combination with a Draytek Vigor 120 ADSL2+ modem. Settings for that are: MpoA page: MpoA Enabled, Encapsulation: 1483 Bridged IP VC-Mux, VPI 0, VCI 40
Any help or advice would be great appreciated, and if anyone can tell me if I could do something similar using command lines with DD WRT.
1) Convert your PPPusername|PPPpassword string into HEX - I used http://www.string-functions.com/string-hex.aspx
e.g. 1a2b3c4d5e6f@skydsl|zzc7Zovbt5Fpa7B turns into 31613262336334643565366640736b7964736c7c7a7a63375a6f766274354670613742
2) In 'Advanced->DHCP/DNS DHCPC options enter '-x 61:00' immediately followed by the converted string from above. e.g. '-x 61:0031613262336334643565366640736b7964736c7c7a7a63375a6f766274354670613742' & save.
3) In 'Basic->Network set your network type to DHCP, default MTU & save
The above works in combination with a Draytek Vigor 120 ADSL2+ modem. Settings for that are: MpoA page: MpoA Enabled, Encapsulation: 1483 Bridged IP VC-Mux, VPI 0, VCI 40
I have it working using an x86 Linux box running the busybox+uclibc dhcp client implementation built using buildroot. I had to use the -x argument and provide the arguments encoded as hex strings, but the rest was perfectly straigforward.
MER is just DHCP with option 60 and 61 using the ISP provided strings. The DHCP client in DD-WRT does not support these flags (on my D-Link DIR-615 D2 at least).
However, I've had no luck with a Buffalo WZR-1800DH using the latest 24/07/2013 build. attempting to downgrade to the 27/05/2013 build bricked the router!
However, I've had no luck with a Buffalo WZR-1800DH using the latest 24/07/2013 build. attempting to downgrade to the 27/05/2013 build bricked the router!
I have been using this method forever on my WNDR3700.
Indeed, build 21676 is the last build that this works on. I installed the latest 23082 build and it will no longer connect to Skys network. Flashing back to 21676, and all is well.
Sash (or anyone), any idea what has changed in the build to prevent this from working?
I'm using the same method described above on a Linksys E3000 running build 21676 for quite a while now.
In case a developer is watching this topic, can you please make this an officially supported option? Its just a one liner change to the udhcpc startup command. The only work required to support it officially would be the GUI modification for users to enable it.
I'm using the same method described above on a Linksys E3000 running build 21676 for quite a while now.
In case a developer is watching this topic, can you please make this an officially supported option? Its just a one liner change to the udhcpc startup command. The only work required to support it officially would be the GUI modification for users to enable it.
Thanks
This (the startup script posted) worked in build 22118, but no longer works in the latest build 23082. It appears that udhcpc has moved or been integrated into busybox, and it has killed this workaround.
I have asked what I can do to get it to work, but no response. Sadly, despite spending over a day flashing, reflashing, looking at the build timelines - I am unable to determine why this is now broken, or how to fix it - I am not familiar enough with Linux
Looks like I am stuck on the last working build now!
Last edited by jasonkruys on Sun Dec 15, 2013 13:34; edited 1 time in total
Success! In the later builds you need to use udhcpc as compiled into busybox, and modify the command line option. Similar to the instructions for Tomato build.
First, convert the entire string for your username and password to HEX - ie 1a2b3c4d5e6f@skydsl|zzc7Zovbt5Fpa7B turns into 31613262336334643565366640736b7964736c7c7a7a63375a6f766274354670613742
Then put the following into your startup command, replacing XXXX with the HEX value determined above:
This will allow you to continue using MER (RFC 2684) (MAC Encapsulated Routing) and in particular sky modified version of MER on the later builds.
Thanks, again, to Dragon2611 on skyuser for his help! And also for supercilious - had I read his comment properly in the first place about using -x option, it would have set me in the right direction!
btw have you already opened a ticket with this problem?
I haven't - I don't see a problem anymore. Putting the code in my previous post in the startup now works again...Or do you mean the OP who requests the feature be added into the GUI?
Correction. This works on 22118, but not the latest released build 23082