I just want to know how they got there, when I pinged the address, the local address turned into an AT&T address.
When an attempt is made to ping those local IP addresses that are on a different subnet, the following happens:
It makes no sense to me, as I'm able to ping a local network on a different subnet, let it's showing up as SNMP traffic. Not only that, when pinged the network resolves the 18.104.22.168 and 22.214.171.124 as its actual IP address (both of which are public class A IP addresses belonging to AT&T): http://www.whois.com/whois/126.96.36.199 and http://www.whois.com/whois/188.8.131.52
Anyone know why I'm seeing this Local network traffic? It shouldn't be there I believe.
asked 12 Oct '14, 15:12
I'd say Graham's answer about the pings is right: when you ping something not in your subnet then it goes out your default router to AT&T's network which sends you back an ICMP saying you can't get to that subnet (through AT&T).
For the SNMP requests whatever the 192.168.10.11 device is, it seems to have that 192.168.1.112 destination programmed into it. Presumably it's not actually succeeding in talking to it since you can't ping it either (and, if this is a home installation with only one subnet, presumably it's not actually something you should be able to reach).
If you're worried about the SNMP requests go find whatever 192.168.10.11 is and try to find some configuration item about 192.168.1.112. Or just unplug the thing. ;-)
answered 20 Oct '14, 03:36