How to put an NGINX caching HTTPS reverse proxy as a “bandwidth booster” between a locked-down box and a...












0















We have a webcam aimed at our snack counter that lets folks see what's available. It outputs various resolutions over HLS and DASH via HTTPS. Our IT team was extremely concerned about the video from that camera escaping the LAN, so they locked down both the webcam and the LAN (down to the MAC address in the switches).



Unfortunately, the camera has become too popular and it keeps falling over, continuously rebooting. A caching HTTPS reverse proxy is what's needed, but IT won't let me inside the webcam box, nor will they change the LAN configuration, but they will let me put a small Linux box between the webcam and the switch. And they will also give me the TLS cert the webcam box uses.



So, I'll have 2 ports, an input to connect to the webcam box, and an output to the switch. The output port must have the same MAC and IP addresses as the input, else the traffic will never reach the LAN.



Basically, I'm trying to make an "invisible bandwidth booster".



Google tells me NGINX is the most direct way to implement a caching HTTPS reverse proxy. Unfortunately, I'm an NGINX noob.



Here's the problem: I'm looking at NGINX config examples, and they seem to use only URL-based references, where I believe I need to use the named physical interfaces.



What am I missing?










share|improve this question



























    0















    We have a webcam aimed at our snack counter that lets folks see what's available. It outputs various resolutions over HLS and DASH via HTTPS. Our IT team was extremely concerned about the video from that camera escaping the LAN, so they locked down both the webcam and the LAN (down to the MAC address in the switches).



    Unfortunately, the camera has become too popular and it keeps falling over, continuously rebooting. A caching HTTPS reverse proxy is what's needed, but IT won't let me inside the webcam box, nor will they change the LAN configuration, but they will let me put a small Linux box between the webcam and the switch. And they will also give me the TLS cert the webcam box uses.



    So, I'll have 2 ports, an input to connect to the webcam box, and an output to the switch. The output port must have the same MAC and IP addresses as the input, else the traffic will never reach the LAN.



    Basically, I'm trying to make an "invisible bandwidth booster".



    Google tells me NGINX is the most direct way to implement a caching HTTPS reverse proxy. Unfortunately, I'm an NGINX noob.



    Here's the problem: I'm looking at NGINX config examples, and they seem to use only URL-based references, where I believe I need to use the named physical interfaces.



    What am I missing?










    share|improve this question

























      0












      0








      0








      We have a webcam aimed at our snack counter that lets folks see what's available. It outputs various resolutions over HLS and DASH via HTTPS. Our IT team was extremely concerned about the video from that camera escaping the LAN, so they locked down both the webcam and the LAN (down to the MAC address in the switches).



      Unfortunately, the camera has become too popular and it keeps falling over, continuously rebooting. A caching HTTPS reverse proxy is what's needed, but IT won't let me inside the webcam box, nor will they change the LAN configuration, but they will let me put a small Linux box between the webcam and the switch. And they will also give me the TLS cert the webcam box uses.



      So, I'll have 2 ports, an input to connect to the webcam box, and an output to the switch. The output port must have the same MAC and IP addresses as the input, else the traffic will never reach the LAN.



      Basically, I'm trying to make an "invisible bandwidth booster".



      Google tells me NGINX is the most direct way to implement a caching HTTPS reverse proxy. Unfortunately, I'm an NGINX noob.



      Here's the problem: I'm looking at NGINX config examples, and they seem to use only URL-based references, where I believe I need to use the named physical interfaces.



      What am I missing?










      share|improve this question














      We have a webcam aimed at our snack counter that lets folks see what's available. It outputs various resolutions over HLS and DASH via HTTPS. Our IT team was extremely concerned about the video from that camera escaping the LAN, so they locked down both the webcam and the LAN (down to the MAC address in the switches).



      Unfortunately, the camera has become too popular and it keeps falling over, continuously rebooting. A caching HTTPS reverse proxy is what's needed, but IT won't let me inside the webcam box, nor will they change the LAN configuration, but they will let me put a small Linux box between the webcam and the switch. And they will also give me the TLS cert the webcam box uses.



      So, I'll have 2 ports, an input to connect to the webcam box, and an output to the switch. The output port must have the same MAC and IP addresses as the input, else the traffic will never reach the LAN.



      Basically, I'm trying to make an "invisible bandwidth booster".



      Google tells me NGINX is the most direct way to implement a caching HTTPS reverse proxy. Unfortunately, I'm an NGINX noob.



      Here's the problem: I'm looking at NGINX config examples, and they seem to use only URL-based references, where I believe I need to use the named physical interfaces.



      What am I missing?







      ethernet nginx-reverse-proxy






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 13 '18 at 20:42









      BobCBobC

      13




      13
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289187%2fhow-to-put-an-nginx-caching-https-reverse-proxy-as-a-bandwidth-booster-between%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289187%2fhow-to-put-an-nginx-caching-https-reverse-proxy-as-a-bandwidth-booster-between%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          這個網誌中的熱門文章

          Hercules Kyvelos

          Tangent Lines Diagram Along Smooth Curve

          Yusuf al-Mu'taman ibn Hud