Yeah, still timing out from here: % ping distfiles.macports.org PING rsync.macports.org (17.251.224.217): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 ^C --- rsync.macports.org ping statistics --- 4 packets transmitted, 0 packets received, 100.0% packet loss % ping packages.macports.org PING packages.macports.org (17.251.224.218): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 ^C --- packages.macports.org ping statistics --- 4 packets transmitted, 0 packets received, 100.0% packet loss
Whereas for hosts on the old vlan: % ping tennine-slave.macports.org PING tennine-slave.macports.org (17.251.224.88): 56 data bytes 64 bytes from 17.251.224.88: icmp_seq=0 ttl=51 time=191.023 ms 64 bytes from 17.251.224.88: icmp_seq=1 ttl=51 time=191.048 ms 64 bytes from 17.251.224.88: icmp_seq=2 ttl=51 time=190.153 ms My traceroutes: % traceroute distfiles.macports.org traceroute to rsync.macports.org (17.251.224.217), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 0.764 ms 0.569 ms 0.744 ms 2 * * * 3 202.7.173.17 (202.7.173.17) 27.203 ms 26.683 ms 26.390 ms 4 syd-sot-ken-crt1-ge-5-1-0.tpgi.com.au (202.7.162.173) 26.823 ms 27.561 ms 26.784 ms 5 ge5-0-5d0.cir1.seattle7-wa.us.xo.net (216.156.100.37) 170.842 ms 170.338 ms 190.400 ms 6 vb2002.rar3.sanjose-ca.us.xo.net (207.88.13.150) 201.102 ms 195.545 ms 195.612 ms 7 ae0.cir1.sanjose2-ca.us.xo.net (207.88.13.73) 188.824 ms 188.773 ms 203.992 ms 8 * * * (no response beyond this point) % traceroute packages.macports.org traceroute to packages.macports.org (17.251.224.218), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 0.751 ms 0.549 ms 0.902 ms 2 * * * 3 202.7.173.17 (202.7.173.17) 27.279 ms 26.940 ms 26.403 ms 4 syd-sot-ken-crt1-ge-5-1-0.tpgi.com.au (202.7.162.173) 26.769 ms 26.682 ms 26.796 ms 5 ge5-0-5d0.cir1.seattle7-wa.us.xo.net (216.156.100.37) 169.985 ms 171.049 ms 170.820 ms 6 vb2002.rar3.sanjose-ca.us.xo.net (207.88.13.150) 189.576 ms 192.616 ms 192.020 ms 7 ae0.cir1.sanjose2-ca.us.xo.net (207.88.13.73) 188.409 ms 188.706 ms 188.747 ms 8 * * * (again no response beyond this point) Same traceroute for the old vlan: % traceroute tennine-slave.macports.org traceroute to tennine-slave.macports.org (17.251.224.88), 64 hops max, 52 byte packets 1 10.0.0.1 (10.0.0.1) 0.957 ms 0.522 ms 0.760 ms 2 * * * 3 202.7.173.17 (202.7.173.17) 27.554 ms 31.540 ms 26.083 ms 4 syd-sot-ken-crt1-ge-5-1-0.tpgi.com.au (202.7.162.173) 26.376 ms 26.652 ms 26.811 ms 5 ge5-0-5d0.cir1.seattle7-wa.us.xo.net (216.156.100.37) 170.386 ms 170.570 ms 170.400 ms 6 vb2002.rar3.sanjose-ca.us.xo.net (207.88.13.150) 197.196 ms 191.015 ms 192.001 ms 7 ae0.cir1.sanjose2-ca.us.xo.net (207.88.13.73) 188.791 ms 188.689 ms 188.796 ms 8 * * * so I guess this may not actually be very helpful? :( - Josh On 2014-3-29 03:14 , Shreeraj Karulkar wrote: > Josh > I suppose this is not working yet? Although there is a freeze they updated > the notes that traffic is not blocked.For where it is failing is it possible > to get a traceroute output from the internet to any of the servers in > question here ? IS&T are asking for this info to troubleshoot this furthur. > > Let me know if anyone can and I’ll try to find another way to figure this > out. > Shree > > Sent from my iPhone > >> On Mar 28, 2014, at 8:30 AM, Joshua Root <j...@macports.org> wrote: >> >> Any news on this, Shree? >> >> - Josh >> >>> On 2014-3-18 06:43 , Shreeraj Karulkar wrote: >>> >>> 2) Ping issue: I have reopened the ticket which IS&T had resolved earlier. >>> <exp2://Ticket/18419273> 3/17 FireWall Rules for Mac OS Forge - ICMP . Will >>> let you know as soon as I find out. >> > _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
