This is about the configuration of the ACS URL onto the CPE via DHCP option 43.
Let’s see how this work.
Suppose we are using Linux DHCP server to perform this task. And suppose that our acs url is
let’s run the following code to get the hex encoding of the string:
This should print something like this:
0000000 h t t p : / / a c s . u r l . c |
68 74 74 70 3a 2f 2f 61 63 73 2e 75 72 6c 2e 63 |
0000020 o m : 9 9 9 9 / s t r i n g |
6f 6d 3a 39 39 39 39 2f 73 74 72 69 6e 67 |
This is the output of the “od” command which actually is an hex dumper.
So we have the ascii characters and the relative hex dump.
Our string should look like this:
68:74:74:70:3a:2f:2f:61:63:73:2e:75:72:6c:2e:63:6f:6d:3a:39:39:39:39:2f:73:74:72:69:6e:67 |
they’re 30 chars, in hex 1E.
Now we have to put in front of the above string two more bytes: the first is “01″ meaning that we are passing acs url, the second is “1E”, actually the length of the string representing acs url.
So the final string we’ll be:
01:1E:68:74:74:70:3a:2f:2f:61:63:73:2e:75:72:6c:2e:63:6f:6d:3a:39:39:39:39:2f:73:74:72:69:6e:67 |
Now let’s edit the DHCP configuration in this way:
option subnet-mask 255.255.255.0; |
option routers 30.30.7.2; |
ddns-update-style interim; |
option domain-name "mydomain.it"; |
subnet 30.30.7.0 netmask 255.255.255.0 { |
option vendor-encapsulated-options 01:1E:68:74:74:70:3a:2f:2f:61:63:73:2e:75:72:6c:2e:63:6f:6d:3a:39:39:39:39:2f:73:74:72:69:6e:67; |
option domain-name-servers 1.1.1.1,2.2.2.2; |
hardware ethernet 00:11:22:33:44:55; |
Reboot CPE and wait for it to ask an IP address to the DHCP server. This is supposed to reply with option 43 (acs url) and CPE’s CWMP agent should contact our ACS server at the specified url.
ref :
http://pierky.wordpress.com/2009/05/20/acs-url-configuration-via-dhcp-vendor-specific-information/
Good sharing!
回覆刪除