[TriLUG] Return of BZFlag

[Ben Pitzer]

Yeah, how about finding out if the SC has (wisely) turned off ICMP
echo on the server?

-Ben


On 6/7/05, Randall Barlow <rpbarlow at eos.ncsu.edu> wrote:
> David McDowell wrote:
> 
> >You don't have any firewall blocking packets returning to you do you?
> >BTW, if folks are using (oh $diety I know) a winxp box for gaming,
> >you'll need to unblock BZflag in win firewall... hopefully you are all
> >using Linux or at least OS X !!!  :)
> >
> >
> Well I am working behind a router (Clark Connect Linux).  Is there a
> port that I need to forward to my PC?  This still doesn't explain why I
> can't ping the address though (and I can ping others like yahoo, etc.)
> Trace route says:
> 
> traceroute bzflag.trilug.org
> traceroute to dargo.trilug.org (64.244.27.139), 30 hops max, 40 byte packets
>  1  192.168.1.1 (192.168.1.1)  2.798 ms  2.785 ms  2.953 ms
>  2  10.43.192.1 (10.43.192.1)  13.420 ms  8.578 ms  10.050 ms
>  3  srp2-0.rlghncg-rtr1.nc.rr.com (24.25.1.99)  16.547 ms  8.626 ms
> 9.922 ms
>  4  srp4-0.rlghnca-rtr1.nc.rr.com (24.25.2.145)  20.542 ms  10.230 ms
> 12.164 ms 5  srp13-0.rlghncrdc-rtr1.nc.rr.com (66.26.33.177)  13.587 ms
> 11.738 ms  9.103 ms
>  6  son0-0-3.rlghncrdc-rtr3.nc.rr.com (24.93.64.34)  26.956 ms  10.331
> ms  30.335 ms
>  7  son0-0-1.chrlncsa-rtr6.carolina.rr.com (24.93.64.53)  19.457 ms
> 16.385 ms 15.789 ms
>  8  pop1-cha-P4-0.atdn.net (66.185.132.45)  18.527 ms  14.903 ms  16.305 ms
>  9  bb2-cha-P0-0.atdn.net (66.185.138.66)  20.946 ms  21.828 ms  17.738 ms
> 10  bb2-atm-P6-0.atdn.net (66.185.152.30)  23.024 ms  21.096 ms  19.897 ms
> 11  pop1-atm-P1-0.atdn.net (66.185.147.195)  30.180 ms  22.198 ms  21.965 ms
> 12  67.111.23.5.ptr.us.xo.net (67.111.23.5)  24.054 ms  24.261 ms  20.053 ms
> 13  p5-1-0-2.RAR2.Atlanta-GA.us.xo.net (65.106.4.9)  22.268 ms  23.195
> ms  23.108 ms
> 14  p1-0-0.RAR2.Washington-DC.us.xo.net (65.106.0.5)  33.595 ms  31.667
> ms  31.685 ms
> 15  p0-0-0.MAR2.Washington-DC.us.xo.net (65.106.3.198)  32.249 ms
> 33.028 ms  33.440 ms
> 16  ge2-0.MRR2.Durham-NC.us.xo.net (64.1.7.134)  38.001 ms  38.369 ms
> 38.520 ms17  p6-0.CHR1.Durham-NC.us.xo.net (64.1.7.150)  61.347 ms
> 63.165 ms  62.686 ms
> 18  216.1.166.50 (216.1.166.50)  47.066 ms  39.185 ms  45.459 ms
> 19  64.244.31.11 (64.244.31.11)  40.797 ms  37.511 ms  39.095 ms
> 20  * * *
> 21  * * *
> 22  * * *
> 23  * * *
> 24  * * *
> 25  * * *
> 
> And etc.  So port forwarding?  Anything else I should check?  Any ideas
> of why I can't ping?
> 
> Randy
> --
> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc
>