Jump to content

Using a /29

Go to solution Solved by CWP,

So what you want to do is have your server take up the entire .170 - .174, as if, to the Internet, there are 5 servers in that range?

 

If so, you will need to use subethernet designations virtual network interfaces. My memory of that is faded, but under Linux, it should be eth0:0, eth0:1, etc. and assigning each an IP address.

 

EDIT: From http://linuxconfig.org/configuring-virtual-network-interfaces-in-linux,

iface eth0 inet static        address 10.8.0.170        netmask 255.255.255.248iface eth0:0 inet static        address 10.8.0.171        netmask 255.255.255.248iface eth0:1 inet static        address 10.8.0.172        netmask 255.255.255.248iface eth0:2 inet static        address 10.8.0.173        netmask 255.255.255.248iface eth0:3 inet static        address 10.8.0.174        netmask 255.255.255.248
There is some logic somewhere (either inside the network stack or in the program/daemon itself) that allows you to only bind to 0.0.0.0 or {list of assigned IP addresses}. This ensures that typos are not made in the configuration, as well as allowing the network stack to be aware that it is responsible for more IP addresses.

I have a dedicated server that I need to use my /29 on. The server is running the latest Debian 8.

 

The info I am provided is (fake addresses are used for an example)

Server IP Address: 10.8.0.170Server Usable IP Range: 10.8.0.170 - 10.8.0.174Subnet Mask: 255.255.255.248Gateway Address: 10.8.0.169DNS1: 123.123.123.123DNS2: 123.123.124.123

The current /etc/network/interfaces (fake addresses are used for an example (same as above))

# This file describes the network interfaces available on your system# and how to activate them. For more information, see interfaces(5).source /etc/network/interfaces.d/*# The loopback network interfaceauto loiface lo inet loopback# The primary network interfaceallow-hotplug eth0iface eth0 inet static        address 10.8.0.170        netmask 255.255.255.248        gateway 10.8.0.169        dns-nameservers 123.123.123.123 123.123.124.123

This is an unmanaged dedicated server, so I would prefer if I didn't break my ability to connect to it. Only respond with answers if you actually know you stuff.

Link to comment
https://linustechtips.com/topic/496524-using-a-29/
Share on other sites

Link to post
Share on other sites

So what's the question here exactly? Will this work? If that is the question then yes, granted there is a router between this network and any other networks you have.

 

This is the default config that the provider had set up. The "10.8.0.X" addresses in the example are actually public facing if that changes matters. Assuming this does work correctly, when I have a server attempt to bind to the address "10.8.0.171" it fails; however, binding to "10.8.0.170" is successful.

Link to comment
https://linustechtips.com/topic/496524-using-a-29/#findComment-6640075
Share on other sites

Link to post
Share on other sites

So what you want to do is have your server take up the entire .170 - .174, as if, to the Internet, there are 5 servers in that range?

 

If so, you will need to use subethernet designations virtual network interfaces. My memory of that is faded, but under Linux, it should be eth0:0, eth0:1, etc. and assigning each an IP address.

 

EDIT: From http://linuxconfig.org/configuring-virtual-network-interfaces-in-linux,

iface eth0 inet static        address 10.8.0.170        netmask 255.255.255.248iface eth0:0 inet static        address 10.8.0.171        netmask 255.255.255.248iface eth0:1 inet static        address 10.8.0.172        netmask 255.255.255.248iface eth0:2 inet static        address 10.8.0.173        netmask 255.255.255.248iface eth0:3 inet static        address 10.8.0.174        netmask 255.255.255.248
There is some logic somewhere (either inside the network stack or in the program/daemon itself) that allows you to only bind to 0.0.0.0 or {list of assigned IP addresses}. This ensures that typos are not made in the configuration, as well as allowing the network stack to be aware that it is responsible for more IP addresses.

CPU AMD 7800X3D | Cooling Noctua NH-D15 chromax.black | Motherboard ASUS PRIME X870-P WIFI | RAM Corsair Vengeance RGB 6GHz CL30 32GB | GPU EVGA GeForce RTX 3070 FTW3 Ultra Gaming |

Case Fractal Design Define R5 | Storage Samsung 980 PRO 500GB, Samsung 970 EVO+ "v2" 2TB | PSU Corsair RM850x 2021 | Display ASUS VP247QG + Samsung SyncMaster T220 | OS CachyOS

Link to comment
https://linustechtips.com/topic/496524-using-a-29/#findComment-6640193
Share on other sites

Link to post
Share on other sites

So what you want to do is have your server take up the entire .170 - .174, as if, to the Internet, there are 5 servers in that range?

 

If so, you will need to use subethernet designations. My memory of that is faded (will edit to confirm later), but under Linux, it should be eth0:0, eth0:1, etc. and assigning each an IP address.

 

You are in fact correct. So you do something like this

auto eth0:0iface eth0:0 inet static        address 10.8.0.171        netmask 255.255.255.248

EDIT: I've seen your edit now...

Link to comment
https://linustechtips.com/topic/496524-using-a-29/#findComment-6640370
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×