[NAT] Publishing internal HTTPS server

I have an internal webserver, serving on HTTPS/443. I'd like to publish this server to the outside world. To accomplish this, I have bound a second external IP-address to my Astaro box (Network - Interfaces - Additional Addresses).

Now I'd like to do the following:
Any request on HTTPS/443 on the external IP-address should be redirected to my internal server (10.10.10.31). My guess would be, that I need to make use of a DNAT Rule (Network Security - NAT - DNAT/SNAT):

Traffic Source: Any
Traffic Service: HTTPS
Traffic Destination: External IP-Address
NAT Mode: DNAT
Destination: Internal IP-Address
Destination Service: HTTPS

Even after a reboot of the Astaro box, this still does not work. Can any of you help me out?

0 ReD-MaN over 17 years ago

Did you create a packet filter rule allowing the https traffic to the internal ip?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jainoxi over 17 years ago in reply to ReD-MaN

I have created a Packet Filter rule:
Source: External Address
Service: HTTPS
Destination: Internal Address
Action: Allow

-----
EDIT: In my Packet Filter Live Log, I see:
12:38:12 Default DROP TCP 62.131.***.***:21080 → 10.10.10.31:443 ([SYN], len=48, ttl=119, tos=0x00, srcmac=00:01:71:0c:xx:xx, dstmac=00:0c:29:84:xx:xx)

This would mean that the packetfilter is not setup correctly?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jainoxi over 17 years ago in reply to jainoxi

I took a better look at the Packet Filter Live Log, and concluded that my initial Packet Filter rule wasn't correct. Offcourse there isn't any request from the External IP to the Internal IP, but from 'any' to the Internal IP. I changed the Packet Filter rule to:

Source: Any
Service: HTTPS
Destination: Internal Address
Action: Allow

Now it works as expected! Thanks for the nudge in the right direction [:)]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel