![]() ICE (Interactive Connectivity Establishment).some will work on OSX but not on Windows). Some of them are likely to be platform specific (i.e. These don't seem to be documented on the public web site. The VSee client has command line options available. Using this NAT strategy no command line options are required (i.e. you don't have to create 250+ rules if you have 10 machines in a small DHCP range). NAT rules only have to be created for those address ranges where a client machines are on the network (i.e. Where the private IPv4 address would be 192.168.1.xx or 10.0.0.xx (specific to your network). the set of rules would be: Public UDP Port the router from your ISP) will need to have pinholes setup for the address range you are using.Į.g. This allows a very simple scheme for small networks of up to ~250 users to concurrently use VSee through a NAT firewall. If you machine has an internal IPv4 address of 192.168.1.34 then it will use a UDP port of 6034 for VSee voice/video traffic. It appears that a VSee client will listen on UDP port number '6000+X' where 'X' is the last octet of the IPv4 address of the interface address. There doesn't seem to be simple description of this from VSee but it appears that VSee will use up to 255 UDP port numbers in the range 6000-6254. These notes may be less applicable for clients that are behind a non-symmetric NAT. It is unclear if one end can initiate this and datagrams can flow in both directions, or whether both ends independently initiate this flow (i.e if one end has a public IPv4 address or their NAT is setup correct then a direction VPN style connection can be established). ![]() Historically this may have been to UDP port 6000 ( TODO: find some sort of description of this from VSee). VSee appears to setup some form of VPN over UDP between clients. ![]() However this doesn't address the requirements for sound/video. Setting up the firewall to allow outgoing (egress) XMPP/Jabber (tcp port 522) and STUN (was 'Simple traversal of UDP through NAT' but now 'Session Traversal Utilities for NAT') is straightforward. The command line options have been extracted from the OSX binaries to form the list below. The online documentation for VSee describing its command line options and network traversal is sparse (see links below).
0 Comments
Leave a Reply. |