ISP using 10. for first hops. Those are not on my local LAN.

[wpaxton3]

My ISP is using 10. addresses for the first couple of hops. Those are not on my local LAN, but oIO sees issues there as Local. Is there a way to adjust this?

[OutagesIO_Support]

Hi,

Yes, we do have a special feature that can be used to adjust where the ISP/GW begins.

By doing this, the agent can better know where your LAN ends and where your ISP/GW begins.
I think all we need to know is the hop count that should be considered the ISP/GW.

[wpaxton3]

My agent machine is directly connected to my edge router (192.168.x.1). The next 2 hops are 10.x.x.x at the ISP, then the fourth one is the routable address at the ISP. After that is beyond ISP.
How do I adjust the borders?

[OutagesIO_Support]

Do you know if the hop IPs change? If not, we can do it, if they do change, then we have to dig a little deeper.

The key is knowing what you consider to be the ISP, usually the WAN side of your router connected to the ISP or the next hop so long as it's still at your location and not in the street.

We can do this custom change based on IP but not hop yet.

[wpaxton3]

The IPs that are showing as LAN that should be ISP are 10.21.0.1, 10.5.0.1, and 10.101.1.34.

[OutagesIO_Support]

Hi, sorry, for some reason, we didn't see this reply.
Can you provide the agent ID please.

[wpaxton3]

Agent ID 130878

[OutagesIO_Support]

Thanks. I'll ask that someone look at this shortly and adjust it.

[OutagesIO_Support]

Can you check it now please or keep an eye on it to see if it's correct? We made the second hop your ISP.

[wpaxton3]

Thanks! I will keep an eye on it.

[OutagesIO_Support]

Is it better now?

[wpaxton3]

Sorry, I've been recovering from a C: drive crash. Yes, it is better now. Thank you for your help.

[OutagesIO_Support]

Great. Please keep this in mind if you add/remove agents.

Glad it's working now.