How internet addressing really works - Revision history

Tinker at 05:21, 27 December 2021

2021-12-27T05:21:36Z

Tinker: /* Port Forwarding */

2020-10-17T05:50:32Z

Port Forwarding

Tinker at 05:44, 17 October 2020

2020-10-17T05:44:28Z

Tinker: Created page with "(This is a very rough draft...) There're 2 ways to get to a machine. IP address & name. But to use name, you need to have DNS set up. Either way, there's also the port. T..."

2020-10-17T05:19:21Z

Created page with "(This is a very rough draft...) There're 2 ways to get to a machine. IP address & name. But to use name, you need to have DNS set up. Either way, there's also the port. T..."

New page

(This is a very rough draft...)

There're 2 ways to get to a machine.

IP address & name.

But to use name, you need to have DNS set up.

Either way, there's also the port.

The port is specific to the actual service on the machine.

i.e.: port 80 is HTTP, port 443 is HTTPS, port 22 is SSH...

When your entire network is on a single address as far as the outside world is concerned, you have a couple options to access individual machines.

You can forward specific ports to specific machines (probably with a bit of fiddling in Firewall/NAT on your pfSense box...) or you can set up proxies.

Port forwarding is pretty straightforward, but you need to remember how you've set up the ports.

← Older revision		Revision as of 05:21, 27 December 2021
Line 1:		Line 1:
		+	<span style="background-color: rgb(153, 204, 0); color: rgb(0, 0, 255);" data-mce-style="background-color: #99cc00; color: #0000ff;">'''<big>Now on Wiki.NerdMage.Ca</big>'''</span>
		+
	(This is a very rough draft...)		(This is a very rough draft...)

← Older revision		Revision as of 05:50, 17 October 2020
Line 24:		Line 24:

	As an example, I have a machine on my network at 192.168.0.99 (Not an address accessible to the outside world) & I'd like access to it while away. I go into Firewall/NAT on my pfSense box & forward port 52099 to this address & translate the port number to 22 (SSH). This gives me the ability to SSH into the machine pretty much anywhere I may be as long as I have internet access.		As an example, I have a machine on my network at 192.168.0.99 (Not an address accessible to the outside world) & I'd like access to it while away. I go into Firewall/NAT on my pfSense box & forward port 52099 to this address & translate the port number to 22 (SSH). This gives me the ability to SSH into the machine pretty much anywhere I may be as long as I have internet access.
		+
		+	You can do the same for any service. You could port 52080 to an internal machine at port 80 (http), but you'll have to remember to add <code>:52080</code> to the machine name or IP address when accessing it from outside. (i.e.: <code>http://my.domain.net:52080/</code>)

	== Proxies ==		== Proxies ==

@@ Line 14: / Line 14: @@
 When your entire network is on a single address as far as the outside world is concerned, you have a couple options to access individual machines.
 You can forward specific ports to specific machines (probably with a bit of fiddling in Firewall/NAT on your pfSense box...) or you can set up proxies.
 Port forwarding is pretty straightforward, but you need to remember how you've set up the ports.