p2p | 易学教程

Android: NAT Traversal?

阅读更多关于 Android: NAT Traversal?

问题 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

How NAT traversal works in case of peer to peer protocols like bittorrent.

阅读更多关于 How NAT traversal works in case of peer to peer protocols like bittorrent.

I know about NAT traversal and about STUN, TURN and ICE and its use. I want to know whether these are implemented in peer to peer file sharing application like bittorrent. Whether trackers facilitate peers behind NATs to communicate with each other by helping in creating direct connection using STUN or relay through TURN. In the case of Distributed Hash Table(DHT) how one peer would communicate with other peer behind NAT ? BitTorrent does not need to connect to any particular member in a swarm, it's not a p2p chat protocol where two specific end points want to talk to each other. All it cares

Remote VideoStream not working with WebRTC

阅读更多关于 Remote VideoStream not working with WebRTC

问题 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

Can HTML5 Websockets connect 2 clients (browsers) directly without using a server? (P2P)

阅读更多关于 Can HTML5 Websockets connect 2 clients (browsers) directly without using a server? (P2P)

Using HTML5 Websockets, can I open a socket directly between 2 clients (browsers) (assuming I know their IP addresses and there are no NAT traversal issues). I want to send some data directly from one browser to another browser, essentially creating a P2P network. Everything I've read so far on the web, websockets are all used to communicate between client and server, but nothing about client to client. Thanks kanaka No Already answered here for more details: Do websockets allow for p2p (browser to browser) communication? Update : The WebRTC protocol and API is making rapid progress and allows

Does Flash10 + p2p really work?

阅读更多关于 Does Flash10 + p2p really work?

问题 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

Connecting P2P over NAT?

阅读更多关于 Connecting P2P over NAT?

问题 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

Peer to Peer: Methods of Finding Peers

阅读更多关于 Peer to Peer: Methods of Finding Peers

问题 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

安卓P2P开源项目

阅读更多关于安卓P2P开源项目

https://github.com/LinYaoTian/P2PChat 一个基于局域网的 Android P2P 聊天系统 https://github.com/ddssingsong/webrtc_android 2P Webrtc VideoConference 视频通话视频会议 https://github.com/cloudups/iTransfer 这是一款基于Android WiFi p2p,ftp,和web进行不同设备间传输文件的客户端 https://github.com/xmtggh/VideoCalling VideoCalling p2p局域网音视频通话的demo，只需要对方的ip，端口和绑定本地端口，即可实现直连的视频聊天，喜欢的朋友请留个star，作者要求不多，谢谢大家！更新日志 2017-12-13日项目成立主要借鉴于开源项目 https://github.com/liuqm/Android-VideoChat-master 学习的相关知识，非常感谢大神的贡献，所以本人从开源社区学习，也回馈开源社区 2018-1-31 发布初版，主要使用java nio传输视频数据，加入音频 2018-11-15 使用了netty传输音视频数据，使用了speex降噪,使用了x264软编，mediacodec硬遍，ffmpeg软解

WebRTC with 3 users connection

阅读更多关于 WebRTC with 3 users connection

I'm now implementing the source code from WebRTC Samples to become 3 users connection by using mesh topology. However, my code doesn't work as I thought it would be. I think I'm stuck at calling function iceCallBack# (# refers to number 1, 2 ,3) because the output result is the same as the original. It only can connect 2 users. I don't know how to fix it in proper way. Here is some of my JavaScript code that I have been working on: var audio2 = document.querySelector('audio#audio2'); var audio3 = document.querySelector('audio#audio3'); var pc1; var pc2; var pc3; function call() { callButton

NAT translation not working from inside the network (hairpin condition)

阅读更多关于 NAT translation not working from inside the network (hairpin condition)

问题 I'm writing a P2P application. Peers regularly ping a main server to update their current IP/port, so when a peer wants to reach another one it can ask the server for that information. For now peers use UPnP to configure the NAT (for classic home setups) to be accessible from outside. So everything works, except when a peer's client tries to reach another (or the same) peer's server and both are behind the same NAT. Since in that case the client is trying to reach its own "external" (public)