The service allows for some servers to have a private network available and therefore can exchange data over a private network that you control.

The RPN uses the second interface of your server to avoid overloading the internet interface of your server.

Therefore, it is possible to configure, modify and create in minutes your network architecture designed according to your needs.

To see the availability of the RPN network for each server modem, check our website.

You want to exchange data with another Dedibox customer?

With the LinkePing function it is really easy! With a few clicks, indicate what are the other ONLINE accounts servers that can interconnect with yours and exchange data a few minutes later!

The private network is connected to the second interface of your server, it is connected to a totally secure network, different of the one you are using to connect to the internet.

For example you have 6 servers and you can easily create RPN groups, as shown in the following example:

  RPN-group-1 = server 1 and 2            the servers 1 and 2 can communicate between each other
  RPN-group-2 = server 1, 6 and 3         the servers 1, 6 and 3 can communicate between each other
  RPN-group-3 = server 1 ,4 and 5         the servers 1, 4 and 5 can communicate between each other

The server 1 is a monitoring server, it needs to connect to all servers. The server 3 contains a critical database so no server other than the 6 (which uses this database) must have access.

You have 50 servers? You can set up multiple groups and allow only one server in your Online account to communitcate with all the others. All configurations between servers are possible.

The same principle applies when you choose to let a server from another account to communicate with one of your own.

Many applications require, for reasons of security and performance a private dedicated network, for example:

• File sharing via CIFS, NFS
• Device Sharing via iSCSI
• Synchronization of block-devices with DRDB
• Load-Balancing
• Cloud Storage with Openstack and Hadoop technologies

You have to connect yourself with your management console, click on “Server” and then on “RPN Groups” - or click directly on this link http://console.online.net/en/server/rpn

In the first step, you need to click on “Create RPN group” then enter the “name of the croup”, select the servers you want to have in the group and confirm your modification.

It takes 5 to 10 minutes until the RPN group becomes active. It has become active, when the status changed to “active”.

To modify a group (add or delete servers) you need to click at “Modify the group”, select or deselect one or more servers and validate the request by clicking on “Remove selected servers of the group” or “Add servers to the group”

It takes 5 to 10 minutes before thez changes of your RPN group become active.

To share an existing group with one or several servers of another client on Online, you have to click to the tab “Shared RPN Groups”, then on the button “Share existing local group”. You simply have to enter the server number in the form. The server will then be added to the existing group and it can now communicate with the other servers in the same RPN group.

Once you can see the server in the RPN group, the other client of Online will receive a notification in his account to validate the request.

This is the IP that you need to use for the connection to the RPN.
It is linked to your server and can not be changed. This IP is not reachable from the Internet.

Depending on the kernel and the Linux version you are using, the name of the interface might be different. You need to identify it for the correct function.

In SSH type:

   ifconfig -a | grep eth

This command will show you a list of all available interfaces on your server.
The interface eth0 is used for your Internet interface (62.210.xxx.xxx)
The second interface should be activated to connect to the RPN.

You need to configure the second interfaces to use DHCP. Everything will be configured automatically.
For example: Edit the file /etc/network/interfaces and add the following lines

  auto eth2
  iface eth2 inet dhcp

After you have saved the file, you need to type the following command

  ifup eth2

Attention: the names of the interface may vary (eth1-eth2-eth3) and need to be verified before you run the command

ifconfig -a | grep eth

The RPN IP must always respond to pings.
Your RPN address must always respond to pings for the the check of fragmentation (TCP-MSS)
In case of a RPN network that has MTU 1500 and 9000 in cohabitation, disabling icmp may cause malfunction.

Type the following command:

    route -n

It will show you the routes on your server and those added by the setup of the RPN image

The RPN network support Jumbo Frames, this means you can configure your network adapter with MTU 9000.

The performance gain can reach up to 20% on resource-intensive applications such as iSCSI, NFS, and DRDB.

To know your current MTU you need to type:

  ifconfig eth2
  

  ifconfig eth2 | grep MTU
  

=== Debian / Ubuntu ===
In the file /etc/network/interfaces you need to add

  auto eth2
  iface eth2 inet dhcp
  mtu 9000

and type

  ifup eth2  

or

  /etc/init.d/networking restart

=== Centos ===
In the file /etc/sysconfig/network-scripts/ifcfg-ethX you need to add (X = the number of the interface)

  MTU="9000"

and restart the network

  service network restart

To modify the MTU in Windows, we recommend the following software which makes the change very easy: http://www.clubic.com/telecharger-fiche305576-tcp-optimizer.html

> Launch the software
> Click on "Custom"
> In "Network adaptater selection" select the network adapter of the RPN
> Change the MTU value to 9000
> Click on "Apply change" 

You need to edit in the file my.cnf the line bind-address

example :

  bind-address            = 10.90.xxx.xxx

After saving the file you need to restart the Mysql server.

The only restriction is not to broadcast a MAC other than that which corresponds to the RPN network card that appears when running

 ifconfig