this post was submitted on 13 Nov 2023
1 points (100.0% liked)
Home Networking
198 readers
1 users here now
A community to help people learn, install, set up or troubleshoot their home network equipment and solutions.
Rules
- Please stay on topic.
- Please use the search function to look for keywords related to what you want to ask before posting since most common issues have been answered.
- No Ads. This community is for support and discussion. Ads and self promotion are not welcome here.
- No product reviews or announcements. If you have a question about a product, be specific about what you want to know.
- Be civil. Don't be a jerk. Not being a jerk is surprisingly easy.
- No URL shorteners. URL shorteners tend to hide the real use of a link. For this reason, please use normal links, even if they're long.
- No affiliate links.
- No gatekeeping. With profession shall come professionalism. Extend help without judging others for their ignorance. The same goes for downvoting of comments or posts for "stupid questions" or not being as knowledgeable as others.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Go in your windows computer and type in 'netstat'. Every router on the traceroute can see the connections.
Found the Indian tech support scammer :p
I'm not wrong.
Netstat shows locally established/awaiting connections to the LAN and WAN. Traceroute is a completely different utility that shows a path traffic takes to get out to a specific address. You are wrong.
The one thing that almost makes sense in your incoherent comment is that the gateway device (typically an isp supplied modem/router) identified from a tracert command is that which an engineer could potentially observe internal clients' traffic on.