Amprgw had apparently wedged for unknown reasons; it's back up now. - Brian

On Wed, May 28, 2014 at 03:20:42PM +0000, lx1duc@laru.lu wrote:

(Please trim inclusions from previous messages) _______________________________________________ Good afternoon/morning,

I'm unable traceroute from the internet to 44.161.200.11, the trace stops at ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu (132.239.255.131).

Is anybody experiencing similar issues?

73 de Marc, LX1DUC _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net

Seems to work ok from 44.135.160.40:

[...] 17 ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu (132.239.255.131) 72.274 ms 72.252 ms 72.237 ms 18 amprgw.sysnet.ucsd.edu (169.228.66.251) 54.377 ms * 50.379 ms 19 192.168.1.149 (192.168.1.149) 90.940 ms 113.903 ms 130.138 ms 73' jerome, Vancouver, Canada

On 14-05-28 08:20 AM, lx1duc@laru.lu wrote:

Good afternoon/morning,

I'm unable traceroute from the internet to 44.161.200.11, the trace stops at ebu3b-6509-nodem-core-interconnect-vl910-bcast-255-131.ucsd.edu (132.239.255.131).

Is anybody experiencing similar issues?

73 de Marc, LX1DUC