CDCC not working.

Karl Kopp kkopp@wdg.com.au
Tue May 13 05:29:34 UTC 2003


OK, I've made a slight modification to the 
access lists regarding UDP in to the network. 
But this should not affect ccdc as it tries to 
connect out from the network?!? Can u see my 
attempts on the DCC servers? 

Cheers - Kolchak 

> -----Original Message-----
> From: Vernon Schryver [mailto:vjs@calcite.rhyolite.com] 
> Sent: Tuesday, 13 May 2003 3:16 PM
> To: dcc@rhyolite.com; kkopp@wdg.com.au
> Subject: RE: CDCC not working.
> 
> 
> > From: "Karl Kopp" <kkopp@wdg.com.au>
> 
> > ...
> > > If you have access to a distant system, it might be interesting to
> > > try `traceroute -p 6265` or some other number less than 6277 that
> > > will be 6277 when it reaches the box with the problem.
> > ...
> 
> I meant to suggest running traceroute on the distant system to see
> how your system looks from outside.
> 
> 
> I see this from here:
> 
> % traceroute -q1 -p6261 203.94.164.232
> traceroute to 203.94.164.232 (203.94.164.232) from 
> calcite.rhyolite.com (192.188.61.3), 40 hops max, 40 byte packets
>  
> 13  sla-uecop-6-0.sprintlink.net (203.222.35.230)  699.435 ms
> 14  et-12-2.que31-cb1.vic.uecomm.net.au (203.94.128.42)  504.639 ms
> 15  webdevel-gw1.vic.uecomm.net.au (203.94.135.86)  527.725 ms !X
> 
> I see the same for base port 6260 through 6263, one of which ought
> be delivering a UDP packet to port 6277 at 15 hops away.
> 
> That "!X" as well says that webdevel-gw1.vic.uecomm.net.au 
> (203.94.135.86)
> responded with an ICMP host or net administrateively prohibited.
> It might be good to check the access control lists on 203.94.135.86.
> 
> 
> Vernon Schryver    vjs@rhyolite.com
> 




More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.