Attention TWTA members

[Jator]

I had 7301 blocks come through my pproxy today that were nobody@64.157.79.166

The other particpants to submit under that Ip were TWTA and celtech@lycosmail.com.

Jay

 

[Possessed Freak]

speaking of twta stuff, I recently (been 3 weeks now) assimilated 3 PC's at work and I wanted to know if they are hitting the round robin okay,

I sent them to the proxy80 rr, and they are from a PSU hostname... somewhere in the 146.186.something ip range.

 

[RaySun2Be]

Anyone from Weehawken? Or on a Level3.net provider? Here's more information:

Doing a "ping -a 64.157.79.166" resulted in:

dialup-64.157.79.166.Dial1.Weehawken1.Level3.net


Tracing route to dialup-64.157.79.166.Dial1.Weehawken1.Level3.net [64.157.79.166]

over a maximum of 30 hops:
6 70 ms 40 ms 50 ms 12.125.143.61
7 60 ms 60 ms 50 ms gbr1-p50.cgcil.ip.att.net [12.123.5.74]
8 50 ms 50 ms 50 ms gbr4-p00.cgcil.ip.att.net [12.122.5.218]
9 50 ms 50 ms 41 ms ggr1-p370.cgcil.ip.att.net [12.123.5.149]
10 60 ms 50 ms 60 ms pos6-0.core1.Chicago1.Level3.net [209.0.225.9]
11 61 ms 50 ms 50 ms so-4-0-0.mp2.Chicago1.level3.net [209.247.10.169]
12 100 ms 70 ms 70 ms so-3-0-0.mp1.Weehawken1.level3.net [209.247.8.1]
13 80 ms * 100 ms loopback0.core1.Weehawken1.Level3.net [209.247.2.1]
14 * * * Request timed out.



Trace complete.

Get those cows a valid IP addy quick! A CPU cycle is a terrible thing to waste! :Q

 

[RaySun2Be]

bump^

Has this been taken care of? Hate to see anyone loose blocks! :Q

 

[BGod]

Jay, Could it have had something to do with my previous post?

I had some more info from a reverse look up I did on the Eons Network in my previous post.

 

[Jay]

BGod,

Yes, this is the same issue. I didn't even see your post. Sorry.

Jay