BuyVM private networking

Shamli

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

Shamli

I have done as advised by buyvm staff, but the vm still cant communicate with each other.

Please ignore those internal IP addresses shown in Stallion. Here are the steps to configure internal networking between VMs in the same location:

    Enable it on VMs from their "Private Networking" tab on the networking page under Stallion.
    Power cycle the VMs from Stallion. Shutdown/Power Off -> On, not reset/restart .
    When your VM boots up it will have a second interface eth1 on them.
    Assign IPs from the same private subnet to this eth1 interface on your different VMs.

For example:
    VM1 => ip addr add 10.0.0.1/24 dev eth1
    VM2 => ip addr add 10.0.0.2/24 dev eth1
    VM3 => ip addr add 10.0.0.3/24 dev eth1

ip link set eth1 up

if anyone that have done it successfully, can you share what you have done.

kevinds

@Shamli said: but the vm still cant communicate with each other.

Communicate how?

I try not to assume things.. Have you adjusted the firewalls on the VMs?

@Shamli said:
address 172.16.n.n
netmask 255.255.0.0
gateway 172.16.0.1
hwaddress 00:16:aa:aa:aa

You are going to need to use actual numbers, not 172.16.n.n

Shamli

@kevinds said: Communicate how?

vps communicating each other

@kevinds said: I try not to assume things.. Have you adjusted the firewalls on the VMs?

both are newly reinstalled debian 12 server.

@kevinds said: You are going to need to use actual numbers, not 172.16.n.n

just a placeholder.

kevinds

@Shamli said: vps communicating each other

Yes... How?

Some application isn't working? Telnet to a TCP port? ICMP?

@Shamli said: just a placeholder.

Placeholders don't work for your interfaces file

@Shamli said: netmask 255.255.0.0

Why are you using this netmask?

Shamli

@kevinds said: Yes... How?

Some application isn't working? Telnet to a TCP port? ICMP?

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)

@kevinds said: Placeholders don't work for your interfaces file

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.

@kevinds said: Why are you using this netmask?

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.

kevinds

@Shamli said:
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)

It is expected that a traceroute and so also mtr fail.

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.

Only for your VMs in the same location.. That is where the "private" part comes from

@kevinds said: Why are you using this netmask?

it is on the stallion. though later i change it as advised by staff.

You have? Or you will change it?

Francisco

Let me know if that’s better

I think I may have run into your ticket a bit ago.

Francisco

Shamli

it is working now. seems like there was an issue on their side. which was resolved. thanks...

Shamli

@kevinds said: Only for your VMs in the same location.. That is where the "private" part comes from

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.

@Francisco said: Let me know if that’s better

it is working now. thanks. =D