vastsit.blogg.se

Retroshare nat behind firewall
Retroshare nat behind firewall













retroshare nat behind firewall
  1. #RETROSHARE NAT BEHIND FIREWALL INSTALL#
  2. #RETROSHARE NAT BEHIND FIREWALL SOFTWARE#
  3. #RETROSHARE NAT BEHIND FIREWALL OFFLINE#
  4. #RETROSHARE NAT BEHIND FIREWALL FREE#

When my friend and I both use Windows, I have networking set to 'manual forwarded port', and 'Public:DHT & Discovery', have a static IP address at my end along with a specific rule in the router to port forward one TCP/UDP port and have manually specified the 'local address' and 'external address' ports in RS. I use Mac OS, Linux (Ubuntu) and Windows. Using tactics like the NAT punch-through that Skype uses would still require some kind of server that would be more likely to be suspicious than the Teredo servers of big companies like (used for providing IPv6 to every Windows machine since XP)Īll RS would have to do in order to benefit would be adding IPv6 to the Network Configuration and try connecting directly with it first before trying with IPv4.Īll the rest, like having native IPv6 support or having it through Teredo, are things that RS shouldn't have to worry about, like it currently doesn't need to worry about if IPv4 is set up correctly or not, that is the User and his OS's business Nonnu Posts: 6 Joined: Wed 11:32 pmĮspecially given the fact that IPV6 flows through routers.

retroshare nat behind firewall

ISP's would not block Teredo servers because there is nothing suspicious in using IPv6, millions of PC's do it every-time they boot up. I like the IPv6 solution, almost every OS has it enabled by default at this time, and even if your ISP is still IPv4 only, Teredo does solve the issue transparently.

#RETROSHARE NAT BEHIND FIREWALL FREE#

NAT to NAT problems would be solved, thanks to the free tunnel providers. Would be still a lot work to do but imho worth it. (like said, they are no proxy, just NAT to NAT helpers, no responsibility for any traffic) Proposed solution #2: few RetroShare users volunteer and offer to be a free IPv6 tunnel provider their self.

#RETROSHARE NAT BEHIND FIREWALL OFFLINE#

Unlikely that they all go offline at once. Proposed solution #1: register at more then one tunnel provider. Dependency to tunnel providers, sometimes they are offline. register a static IPv6 address and you do not need dht anymore register a dynamic IPv6 address and continue to use dht, OR RetroShare should do that, register at the tunnel provider. If the user has no IPv6 then RetroShare should ease the process of registering at the tunnel provider. On startup RetroShare will check if the user has native IPv6 from his provider.

retroshare nat behind firewall

Now, how RetroShare shall make use of all that?ġ. The data transfer rate is just like IPv4 to IPv4 directly. The tunnel provider just helps to establish the NAT to NAT connection. None of the traffic is relayed over the tunnel provider! A tunnel provider is NOT a proxy. IPv6 to IPv6 with NAT to NAT tunneling working. One sets up an IPv6 webserver or IPv6 SSH server and the other one can normal connect to it using IPv6. Great thing is, you can still establish direct connections.

#RETROSHARE NAT BEHIND FIREWALL INSTALL#

On Ubuntu (and many other Linux) just install miredo and you have an IPv6 address. It will work in any case! Terredo is a special protocol designed to work through NAT. Do not care if you are behind router / NAT. Getting an IPv6 address is very easy under linux. I am not a developer but experimenting with in network configurations a lot. Here is a list of tunnel providers and IPv4 to IPv6 tunnel software.

#RETROSHARE NAT BEHIND FIREWALL SOFTWARE#

The software clients they are talking about on that site will also mostly also work on Windows. The following site is not hardcoded to Ubuntu. There are other ways to obtain an IPv6 address. And I also know it will take a while until everyone has working IPv6 from their providers. Yes, I know at the moment there are not very much IPv6 providers, not very much IPv6 routers, software and so on. I searched the forum and my solution isn't that hard to implement but still has never been proposed.















Retroshare nat behind firewall