VirtualBox Port Forward Issue

This video shows how to fix some port forwarding issues when running SOA Suite on a Virtual Box instance and using NAT and port forwarding. The main key is to set the Listen Address of the servers to 'localhost' and setup a new channel to listen to the default network address of 10.0.2.15. In essence, this simply reverses the addresses which come by default (ip,localhost) to become (localhost,ip). This fixes a problem with deployment from JDev. Also, this video gives a sneek peak at some VMs I plan to distribute soon. -John 


Comments:

John, nice explanation of the issues and solutions. I guess another approach could be to use VirtualBox Host Only Networking for the vms, instead of the NAT/Port forwarding setup you are using. The vm's would only be reachable from the host unless you gave the front-end vm another virtual NIC which was publicly visible (via Bridged or NAT/Port forwarding). Cheers - FB

Posted by Fat Bloke on June 01, 2011 at 10:47 PM EST #

Good point FB. The problem with using host only is trying to update the VM. I try to keep the JEOS up to date and the host-only network prevents the VM from getting to the outside world. Also, the setup of another front-end to make the VMs accessible is more work then I care to do... I don't like playing IP address games. I'd prefer to deal with port mappings. Thanks for the comment.

Posted by John Graves on June 02, 2011 at 03:48 AM EST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

me

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today