[server-admins] routes

Peter von Kaehne refdoc at gmx.net
Tue Apr 27 00:23:50 MST 2010


Troy A. Griffitts wrote:
> Could you please confirm that there are no longer any blocks banned from
> accessing our server?

I would think there are huge swathes still banned.

Peter
> 
> 
> 
> 
> Extreme Internet Support wrote:
>> We were having issues with, for the most part, with ALL of Africa. I
>> banned several netblocks to prevent them from their continued
>> hacking/spamming attacks.
>>
>> I removed the one for .zw and now those should resolve.
>>
>> Thank you for writing us here at Extreme Internet Technical Support, and
>> please let us know if we may be of assistance to you in the future by
>> contacting us at the different options listed below...
>>
>> We want to hear from you!
>>
>> Extreme Support
>>                                           \\  - -  //
>>                                            (  0 0  )
>> -----------------------------------------oOOo-(_)-oOOo----------
>>   Extreme Internet                            / \
>>   Technical Support
>>   8655 East Via de Ventura G-181               o
>>   Scottsdale, Arizona 85258-3321               o
>>   Phone : (480) 368-4638  Opt #1               o
>>   Fax   : (480) 368-4637
>>   E-mail: support at extremezone.com
>>   Web   : www.extremezone.com
>>
>>   Technical Support Hours:
>>   Monday-Friday 9:00am to 5:30pm
>>   Sat-Sun/Holidays 10:00am to 6:00pm
>>  --------------------------------------------------Ooo-----------
>>                                           ooO    (   )
>>                                          (   )    ) /
>>                                           \ (    (_/
>>                                            \_)
>>
>> On Mon, 26 Apr 2010, Troy A. Griffitts wrote:
>>
>>> Dear Support at Extreme Internet,
>>>
>>> Within the past few weeks CrossWire.org has seen routing problems from
>>> various parts of the world.  We've had problems reported from Mexico,
>>> Brazil, and Africa / Zimbabwe among others.  Below is a traceroute from
>>> our server to IPs which are reporting problems, and one from the IP to
>>> our server.  Any help would be appreciated.
>>>
>>>
>>>
>>> Traceroute away from crosswire.org toward any of the addresses in
>>> question dies, not on crosswire.org itself, but 2 hops away:
>>>
>>> [charcoal at www ~]$ traceroute 196.215.26.11
>>> traceroute to 196.215.26.11 (196.215.26.11), 30 hops max, 60 byte packets
>>> 1  ip-140-154-249.phx.extremezone.com (64.140.154.249)  2.332 ms  2.748
>>> ms  3.204 ms
>>> 2  fe1-0-0.phx.extremezone.com (208.129.255.1)  1.432 ms  1.426 ms
>>> 1.382 ms
>>> 3  * * *
>>> 4  * * *
>>> 5  * * *
>>>
>>> -------------------------------------------------------------------------------
>>>
>>>
>>> [scribe at www ~]$ traceroute 196.201.23.53
>>> traceroute to 196.201.23.53 (196.201.23.53), 30 hops max, 60 byte packets
>>> 1  ip-140-154-249.phx.extremezone.com (64.140.154.249)  1.638 ms  2.048
>>> ms  2.529 ms
>>> 2  fe1-0-0.phx.extremezone.com (208.129.255.1)  1.536 ms  1.521 ms
>>> 1.497 ms
>>> 3  * * *
>>> 4  * * *
>>> 5  * * *
>>>
>>> -------------------------------------------------------------------------------
>>>
>>>
>>> teus at 2530p:~$ tracepath www.crosswire.org
>>> 1:  2530p.local (192.168.0.1)                              0.271ms pmtu
>>> 1500
>>> 1:  192.168.0.8 (192.168.0.8)                              5.689ms
>>> 1:  192.168.0.8 (192.168.0.8)                              2.449ms
>>> 2:  10.2.4.1 (10.2.4.1)                                   14.829ms
>>> 3:  192.168.221.2 (192.168.221.2)                         48.459ms
>>> 4:  transmedia-byo-transit-gateway.zol.co.zw (196.201.23.53) 140.769ms
>>> 5:  transit-mercury-bulgaria.zol.co.zw (196.201.1.181)   145.678ms
>>> 6:  earth.zol.co.zw (196.201.1.113)                       96.517ms
>>> 7:  pt-btc.zol.co.zw (196.201.1.234)                      94.104ms
>>> 8:  41.78.76.145 (41.78.76.145)                          190.166ms
>>> 9:  168.167.255.69 (168.167.255.69)                       92.135ms
>>> 10:  bw-gbe-msu1-pr2.btc.net.bw (168.167.253.12)           87.636ms
>>> 11:  168.167.255.73 (168.167.255.73)                      448.305ms
>>> 12:  166.49.170.45 (166.49.170.45)                        383.748ms
>>> asymm 20
>>> 13:  166-49-135-229.eu.bt.net (166.49.135.229)            401.982ms
>>> asymm 19
>>> 14:  t2c1-p9-2.uk-eal.eu.bt.net (166.49.195.202)          523.328ms
>>> asymm 19
>>> 15:  t2c1-p5-0-0.us-ash.eu.bt.net (166.49.164.65)         521.726ms
>>> asymm 20
>>> 16:  166-49-151-134.eu.bt.net (166.49.151.134)            443.469ms
>>> asymm 19
>>> 17:  phx-core-02.inet.qwest.net (67.14.32.162)            477.319ms
>>> asymm 22
>>> 18:  phx-edge-10.inet.qwest.net (205.171.129.38)          491.561ms
>>> asymm 22
>>> 19:  no reply
>>> 20:  no reply
>>> 21:  no reply
>>> 22:  no reply
>>> 23:  no reply
>>> 24:  no reply
>>> 25:  no reply
>>> 26:  no reply
>>> 27:  no reply
>>> 28:  no reply
>>> 29:  no reply
>>> 30:  no reply
>>> 31:  no reply
>>>     Too many hops: pmtu 1500
>>>     Resume: pmtu 1500
>>>
>>>
>>>
>>>
>>>> If there's a firewall with a bias against South Africa, it's in the
>>>> middle of, or perhaps at the edge of, extremezone.com.
>>>>
>>>> _______________________________________________
>>>> server-admins mailing list
>>>> server-admins at crosswire.org
>>>> http://www.crosswire.org/mailman/listinfo/server-admins
> 
> 
> _______________________________________________
> server-admins mailing list
> server-admins at crosswire.org
> http://www.crosswire.org/mailman/listinfo/server-admins




More information about the server-admins mailing list