dhcpcd-discuss

our ISP here (Orange) is using custom auth for DHCPv4 & DHCPv6.

The packet to send must be exactly like this (as captured by wireshark:)

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/xxxxxx

I've tried to do this using the autoprotocol and authtoken options but It doesn't work. Algo can't be 0 and RDM value neither.

with dhclient we do this using a custom option like this:

option authsend code 90 = string;
send authsend 00:00:00:00:00:00:00:00:00:00:00:66:74:69:2f:*:*:*:*:*:*:*;



Le ven. 18 nov. 2016 à 12:11, Roy Marples <roy@xxxxxxxxxxxx<mailto:roy@xxxxxxxxxxxx>> a écrit :
Hi

On 18/11/2016 10:50, Kirth Gersen wrote:
> I'm trying to send (not receive) a custom authentication option (option
> 90) but I don't understand the behavior of define , embed, encap, etc
>
> I've read dhcpd.conf(5) but it's not very clear on how to do this. What
> is the difference between embed and encap for instance ? how do I fill
> values to send ?
>
> any help would be appreciated

dhcpcd does not support the sending of customised options, just their
retrieval and expansion into shell variables.

dhcpcd fully supports all RFC's for authentication on option 90 .... and
this is documented in dhcpcd.conf(5).

What are you trying to do that is not supported by this?

Roy