You could set up dynamic DNS and port forwarding instead, but that won't work in some network environments. The reason that so many things need to call home is that, between NAT preventing either peer from sending a message through to the other until the other has sent one to it first, and neither peer knowing the other's dynamically assigned Internet IP address to begin with anyway, some sort of centralized rendezvous and NAT traversal system is essential if you want two peoples' computers at home to actually be able to send any data to each other at all. If you want a solution where you can have a group of computers anywhere on the Internet automatically find each other, punch holes in whatever NAT heeps them from talking directly to each other, assign themselves IPv4 addresses that don't conflict with anyone else's in the increasingly depleted IPv4 address space, and happily exchange and route packets with no configuration over virtual interfaces that also work on OSes like Windows that don't really have proper virtual interfaces, you're in for a lot of software development, because as far as I know such a thing does not exist for free. But it requires links to be manually created as well, by exchanging public keys. If you can get away with having only IPv6 on your network (or with the built-in IPv4 tunnel feature), and you don't really need Windows support that doesn't involve virtualizing an entire Linux system, you could always go with cjdns, which is dedicated mesh networking software. A network that runs somewhat like this is Dn42, which employs normal Internet routing protocols between manually managed IP addresses over manually created point to point VPN links. If it's not an all-to-all topology as you depicted, and some hosts need to send packets that get routed by other hosts, you would need either static routes that you manually configured, or break out full BGP or OSPF to dynamically share routes as on the real Internet. can set up inbound port forwarding and manually create each peer to peer link), you could assign static private IP addresses to everything and manually set up all the links. If you have a fair bit of control over the peers themselves and their local network environments (i.e. So you want each peer in the network to have connections to some (or all?) other peers? And the peers may be Windows, Mac, or Linux? And it needs to be a private, normal IP network (and not something like Tor or I2P)? It works, but, like Hamachi, it needs to call home to get the actual connection setup. What I'm looking for a client/server VPN software that can run a mesh network on its own, and accept clients of most any OS, be it Windows, Linux, or OS X/Macintosh.Įdit: currently I'm using NeoRouter, I have a server setup on my raspberry pi running raspbian, and i have my clients of a few windows computers and a few mac computers connecting to it. Another that both NR and Hamachi NEED to call home to their operators to be able to configure a network, which is not ideal. But their setback come in the way, one of them being that LogMeIn has crippled Hamachi beyond belief in the form of limiting your networks and disabling automatic connections. The most attractive out of all of these is Hamachi and NeoRouter, because they are multi-platform, Windows, Linux, OS X, Android/IOS. But they all have their setbacks which make them less than desirable. Hamachi, NeoRouter, OpenVPN, tinc, SoftEther, Tunngle, P2pVPN, FreeS/WAN, Wippien, Cisco VPN, DirectAccess. See this picture for an idea: - imagine as if all the clients are on the same switch. I am looking for a piece of software, a VPN client & server, which can do a "Mesh" sort of network, similar to what Hamachi does, but everything by me. Hi all- First post ever on Reddit, please forgive me if I do something wrong. Not sure how/if the server connects back to home with a paid/pro license. EDIT: I've been playing around with NeoRouter on my own recently, and found that while you do need to create an account on their site for the domain management, in the client you are able to put in whatever IP/Domain name that you want, and it doesn't have to reach out to the NR home servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |