NAT VPS with good network?

mikho

@sandro said:

@Cam said:

@sandro said:
can you explain what you mean by https forwarding?

You enter your domain into his control panel and all http or https traffic will be forwarded to your vps server on port 80 or 443. Thus giving you the ability to host a website without using IPv6

I'm confused, I have a NAT VPS with a specific range of ports listening to ipv4. So my webserver is listening to a dedicated port, not 80. This works differently? I could have done that even with inception hosting since it should do http forwarding?
Where can I read more about that?

If you setup your webserver to listen on port 80 you can enter your domain name in the control panel and it will work as a "regular" web server.
Same thing with https (443).
No need to tell your visitors to add port 10215 (example) to the url.

All(?) NAT providers do http forwarding on ipv4.

@sandro said:

@WSS said:
This is just a special bit of software that forwards ports 80/443 on the public IP to your VPS for the given domain name. That's all there is to it.

OK, so clients can't manually configure others custom ports to do the same for ssh for example?

If it was allowed. I removed the port forwarding feature for ports other then 80/443 from the client panel since it could cause issues when "stealing" other users ports and forwarding it to your own server.

sandro

@WSS said:
Your NAT VPS still has the private ports, and those listed forwarded from the public interface to your private IP. It's up to you do still do your own administration.

So can I forward a public 22 port to a an internal, say, 3500 used for ssh?

mikho

@sandro said:
Where can I read more about that?

Haven't seen written work about this feature.

sandro

@mikho said:

@sandro said:

@Cam said:

@sandro said:
can you explain what you mean by https forwarding?

You enter your domain into his control panel and all http or https traffic will be forwarded to your vps server on port 80 or 443. Thus giving you the ability to host a website without using IPv6

I'm confused, I have a NAT VPS with a specific range of ports listening to ipv4. So my webserver is listening to a dedicated port, not 80. This works differently? I could have done that even with inception hosting since it should do http forwarding?
Where can I read more about that?

If you setup your webserver to listen on port 80 you can enter your domain name in the control panel and it will work as a "regular" web server.
Same thing with https (443).
No need to tell your visitors to add port 10215 (example) to the url.

All(?) NAT providers do http forwarding on ipv4.

@sandro said:

@WSS said:
This is just a special bit of software that forwards ports 80/443 on the public IP to your VPS for the given domain name. That's all there is to it.

OK, so clients can't manually configure others custom ports to do the same for ssh for example?

If it was allowed. I removed the port forwarding feature for ports other then 80/443 from the client panel since it could cause issues when "stealing" other users ports and forwarding it to your own server.

This forwarding method also works for ipv6 only vps? I mean domain ipv6 80 forwarded to dedicated ipv6 port 80? Now that I think about if I got it right I guess it's the same since you forward to a private network? so it has nothing to do with public ips...

anyway I never seen that on in my IH panel... maybe it's there.
Sorry but this is new for me I thought that tunneling was the only way to access a website transparently. Why 80/443 for all users is not "stealing"? Is this configuration multidomain?

WSS

@sandro said:

@WSS said:
Your NAT VPS still has the private ports, and those listed forwarded from the public interface to your private IP. It's up to you do still do your own administration.

So can I forward a public 22 port to a an internal, say, 3500 used for ssh?

No, you're misunderstanding.

NAT gives you say, IPv4 ports #13020 - #13041. Let's assume 13041 is already taken by SSH (you always get an ssh port setup). You get ALL ports available on your IPv6.

Your SSH is already bound to port 22, and is accessible from your IPv6 via port 22. Port 13041 goes to your port 22 from the public IPv4- the host set this up for you. The other ports, #13020-#13040 are forwarded to your private IP #13020-#13040.

There really isn't any more to it.

mikho

@sandro said:

This forwarding method also works for ipv6 only vps? I mean domain ipv6 80 forwarded to dedicated ipv6 port 80? Now that I think about if I got it right I guess it's the same since you forward to a private network? so it has nothing to do with public ips...

anyway I never seen that on in my IH panel... maybe it's there.

Well, ipv6 is dedicated to your vps, so no need for a forwarding feature. Only ipv4 as it is shared between clients.
Thats why you get 20-ish (depends on provider) ports on ipv4.
If you run your web server over ipv6 you just point the AAA record to your ipv6 and your done.

Basicly what happens is
You add an A record on your domain to the public IP.
In the control panel you enter the domain name and where the traffic should be forwarded to and on what port(s).

The browser connects to the host node and says "I want to connect to this domain" and the host node shows the way to your vps.

zongyouxiao

@Cam said:

@sandro said:
can you explain what you mean by https forwarding?

You enter your domain into his control panel and all http or https traffic will be forwarded to your vps server on port 80 or 443. Thus giving you the ability to host a website without using IPv6

Your price is cheap, does your panel support this feature:)?

Cam

@zongyouxiao said:

@Cam said:

@sandro said:
can you explain what you mean by https forwarding?

You enter your domain into his control panel and all http or https traffic will be forwarded to your vps server on port 80 or 443. Thus giving you the ability to host a website without using IPv6

Your price is cheap, does your panel support this feature:)?

I do not support this. If you would like to host a website on my service I suggest using cloudflare as they have a built in IPv6 to IPv4 proxy.

sandro

@Cam said:

@zongyouxiao said:

@Cam said:

@sandro said:
can you explain what you mean by https forwarding?

You enter your domain into his control panel and all http or https traffic will be forwarded to your vps server on port 80 or 443. Thus giving you the ability to host a website without using IPv6

Your price is cheap, does your panel support this feature:)?

I do not support this. If you would like to host a website on my service I suggest using cloudflare as they have a built in IPv6 to IPv4 proxy.

What are the advantages?

Cam

@sandro said:

@Cam said:
I do not support this. If you would like to host a website on my service I suggest using cloudflare as they have a built in IPv6 to IPv4 proxy.

What are the advantages?

I wouldn't say there are any advantages or disadvantages, just another way to view a website.

sandro

Sorry I thought support was as in favour

sandro

One thing still unclear... why this can't be done for all ports like 22? we all "share" 80/443 so what is the difference with others if all connected to a domain?

WSS

You obviously don't understand what is undertaken to make this happen. Of course common ports would need to multiplex between the different NAT services. You can't just do that; the way the web proxy works is because you tell it the domain, and it looks that up and sends it to you.

Just pay the extra couple of bucks for a non-NAT service.

WSS

Read this and decide if it makes any more sense. HTTP/HTTPS proxies are a feature. You don't generally get those. They're done by the host just to enable outworld IPv4 connectivity without specifying port numbers.

https://www.mpkossen.com/2016/02/getting-started-with-lowendspirit/

AnthonySmith

I mean this in a friendly way, but how is it possible in 2017 that NAT still confuses people, for at least the last decade that is how your home network has worked.

sandro

I got it now, its because they are web proxies...

mikho

@sandro said:
I got it now, its because they are web proxies...

Waiting for your order

vimalware

I use my @mikho NAT daily for surfing.

sandro

@AnthonySmith said:
Yep, the network in Italy is not the best, seems to fall over if someone in Romania farts the wrong way, sadly it is out of my hands.

It has a minute or so of down time most days on IPv6, just FYI there is no problem changing locations, migration (with data) takes a few minutes.

Thanks for confirming, I have nothing against your service really but I many times tried to just play with my VPS for testing stuff and it just wouldn't connect. Randomly.

Timtimo13

Awesome, I'm a freaking valued customer @mikho

:-P
I should consider to connect my, from you bought, domains to this server lulz

mikho

@Timtimo13 said:
Awesome, I'm a freaking valued customer @mikho

:-P

You all are

@Timtimo13 said:
I should consider to connect my, from you bought, domains to this server lulz

Timtimo13

Some benchmark from one of mikho's VPS @BG location:

root@bg:~# wget -qO- bench.sh | bash

---

CPU model : Intel(R) Xeon(R) CPU L5630 @ 2.13GHz

Number of cores : 1

CPU frequency : 2133.362 MHz

Total size of Disk : 3.0 GB (0.2 GB Used)

Total amount of Mem : 128 MB (24 MB Used)

Total amount of Swap : 0 MB (0 MB Used)

System uptime : 0 days, 0 hour 15 min

Load average : 0.14, 0.04, 0.01

OS : Debian GNU/Linux 7

Arch : x86_64 (64 Bit)

Kernel : 2.6.32-042stab123.9

----------------------------------------------------------------------

I/O speed(1st run) : 281 MB/s

I/O speed(2nd run) : 299 MB/s

I/O speed(3rd run) : 245 MB/s

Average I/O speed : 275.0 MB/s

----------------------------------------------------------------------

Node Name IPv4 address Download Speed

CacheFly 205.234.175.175 58.4MB/s

Linode, Tokyo, JP 106.187.96.148 6.96MB/s

Linode, Singapore, SG 139.162.23.4 9.37MB/s

Linode, London, UK 176.58.107.39 391KB/s

Linode, Frankfurt, DE 139.162.130.8 54.9MB/s

Linode, Fremont, CA 50.116.14.9 5.78MB/s



@mikho

You should sack that dude, who is carring the packages from my

VPS to Softlayer DCs seriously. That dude is awful.

The test took that long, that I canceled it at that point.



But still... love you @mikho

But for me it's pretty usable 'cause of good connection to Germany.

Regards

mikho

@Timtimo13 said:
@mikho

You should sack that dude, who is carring the packages from my

VPS to Softlayer DCs seriously. That dude is awful.

The test took that long, that I canceled it at that point.



But still... love you @mikho

But for me it's pretty usable 'cause of good connection to Germany.

Regards

Whats the url for the softlayer testfile? I can have a look
Or better yet, what benchmark script did you run?

Timtimo13

I simply ran bench.sh: https://bench.sh

I had problems with dal05 as well as sea01, I simply commented out dal05 but that did not
help, so i gave up on softlayer completely.
FRA02, SNG01, HKG02 might be OK.

AnthonySmith

sandro said: Thanks for confirming, I have nothing against your service really but I many times tried to just play with my VPS for testing stuff and it just wouldn't connect. Randomly.

odd. I have it monitored on Ipv4 and 6. I can see daily dips on ipv6 for very short periods of time but nothing like you are describing, no idea what is causing that as its the first I am hearing of it and no one else has mentioned anything.

sandro

@AnthonySmith said:

sandro said: Thanks for confirming, I have nothing against your service really but I many times tried to just play with my VPS for testing stuff and it just wouldn't connect. Randomly.

odd. I have it monitored on Ipv4 and 6. I can see daily dips on ipv6 for very short periods of time but nothing like you are describing, no idea what is causing that as its the first I am hearing of it and no one else has mentioned anything.

I wrote about it in the LES forum, maybe things changed in the last months.