[Solved] Connection problem [Win7 x64]
#1
Posted 14 December 2009 - 16:03
I've received no errors during the instalation of Tunngle, i specifically portforwarded the 11155 and 6112 ports to my ip, still, Tunngle doesn't work properly.
Hint : Seems like I got an issue close to this one -> http://www.tunngle.n...-t20161/p1.html
In the router logs i found those "Twinge Attack Detect" and "Packet Dropped".
But, unlike that unfortunate man, i can still start Tunngle. I execut it, it hangs on the "Connecting to Tunngle server", after 20-30s it tells me if can't connect and asks me if i want to connect.
And, strangely, i can. I have no issues seeing the rooms, the other people, i can play every game i want. But, here's the big problem. After a random amount of time, my connection suddenly gets intrerupted and i have to restart tunngle to login again.
I've got no firewall installed (Windows Firewall is disabled, and tunngle was in it's exceptions) and the program is properly configured.
Any ideas ?
#2
Posted 14 December 2009 - 19:53
#3
Posted 14 December 2009 - 20:56
The last picture shows the "Dropped packets" in the log, just when i start Tunngle.
Attached File(s)
-
Untitled.png (166.9K)
Number of downloads: 35 -
Untitled2.png (142.67K)
Number of downloads: 30 -
Untitled3.png (168.33K)
Number of downloads: 25
#4
Posted 14 December 2009 - 21:46
So no trigger port specified, while you specify the destination IP.
Check if this helps: http://www.portforwa...BRP/Tunngle.htm
Edit: Don't forget to disable triggering
#5
Posted 14 December 2009 - 21:58
I've looked all over the support posts on this forum, including what you've sugested me.
The only thing that was close to my problem was this post http://www.tunngle.net/forum/router-comp…-t20161/p1.html
If you look with more attention to my images, at the time i was writing i had port forwarding and not port triggering
And still.....i got disconected once like....30 minutes. Each time i get my connection reset from 5-60 seconds, causing my game to end...not gently.
So, any other things to try ?
#6
Posted 14 December 2009 - 22:10
You can try DMZ (dangerous if you don't have a software firewall).
You can try with another router or wait that this false positive issue is examined more in detail when the developers have time for it
Edit: you can also try to disable the detection for those kind of attacks, search for an updated firmware, report the issue to the router maker
#7
Posted 14 December 2009 - 22:18
Dmz thing - Tried, no change.
Another router - Will do, but it will take time to change. I sence it isn't the pc that's faulty.
Disable detection - Can't, the firewall is integrated in the router, i think i read somewhere that is uses NAT. Disabling Nat led to disabling my internet
Soooo...let's see, UnPn then. Will keep in touch.
Later Edit : Nope, doesn't work. I did what you said, i looked at my router to see the UpNp is enabled, i disabled port forwarding, but still it didn't work.
It failed to find a port, still, i could login and enter rooms. That's very odd
#8
Posted 14 December 2009 - 22:39
We should be including some fixes and improvements for Upnp quite soon (this could in some cases fix some issues). As for specific model investigation, this will obviously require greater time (but for some that don't provide options to configure firewall settings it might be difficult to achieve good results).
#9
Posted 14 December 2009 - 22:45
And even more odd, that i can connect to other ppl and play. And why those intreruptions.....
Ill try tommorrow on my other pc on the network...hope i will get other results
#10
Posted 15 December 2009 - 23:39
I guess i'll have or to wait for the developers to find a workaround, or just buy a new router....the 1st option seems better
Btw, can i post my issue in the Router Compatibility forum....cause it seems it isn't a pc problem ?
#11
Posted 16 December 2009 - 00:45
We will do the possible to fix what is fixable
Edit: About DMZ you need to disable other Tunngle port forwardings when you enable dmz. Anyway it's not a solution cause it's insecure.
#12
Posted 28 December 2009 - 17:36
It seems that some other people got the same problem, more specifically, the Avast Team with their anti-virus.
Here's the link, look at the 4) point : http://www.avast.com/eng/updates2.html
As i said, my problem is that tunngle checks his connection to the net every 30 mins and disconects me.
So, a solution would be to disable the checking. Can someone of the developer team help me with this ?
or let`s say a little different, can you set Tunngle to assume that it is ALWAYS connected to internet, and not check at start ( which can be bypassed with "just connect" ) and not check at 30 minutes?
if you can set an option like this, at least 2 people will be happy. me and the other guy that has a similar problem
thank you.
#13
Posted 28 December 2009 - 17:58
Tunngle doesn't diconnect you, your router does because its bugged detection routines think that something bad is going on.
I don't know where you got this info about keep alive connections every 30 mins but i think that the false positive detection can't be possibly triggered by a connection every 30 mins.
If it was like this you should throw away your router
I am afraid that there is no simple solution to this. We are not talking about an antivirus update. We are talking about a complex VPN software that needs certain network functions.
Keepalives and checks are needed for the normal operation of Tunngle and they can't be turned off lightly.
I suggest that you download the latest version and try again with UPnP.
Of course to have UPnP working you need to have the UPnP host and SSDP discovery service running as well as svchost outbound enabled in your firewalls (both windows and third party).
If this doesn't work you could try to test with a different router and see you get better results
#14
Posted 28 December 2009 - 18:05
Well, every 30 mins my logs start showing the TWINGE Attack and then my whole internet goes down for like 10 seconds.
Does it matter if it is Port forwarding/port triggering or UPNP ?
#15
Posted 28 December 2009 - 18:09
Yes it matters. Although all the possible methods should achieve the same results, some routers are known to react differently depending on the method.
Trying won't hurt
#16
Posted 28 December 2009 - 18:21
it appears that the communication between Tunngle and it`s servers creates some strange answers that are interpreted by the TrendNet router as a form of attack.
This strange packages are not some normal ones as they are not important for the VPN connection but appear to be connected to a signal between client and server. i know this because i`ve look for the exact moment of package drop.
let`s go step by step, hope is important. I launch the Tunngle Beta executable and in this moment the router start dropping a lot of packages . after 10-15 seconds i get the screen attached. If i click "yes" on Start Tunngle Anyway ( this is for sure a bypass of the server client signalling ) i can play and connect to the others without any problem.
After ~ 30 minutes the link is dropped because same exotic packages are exchanged between client and server and router is dropping all of them. In this moment i don`t get any "continue anyway" so i`m kicked out
maybe one of the developers can look over those signal packages or offer an option to disable in a experimental version at least
UPNP is working the same, i`ve tested it today. ( run - router drops packages - connect anyway ... works ... 99% at 30 minutes drop )
on the other side, i`ve raised a ticket with TrendNet too, so let`s see if they can either white list that signal or ...a solution.
Attached File(s)
-
Untitled2.jpg (25.62K)
Number of downloads: 20
#17
Posted 28 December 2009 - 19:15
This packet is dropped by your router and this is the reason why you get the Server not reachable message.
There is no further server availability check so the 30 min issue must be different.
Can you please attach the router log entries at the 30 min disconnection time?
Do you get any other info beyond "Dropped Packet"?
#18
Posted 30 December 2009 - 19:36
So, i increased the duration to 1 week, and now i didn't get a internet restart for like...4-5 hours.
Still, i got the error at starting the program, but it's just a minor issue.
Damn, it took me about 7 hours to fix this.....it feels soo good to be able to play, finally
Thank you for your kind support
#19
Posted 02 January 2010 - 16:34
Hopefully it will help others with the same router model
Share this topic:
1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users
Toggle chat Chat
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

Sign In »
Register Now!
Help
This topic is locked















