Re: [twsocket] UDP Hole Punching
I'll take a look. Cheers. Dave B. -Original Message- From: wayne forrest [mailto:[EMAIL PROTECTED] Dave, thank you for all the advice, I will look into all of it for sure, about the Telnet Application: I recall seeing one at sourceforge.net. Hope that helps. This mail has been scanned by Palmer Cook Computer Services Limited. www.palmercook.co.uk -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] UDP Hole Punching
http://sourceforge.net/projects/ktelnet On Thu, Mar 6, 2008 at 7:29 PM, Dave Baxter [EMAIL PROTECTED] wrote: I'll take a look. Cheers. Dave B. -Original Message- From: wayne forrest [mailto:[EMAIL PROTECTED] Dave, thank you for all the advice, I will look into all of it for sure, about the Telnet Application: I recall seeing one at sourceforge.net. Hope that helps. This mail has been scanned by Palmer Cook Computer Services Limited. www.palmercook.co.uk -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- C: 076 337 4368 T: 021 880 2037 F: 021 880 2530 -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] UDP Hole Punching
H Probably right, Hamachi run's on full blown Windows (NT based), Linux or Apple systems. Guess in principle it could run on something else, but it's not open source. Take a look at Tinc. That is an open source VPN system. Maybe that could be adapted to your needs? http://www.tinc-vpn.org/ I don't know much about the mobile platform arena, but from my own experiments and other messings, though UDP is easier to program (at least I find it so) TCP is better at maintaining links, especaily through multiple routers and firewall's etc. If you have control of the routers in question, it's not dificult to manualy setup port forwarding of course, and there is the questionable UPnP protocol where an Application can do it for itself. But, that can also allow some very bad things to happen in regard to network security. As you obviously know more about the mobile environment than I do, I'll bow out now. But with one question in return... Do you (or anyone else) know of a generic Telnet client for phones like the N6110? It'd be so usefull.. Cheers. Dave B. -Original Message- From: wayne forrest [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2008 7:06 AM To: ICS support mailing Subject: Re: [twsocket] UDP Hole Punching Dave, maybe I as not all that clear on my Specification: My ICS Clients will be Mobile PHones MIDP2.0, therefor I do not think Hamatchi will work, or would it ? On Tue, Mar 4, 2008 at 4:10 PM, Dave Baxter [EMAIL PROTECTED] wrote: NAT Traversal is well documented, but less than easy to make work from scratch But why bother rolling your own? Just download and use Hamachi. (Google for it) Even the free one will start automaticaly when Winderz boots, then you have a UDP based secure VPN between 2 (or more) sites. Just about any LAN type app will run across it. (Versions for Winders, Linux, and some Apple OSwhatsit type things) Works very well. I have no affiliation with Hamachi or LogMeIn, just a very satisfied user of the free version so I can get to my home Win2k desktop securely wherever I am, and leaving no unwanted holes poked in the firewall. Cheers. Dave. -Original Message- From: JLIST [mailto:[EMAIL PROTECTED] Sent: Saturday, February 23, 2008 8:45 AM To: ICS support mailing Subject: Re: [twsocket] UDP Hole Punching My understanding is that it works on certain types of NAT firewalls. On these NATs, an external port is mapped to an internal IP:Port. If this is the case, all packets going to that external port will go to the internet IP:Port. Making it work is not that simple though, with the difficult part being coordinating two parties that do not talk to each other. I'm not sure what's being used in real life solutions but it sounds to me that both A and B have to have very frequent UDP communications with S, or have a TCP connection with S in order to coordinate a hole punching attempt. Isn't the translation state based on the remote peer IP address, too? Then the same translation created for A-S and B-S would not work when you try to connect directly A with B. - Original Message - From: wayne forrest [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, February 21, 2008 8:22 PM Subject: [twsocket] UDP Hole Punching Has any one made a UDP Hole puncher with ICS ? Let A and B be the two hosts, each in its own private network; N1 and N2 are the two NAT devices; S is a public server with a well-known globally reachable IP address. 1. A and B each begin a UDP conversation with S; the NAT devices N1 and N2 create UDP translation states and assign temporary external port numbers 2. S relays these port numbers back to A and B 3. A and B contact each others' NAT devices directly on the translated ports; the NAT devices use the previously created translation states and send the packets to A and B If I were to implement the above, is it really that simple? or is there much more to it than that ? Any help appreciated, or alternatives, maybe a plugin / generic solution that can be incorporated. Our current setup is Server on PC behind nat and then client on Cell phone. We will have a lot of users not knowing how to do port forwarding. This mail has been scanned by Palmer Cook Computer Services Limited. www.palmercook.co.uk -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- C: 076 337 4368 T: 021 880 2037 F: 021 880 2530 This mail has been scanned by Palmer Cook Computer Services Limited. www.palmercook.co.uk
Re: [twsocket] UDP Hole Punching
NAT Traversal is well documented, but less than easy to make work from scratch But why bother rolling your own? Just download and use Hamachi. (Google for it) Even the free one will start automaticaly when Winderz boots, then you have a UDP based secure VPN between 2 (or more) sites. Just about any LAN type app will run across it. (Versions for Winders, Linux, and some Apple OSwhatsit type things) Works very well. I have no affiliation with Hamachi or LogMeIn, just a very satisfied user of the free version so I can get to my home Win2k desktop securely wherever I am, and leaving no unwanted holes poked in the firewall. Cheers. Dave. -Original Message- From: JLIST [mailto:[EMAIL PROTECTED] Sent: Saturday, February 23, 2008 8:45 AM To: ICS support mailing Subject: Re: [twsocket] UDP Hole Punching My understanding is that it works on certain types of NAT firewalls. On these NATs, an external port is mapped to an internal IP:Port. If this is the case, all packets going to that external port will go to the internet IP:Port. Making it work is not that simple though, with the difficult part being coordinating two parties that do not talk to each other. I'm not sure what's being used in real life solutions but it sounds to me that both A and B have to have very frequent UDP communications with S, or have a TCP connection with S in order to coordinate a hole punching attempt. Isn't the translation state based on the remote peer IP address, too? Then the same translation created for A-S and B-S would not work when you try to connect directly A with B. - Original Message - From: wayne forrest [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, February 21, 2008 8:22 PM Subject: [twsocket] UDP Hole Punching Has any one made a UDP Hole puncher with ICS ? Let A and B be the two hosts, each in its own private network; N1 and N2 are the two NAT devices; S is a public server with a well-known globally reachable IP address. 1. A and B each begin a UDP conversation with S; the NAT devices N1 and N2 create UDP translation states and assign temporary external port numbers 2. S relays these port numbers back to A and B 3. A and B contact each others' NAT devices directly on the translated ports; the NAT devices use the previously created translation states and send the packets to A and B If I were to implement the above, is it really that simple? or is there much more to it than that ? Any help appreciated, or alternatives, maybe a plugin / generic solution that can be incorporated. Our current setup is Server on PC behind nat and then client on Cell phone. We will have a lot of users not knowing how to do port forwarding. This mail has been scanned by Palmer Cook Computer Services Limited. www.palmercook.co.uk -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] UDP Hole Punching
Dave, maybe I as not all that clear on my Specification: My ICS Clients will be Mobile PHones MIDP2.0, therefor I do not think Hamatchi will work, or would it ? On Tue, Mar 4, 2008 at 4:10 PM, Dave Baxter [EMAIL PROTECTED] wrote: NAT Traversal is well documented, but less than easy to make work from scratch But why bother rolling your own? Just download and use Hamachi. (Google for it) Even the free one will start automaticaly when Winderz boots, then you have a UDP based secure VPN between 2 (or more) sites. Just about any LAN type app will run across it. (Versions for Winders, Linux, and some Apple OSwhatsit type things) Works very well. I have no affiliation with Hamachi or LogMeIn, just a very satisfied user of the free version so I can get to my home Win2k desktop securely wherever I am, and leaving no unwanted holes poked in the firewall. Cheers. Dave. -Original Message- From: JLIST [mailto:[EMAIL PROTECTED] Sent: Saturday, February 23, 2008 8:45 AM To: ICS support mailing Subject: Re: [twsocket] UDP Hole Punching My understanding is that it works on certain types of NAT firewalls. On these NATs, an external port is mapped to an internal IP:Port. If this is the case, all packets going to that external port will go to the internet IP:Port. Making it work is not that simple though, with the difficult part being coordinating two parties that do not talk to each other. I'm not sure what's being used in real life solutions but it sounds to me that both A and B have to have very frequent UDP communications with S, or have a TCP connection with S in order to coordinate a hole punching attempt. Isn't the translation state based on the remote peer IP address, too? Then the same translation created for A-S and B-S would not work when you try to connect directly A with B. - Original Message - From: wayne forrest [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, February 21, 2008 8:22 PM Subject: [twsocket] UDP Hole Punching Has any one made a UDP Hole puncher with ICS ? Let A and B be the two hosts, each in its own private network; N1 and N2 are the two NAT devices; S is a public server with a well-known globally reachable IP address. 1. A and B each begin a UDP conversation with S; the NAT devices N1 and N2 create UDP translation states and assign temporary external port numbers 2. S relays these port numbers back to A and B 3. A and B contact each others' NAT devices directly on the translated ports; the NAT devices use the previously created translation states and send the packets to A and B If I were to implement the above, is it really that simple? or is there much more to it than that ? Any help appreciated, or alternatives, maybe a plugin / generic solution that can be incorporated. Our current setup is Server on PC behind nat and then client on Cell phone. We will have a lot of users not knowing how to do port forwarding. This mail has been scanned by Palmer Cook Computer Services Limited. www.palmercook.co.uk -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- C: 076 337 4368 T: 021 880 2037 F: 021 880 2530 -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] UDP Hole Punching
My understanding is that it works on certain types of NAT firewalls. On these NATs, an external port is mapped to an internal IP:Port. If this is the case, all packets going to that external port will go to the internet IP:Port. Making it work is not that simple though, with the difficult part being coordinating two parties that do not talk to each other. I'm not sure what's being used in real life solutions but it sounds to me that both A and B have to have very frequent UDP communications with S, or have a TCP connection with S in order to coordinate a hole punching attempt. Isn't the translation state based on the remote peer IP address, too? Then the same translation created for A-S and B-S would not work when you try to connect directly A with B. - Original Message - From: wayne forrest [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, February 21, 2008 8:22 PM Subject: [twsocket] UDP Hole Punching Has any one made a UDP Hole puncher with ICS ? Let A and B be the two hosts, each in its own private network; N1 and N2 are the two NAT devices; S is a public server with a well-known globally reachable IP address. 1. A and B each begin a UDP conversation with S; the NAT devices N1 and N2 create UDP translation states and assign temporary external port numbers 2. S relays these port numbers back to A and B 3. A and B contact each others' NAT devices directly on the translated ports; the NAT devices use the previously created translation states and send the packets to A and B If I were to implement the above, is it really that simple? or is there much more to it than that ? Any help appreciated, or alternatives, maybe a plugin / generic solution that can be incorporated. Our current setup is Server on PC behind nat and then client on Cell phone. We will have a lot of users not knowing how to do port forwarding. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] UDP Hole Punching
Isn't the translation state based on the remote peer IP address, too? Then the same translation created for A-S and B-S would not work when you try to connect directly A with B. - Original Message - From: wayne forrest [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, February 21, 2008 8:22 PM Subject: [twsocket] UDP Hole Punching Has any one made a UDP Hole puncher with ICS ? Let A and B be the two hosts, each in its own private network; N1 and N2 are the two NAT devices; S is a public server with a well-known globally reachable IP address. 1. A and B each begin a UDP conversation with S; the NAT devices N1 and N2 create UDP translation states and assign temporary external port numbers 2. S relays these port numbers back to A and B 3. A and B contact each others' NAT devices directly on the translated ports; the NAT devices use the previously created translation states and send the packets to A and B If I were to implement the above, is it really that simple? or is there much more to it than that ? Any help appreciated, or alternatives, maybe a plugin / generic solution that can be incorporated. Our current setup is Server on PC behind nat and then client on Cell phone. We will have a lot of users not knowing how to do port forwarding. Thank you. Wayne Forrest. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
