dhcpcd-discuss

Hi Ron,

 

> without thinking how to integrate it with dhcpcd. I mean, start by writing the commands
> assuming it has all the information it needs. You might use pseudo values like

> ip route I_WILL_SOMEHOW_FIND_THE_IP_LATER
that’s not the point, it’s obvious:

/usr/bin/ip -6 route add default via GATEWAY dev WAN table main mtu MTU expires EXPIRATION

 

But, ipv6-route added this way needs all those parameters. For example: routes communicated by ROUTERADVERTISMENT message (IPv6 NDP) have explicitely defiled lifetime, typically 1800 sec. How to get the lifetime from RA? Are routes communicated by DHCPv6 response also expiring? How to bring those two sources of routing information together? DHCPCD is already managing it in code properly (hopefully), why to reconstruct this logic in the shell script?


> Don't hesitate to reply I was too basic, and you are more experienced then me. 

Indeed, I’m software developer so I know how to create a script. I’d surely manage it finaly but it would take plety of iterations to fugure out all undocumented details (or to find it in DHCPCD source code).