ypy705 / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 0 forks source link

Request:Addition of Option 61 Client ID for DHCP #631

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

I'm currently running 3.0.3.1-027, glad to report for me it's stable with no 
issues.
I have a request, my ISP ( SKY ) use option 61 where by the clientID as 
username|password converted to a HEX string is sent.

This can manually be achieved using the commend: /sbin/udhcpc -i eth3 -x 
0x3d:667265647c66726564
and it does work.

There is also the chance they may at some point add the DeviceID/MAC Address to 
the options, at present they are not doing this and I am not sure where it 
would be inserted into the ID hex string.

In the above case the password|username is fred|fred, note this is not my 
username or password! :)

Would it be possible to add this to the Web WAN Settings interface?

Or is it there and I cant see it?

Original issue reported on code.google.com by mjwas...@googlemail.com on 6 Dec 2012 at 3:10

GoogleCodeExporter commented 8 years ago
Do you mean to add option to Web WAN settings which allows to send hex string 
of username|password to ISP with option 61 of udhcpc?
I can't see option which allows to send DeviceID/MAC Address to ISP with 
udhcpc. Are you sure it can be required?...

Original comment by d...@soulblader.com on 6 Dec 2012 at 10:07

GoogleCodeExporter commented 8 years ago
I can add ClientID (OPT61) field to Advanced_WAN_Content.asp and you will be 
able to set any HEX value to this field. 

Original comment by andy.pad...@gmail.com on 8 Dec 2012 at 11:17

GoogleCodeExporter commented 8 years ago
Hi Guys,

Thanks for getting back to me. 
I've had chance to to a little more research this morning, and it would seem 
DeviceID/Mac address is option 60; currently the ISP do not use it, but that 
does not mean they would not use it in future.

Here's a link to the Wiki I found that details it, and a this is a snippet I 
copied from that wiki.

Unfortunately this step is a bit harder. When the official Sky router requests 
an IP address, it sends some extra details as "DHCP Options". The details are 
as follows:
Vendor Identifier 

(Option 60):     
Hardware Identifier
                       firmwareversion|2ndHardwareSerial|skysg2|1stHardwareSerial

(Option 61)
Client Identifier    PPPUsername|PPPPassword

Thankfully, the vendor identifier does not seem to be required to get an IP 
address, this could however change in the future.

This is the link to the relevant wiki.

http://wiki.ph-mb.com/wiki/MER

Obviously MER itself is not the issue, as the BT modem that sits in front of 
the sky router handles that part of the job; only getting an IP address is what 
we are interested in.

Original comment by mjwas...@googlemail.com on 9 Dec 2012 at 11:23

GoogleCodeExporter commented 8 years ago
Has MER been implemented in the latest version of the firmware? 

Original comment by Datab...@googlemail.com on 18 Jul 2013 at 8:32