%[ip] option for right click menu..

OLDoMiNiON · Post by **OLDoMiNiON** » 2003-05-27 19:12

well, we have nick..etc etc, how about IP? it'd make banning through a standard dc++ client a heck of a lot easier

Atomic Jo · Post by **Atomic Jo** » 2003-05-27 23:53

Check the latest release of sarf's DC++k... It has an option to put the user ip in User Command.

OLDoMiNiON · Post by **OLDoMiNiON** » 2003-05-29 11:51

Yeah, but i want it in standard DC++

Since it's so useful for Op's, why not implement it?
It's not exactly abusable, since anyone can get their connected users IP though netstat in 2 sec's anyway.. I dunno why it hasn't already been implemented tbh.

Sedulus · Post by **Sedulus** » 2003-05-29 15:08

because it uses an extension to the DC protocol, and most hubs do not have this implemented (afaik it's only available for dch++ so far)

see: http://dcplusplus.sourceforge.net/wiki/ ... %20command

dieselmachine · Post by **dieselmachine** » 2003-05-29 19:53

my client has this. the problem with it is that the only way to really get an ip is to initiate a connection to the user first, and then have a hook which saves the ip addy to the user instance. Since im autoscanning filelists on entrance to the hub, this isnt a problem, but for standard dc client, you would have to connect somehow (get filelist perhaps), and only then would you actually know the ip.

OLDoMiNiON · Post by **OLDoMiNiON** » 2003-05-30 08:41

So? It's easy enough. It's done in DC++k, DC++ ClientDetect Mod, and BCDC++ also. I don't see the problem. It works fine, and doesn't cause any unwanted things to happen...

%[ip] option for right click menu..

%[ip] option for right click menu..

%ip