<story><title>Subspace – A simple WireGuard VPN server GUI</title><url>https://github.com/subspacecommunity/subspace</url></story><parent_chain><item><author>rubatuga</author><text>Is there anybody interested in building or using a service that routes static public IPs to self-hosted servers, over WireGuard? I made a prototype a week ago, here&amp;#x27;s the homepage:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;hoppy.network&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;hoppy.network&lt;/a&gt;&lt;p&gt;I realized that I didn&amp;#x27;t want to ever deal with port-forwarding, NAT, or dynamic DNS and decided to create this. Message me if you want a signup link.</text></item></parent_chain><comment><author>xrisk</author><text>I tried your service and it just works™, which is great. But a couple of points:&lt;p&gt;1) I saw that you&amp;#x27;re basically using one OVH box per IP. How do you plan to ever monetize this then?&lt;p&gt;What prevents a user from creating their own VPN instance on their own box and port forwarding from there? Granted this process is somewhat involved, but the kind of user who needs to do this is likely to be somewhat technically inclined anyway. (Some ideas: negotiate long-term deals for IP addresses and try to map &amp;gt; 1 IP per box &amp;#x2F; remove the static IP guarantee and keep a rotating pool of addresses – &lt;i&gt;public&lt;/i&gt; IPs are more valuable than &lt;i&gt;static&lt;/i&gt; IPs anyway IMO and you can integrate dynamic DNS into your service)&lt;p&gt;2) How do I know that you&amp;#x27;re not sniffing my traffic? Granted that most traffic being encrypted these days is a thing, but still I think it&amp;#x27;s a genuine concern.&lt;p&gt;3) I live in Asia, so latency was off-the-charts for me. (On the order of 500ms). But this problem could easily be solved by introducing servers in more locations.</text></comment>
<story><title>Subspace – A simple WireGuard VPN server GUI</title><url>https://github.com/subspacecommunity/subspace</url></story><parent_chain><item><author>rubatuga</author><text>Is there anybody interested in building or using a service that routes static public IPs to self-hosted servers, over WireGuard? I made a prototype a week ago, here&amp;#x27;s the homepage:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;hoppy.network&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;hoppy.network&lt;/a&gt;&lt;p&gt;I realized that I didn&amp;#x27;t want to ever deal with port-forwarding, NAT, or dynamic DNS and decided to create this. Message me if you want a signup link.</text></item></parent_chain><comment><author>jo909</author><text>I&amp;#x27;m sure there is and will be demand for good static IPv4 tunnel brokers. I&amp;#x27;m personally fine with dealing with dynamic DNS and port forwards for my home setup for now, but once I no longer have a public IPv4 assigned I would be a potential customer.&lt;p&gt;How do you deal with the global scarcity of IPv4-addresses that you would need to scale your service? I think this can only work long term if you own the address space yourself and are not dependent on some specific provider or cloud.&lt;p&gt;Also very important is a local endpoint to get a reasonable end to end latency.</text></comment>