p2p

It appears to me that newer Android devices run behind a NAT, where the local address is an internal carrier or LAN address and the public address is the router or carrier assigned external address. Nevertheless, newer phones don't return the same address using the NetworkInterface as when accessing an IP detection service. Therefore, connecting via direct P2P SocketChannels inherently fails. Are there any common workarounds to this problem designed for the Android platform? Can anyone clarify what is causing this NAT-like security issue? Any links to Java NAT traversal tutorials or examples (

Does anyone have any advice how to write such app? Or maybe knows some nice tutorial? I would like to use System.Net.PeerToPeer namespace, but everything I can find about it is MSDN which I can't read without getting mad. Or maybe using "old-school" TCP/IP would more efficient? I will appreciate every piece of advice. Every sample code I will shower with gold ;) And please, don't send me back to Google for I have searched for a long time for sth useful - maybe inaccurately but time is running out and I really need some help. [edit] What about the Brunet library ? Has anyone used it? There is a

EDIT: I wrote a detailed tutorial explaining how to build an simple Videochat-application including a signaling server: Tutorial: Create your own Videochat-Application with HTML and JavaScript Please tell me if you find it helpful & understandable. Thanks! i am trying to get Streams to work via WebRTC and Websocket (nodejs-server). As far as i can see the handshake via SDP works and the Peerconnection is established. The problem is - the Remote-Video is not playing. The src-Attribute gets the Blob and autoplay is set, but it just won`t play. Maybe i am doing something wrong with the ICE

I've been googling around and I still can't get it. Some people say: here you go, just use it. Others claim it has certain restrictions that does not allow you to use p2p the way you want it in Flash. So, here's a simple question: is it possible to implement a Flash10 application, that uses some of the existing torrent files to stream video/audio right into the user's browser? If no - why? Is there any possible workaround for this 'no'? If yes - what are the difficulties of the implementation and why have no one actually done it yet? back2dos The answer is pretty much no ... well, it's just no

I started to explore the option of connecting with other using a p2p connection, so I coded a simple socket program in JAVA for android devices in which the users can share simple messages p2p (I didn't have any idea about NAT then). I got to know about NAT, so I now need to establish a TCP connection with another user which uses a server for discovery but payload is transferred p2p. I have also looked at XMPP(a very good and detailed explanation of how protocol works is here ) and UPnP but I dont know how to implement them. Another interesting question that arises is of BitTorrent because

Are there any known methods of finding peers without using a dedicated central server? ie: If I have peers which are disconnecting and reconnecting to the internet but getting a new IP address each time, and I want to connect to them without setting up a dedicated server to register with. I was thinking about using peers email address to send a manifest of connected peers periodically, with some sort of timecode, negating the need for a dedicated server. This would be a fallback if none of the peers could be connected to after trying all the previously known peer addresses. But existing models

P2P Device：它是P2P架构中角色的实体，可把它当做一个Wi-Fi设备。 ·P2P Group Owner：Group Owner（GO）是一种角色，其作用类似于Infrastructure BSS中的AP。 ·P2P Client：另外一种角色，其作用类似于Infrastructure BSS中的STA。 为了保证一定的传输速率，P2P要求P2P Device必须支持802.11g及以上的规范。其中，安全部分必须支持WPA2。 P2P Client关联到GO之前，需要先通过WSC来协商安全信息，所以WSC也是P2P的依赖技术项。 P2P Discovery 的作用很简单，就是使多个 P2P Device 能够互相发现并构建一个 Group 。根据规范，它包括四个主要技术子项。 · Device Discovery ：用于 P2P 设备搜索周围其他支持 P2P 的设备。 · Service Discovery ：该 Device Discovery 基础上， P2P 还支持搜索指定的服务。这部分功能属于可选项，笔者觉得它和 2.2.5 节中提到的 Bonjour 类似。 · Group Formation ：用于决定两个 P2P Device 谁来扮演 GO ，谁来扮演 Client 。 · P2P Invitation ：用于激活一个 Persistent Group

From a Joel's post on Copilot : Direct Connect! We’ve always done everything we can to make sure that Fog Creek Copilot can connect in any networking situation, no matter what firewalls or NATs are in place. To make this happen, both parties make outbound connections to our server, which relays traffic on their behalf. Well, in many cases, this isn’t necessary. So version 2.0 does something rather clever: it sets up the initial connection through our servers, so you get connected right away with 100% reliability. But then once you’re all connected, it quietly, in the background, looks for a

I've come across an interesting problem. Basically I have 2 mobile phones that are both behind NATs. I want to communicate directly between the 2 devices using UDP. I know if I initiate a connection from the phones to a server then I can push data back down that connection to the phone (ie send it back from the same port that received the message to the same ip and port that it was received from). So I can easily communicate between the 2 devices by connecting both phones to the server. Then sending data to the server and having it re-routed back to the phones. This bypasses any NAT traversal