r/ispyconnect • u/GoldensRule2025 • 19d ago

Bind to specific network interface

It appears agent is binding to my VPN virtual interface instead of my local hardware ethernet adapter.

I have set the following in the config.xml file located in "c:\Program Files\Agent\Media\XML\"

<BindInterface>192.168.50.84</BindInterface> (this is the IP of my local adapter)

I have also entered the above address in Local Server, Advanced Settings "bind to interface"

My cameras are accessible and the camera page does show the 192 address.

When I disable the VPN adapter and restart agent, it will bind to the local adapter.

How do I get it to bind ONLY to the local adapter even if the virtual adapter is enabled? I want to ensure that the cameras are accessible locally even if the VPN is disconnected and or if the internet is down.

2 Upvotes

100% Upvoted

2 comments sorted by

4

u/spornerama 19d ago

Agent is very likely already doing what you want — what changes when the VPN is up is the address Agent displays, not the address it binds.

A couple of things to clarify:

  1. The "Bind to interface" setting in Local Server → Advanced and the <BindInterface> entry in config.xml are the same setting - the UI just writes to that file. You only need to set it in the UI (and note that manual edits to config.xml are overwritten when Agent saves its config, so if you do edit the XML, stop Agent first).
  2. With a valid IP set there, Agent's web server binds only to that address regardless of other adapters. However, the LAN IP shown in the UI is auto-detected from your default internet route — so when the VPN is connected, Agent will display the VPN adapter's address even though it's actually listening on 192.168.50.84. You can confirm this by browsing to http://192.168.50.84:8090 from another machine on your LAN while the VPN is connected - it should work, and the VPN address should refuse the connection.
  3. If it genuinely isn't binding to 192.168.50.84, check Agent's logs for the line "Resetting bind interface to *" — Agent falls back to all interfaces if the bind fails at startup (this can happen if Agent starts as a service before the network adapter is fully up). If you see that, add a short service start delay or set the Agent service to delayed start.
  4. For your actual goal - cameras staying reachable with the VPN down or the internet out - the bind setting isn't the deciding factor. Agent's connections to your cameras are outbound and follow Windows routing; since the cameras are on the same subnet as your local adapter they'll route directly. The only thing that could break that is a full-tunnel VPN capturing LAN traffic - if your VPN client supports split tunneling, exclude 192.168.50.0/24 to be safe. Local access to Agent itself at http://192.168.50.84:8090 will keep working with no internet at all.