Re: Port forwarding without a hardware router.
- From: Ram <Ram@xxxxxxxxxxx>
- Date: Sun, 21 Dec 2008 16:02:23 +0000
Gary Gapinski wrote:
Ram wrote:I have setup Virtual Box which is using the internal address(NAT)
192.xxx.xxx.xxx
I have setup a website on the Virtual Box and would like to access it
from the Internet / Work.
I need to know howto forward traffic on port 80 to the website on the
Virtual Box.
This is known as "forwarding" in SuSEfirewall2 parlance. See
FW_FORWARD_MASQ in /etc/sysconfig/SuSEfirewall2. The value can be set
using YAST Security and Users Firewall, YAST System /etc/sysconfig
Editor, or manually edited. The value should be something like
FW_FORWARD_MASQ="0/0,192.xxx.xxx.xxx,tcp,80".
That's where I thought I should be doing it. However I did not get the result I was expecting.
For testing I have a dummy site running on the host server internal ip 192.xxx.xxx.10 which can be accessed from the LAN and from the internet.
I have setup a 2nd dummy site in Mint running in a VM with an ip of 192.zzz.zzz.20 which is currently only accessible from the LAN.
I tried masquerading port 80 in YaST/Firewall setting both with using the external/internal to 192.zzz.zzz.20 neither worked.
Would I need 2 entries one for the external address pointing to 192.zzz.zzz.20 and one for ther internal ?
.
- References:
- Port forwarding without a hardware router.
- From: Ram
- Re: Port forwarding without a hardware router.
- From: Gary Gapinski
- Port forwarding without a hardware router.
- Prev by Date: Re: Backend plugin?
- Next by Date: after upgrade 11.0 -> 11.1, in KDE3 control center, the screensaver list is empty
- Previous by thread: Re: Port forwarding without a hardware router.
- Next by thread: Warning for multi-disk/multi-boot users
- Index(es):
Relevant Pages
|
Loading
