Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DHCPv6 relay-forward message sent through wrong socket #50

Closed
sodz opened this issue Jul 17, 2015 · 2 comments
Closed

DHCPv6 relay-forward message sent through wrong socket #50

sodz opened this issue Jul 17, 2015 · 2 comments

Comments

@sodz
Copy link

sodz commented Jul 17, 2015

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.

@sbyx
Copy link
Member

sbyx commented Jul 17, 2015

Should be fixed in sbyx@60bb0a1 thanks.

@sbyx sbyx closed this as completed Jul 17, 2015
@sodz
Copy link
Author

sodz commented Jul 17, 2015

But it was designed not to create such a socket on the master interface (dhcpv6.c:54):

if (enable && iface->dhcpv6 && !iface->master)

That should be fixed too, by deleting && !iface->master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants