:)
lists@xymox1.com
Wed, 1 Jan 2003 19:01:19 -0700
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >It also practically proves that the problem is some sort of packet filter or firewall that attacks either (or both) UDP packets to or from distant port 6277. << Interesting... Frustrating !... I guess I will ask my hosting company about it. However they are idiots and this will cause complete brain boilover from them. My odds of fixing this are slim to none. Man this sure is very specific filtering ! The very last line from the cdcc info command shows: localhost,- RTT-1000 ms 32768 1112443001x689 # 127.0.0.1,- localhost # not answering Is just because its looking for a local host at id 32768 and needs to be told about my dccd at ID 32112 right ? - --- HUGE sigh...... The odds of my getting this UDP thing working are slim. It might be that for whatever reason the hosting company has pulled the ping and traceroute commands from my server could well be the same reasons they have blocked UDP in the selective directions they seem to have blocked it. Well at least I wasn't quite as stupid as I thought. Man this sucks :( I will send a support request to my server hosting company ( www.interland.com ) now and ask them to confirm "They broke it".. Considering the power of dcc you would think that the largest server hosting farm company would allow it, But NooOoOOoOooOo.... I greatly appreciate the help !. If anyone has a spamtrap you want me to feed email me the address :) - -----Original Message----- From: dcc-admin@rhyolite.com [mailto:dcc-admin@rhyolite.com] On Behalf Of Vernon Schryver Sent: Wednesday, January 01, 2003 6:34 PM To: dcc@rhyolite.com Subject: RE: Newbie bewilderment IV the saga continues > From: ":\)" <lists@xymox1.com> > %cdcc "host 127.0.0.1; stats" > localhost 127.0.0.1,6277 > server-ID 32112 18:20:13 > version 1.1.17 tracing ANON CLNT > 903165 hash entries 256 used 9984 DB bytes > ... > %cdcc "host 216.122.249.51; stats" > xymox1.com 216.122.249.51,6277 > server-ID 32112 18:24:13 > version 1.1.17 tracing ANON CLNT > ... That shows that your DCC clients can talk to local DCC servers and that there is nothing noticably wrong with the installation of the clients. It also practically proves that the problem is some sort of packet filter or firewall that attacks either (or both) UDP packets to or from distant port 6277. Vernon Schryver vjs@rhyolite.com _______________________________________________ DCC mailing list DCC@rhyolite.com http://www.rhyolite.com/mailman/listinfo/dcc -----BEGIN PGP SIGNATURE----- Version: PGP 8.0 iQA/AwUBPhOdb3zhLX3UbeVTEQLIUQCgnzlHq1MCVoRN6hxR1wLt7Uc0QwgAn2Xc ohhrCqJY9ayv5VQpkFRaeNKI =1YuW -----END PGP SIGNATURE-----