Track Internet disconnections, provider outages with historical data, and automated speed testing.
For Windows, Linux, ARM64, ARMa7. Learn more by visiting www.outagesio.com
Notice: If you created an account on app.outagesio.com, simply use the same credentials to log in here.
Setting Static IP on Hardware Agent
-
I'm looking at switching from the software agents to hardware agents, but want to know if it's possible to assign a static IP to them so I can give them a public static IP and have it sit outside of our firewall to monitor one of our ISPs. Do you lock down the Linux terminal, or provide root credentials for it? - Thanks!
-
I'm looking at switching from the software agents to hardware agents, but want to know if it's possible to assign a static IP to them so I can give them a public static IP and have it sit outside of our firewall to monitor one of our ISPs. Do you lock down the Linux terminal, or provide root credentials for it? - Thanks!
Hi,
If you access the dashboard of your software agent you have a menu option named "Available packages" where you can buy an hardware agent (you will be redirected to the main site to do so)
We don't provide credentials for HW agents but you can use DDNS which is free for both SW and HW agent and eventually can help
Another way, if you have an internal DHCP, is to reserve a local IP and then associate that local IP to the public IP you want
Hope this helps
-
I'm looking at switching from the software agents to hardware agents, but want to know if it's possible to assign a static IP to them so I can give them a public static IP and have it sit outside of our firewall to monitor one of our ISPs. Do you lock down the Linux terminal, or provide root credentials for it? - Thanks!
-
Thanks for the quick response! I think I'll try to give the Raspberry Pi or other custom Linux distro option another shot, since it would help me situate these probes upstream of the firewall.
If they were downstream of the firewall, I could set them up with DHCP, but then would need to set up custom routing rules to keep them on respective ISPs ie: WAN-A vs WAN-B ... so we can monitor redundant connections independently. -
I'm looking at switching from the software agents to hardware agents, but want to know if it's possible to assign a static IP to them so I can give them a public static IP and have it sit outside of our firewall to monitor one of our ISPs. Do you lock down the Linux terminal, or provide root credentials for it? - Thanks!
Hi,
Just one thing to keep in mind. These agents are not security hardened, they act as simple LAN side clients and have little security.
That said, there are only two ports open on them. One is used for emergency purposes by our team and the other is for the DNS server that is built into the agent for DNS redundancy.
Based on that, you can decide if it would matter or not if someone got into the device but it's unlikely.
-
So how is it going? Did you figure it out?
