Information and Support

https://www.outagesio.com/product/agent-with-2-5gbps-port/
In the link above I found this reference about the extra features: "Note that at this time, extra features such as camera/snapshots, built-in DNS server, Remote Access Service and Wireless monitoring are not available on this model. These features will be automatically rolled out to this agent in the future."
I know we are working to deliver all the functionalities also to this model but at the moment I have no ETA for it.

MT-300-V2 models have the ability to switch between wired and wireless connectivity and also to act as an access point.

When you refer to "the ability to monitor wifi networks" are you referring to something like this?

I am still checking on this since technically the code running in the MT-300 is very similar to the one running on the MT-3000 but, as far as I can see, the wireless feature has not been enabled on this new model.
The main plus of the MT-3000 is that it has a GBit interface.
Please give me one more day to come back to you with a definitive answer.

As far as I can see, IDs 131162 and 131163 are MT-300N-V2 (3 hundreds), while the 131166 is an MT-3000 (3 thousands), and for what I know, the code to manage the wireless has only been enabled for model 300 and not 3000.
Again, not 100% sure of it, still checking it...

Hi Stephan,
Gimme few minutes and I will check your setup

If the agent you are referring to is the 131152, all is fine but the other three (131099, 131106, 131151) they are not communicating properly since hops are not coming in for them

I have made a tiny change in the logic
Please let me know if the following outages are correctly identified
The hops looks better now for both agents

Let me analyze the logic for this
I will get back to you as soon as I have an answer

Jina, the problem is that the 131124 is connected in a totally different way that the 131123.
Can you please explain the difference since I can see that we are able to determine that the 192.168.x.x is the network belonging to your LAN but not for 131124.

Any firewall settings in your windows PC?

This is because your agent is not sending hops and this is due to blocked ICMP, which is weird since Pings are coming in

Your agent seems to be OK
Can you confirm all is fine?

I did it but I bet it is incorrect
Let it run this way we will check it at your first outage

We can change it back, it is a function we would like to give to users but not yet

There it is, let's see if this reflect better your installation

I forced the IP 10.x.x.195 to be the provider hop for both agents
I will try to force the next hops retrieval in few minutes so we can check it together

I would suggest you take a look at the historical hops to understand why the system is assigning the outage to the internal (i.e. LAN) network.
The two devices are connected in different way to the router
My question is the 10.x.x.x network is the one of the provider router or is it still in your network?

Let me take a look

Refunding should be on its way

I just removed the two agents, 131116 and 131117

Administration is taking care of the refunding

I saw you were removing 131116, good

My suggestion is to buy two new subscription for the new devices and I will take care to ask for refunding what you already paid for 131117.

This way every single agent is associate to the correct subscription.

Just let me know if I can proceed to the refunding

About changing the nickname just refer to this image to configure it