Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Route from prefix dns name

    NAT
    4
    7
    1646
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      stanthewizard last edited by

      Hello

      I'd like to know if it is possible to port route inside the lan from the prefixe dns name.

      Ex:

      toto.mydnsname.com -> machine1:80
      titi.mydnsname.com -> machine2:80
      tutu.mydnsname.com -> machine3:34567

      Thanks for the help

      1 Reply Last reply Reply Quote 0
      • jimp
        jimp Rebel Alliance Developer Netgate last edited by

        You can do that but it requires an add-on package to proxy http based on the hostname, such as Varnish.
        I believe haproxy can do it also as well as the apache+mod_security package.

        Either way, it isn't possible in the base system alone because pf doesn't look that deep in the packets, it just looks at the source/destination and makes decisions that way.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • S
          stanthewizard last edited by

          ok
          I'll look into that

          1 Reply Last reply Reply Quote 0
          • S
            stanthewizard last edited by

            Apparently … Varnish canno't be used to cache Exchange (SSL OK I understand)

            1 Reply Last reply Reply Quote 0
            • J
              joako last edited by

              If you control the certificates there' s no issue to proxy the SSL. Or just run everything in IIS! /exchange is one site /toto is another site etc.

              However look at this, I'm pretty sure Exchange needs HTTP 1.1. When I use HTTP (not HTTPS) and Squid proxy the requests fail due to HTTP 1.0 being used.

              1 Reply Last reply Reply Quote 0
              • G
                Gloom last edited by

                Exchange 2003 or 2010? Two different beasts and need a slightly different approach. Also is it only the OWA you are trying to access or are you trying to run the outlook client in RPC over HTTP mode.

                Never underestimate the power of human stupidity

                1 Reply Last reply Reply Quote 0
                • J
                  joako last edited by

                  @Gloom:

                  Exchange 2003 or 2010? Two different beasts and need a slightly different approach. Also is it only the OWA you are trying to access or are you trying to run the outlook client in RPC over HTTP mode.

                  Just to use the EWS API with our own software. Solution: place exchange IP in squid proxy "bypass proxy for this IP"  box. For some reason "Bypass all private IP"  option has no effect.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post