Navigation

    Home
    All Categories
    • KEEN Trail Camera
    • Top #ReolinkCaptures Awards
    • Announcements and News
    • Wishlist
    • #ReolinkTrial
    • Discussion About Products
    • Reolink Captures
    • Reolink Client & APP
    #ReolinkTrial
    Reolink Captures
    Log in to post
    Guest
    • Guest
    • Register
    • Login

    Learn More

    Reolink updates Learn More

    Meet Reolink at IFA 2024! Learn More

    Reolink Q&A Learn More

    NVR times out if connected to from a different subnet (using Site-to-Site VPN)

    Discussion About Products
    2
    2
    606
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • pierre
      user_752953242513617 last edited by

      Hey!

      I’ve already tried to talk with the support about this problem but haven’t received a helpful answer at all - so maybe someone else had this problems or generally has another idea:

      I'm currently running a RLN-410 with RLC-510A cameras connected to it. When accessing the NVRs IP Adress in the same network I can access the WebUI and their components with no issue at all.
      Now I'm using Tailscale to connect two networks. One away from home where the cameras are connected to - and my simple home network. It's a basic Site-To-Site Connection. The NVR is in the 192.168.1.0/24 network, at home the 192.168.178.0/24 subnet is utilized.
      When requesting an address from the 192.168.1.0/24 subnet it's routed through an LXC container running tailscale and routed to the external network. Same goes the other way around - just with a simple Raspberry PI.
       
      I'm totally able to SSH into the Raspberry PI functioning as the Tailscale Gateway in the network of the cameras from my home network, but can't access the NVRs WebUI, Streams, etc. It just times out. Pinging won't work either.
       
      I can't get my head around why the NVR can't be access from outside the local address range. I've tried switching a few settings, even disabled the firewall completely in router settings (tho SSHing into the Raspberry PI worked - so there is no reason why HTTP shouldn't work). Is there any particular setting I could've overlooked?
       
      The trace route to the NVR works flawlessly. Every other device can be accessed. It’s only the NVR.

      Reply Quote
      Share
      • Share this Post
      • Facebook
      • Twitter
      • copy the link
        Copied!
      0
        • joseph_1979
          Joseph Global Moderator @user_752953242513617 last edited by joseph_1979

          @pierre Are you using VPN between the sites? Do you have routers at the endpoints? Try to use 192.168.1.0/23 at both sites. Have a look at https://community.reolink.com/topic/6726/unable-to-access-reolink-ip-cams-from-different-vlan

          Reply Quote
          Share
          • Share this Post
          • Facebook
          • Twitter
          • copy the link
            Copied!
          0
          View 0 replies
        • First post
          Last post
        All Categories
        Announcements and News Reolink Client & APP Discussion About Products #ReolinkTrial Reolink Captures Wishlist KEEN Trail Camera
        Never miss Reolink hot deals, news, and updates tailored for you.

        Thanks for your subscription!

        Please enter a valid email address.

        Oops… Something went wrong. Please try again later.

        You are already subscribed to this email list. :)

        Submission failed. Please try again later.

        Reolink Store|Support|About Us|Privacy Policy|Terms and Conditions

        Copyright 2025 © Reolink All Rights Reserved.

        Welcome Back!

        Hi there! Join the Commnunity to get all the latest news, tips and more!

        Join Now