Information and Support

Stephan, can you access to this forum's chat ?
I am writing there ...

Yes sure

10am EST tomorrow could be ok for you ?

Sure, just let me know a convenient time for you

Let me know when you are back tomorrow and we try to continue from here or better from the chat

Did you leave also the wired connection or just removed it ???

From here we can see that the agent is stopping the wired and activating the wireless, just wondering if something else is happening at your site.
I thought the wireless provider was different from the wired, but just my assumption

It is strange, I see the same IP address both with wired and wifi connection
Can you confirm it is this way ???

This is the IP that the agents gets when in wireless mode

Can you please manually power cycle the agent so I can debug the communication from here ?

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."

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?