We have recently expanded the capabilities and resources available on our Private Network. While previously you were able to use the Private Network to perform server to server traffic internally, you were not able to access our services such as OS Repositories, backups, and more over the private network. We have completed the implementation of this ability and you will need to update any machine that you have currently deployed at the time of this blog post (any new setups will be automatically pre-configured).
This will also enable compatibility for Automated OS Installs and new features yet to be released.
The task which must be done is creating a static route in the OS of your server to tell your server to use your Private Network gateway for all private network targetted communication (otherwise it would use your default network gateway, which is the Public Network and thus not reach your Private Network target).
This feature only relates to servers that have Private Network functionality. If your server has an IP address beginning with 172.16.xxx.xxx assigned in your Device Manager, then it is Private Network Enabled.
We have put together a simple script for the following operating systems:
To implement the advanced Private Network capability on your server, simply download and execute this bash script which will create the static route and modify your OS Update mirrors to use our local (thus, faster and no public BW usage) repositories.*
*FreeBSD’s mirrors will not be auto-updated. The static route however will be created.
Step 1: Download: http://repos.lax-noc.com/private_route.sh
Step 2: Execute on your server
Step 3: Finished
You can also copy and paste the following commands which will download, execute, and then delete the install file:
- wget http://repos.lax-noc.com/private_route.sh ; sh private_route.sh ; rm -f private_route.sh
IF YOU WOULD RATHER HAVE OUR SUPPORT TEAM ENABLE ADVANCED PRIVATE NETWORK CONNECTIVITY, SIMPLY MAKE A TICKET, WE WILL GLADLY DO THIS COST-FREE.
FOR WINDOWS OS:
Step 1: Open a command line window
Step 2: Input the following: route add -p 172.16.0.0 mask 255.240.0.0 LOCALGATEWAY** metric 1
**Replace LOCALGATEWAY, with the actual GATEWAY IP ADDRESS of your Private Network VLAN. This is the second IP address in your /26 CIDR IP block. If you need help configuring your Windows server private network, simply make a ticket and our support team will gladly do this for you!
This is a seamless, no downtime, no service interruption update. It will simply enable advanced communications to our backend local resources to provide you with fully internal and secure transfers between OS Update servers, data storage services, server to server communications, DNS services, Automated OS Installs, and more.
Feel free to submit a ticket with any questions or needs for assistance.