-
Notifications
You must be signed in to change notification settings - Fork 325
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
tunneldigger dies somtimes #1188
Comments
The right place to report this is the Tunneldigger bug tracker at https://dev.wlan-si.net/report/15. I'll still keep this ticket open to track it for Gluon. |
cc @kostko |
I was not able to report this bug on there site ... this bug happens when dns-resolution failed and despite sending data through a socket: I think there is a bug in the broker selection. The selector should wait for successful address-resolution. To workaround this bug you can use ip's instead of names. |
thanks for the hint. |
Interesting. We always use IPs, so this is why we didn't notice this before. |
@mitar: How can i report bugs at https://dev.wlan-si.net/newticket?component=tunneldigger ? The registration link automatically moves me to the wlan-slovenia registration but the created account doesn't work on dev.wlan-si.net. And without an account, I will only see the message "TICKET_CREATE privileges are required to perform this operation" Btw. the bug I see is with newer kernels ( Only one session (tunnel interface) can be created. All other sessions create a "Failed to setup tunnel with id 102!". The test kernel is linux-image-4.9.0-4-amd64. And I saw some changes which might be related:
|
Report them in the GitHub repository. |
BTW, there is already a fix for the session ID issue you mention. It is in wlanslovenija/tunneldigger#64 (not yet merged into master). |
we will close this issue here, as tunneldigger has recently been updated to the latest version. |
If internet lost connection (like reboot of router or plug off lan-cable) then the tunneldigger sometime dies.
After strace the tunneldigger i found that a assert is triggered: https://github.com/wlanslovenija/tunneldigger/blob/master/client/asyncns.c#L884
https://pastebin.com/R6CQmGXr
The text was updated successfully, but these errors were encountered: