Shorewall users - May 2004 - Problems in World Client from Mdaemon

Hi,

my shorewall version = 1.4.6a

my ip addr show

1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
    link/ether 00:03:47:a5:fd:0f brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.1/24 brd 192.168.100.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc cbq qlen 100
    link/ether 00:10:5a:6d:62:d7 brd ff:ff:ff:ff:ff:ff
    inet 202.88.178.38/30 brd 202.149.202.51 scope global eth1
my ip route show

202.88.178.36/30 dev eth1  scope link
192.168.100.0/24 dev eth0  scope link
127.0.0.0/8 dev lo  scope link
default via 202.88.178.37 dev eth1

I wish to give SSL access to external users on my Shorewall box. I have only
one global IP i.e. 202.88.178.38. I have an Mdeamon webmail server running
on IP 192.168.100.29 and this server accepts secure connections on port 443
i.e. SSL. So if I go to https://192.168.100.29:443 on any machine on my LAN
I am able to get the WebMail login page. However I wish to enable the same
for external cients as well. I have tried SNat but does''nt seem to
work. I
wish that when any client on the Internet goes to https://202.88.178.38:443
then they should get the secure login page of webmail, even though the
webmail server is on an internal IP i.e. 192.168.100.29.

Thanks in advance.

Ashwin John

Support wrote:
> 
> I wish to give SSL access to external users on my Shorewall box. I have
only
> one global IP i.e. 202.88.178.38. I have an Mdeamon webmail server running
> on IP 192.168.100.29 and this server accepts secure connections on port 443
> i.e. SSL. So if I go to https://192.168.100.29:443 on any machine on my LAN
> I am able to get the WebMail login page. However I wish to enable the same
> for external cients as well. I have tried SNat but does''nt seem to
work. I
> wish that when any client on the Internet goes to https://202.88.178.38:443
> then they should get the secure login page of webmail, even though the
> webmail server is on an internal IP i.e. 192.168.100.29.
> 
This is called port forwarding -- the two-interface QuickStart guide 
tells you how to do this and it is also the subject of Shorewall FAQ #1

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net