Development Update #30

Summary:

IPv6 support is working. We were having trouble before. Many of the residential routers appear as IPv4 but actually have IPv6 public IP addresses and are IPv4 NATs.

Configuring the IPv4 DNS settings on the local host does not override the IPv6 DNS server the router is using during 4to6 translation. We have no idea what is happening.

We are not sure if IPv4 and IPv6 hosts are able to operate on the same DHT network.

Meshnet News

The meshnet design is really a darknet, that allows ethernet and peering over wifi. This has several implications and we are still working out everything this implies

There is an IPv6 tunnel. If two nodes are running the software:
We think the darknet can act as a simple corporate VPN replacement:

Skywire Multihoming and BGP

We proved that efficient stateless multihoming is impossible. IPv6 is stateless and Skywire routing is stateful.

We accidentally noticed that Skywire can achieve IPv6 multihoming by tunneling IPv6 over Skywire.

We noticed several things:
We believe that the new darknet may be able to replace BGP for routing between domains
Within an AS:
The tunnel is:

IPv6/IPv4 (private addresses) -> Skywire -> IPv6 (public address)

In this tunneling application Skywire acts as intermediate layer between the physical network topology and the IP address space.

IPv6 Address Space Reverse compatibility

What we are trying to figure out, is whether the darknet can be reverse compatible with legacy applications at the application layer without modification, or whether the darknet will require application such as Bitorrent to be rewritten into the Skywire address space.

A user running over the IPv6 reverse comparability adapter:

A native Skywire application - will have increased privacy (each application connection will have independent route endpoints) - will have application level control over routes and traffic policies (low latency, high throughput and so on)

External Traffic off the Skywire Darknet will go through a “gateway” which is similar to a VPS provider. Your IP to public will appear as the gateway server’s IP. This is like a TOR exit node. However, for quality of service, a person will probably have to subscribe to an individual gateway service provider.

Public gateways in TOR are unusable because their IPs are banned from most websites because of spamming. The IP addresses are also easier to identify than private gateways and are prime targets for monitoring. Private gateways are more difficult to identify and offer a higher quality of service.

No translation bounty

Discuss this post on telegram

Skycoin Telegram