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

    Blue Iris Remote access?

    Scheduled Pinned Locked Moved NAT
    47 Posts 4 Posters 9.4k Views
    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.
    • J
      Jarhead @Elmojo
      last edited by

      @elmojo Post a screenshot of your firewall rules.

      1 Reply Last reply Reply Quote 0
      • chpalmerC
        chpalmer @Elmojo
        last edited by

        @elmojo

        Did you do a packet capture on your LAN port? You do have a NAT forwarding rule??

        The WAN firewall rule should have the BI address as the destination address..

        wanrule1.jpg

        Triggering snowflakes one by one..
        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

        E 1 Reply Last reply Reply Quote 0
        • E
          Elmojo @chpalmer
          last edited by

          @chpalmer I did, as noted in the OP, please see above for output.
          Do you mean it should be the BI LAN address for destination? That's not what the BI documentation says, but I'm willing to give it a try. Or do you mean it should be my external IP (WAN) address? That's what I have in there now, that doesn't work. My WAN for BI and for everything else is the same, it's all on the same physical network. Maybe I'm not understanding you properly, sorry. :/

          1 Reply Last reply Reply Quote 0
          • E
            Elmojo
            last edited by Elmojo

            I'm doing all this under NAT. Is that wrong? Should I just be adding a firewall rule directly? All the documentation I've found says to add the NAT entry, and let it populate the rule, but that screenshot you posted kinda looks like the rule screen....

            Does this help?
            NAT clip.jpg

            chpalmerC 2 Replies Last reply Reply Quote 0
            • chpalmerC
              chpalmer @Elmojo
              last edited by

              @elmojo

              Destination should be "WAN Address".

              Is your Blue Iris setup to use port 81 on the host computer? otherwise Redirect Target Port should be 80.

              Triggering snowflakes one by one..
              Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

              E 1 Reply Last reply Reply Quote 0
              • chpalmerC
                chpalmer @Elmojo
                last edited by

                @elmojo

                natrule.jpg

                Triggering snowflakes one by one..
                Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                1 Reply Last reply Reply Quote 0
                • E
                  Elmojo @chpalmer
                  last edited by

                  @chpalmer said in Blue Iris Remote access?:

                  Destination should be "WAN Address".
                  Is your Blue Iris setup to use port 81 on the host computer? otherwise Redirect Target Port should be 80.

                  I had it set to WAN address previously, but I changed it based on the image you posted, which didn't seem to make any difference.
                  Yes, port 81 is the correct port for BI remote access.
                  Using the settings you show in the image above, I'm back to "connection refused" when I check port 81.

                  chpalmerC 1 Reply Last reply Reply Quote 0
                  • chpalmerC
                    chpalmer @Elmojo
                    last edited by

                    @elmojo

                    Can you post a picture of you wan firewall rule?

                    Do a packet capture on the LAN side of this connection. I think you will find out that you are hitting the BI computer now.

                    Triggering snowflakes one by one..
                    Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                    E 1 Reply Last reply Reply Quote 0
                    • E
                      Elmojo @chpalmer
                      last edited by

                      @chpalmer
                      WAN rule:
                      wan rule.jpg

                      I'm not real familiar with packet captures, so it's entirely possible I'm not doing it correctly, but here's my output...
                      When I set it up as shown in the image below, then try to access the BI GUI from my phone, I get no results.
                      LAN capture.jpg
                      If I change the capture interface to WAN, I get this...
                      18:38:01.251228 IP 174.203.211.11.10057 > 174.19.24.xxx.81: tcp 0
                      18:38:01.251248 IP 174.19.24.xxx.81 > 174.203.211.11.10057: tcp 0
                      18:38:01.251565 IP 174.203.211.11.10058 > 174.19.24.xxx.81: tcp 0
                      18:38:01.251576 IP 174.19.24.xxx.81 > 174.203.211.11.10058: tcp 0
                      18:38:02.041991 IP 174.203.211.11.10060 > 174.19.24.xxx.81: tcp 0

                      The IPs with ".xxx" are my external IP. I'm not sure what the others are. I assume my phone...
                      No idea why the traffic appears to be 2-way now? It was only incoming last night.

                      J 1 Reply Last reply Reply Quote 0
                      • J
                        Jarhead @Elmojo
                        last edited by

                        @elmojo The destination should be the BI address

                        E 1 Reply Last reply Reply Quote 0
                        • E
                          Elmojo @Jarhead
                          last edited by

                          @jarhead said in Blue Iris Remote access?:

                          The destination should be the BI address

                          That IS the BI address. It's designed to be accessible via the external IP.
                          I've tried putting the LAN address in there, and it makes no difference anyway.

                          J 1 Reply Last reply Reply Quote 0
                          • J
                            Jarhead @Elmojo
                            last edited by

                            @elmojo In the rule, you have destination as wan. Should be single host, then the BI address.

                            E 1 Reply Last reply Reply Quote 0
                            • E
                              Elmojo @Jarhead
                              last edited by

                              @jarhead Please read back through the thread, we've covered this already.
                              Thanks for the input, though. :)

                              J 2 Replies Last reply Reply Quote 0
                              • J
                                Jarhead @Elmojo
                                last edited by

                                @elmojo Look at your rule. You have the destination as the wan address. You're forwarding port 81 back to the wan. It needs to forward to BI.

                                E 1 Reply Last reply Reply Quote 0
                                • J
                                  Jarhead @Elmojo
                                  last edited by Jarhead

                                  @elmojo This is what your NAT and Rule should look like. Insert your IP's and ports.
                                  NAT.jpg

                                  Rule.jpg

                                  E 1 Reply Last reply Reply Quote 0
                                  • E
                                    Elmojo @Jarhead
                                    last edited by

                                    @jarhead I've tried it that way as well, and it still just times out or refuses the connection outright, depending on if I use the WAN or LAN IP. If you scroll back through the thread, you'll see the various configs I've tried, and that none of them seem to make any difference.

                                    J 1 Reply Last reply Reply Quote 0
                                    • E
                                      Elmojo @Jarhead
                                      last edited by

                                      @jarhead See, this is how I have it set up now, which unless I've missed something obvious is the same as your example. When I try to connect from my phone (cellular), I get an immediate "connection refused".

                                      NAT rule2.jpg

                                      J 1 Reply Last reply Reply Quote 0
                                      • J
                                        Jarhead @Elmojo
                                        last edited by

                                        @elmojo You're saying you did but there's no images with it like that.
                                        The guess is you had something wrong, that's why you're here now.
                                        So why not try it again?

                                        1 Reply Last reply Reply Quote 0
                                        • J
                                          Jarhead @Elmojo
                                          last edited by

                                          @elmojo Posted when you did..

                                          The NAT is good. In the RULE you had WAN as destination. It needs to be the BI address. Can you check that it is?

                                          E 1 Reply Last reply Reply Quote 0
                                          • E
                                            Elmojo @Jarhead
                                            last edited by

                                            @jarhead So the rule is being automatically set up by the NAT. Are you saying that I need to override it and manually change it to the LAN IP of my BI server?

                                            J 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.