Why IPv6AcceptRA is disabled in phosphor-network
Hi all,
I want to set DHCPv6 to enable by default in my BMC.
That is, I can delete /etc/systemd/network/00-bmc-eth*.network and reboot and still have DHCPv6 reachable.
But I notice that IPv6AcceptRA is disabled in phosphor-network in order not to handle the ipv6 routing advertisement message periodically.
See: https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-networkd/+/8361
Why we need to avoid handling RA periodically?
Does it cause any bad effect?
If I want to keep the acceptance RA, how should I configure it? Or should I just patch "IPv6AcceptRA=true" in phosphor-network of my BMC?
Thank you,
Regards,
David
Hi David,
Quoted 8 lines · David Wang (王振宇)
Hi all,
I want to set DHCPv6 to enable by default in my BMC.
That is, I can delete/etc/systemd/network/00-bmc-eth*.networkand reboot and still have DHCPv6 reachable.But I notice that IPv6AcceptRA is disabled in phosphor-network in order not to handle the ipv6 routing advertisement message periodically.
See: https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-networkd/+/8361
Currently phosphor-networkd doesn't support SLAAC(DHCPV6, Router advertised address).
Quoted 2 lines
Why we need to avoid handling RA periodically?
If you have bad router configured in network which keeps sending the routing prefix frequently, phopshor-networkd frequently refreshing its D-bus objects.It can be fixed as ignore the refreshing of the Dbus objects if there is a D-bus object entry for the given IP address.
Quoted 3 lines
Does it cause any bad effect?
If I want to keep the acceptance RA, how should I configure it? Or should I just patch "IPv6AcceptRA=true" in phosphor-network of my BMC?
If we fix the behavior as suggested above there should not be a problem.
Quoted 5 lines
Thank you,
Regards,
David