New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
BuyVM private networking
HI,
Not sure if there are existing tutorial, but I couldnt find any on google and buyvm wiki.
Already created ticket, but the ticket time almost midnight.
I have bought and setup two server on same location, enabled private networking, setup /etc/network/interfaces, restart server, yet the server unable to communicate with each other.
Ping, mtr, traceroute, all failed.
Does anyone have any howto, or tutorial they can point to.?
/etc/network/interfaces
auto eth1
iface eth1 inet static
address 172.16.n.n
netmask 255.255.0.0
gateway 172.16.0.1
hwaddress 00:16:aa:aa:aa
ip route
default via 205.a.a.a dev eth0
172.16.0.0/12 dev eth1 proto kernel scope link src 172.16.n.n
Thanks
Comments
I have done as advised by buyvm staff, but the vm still cant communicate with each other.
if anyone that have done it successfully, can you share what you have done.
Communicate how?
I try not to assume things.. Have you adjusted the firewalls on the VMs?
You are going to need to use actual numbers, not 172.16.n.n
vps communicating each other
both are newly reinstalled debian 12 server.
just a placeholder.
Yes... How?
Some application isn't working? Telnet to a TCP port? ICMP?
Placeholders don't work for your interfaces file
Why are you using this netmask?
ping 172.16.n.n
ping 172.16.n.n -I eth1
traceroute unreachable
mtr not working
mysql connection unreachable(as one of the server i setup mysql server for development)
as I was told, private network is open to all vms in the same location. i dont want some one to try on my server.
it is on the stallion. though later i change it as advised by staff.
though, after reply's from buyvm staff, they are investigating this. perhaps it is an isolated issues.
It is expected that a traceroute and so also mtr fail.
Only for your VMs in the same location.. That is where the "private" part comes from
You have? Or you will change it?
Let me know if that’s better
I think I may have run into your ticket a bit ago.
Francisco
it is working now. seems like there was an issue on their side. which was resolved. thanks...
the earlier reply by staff make me confused. though it has been cleared. the network is private(unique?) to single user in the same location.
it is working now. thanks. =D