Could it be done to somehow autoping users to see if they are firewalled? then if no response from the ping disconnect user? this is because some of the fakers are immune to remote commands from CDM and the only way to get rid of them is ban them in the hub software users window. I suspect they are simply firewalled in one direction on port 412. I really need a good idea here if anyone knows one.
I don't understand what you want. Can you just have DC++k disconnect/kick/ban a user if they do not allow a connection? I'm also assuming the DC++k nickname has Operator rights.
-NotRabidWombat
icmp has nothing 2 do with what you have in mind.
in extreme dummy style a ping/icmp is like me standing infront of your house shouting "ARE YOU HOME".
now if you ain't home i'm shouting for nothing, when you block icmp again i'm shouting for nothing, but when you are home you shout back "YEEEEEESSSSSSSSSS".
now when i would try 2 download from you i look for door number 412 (lets asume you use that for active mode) and knock on it, if your firewall doesn't block it i can enter and grab what i want and leave.
plop
* NotRabidWombat shouts back, No I'm NOOOOOOT!! We don't want any!
-NotRabidWombat
ok another way of asking......these users are showing up with some client or some firewall trick to become immune to any action from dc++ or cdm. the kick, drop-, ban functions do nothing to them and the commands show to all in main chat. the only way to get rid of them is in the hub software userlisting by right clicking there username. (TD4) it acts as if their client doesnt recognize the data im sending in the command, or mayby as I said a one direction FW rule. The idea to ping them was if no response, couldnt I then assume that if they are indeed still in the hub, I should be able to ping or tracrt their ip?
Or if thats not a good test method then any test that will determine if they are allowing proper communication with the hub and my client? Also has anyone else seen these "occasional bulletproof users"?
i think youll find there users whos client have crashed and not sent the $Quit to the hub..
do the nicks of those users end with <++
if not try 2 pm them, if they are ghost ptokax should drop them.
plop
It is still happening about two or so users a day. they cannot be kicked banned or dropped by cdm, or black dc. refreshing the userlist shows them still there. then if I right click ban them directly from the hub software (TD4) it puts there ip and nick in permban just like its suppose to. these guys have some way of ignoring client side commands. I am not hallucinating. If the user was a goast and not really there, then refreshing the userlist should do it right? and also The software would not have an ip or nickname to enter into the permban list if he was gone would it? Hmm Im wide open for ideas on this one thats for sure. Oh yeah and also my ops cannot get rid of them at all because the can sit at my machine and do it from ptokax userlist window. :(
gone be anoying. lol
do there nicks look like nickname<++ (the start of the tag glued 2 the nick).
if so you can get rid of them by doing !ban nickname.
otherwise the user indeed can't be banned/kicked as dc++ interprets the nick wrong.
plop