Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 940 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HTTPS-Webseite über VPN/umgeleitete Adresse erreichbar machen

fromthenorth

Hallo zusammen,

 

ich möchte über eine etablierte Site-To-Site Verbindung zu einem Nicht Sophos-Gerät eine interne Webseite (HTTPS) aufrufbar machen.
Dies funktioniert auch direkt über Firewall-Regeln direkt auf den Webserver.

Ziel ist https://192.168.50.250 (intern). Extern soll die Seite über https://10.10.50.250 (Partner, VPN-Strecke) erreichbar gemacht werden.

Ich habe es per NAT- und Firewall-Regeln versucht, jedoch bisher ohne Erfolg. Ist hier ein Sprungserver nötig?

HTTPS sowie PING soll möglich sein.

 

Netz A (eigenes Netz)

Netzwerk 192.168.50.0
GW: 192.168.50.1
Webserver: 192.168.50.250


Netz B (Partner Netz)

Netzwerk 172.16.18.0
GW: 172.16.18.0



This thread was automatically locked due to age.
Parents
  • 0

    Hallo ftn,

    (Sorry, my German-speaking brain isn't creating thoughts at the moment. [:(])

    Have you tried a Full NAT instead of a DNAT?  Note that the "All" Service only includes TCP and UDP, so Ping and other protocols must be added to the Services Group in your NAT rule.

    I know you know the following, but I want to alert others that see this in the future: be sure you don't violate #3, #4 or #5 in Rulz when configuring this solution.

    MfG - Bob (Bitte auf Deutsch weiterhin.)

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0

    Hallo ftn,

    (Sorry, my German-speaking brain isn't creating thoughts at the moment. [:(])

    Have you tried a Full NAT instead of a DNAT?  Note that the "All" Service only includes TCP and UDP, so Ping and other protocols must be added to the Services Group in your NAT rule.

    I know you know the following, but I want to alert others that see this in the future: be sure you don't violate #3, #4 or #5 in Rulz when configuring this solution.

    MfG - Bob (Bitte auf Deutsch weiterhin.)

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data
Unfiltered HTML