ghost32 wrote:
MrT0ad wrote:
It should be username|password rather than just username. The character in between both is "|".
You can try to obtain an IP automatically after doing this (rather than setting the previously assigned IP manually). If this works for you is very good news indeed.
unfortunately I can add it in but it doesn't make any difference.
is there any one from the draytek support reading this... that could at least point us in the right direction till they provide beta firmware for more models?
what did they have to add to make it work for the other model?
Is it just a matter or editing the srv dhcp custom_option with a specific dhcp code (61 or which ever) and then your sky details?
or are we way off base?
I find the documentation of the "custom_option" a bit... sketchy.
Perhaps to someone with better knowledge than mine is all glaringly obvious, but at this point I'm not even sure on what would be the command to enable this...
srv dhcp custom_option -e 1 -t 1 -q 61 -n 1234567890ab@skydsl|1234567890abcde perhaps?
alternatively you could try converting the string "1234567890ab@skydsl|1234567890abcde" (that's just an example, you should use your own
;) )into HEX (for instance using
http://www.string-functions.com/string-hex.aspx) and use the output string instead.
I've used the -q and -n modifiers because according to the documentation the custom option is limited to either one single 64B option or two 32B options, and when I converted my username|password to hex the resulting string was bigger than 32B (35B exactly) so I went for the single 64B option.
Of course this is all theory + wild guessing from the info in the Sky MER wiki and the information about this particular terminal command scattered along the net... I don't have a Draytek router myself, I'm using pFsense because it supports this authentication method "out of the box".
EDIT: In fact I have the feeling that this command affects the DHCP server (the one used to assign IPs to the devices within your LAN) and not the DHCP client (the one used to dynamically obtain an external IP from your ISP).
Most of these devices are multi-WAN yet this command doesn't seem to have a modifier to discriminate which interface it applies to, that combined with the fact that the command starts with "srv" (short for "server" in many circumstances) makes me think we are barking at the wrong tree here.
