search

gjedeer / tuntox

Tunnel TCP connections over the Tox protocol
https://gdr.name/tuntox/
Other
343 stars 57 forks source link

Tuntox seems to be not accessible if running too long and network is too unstable #48

Closed a1batross closed 5 years ago

a1batross commented 6 years ago

I am running tuntox on my ARM server in my university dorm. Server is connected through wireless network, because I don't have access to Ethernet cable.

When tuntox is running too long, it seems not accessible anymore. Maybe it depends on network, when server changes IP address.

I will continue watching to know which exactly causing this bug.

gjedeer commented 6 years ago

When you're back in the dorm, check the output please. If you want to spend some time, try to reproduce with -ddd and logging the output somewhere.

These kinds of bugs are usually caused by c-toxcore but I'll be happy to help. Did you try running uTox or other client for extended periods of time on that network?

gjedeer commented 6 years ago

Also, in terms of reproducing: do you have a public IP address thats' changing or is it a private IP behind a NAT? If NAT: does the external address sometimes change too when private IP changes?

a1batross commented 6 years ago

Thank you for replying!

I am new to Tox, and not tried to use it anywhere except Tuntox. I have restrarted tuntox yesterday and realized I have lost previous one week log. At this time, I still can connect. External IP was not changed, private IP was changed from 192.168.1.7 to 192.168.1.5. So it's maybe not private IP changing bug?

External IP address is dynamic. Private IP changes randomly, as this is wireless network and there is too much channels on 2.4 Ghz. Even my laptop is reconnecting to WiFi network from time to time.

I have restarted it again with -ddd key, so when problem will occur, I will post a log here.

gjedeer commented 5 years ago

Closing this, reopen please if you're encountering this.