Allocate IP address from /29 subnet to virtual machines
Allocate IP address from /29 subnet to virtual machines
So here's the deal, I have a /29 IP block from ExtraIP, and I want to assign those to my virtual machines on my server so that I can access them through (for example) 37.123.213.231 instead of my usual public IP. I have a KPN Experia Box V12 router, and I can't use that to route any IP addresses. Can anyone help me? I have virtual machines (ubuntu server) set up on my dedicated Ubuntu (GUI) server. I would like to know how to assign each of them a public IP address, since I want to start a VPS hosting business, but I don't know how to get started with the user's IP addresses. Explain to me like I'm 5 if you can, as I'm quite a noob when it comes to networking
You can configure your virtual machines for bridged networking either by manually assigning IP addresses or letting them obtain them automatically from the upstream modem or gateway through DHCP. Today you often don’t require separate IPs—multiple domains can point to the same IP, with a reverse proxy handling traffic transparently to any target machine, regardless of its public address or port. Alternatively, implement virtual hosts for more flexibility.
The problem is not the domains. It's not for web hosting, it is for VPS hosting. I want to be able to give a customer an IP that they can access their server on, instead of ssh'ing with port numbers. Also, since it's a server in my family home, I'd rather use different public IP addresses for my VM's (the customer VPS's) rather than my parent's public IP
Well there are a myriad of problems here but just a few: 1) You NEED to know networking and security for this or you're going to be in for a really bad time. 2) You can't just get public IPs from ExtraIP and have them work at your home, you need to tunnel to where they are hosted at, it's not as simple as take IPs from Place A and make them work at Place B without anything else. The gateway for those addresses is in Place A still, you need to tunnel those IPs back to Place A. 3) Unless you're segmenting everything off from anything else in the home you're basically asking for trouble there too. 4) Nobody is going to rent a VPS from someone random on the internet with no infrastructure and guaranteed levels of support unless they just need to mask their IP while doing something nefarious and are probably paying with a stolen card or something. 5) What is your logging plan? What will you do if the cops come knocking because someone was hosting something illegal? How do you plan to deal with torrents and notices? 6) Why are you trying to do 1:1 machine to IP mapping to being with? That's 5 people you can rent to instead of 500 when you do many:1 mapping. Not trying to be a downer or anything but there is a TON more to this than a few VMs + some IPs = VPS hosting & money
They wouldn't be able to reach them using an IP address but you could assign a name such as server1.domain.com so you can manage more than five. This setup relies on the gear your provider supplies, its configuration, and the capabilities it offers, which we don’t know. For home use, you usually get a modem or gateway that assigns one of those IPs via DHCP to any of the first five devices directly connected to it—just set it up manually. You should turn off DHCP on that device if possible, connect your VM host to it, assign an IP yourself, then configure the VMs as bridges and assign the remaining ones individually. Yes, what I said here is more suited for friends or local hosting, not general customers.
Im aware of all of those problems, this is a long term idea and all that im currently looking for is a few links and references as to how I can tunnel the ip's from extraip to my servers. I want to figure out how it all works and how I can do it before I start to worry about the next part (s). Do you by any chance know how I can tunnel them. Idk what ip mapping is, as I said im still learning. Do you have any links where I can learn these things?
This approach is more straightforward for those who prefer relying on others to handle the process. If you're not aiming to dive deep, it becomes simpler to assist. For tunnels, the setup relies on ExtraIP's capabilities, and you'll likely need to configure a GRE tunnel at a minimum. You might consider using a VM as a tunnel endpoint that connects to ExtraIP. The main challenge lies in the lack of a unified guide, with many resources available but varying based on your specific setup. Mapping typically involves PAT(many:1) instead of traditional NAT(1:1), enabling multiple devices to share a single IP address. This concept mirrors how home internet allows several connections behind one public IP. PAT here refers to assigning one IP to multiple ports or ranges. Still, there are numerous possible configurations, depending on ExtraIP's configuration. Areas to explore: PAT/NAT GRE tunnels, IP logging/security (start with logging), and general resources like cisco.com, juniper.com, StackOverflow, and Google.