You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sending DHCPv6 relay-foward messages (dhcpv6.c:535), the used socket is bound to the slave interface (dhcpv6.c:63), while it is required to be sent through the master interface; thus the `sendmsg' system call returns EINVAL.
It seems that a UDP socket is also required on the master interface (dhcpv6.c:54), and the relay-forw message should be send through that socket. This solution works for me.
The text was updated successfully, but these errors were encountered:
When sending DHCPv6 relay-foward messages (dhcpv6.c:535), the used socket is bound to the slave interface (dhcpv6.c:63), while it is required to be sent through the master interface; thus the `sendmsg' system call returns EINVAL.
It seems that a UDP socket is also required on the master interface (dhcpv6.c:54), and the relay-forw message should be send through that socket. This solution works for me.
The text was updated successfully, but these errors were encountered: