Access cameras from 2nd site [SOLVED]



  • @mikedn

    I’m working (next week) on adding support for another user to allow them to override their DNS hostname with their own custom DNS. Of course this means that they will also have to obtain their own SSL certificate but that puts the entire public IP, DNS, SSL stuff in control by the user. Do you have any interest in that route?

    Thanks, Robert



  • probably more work than I’m looking for. I have a small routine in /etc/rc.local

    IP=ifconfig enp3s0 | grep inet | awk '{print $2}'
    echo rtsp.register.host=$IP > /etc/monocle/monocle.properties
    /usr/local/bin/monocle-gateway

    to handle the situation. granted, if my dhcp lease changes between reboots, I have an issue, but I’ve never seen that happen in the 10 years I’ve had Comcast as my ISP.



  • @mikedn

    We can probably add some keyword/identifier to allow the system to auto-detect your public IP address. At a minimum it could detect this each time the monocle gateway reconnects. If we got more sophisticated it could run a check several times a day to auto-detect IP changes. I’ll look into this further this week.

    Thanks, Robert



  • @mikedn

    I have added this new function to try/test out.
    In your monocle.properties file, change the rtsp.register.host property to @PUBLIC_IP

    #--------------------------------------
    # RTSP SERVICE REGISTRATION OVERRIDES
    #--------------------------------------
    #rtsp.register.fqdn=
    rtsp.register.host=@PUBLIC_IP
    #rtsp.register.port=443
    

    Next, restart Monocle Gateway and look for the block that shows something like this and see if the HOST shows your correct public IP address.

    -------------------------------------------------
    MONOCLE RTSP SERVICE - INITIALIZED
    -------------------------------------------------
    FQDN = f065fdn6-2e66-433d-axa8-6g3aau7132aae.mproxy.io
    HOST = 10.1.1.56
    PORT = 443
    -------------------------------------------------
    

    This still only works on a gateway reconnect, but could eliminate your scripting step to get the IP directly from the network interface which may not work for some users who are behind other network layers/routers.

    Thanks, Robert



  • @mikedn

    … on second thought …
    This may be sufficient because its unlikely to get a new public IP from the ISP’s DHCP server if your connection is active. This typically only happens if your Internet connection is down for some time or if you are replacing the modem/gateway/hardware/etc. So this would result in a reconnect anyways. So this may solve all the public IP address issues/workflow needed.

    With @PUBLIC_IP identifier in place we will re-evaluate the client endpoint connected to our servers and extract the public IP address and update the DNS record on our end each and every time the monocle gateway reconnects.

    Thanks, Robert



  • @Monocle said in Access cameras from 2nd site [SOLVED]:

    @PUBLIC_IP

    Works for me, haven’t had an IP refresh happen but when i do i will let you know if there are issues, probably an 8 hour check / refresh routine would be smart but not critical



  • @skarragallagher

    Does your IP change regularly and transparently … meaning no downtime on the connection?

    Thanks, Robert



  • able to access the camera now from work. Thanks for all the help! Popping a donation over now for this great service!



  • @mikedn

    FYI, if you are exposing your monocle gateway (port 443) to the Internet, you may want to have a look at this thread:

    We have added additional security in the form of authenticated requests to the monocle gateway for users who want/need to expose the service to the Internet.
    This experimental version will significantly enhance the security for incoming requests to the Monocle Gateway.

    Thanks, Robert



  • @Monocle Thanks for the heads up. I’ll take a look.


Log in to reply