[2107] in athena10
Re: [Fwd: [hostmaster] Traffic to physics.unc.edu blocked from
daemon@ATHENA.MIT.EDU (Nelson Elhage)
Tue Apr 7 17:31:16 2009
Date: Tue, 7 Apr 2009 17:30:42 -0400
From: Nelson Elhage <nelhage@MIT.EDU>
To: Stephen Joyce <stephen@physics.unc.edu>
Cc: Dee Jarrell <djarrell@email.unc.edu>, linerva@mit.edu
Message-ID: <20090407213042.GD5764@mit.edu>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="tKtFalx5NIx0HZ72"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.64.0904071150500.24626@hellbender.physics.unc.edu>
--tKtFalx5NIx0HZ72
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Thanks for the reply, Stephen.
`traceroute login.physics.unc.edu' fails from Linerva because we can't
reach ns1.physics.unc.edu. to resolve it, but tracerouting 152.2.5.5
drops off after el-loco-v1627.net.unc.edu:
1 NW12-RTR-2-SIPB.MIT.EDU (18.181.0.1) 0.349 ms 0.352 ms 0.398 ms
2 EXTERNAL-RTR-2-BACKBONE.MIT.EDU (18.168.0.27) 0.354 ms 0.417 ms 0.480 ms
3 NY32-RTR-1-BACKBONE.MIT.EDU (18.168.0.34) 5.912 ms 5.976 ms 6.039 ms
4 216.24.184.101 (216.24.184.101) 7.269 ms 7.279 ms 7.265 ms
5 wash-newy-98.layer3.nlr.net (216.24.186.23) 11.822 ms 11.821 ms 11.806 ms
6 dep7600-gw2-to-nlr-dc.ncren.net (128.109.70.101) 17.257 ms 17.197 ms 17.183 ms
7 unc-manning-10G-to-dep7600-gw2.ncren.net (128.109.70.162) 18.321 ms 18.430 ms 18.510 ms
8 el-loco-v1627.net.unc.edu (152.19.255.220) 18.042 ms 17.667 ms 17.668 ms
9 * * *
(mtr, using ICMP tracing, gets the same result).
I see the same behavior for at least 152.2.5.4, 152.2.5.5, 152.2.5.15
(ns1.physics.unc.edu), 152.2.5.16 (ns6.physics.unc.edu), and 152.2.4.9
(www.panic.unc.edu).
I've attached the output of 'ssh -vvv 152.2.5.5', but it's
uninteresting.
- Nelson
On Tue, Apr 07, 2009 at 12:05:31PM -0400, Stephen Joyce wrote:
> Hi Dee,
> Thanks for the heads-up.
>
> linerva admin:
> We use software which automatically blocks abusive hosts for a number of
> days. The 3rd such block is permanent. However each physics host does
> this independently and there is no block for anything in the 18.181 range
> on several hosts I checked.
>
> If a single host cannot ping anything in our subnet, I suspect a problem
> with that host's network configuration.
>
> The output of "traceroute login.physics.unc.edu", and "ssh -vvv
> login.physics.unc.edu" from 18.181.0.51 would be beneficial to see where
> the problem lies.
>
> PS. problem@physics only accepts email from unc.edu addresses by design;
> all our users have multiple unc.edu addresses.
>
> Cheers, Stephen
> --
> Stephen Joyce
> PANIC - Physics and Astronomy Network Infrastructure and Computing
> University of North Carolina at Chapel Hill
> voice: 919.962.7214
> fax: 919.962.0480
>
> A cubicle is just a padded cell without a door.
>
> On Tue, 7 Apr 2009, Dee Jarrell wrote:
>
>>
>> FYI
>>
>>
>> --
>>
>>
--tKtFalx5NIx0HZ72
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=sshvvv
[nelhage@vinegar-pot:~]$ ssh -vvv 152.2.5.5
OpenSSH_5.1p1 Debian-5, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /mit/nelhage/.ssh/config
debug1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 152.2.5.5 [152.2.5.5] port 22.
debug1: connect to address 152.2.5.5 port 22: Connection timed out
ssh: connect to host 152.2.5.5 port 22: Connection timed out
--tKtFalx5NIx0HZ72--
