dhcpcd-discuss

Le dimanche 29 avril 2018, 23:30:28 CEST Roy Marples a écrit :
> Hi
> 
> On 29/04/2018 21:04, stephane@xxxxxxxxxxxxx wrote:
> > Hello all.
> > 
> > In order to make my dhcp6 requests work, I have to make a specific
> > request where 80 % of options are useless, but it's what it takes to
> > get my ISP's routers to let them through.
> > 
> > I particularly have to have options sol_max_rt, inf_max_rt, then 94,
> > 95 and 96 (which are S64 map-e, map-t and 4over6).
> > 
> > I wonder how I can make those three last options.
> > 
> > Notice also that I am ok, if need be, to be tester. (I just have no
> > clue about how to program a dhcp client, ipv4 or 6).
> 
> I just looked up rfc7598 for option 94 and it went woosh over my head.
> My understanding is that the DHCP client just requests these options in
> the ORO. dhcpcd can then decode the contents for option use via a hook
> script.
> 
> Attached is a patch to allow this.
> You should be able to add this to dhcpcd.conf
> 
> # SOL_MAX and INF_MAX should already be requested by default
> option dhcp6_sol_max_rt, dhcp6_inf_max_rt
> # Request 94, 95 and 96
> option dhcp6_s46_cont_mape, dhcp6_s46_cont_mapt, dhcp6_s46_cont_lw
> 
> You should then see the options appear as variables for use in
> dhcpcd-run-hooks(8). However, I have no means of testing this. dhcpcd
> cannot fully decode option 92 due to the options appearing AFTER a
> variable length part. I have no interest in even attempting to fix this
> as you've not noted it as a requirement.
> 
> Let me know how it works out for you!
> 
> Roy

stephane@mirror:/usr/local/src/dhcpcd doas /sbin/dhcpcd -D re0 
persistent
# Request 94, 95 and 96 

-- 
Ce fichier signature.asc ? C'est une signature GPG.
Si vous voulez savoir pourquoi j'utilise GPG et pourquoi vous le devriez aussi, vous pouvez 
lire mon article :
http://www.22decembre.eu/2015/03/21/introduction-fr/

Attachment: signature.asc
Description: This is a digitally signed message part.