[TriLUG] accessing mail.trilug.org, port 993

[Jon Carnes]

Couple of possibilities come to mind:
 1) He's being filtered out at Inflows firewalling. (possible virus
problem in the past...)
 2) mail.trilug.org has a route or filter on it that is sending his
packets wide of where they should be...

Well I can check on 2 (as can anyone with Trilug shell access)...
Yep, there is a route there that is making his packets land wide of the
mark:
64.244.27.128   0.0.0.0    255.255.255.240 U    0 0     0 eth0

Well I can look at it, but I can't correct it.  I leave that up to the
folks on the SC.

Jon


On Wed, 2004-12-29 at 14:23, Alan Porter wrote:
> AJ> MTA was mentioned before, but given that you can't even make a
> AJ> SYN / ACK pair, it's not the MTA, as MTA problems only affect
> AJ> large packet transfers.
> 
> If I establish an ssh tunnel through dargo (as mentioned in a
> previous email), Thunderbird works fine.  Otherwise, I could not
> have posted from home last night!
> 
> 
> AJ> Can you traceroute to dargo.trilug.org, and provide the output,
> AJ> please?
> 
> # traceroute -I dargo.trilug.org
> traceroute to dargo.trilug.org (64.244.27.139), 30 hops max, 38 byte packets
>   1  funky.kr4jb.dyndns.org (172.31.1.1)  4.568 ms  4.014 ms  3.688 ms
>   2  68.216.218.60 (68.216.218.60)  16.000 ms  12.682 ms  65.026 ms
>   3  68.216.218.1 (68.216.218.1)  25.184 ms  16.193 ms  26.190 ms
>   4  205.152.181.25 (205.152.181.25)  16.703 ms  27.834 ms  13.069 ms
>   5  axr00asm-7-1-0-0.bellsouth.net (65.83.237.36)  179.154 ms  30.905 ms  31.930 ms
>   6  pxr00asm-0-0-0.bellsouth.net (65.83.236.0)  120.592 ms  143.204 ms  49.388 ms
>   7  0.so-0-0-0.GW13.ATL5.ALTER.NET (157.130.73.97)  30.891 ms  31.270 ms  31.025 ms
>   8  0.so-4-3-0.XL1.ATL5.ALTER.NET (152.63.84.106)  139.393 ms  31.405 ms  30.113 ms
>   9  0.so-0-0-0.TL1.ATL5.ALTER.NET (152.63.10.102)  29.925 ms  74.618 ms  47.177 ms
> 10  0.so-4-0-0.TL1.DCA6.ALTER.NET (152.63.38.61)  52.859 ms  45.860 ms  130.638 ms
> 11  0.so-7-0-0.CL1.RDU1.ALTER.NET (152.63.0.77)  58.758 ms  58.358 ms  57.889 ms
> 12  123.ATM7-0.GW5.RDU1.ALTER.NET (152.63.35.177)  61.496 ms  63.290 ms  84.991 ms
> 13  inflowdurham-gw.customer.alter.net (157.130.40.198)  140.582 ms  57.528 ms  138.270 ms
> 14  64.244.31.11 (64.244.31.11)  59.492 ms  145.285 ms  60.088 ms
> 15  dargo.trilug.org (64.244.27.139)  60.756 ms  70.711 ms  58.827 ms
> 
> # traceroute -I mail.trilug.org
> traceroute to mail.trilug.org (64.244.27.141), 30 hops max, 38 byte packets
>   1  funky.kr4jb.dyndns.org (172.31.1.1)  98.614 ms  4.526 ms  3.970 ms
>   2  68.216.218.60 (68.216.218.60)  17.987 ms  13.930 ms  145.045 ms
>   3  68.216.218.1 (68.216.218.1)  35.566 ms  15.919 ms  13.931 ms
>   4  205.152.181.25 (205.152.181.25)  89.300 ms  16.267 ms  121.978 ms
>   5  axr00asm-7-1-0-0.bellsouth.net (65.83.237.36)  31.010 ms  29.900 ms  30.133 ms
>   6  pxr00asm-2-0-0.bellsouth.net (65.83.236.2)  29.787 ms  123.145 ms  33.425 ms
>   7  0.so-0-0-0.GW13.ATL5.ALTER.NET (157.130.73.97)  39.543 ms  31.515 ms  57.699 ms
>   8  0.so-4-3-0.XL1.ATL5.ALTER.NET (152.63.84.106)  97.994 ms  48.689 ms  35.145 ms
>   9  0.so-0-0-0.TL1.ATL5.ALTER.NET (152.63.10.102)  30.947 ms  31.691 ms  48.863 ms
> 10  0.so-4-0-0.TL1.DCA6.ALTER.NET (152.63.38.61)  96.256 ms  48.350 ms  44.605 ms
> 11  0.so-7-0-0.CL1.RDU1.ALTER.NET (152.63.0.77)  56.732 ms  142.849 ms  57.060 ms
> 12  123.ATM7-0.GW5.RDU1.ALTER.NET (152.63.35.177)  78.138 ms  60.510 ms  71.543 ms
> 13  inflowdurham-gw.customer.alter.net (157.130.40.198)  59.194 ms  192.479 ms  153.027 ms
> 14  64.244.31.11 (64.244.31.11)  58.531 ms  58.157 ms  147.323 ms
> 15  * * *
> 16  * * *
> 
> 
> BD> It looks like you are on Bellsouth.net service?  BS blocks
> BD> access to port 25, so trying to telnet to that port will hang.
> 
> Actually, Bellsouth only blocks *some* customers.  We use BS DSL
> at work and at home, and I have never seen port 25 blocked.  But
> I have a friend with BS DSL "extreme" and his is blocked.  I
> suspect that they block either:
> 
>   - everyone who uses DSL extreme
>   - IP's that have given them trouble in the past
> 
> Still, the issue is not port 25.  It's routing to the mail server.
> 
> 
> Alan
>