Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

For Providers: Reasonable Expectation in Purchasing Question NAT Firewall

In buying VPSs, I generally find that the IP provided is the IP that will show in Virtualmin after installation. If it doesn't, a different IP shows, Virtualmin states that this is usually because the VPS is behind a NAT firewall. I then need to modify the settings in Virtualmin so DNS entries use the external not internal IP address.

In selling VPSs, is it reasonable to expect that the provider would disclose this fact in the offer? Alternatively, is this just a different way of setting up a VPS sales operation, so the fact that the VPSs are behind a NAT firewall is of no consequence. Lastly, another alternative, is something else besides a NAT firewall causing this difference in internal and external IP?

Please advise.

Comments

  • If you run ifconfig from the machines, what IP is bound? This sounds bizarre.

  • FlamesRunnerFlamesRunner Member
    edited February 2016

    Edit: Ignore this

  • rm_rm_ IPv6 Advocate, Veteran
    edited February 2016

    Riz said: This sounds bizarre.

    Scaleway for example uses NAT where you get a 10.x.x.x IP on your interface on the machine, and it's mapped 1:1 to an external IP. AFAIK Amazon AWS does too.

    In general this allows for easier migration of IPs between the actual machines, as you don't need to reconfigure networking on the machine itself to attach/detach different IPs to it.

    Thanked by 1Riz
  • @rm_ said:
    In general this allows for easier migration of IPs between the actual machines, as you don't need to reconfigure networking on the machine itself to attach/detach different IPs to it.

    Interesting, is the NAT not user controlled?

  • rm_rm_ IPv6 Advocate, Veteran

    Riz said: Interesting, is the NAT not user controlled?

    It's a full 1:1 NAT, which means every possible port is already forwarded to your internal IP, so you don't need to 'control' it in any way really.

  • I understand that, but meant do they allow control of the internal IP you are 1:1 NATing, or is it 'stickied' to one LAN IP?

Sign In or Register to comment.