-
Notifications
You must be signed in to change notification settings - Fork 35
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
dlep_router datapath_if not honored for session tcp connection #41
Comments
A bit of digging later, it seems like this is caused by (so the discovery packet is sent on the correct interface and the offer is received on the correct interface but it then tries to establish the TCP connection on the wrong interface) |
@XDjackieXD Many thanks for providing more research at this topic. Do you don't mind to create a patch, compile it and test it in your environment? I pull request with your tested change is highly appreciated. |
I will prepare a PR. I'd guess you prefer the PR to be against the develop branch? |
PR is open and seems to be working fine on my OpenWrt setup! |
@mathiashro could you please merge the PR? |
PR #55 has been merged. |
When trying to run DLEP information out of band (so you don't have to use ebtables) it is impossible to get the dlep_router to actually try the session connection on the interface specified by
datapath_if
.It correctly uses the
datapath_if
for the UDP discovery but then tries to connect to the discovereddlep_radio
on the "main" interface instead of thedatapath_if
...Even using non-link-local IPv4 addresses with connect_to doesn't work as the connect syscall seems to have the interface specified.
When setting the datapath interface as the "main" interface for
dlep_router
, this leads to it correctly connecting todlep_radio
and getting all the l2 info but not using them for the real "main" interface but showing a new interface in olsrd2layer2info interface
.Example output when using the datapath interface as "main" interface for the
dlep_router
config (eth4.255
should have all the l2 info now displayed as a new interfaceeth4.254
):The text was updated successfully, but these errors were encountered: