On Sat, Sep 22, 2012 at 2:47 PM, Rich Shepard <[email protected]>wrote:
> 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. > *shrug* may be worth looking into. > > 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/ it works for me, and my traceroute stops in approximately the same place: 13 56 ms 54 ms 57 ms cr1.sffca.ip.att.net [12.122.86.198] 14 56 ms 54 ms 57 ms cr1.sc1ca.ip.att.net [12.122.30.121] 15 56 ms 57 ms 54 ms cr2.sc1ca.ip.att.net [12.122.30.126] 16 56 ms 54 ms 51 ms cr2.slkut.ip.att.net [12.122.30.114] 17 52 ms 69 ms 52 ms 12.122.212.1 18 * * * Request timed out. I'm on Frontier FIOS. > > 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. > most likely, it will just start working again soon. could be hours, could be days. just depends on how long it takes someone to notice the broken route and fix it. not sure what else to tell you. maybe run to the library and use one of their computers to check? or a smartphone if you have one (turn off wifi)? for some reason I imagine you to be the non-smart-phone type. :) -wes _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
