On Sat, 22 Sep 2012, wes wrote: > ... see if your distro's package repository includes a utility named > tcptraceroute, which will more closely resemble the real traffic your web > browser generates and be more likely to represent the path that traffic > takes.
Wes, There's only /usr/doc/traceroute-2.0.14/wrappers/tcptraceroute which is a shell wrapper. Slackbuilds.org does not have a package for tcptraceroute. > 12.122.81.137 is also an AT&T IP, so there's no real useful data here. > this would be more useful if compared to a traceroute from a working > machine. if you provided the bank's URL, more of us could try it and see > how our results compare to yours. I'm sure it will work for others: https://www.key.com/ > in my experience AT&T is very unlikely to respond. you may also try > contacting your ISP's support. also unlikely to help. Well, it worked until yesterday afternoon. > one other possible idea would be to proxy your traffic through somewhere > else. there are many anonymizing proxies available out there. the downside > of this approach is that the owners of such proxies would then be privy to > your banking info. if you know how, you can proxy through your own server > if you have one. I have a virtual server at SliceHost and use it for this > purpose when needed. A long time ago I had a proxy set up here; don't know if it's still there. If so, probably well out of date. Thanks, Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
