Criamos uma Rede Local (LAN) privada, em cada centro de dados, à qual os Linodes podem aderir, sem ter que se preocupar com a transferência contando com a sua quota mensal de rede. Esta funcionalidade permite algumas possibilidades interessantes. Por exemplo, a criação de conjuntos de front-end webserver Linodes e processo interno de dados no servidor Linodes que comunicam através desta rede privada. A replicação de bases de dados, backups e rsync também me vêm à mente. Ah, e o IP Failover funciona tanto para IPs públicos como privados.
Para entrar na diversão, entre no site dos membros e dirija-se a esta página. Clique no botão para ter um endereço IP privado atribuído ao seu Linode. Reinicie seu Linode e traga o novo IP no eth1 - um comando de exemplo para fazer isso é fornecido na página. Você precisará completar estes passos para cada Linode que você quer ser capaz de se comunicar através da rede de processo interno.
Isto só funciona para Linodes dentro do mesmo centro de dados Os Linodes não têm de estar sob uma conta/ligados.
Então, qual é o valor desta característica? Adivinhou-o: GRÁTIS!
Sweet. Wondered when this would come about, remember a mention about it a long time ago
This is really great; I was recently thinking that something like this would be a great feature to add 🙂
I couldn’t find a link to this within the Linode manager. Am I looking in the wrong place (e.g. Utilities) or is there a reason this wasn’t added to the manager yet?
@marvinp the link is…linked in the article text. You’ll know when you get there. It’s the page titled “Lassie” lol.
Heh, thanks for the heads up jharrison, I’ve corrected that. The Private IP page is now linked from the Utilities page as well.
interesting feature 🙂 just wondering though whats the story with security? is this safe enough to treat like your average “internal LAN”? or should it be firewalled as well? you say they dont have to be apart of the same account, im guessing its one big subnet for everyone? just wondering if i should consider firewalling it or not 🙂
We filter traffic based on MAC and IP addresses. You can’t sniff traffic on the back-end LAN. You won’t see other people’s traffic. The only packets you’ll receive are those that are destined for your Linode. It works no differently from our public-networking filtering.
A follow up to the last security question:
‘The only packets you’ll receive are those destined for your Linode’.
This would include port scanning packets and connections from other Linode customers in the same data center correct?
Is there a way to form a vpn using the private IPs of just the nodes within your Linode account – to get LAN speed, no bandwidth charges for local traffic AND security?
It’s an open local network, so others in your facility can connect to services running on your local IP. You’ll want to firewall or ACL appropriately.
You can form VPNs as you typically would — openvpn for example.
I know this is a very old post but Is there any possibility of having my two linodes connected if they are on a different DC now? I would really love to have that since if a DC has a problem the other DC would still be working.
I’d like to see this feature improved to be available only between your own hosts and between DCs.
I am trying to use this feature.
I use two vm in the same DC, one is for web app and other for MariaDB.
I bind the maria db server do private ip. When I try to connect to my db server from myweb I can’t connect.
I try a talnet command and the result is: No route to host
I do a nmap and only port 22 is open. I Don’t use any fw rules.
Hey Paulo. You’ll want to make sure that both Linodes have private IPs assigned to them; this is how they can both send and receive information over the private network.
This Community post does a nice job explaining how Linodes communicate with private IPs:
Otherwise, if you suspect there is an issue, I would recommend opening a ticket with our Support team so they can take a look.