Size: 1480
Comment:
|
Size: 1627
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
Below is a diagram that shows how your virtual network sees the world and how the world sees it. We have eliminated for the moment the complications of the <<latex($\mu$)>>Cloud. The IP address 216.249.119.123 is a place holder for your IP address. | {{{ NOTE: THERE HAS BEEN A CHANGE THE PROCEDURE BELOW! YOU NO LONGER NEED TO SETUP THE WHOLE SYSTEM SEE THE NEW DIRECTIONS }}} Below is a diagram that shows how your virtual network sees the world and how the world sees it. The IP address 10.10.4.X is a place holder for your IP address. |
Line 6: | Line 10: |
== New Instructions == | |
Line 7: | Line 12: |
In order for you to do port forwarding for your server, you must setup the iptable rules. We need two pieces of functionality: | First it is possible for you to use the old instructions, but the following procedure will make it easier. |
Line 9: | Line 14: |
1. NAT 1. Port forwarding 3389 -> 192.168.1.2:3389 and 3390 --> 192.168.1.3:3389 |
1. Download the new scripts: [[attachment:nat]], [[attachment:interface]], [[attachment:list]] 1. Using !FileZilla or your favorite scp client and login to your server (use the Host=IP address, username=[name given in class] and port=22). 1. Upload the "nat" file you downloaded. (A real linux person would use wget or some such utility to get it directly from this site to your linux machine if you want try that instead ;-) 1. On your linux machine issue the commands: a. {{{ chmod u+x nat }}} a. {{{ chmod u+x list }}} 1. Now run it {{{./nat -a [your ip address]}}} /* How do you find your IP address? # ifconfig */ |
Line 12: | Line 22: |
To setup NAT on Ubuntu, see [[https://help.ubuntu.com/community/Internet/ConnectionSharing#Ubuntu_Internet_Gateway_Method_.28iptables.29|Ubuntu NAT]]. We'll add a short bit of instructions to the system to forward the ports as follows: | Your system is now setup! You can double check this by running {{{ ./list }}} which shows the configuration changes that we just made. Of course you can always just look at the script to see what it did ;-} |
Line 14: | Line 24: |
{{{ #Port Forwarding Stuff: iptables -t nat -A PREROUTING -i eth0 -p tcp -d 216.249.119.[your ip] --sport 1024:65535 --dport 3389 -j DNAT --to-destination 192.168.1.2 iptables -t nat -A PREROUTING -i eth1 -p tcp -d 216.249.119.[your ip] --sport 1024:65535 --dport 3389 -j DNAT --to-destination 192.168.1.2 iptables -t nat -A PREROUTING -i eth0 -p tcp -d 216.249.119.[your ip] --sport 1024:65535 --dport 3390 -j DNAT --to-destination 192.168.1.3:3389 iptables -t nat -A PREROUTING -i eth1 -p tcp -d 216.249.119.[your ip] --sport 1024:65535 --dport 3390 -j DNAT --to-destination 192.168.1.3:3389 }}} |
|
Line 22: | Line 25: |
NOTE: ALL OF THIS CAN BE FOUND BY TYPING "man iptables" from the command line in linux. | === Troubleshooting === So you may have noticed that there is already a nat script on your server. Well it does an extra thing that will cause trouble. If you ran that script you need to edit /etc/network/interfaces and remove the duplicate eth1 information. |
Virtual Network Configuration
NOTE: THERE HAS BEEN A CHANGE THE PROCEDURE BELOW! YOU NO LONGER NEED TO SETUP THE WHOLE SYSTEM SEE THE NEW DIRECTIONS
Below is a diagram that shows how your virtual network sees the world and how the world sees it. The IP address 10.10.4.X is a place holder for your IP address.
New Instructions
First it is possible for you to use the old instructions, but the following procedure will make it easier.
Using FileZilla or your favorite scp client and login to your server (use the Host=IP address, username=[name given in class] and port=22).
Upload the "nat" file you downloaded. (A real linux person would use wget or some such utility to get it directly from this site to your linux machine if you want try that instead
- On your linux machine issue the commands:
chmod u+x nat
chmod u+x list
Now run it ./nat -a [your ip address]
Your system is now setup! You can double check this by running ./list which shows the configuration changes that we just made. Of course you can always just look at the script to see what it did ;-}
Troubleshooting
So you may have noticed that there is already a nat script on your server. Well it does an extra thing that will cause trouble. If you ran that script you need to edit /etc/network/interfaces and remove the duplicate eth1 information.