Add user-defined options (77 & 90) for WAN DHCP requests (Orange French ISP)

[Ahbrasax]

Hello,

The present release branch 384.5 support two WAN DHCP options : 60 and 61.

My current Internet access is provided by Orange ISP in France. This one allows me two methods of wan connexion :

An old connection type based on PPPoE protocol and an other based on dynamic IP attribution (IPoE).

At present, Orange ISP is trending to migrate all of their customer to IPoE for the new xDSL and fiber customers.

Anyway, if I want to get an IP though DHCP on my WAN connection, I need to provide the following DHCP options :

- **(60)** vendor-class-identifier=sagem
- **(77)** userclass=+FSVDSL_livebox.Internet.softathome.Livebox3
- **(90)** authsend=fti/xxxxxxx ## xxx hidden for anonymity, it is my ISP personal identifier

This is required by my ISP for identification purpose.
All these values need to be supplied in hex format

**Linux dhclient example :**

```
send vendor-class-identifier = "sagem";
option userclass code 77 = string;
send userclass 2b:46:53:56:44:53:4c:5f:6c:69:76:65:62:6f:78:2e:49:6e:74:65:72:6e:65:74:2e:73:6f:66:74:61:74:68:6f:6d:65:2e:4c:69:76:65:62:6f:78:33;
option authsend code 90 = string;
send authsend 00:00:00:00:00:00:00:00:00:00:00:66:74:69:2f:*:*:*:*:*:*:*; ## replace star with your identifier in hex format..
```

If this DHCP options code were implemented udhcpc command line should be :

/sbin/udhcpc -i br1 -p /var/run/udhcpc0.pid -s /tmp/udhcpc -O33 -O249 -V sagem -x "0x4d:2b46535644534c5f6c697665626f782e496e7465726e65742e736f66746174686f6d652e4c697665626f7833" -x "0x5a:00000000000000000000006674692f**************"​

Tested and approved : I am able to retrieve my public IP from my ISP with this customized udhcpc command line

**DHCP dump WAN request (Wireshark)**

```
802.1Q Virtual LAN, PRI: 6, CFI: 0, ID: 832
Bootstrap Protocol (Discover)
Message type: Boot Request (1)
Hardware type: Ethernet (0x01)
Hardware address length: 6
Hops: 0
Transaction ID: 0x0f48395c
Seconds elapsed: 1
Bootp flags: 0x8000, Broadcast flag (Broadcast)
1... .... .... .... = Broadcast flag: Broadcast
.000 0000 0000 0000 = Reserved flags: 0x0000
Client IP address: 0.0.0.0
Your (client) IP address: 0.0.0.0
Next server IP address: 0.0.0.0
Relay agent IP address: 0.0.0.0
Client MAC address: Sagemcom_xx:yy:zz (2c:39:96:xx:yy:zz)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name not given
Magic cookie: DHCP
Option: (53) DHCP Message Type (Discover)
Length: 1
DHCP: Discover (1)
Option: (55) Parameter Request List
Length: 11
Parameter Request List Item: (1) Subnet Mask
Parameter Request List Item: (3) Router
Parameter Request List Item: (6) Domain Name Server
Parameter Request List Item: (15) Domain Name
Parameter Request List Item: (28) Broadcast Address
Parameter Request List Item: (51) IP Address Lease Time
Parameter Request List Item: (58) Renewal Time Value
Parameter Request List Item: (59) Rebinding Time Value
Parameter Request List Item: (90) Authentication
Parameter Request List Item: (119) Domain Search
Parameter Request List Item: (120) SIP Servers
Option: (60) Vendor class identifier
Length: 5
Vendor class identifier: sagem
Option: (77) User Class Information
Length: 44
Instance of User Class: [0]
User Class Length: 43
User Class Data: 46535644534c5f6c697665626f782e496e7465726e65742e736f66746174686f6d652e4c697665626f7833
Option: (90) Authentication
Length: 22
Protocol: configuration token (0)
Algorithm: 0
Replay Detection Method: Monotonically-increasing counter (0)
RDM Replay Detection Value: 0x0000000000000000
Authentication Information: fti/*******
Option: (255) End
Option End: 255

```


Could you please expose option 77 and 90 in the asuswrt-merlin Gui ?

Regards

 

[el pescador]

Im with orange espana.
vlan832
dhcp/static ip

Not sure what your trying to say as some of that is too technical for me.

I had a 2 in one modem router....orange eventually updated firmware to put the livebox frbra into bridge mode....from there on the ASUS you put it in automatic ip....dhcp query frequency "agressive mode".

I messed about with the router ip but thats another story i think

 

[RMerlin]

I'd rather not start implementing non-standard support for every ISP out there that has a twisted setup, sorry. Options 60 and 61 were added because multiple ISPs rely on it, and also because a good portion of the support was already there from Asus (for DSL ISPs). I simply exposed the setting to DHCP users as well.. If I added two more options for Orange, then every weird ISP will also require me to start adding their own particular options - it will never end. It will lead to general code and UI bloat, and also introduce a bunch of settings that I have no way of testing to ensure their continued functionality.

 

[Ahbrasax]

I understand the problematics you exposed to me. I fully agree with it. Maybe I was too driven by my issue in asking a GUI update.

My weird ISP is using uncommon DHCP options thats no need to be exposed in the common ui. However the asus udhcpc binaries manage the "-x" commutator that's allow us to add options in our dhcp requests.

Yesterday, I compiled a custom firmware with my specifics included in udhcpc.c file in barbarian way, hard coded for quick testing purposes. I have been able to connect in IPoE to my ISP, so far, so good.

I saw that actual firmware provides postconf customization for appending content to various configuration files that are created by the firmware. Unfortunately at this time, udhcpc.conf file is not exposed for such config additions.

If we were able to have the ability to access to specific configuration additions to udhcpc, it would be great for all of us whom rely on a no standard ISP.

 

[RMerlin]

There is no udhcpc.conf, the busybox applets don't support config files, only command line switches.

 

[Drthrax74]

supply add