I'm new to networking as a whole so please forgive any ignorance. I have a block of IPs from my ISP. I am getting x.x.x.185 (Gateway) x.x.x.186-190 (Useable IPs) x.x.x.191 (Broadcast)
From what I'm aware of I have my interface setup correctly?
I am attempting to create a NAT rule pointing x.x.x.187 to my local a local ip 10.0.0.225. From that machine I will be running a game server. I will again want to point x.x.x.188 To a machine with another game server.
SEE FIRST COMMENT FOR ADDITIONAL PICS
At this point when I try and pull my public IP from that machine I get my routers x.x.x.186
What am I missing?
You can use routing and point /32 routes to i.e. a local server. (I think you might need proxy_arp, then...)
Or, you can span your layer-2 connection and attach it as additional interface to servers.
Is what you're recommending an alternative to what I'm doing, or in addition to what I've already set up? /32 is just a single IP out of my pool? EX x.x.x.187/32? Sorry if this is obvious. I'm learning as I go. I'm doing everything VIA the web based interface as I am not too familiar with the commands via ssh. I'm not afraid to use it though
Yes you could of course do a handfull of one-to-one NAT from public to private IP, but that will introduce so many issues later, that's why it's best to just pass the IP Packets.
But most importantly: What do you want to do with those addresses?
Use them on servers (physical or virtual; and how are they connected)?
Use them for a client-nat-pool?
I'm trying to host a game server on a single machine with a single ip. I would like each server to have their own public facing IP so each of them can have duplicate ports open for their own needs. Like having each machine run a Valve Server with the default port. Also giving whoever runs the server the ability to point their domain to the server with DNS records. This might sound like a longshot for a beginner but its what peaked my interest and I'm using the interest to learn
(I would go the routing way.)
But of course these proxy_arp constructs do there service, too... Have done so too in the past if we got no other option mostly based on lack of knowledge...
(I would recommend proxy_arp for you... Maybe someone else has something to add...)
https://book.systemsapproach.org/ This. It's free. It's good. (Don't try read cover to cover at first. Peak into the chapters and read as long as you go and go back and forth...)
In addition. To just getting starting and so on. If you have for now just a gameserver (udp/tcp) then there is also not much wrong with 1:1 NAT (if your router has the resources; if don't know how much clients and how much traffic you have). Depending on the size of your allocated network by the ISP, leave some addresses free, so you can experiment other stuff, later, while in progress.
That book is what I've been looking for. I feel as if I am asking very basic questions and I really have no hard resources to go off of other that Reddit, Discord and some community forums. For now though does it look like what I have setup is a valid 1:1 NAT rule? Should that, as I have it, point any incoming traffic to the specified local ip? And with 1:1 NAT does the local device see its public ip as the one defined in the NAT rule or as the access points public ip (OpenWRT in this case)
