hi,
在 2020-11-28 15:46:59，"Andrei Borzenkov via networkmanager-list" <networkmanager-list gnome org> 写道：
>That's rather concise answers.
>
>28.11.2020 06:00, Mars via networkmanager-list пишет:
>> Hi Thomas,
>>
>>
>> Much thanks for your reply, my problem is that NM cannot deal with the DHCPv6 message with IA_PD option,
>
>It is unclear what you mean here. NM supports IA_PD for connection
>sharing, it will use prefixes provided by IA_PD on upstream interface to
>configure downstream interface. Downstream interface (or more precisely
>- connection active on downstream interface) has to be configured with
>ipv6.method=shared.
>
dhclient can send dhcpv6 request with -P option for IA_PD as follows :
/sbin/dhclient -6 -1 -P -lf /var/lib/dhclient/dhclient6--eth0.lease
lease6 {
interface "eth0";
ia-pd 3e:14:5e:4a {
starts 1606555291;
renew 3600;
rebind 6300;
iaprefix 240e:1234:cc20:4000::179/64 {
starts 1606555291;
preferred-life 4294967295;
max-life 4294967295;
}
}
NM always configures the prefixlen 128 with hardcode .
>You need to describe what you have configured, what results did you
>expect and what results you observe before any useful comment can be made.
>
>
>> the default IA_NA option with NM cannot generate the right prefixlen, just configuring 128 .
>>
>
>Is it separate issue or somehow connected to the previous one?
>
>DHCPv6 does not provide address prefix length at all. Every address
>returned by "IA Address" DHCPv6 option has prefix 128.
>
>Again you need to explain what you observe and what exactly does not
>work or works incorrectly and why you think it is related to address
>prefix length.
>
>>
>> Best Regards
>> ------------------
>> Mars
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> At 2020-11-27 17:54:26, "Thomas Haller" <thaller redhat com> wrote:
>>> On Fri, 2020-11-27 at 09:48 +0800, Mars via networkmanager-list wrote:
>>>> hi,
>>>> NM uses nm-dhcp-helper as network configuration script for dhclient
>>>> as follows , how to confiure dhclient-script file within NM ?
>>>>
>>>> /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf
>>>> /var/run/dhclient-eth0.pid -lf /var/lib/NetworkManager/dhclient-
>>>> 5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03-eth0.lease -cf
>>>> /var/lib/NetworkManager/dhclient-eth0.conf eth0
>>>> Thank you very much for any help you can provide.
>>>
>>>
>>> Hi,
>>>
>>>
>>> You cannot (*). When NetworkManager runs dhclient, then this is mostly
>>> an implementation detail for doing DHCP. Sure, it honors dhclient's
>>> config files in /etc/dhcp and it also dispatches the dhclient hooks.
>>> That is very powerful (since it's just arbitrary scripts that get
>>> executed), but it's also undesirable because the funcitonality is not
>>> available with dhcp=internal plugin and not available via
>>> NetworkManager API and NetworkManager mostly doens't know what is
>>> happening there. But in general, this is not supposed to give the user
>>> direct access to dhclient.
>>>
>>> (*) well, of course you can do all kind of hacky solutions, like
>>> replacing /usr/libexec/nm-dhcp-helper with a wrapper script.
>>>
>>> It might be better to explain what you ultimately want to do. Instead
>>> of asking how to do something that you think might be a solution for
>>> you (without explainging what your actual problem is).
>>>
>>>
>>> best,
>>> Thomas
>>>
>>> _______________________________________________
>>> networkmanager-list mailing list
>>> networkmanager-list gnome org
>>> https://mail.gnome.org/mailman/listinfo/networkmanager-list
>
>_______________________________________________
>networkmanager-list mailing list
>networkmanager-list gnome org
>https://mail.gnome.org/mailman/listinfo/networkmanager-list
