Context Navigation

Changes between Initial Version and Version 1 of Ticket #2305, comment 34

initial	v1
5	5	We tested it with Sestroretsk1714 (lobby nickname) and it works for his 3G modem-based connection.
6	6
7		To my surprise, my own primary connection is routed through a provider's symmetric NAT now (at least 3 months ago my router received a public IP and [[http://manpages.ubuntu.com/manpages/zesty/man1/stun.1.html\|stun test utility]] reported 'Port Restricted Cone' NAT (my own router); now router receives LAN IP and the utility says that there is a symmetric NAT on the route), so neither the current implementation of NAT traversal nor port forwarding does~~n't~~ work with this connection anymore.
	7	To my surprise, my own primary connection is routed through a provider's symmetric NAT now (at least 3 months ago my router received a public IP and [[http://manpages.ubuntu.com/manpages/zesty/man1/stun.1.html\|stun test utility]] reported 'Port Restricted Cone' NAT (my own router); now router receives LAN IP and the utility says that there is a symmetric NAT on the route), so neither the current implementation of NAT traversal nor port forwarding does work with this connection anymore.
8	8
9	9	Currently the code doesn't build on Windows, but it should be easily fixable by including the proper headers. Also non-primary connection modes (direct connection, STUN enabled host with non-STUN client and vice versa etc.) may have some easily noticeable/fixable bugs. And the code still requires some style fixes (in particular part of those reported by elexis in comment:25)