Vhost list

^DooM^ · Post by **^DooM^** » Wed May 25, 2005 4:28 pm

You saved the script onto a text file and called it something.tcl ? placed it into your eggdrop/scripts directory and added source scripts/something.tcl to the bottom of your config?

Galadhrim · Post by **Galadhrim** » Wed May 25, 2005 6:20 pm

manual read you did?

Thunderdome · Post by **Thunderdome** » Thu May 26, 2005 10:02 am

You saved the script onto a text file and called it something.tcl ? placed it into your eggdrop/scripts directory and added source scripts/something.tcl to the bottom of your config?

yes, I did all that.... I installed it as a normal TCL. but still does not work. The bot is klined, but does not return under a new vhost. :\
I don't understand...

Alchera · Post by **Alchera** » Thu May 26, 2005 10:10 am

A connection there is to be before knowing if exists a kline etc and, unfortunately for you, the server to you it gets first.

May the Force be with you.

Thunderdome · Post by **Thunderdome** » Thu May 26, 2005 12:49 pm

yes, but I don't get it. so how can the script choose another vhost on disconnect and reconnect to that vhost?
sounds quite simple...
bot gets disconnected, it changed vhost and connects again...
is this posible?

Alchera · Post by **Alchera** » Fri May 27, 2005 6:20 am

In a nutshell, no! The ban is enforced before your bot can ever get the needed info to swap the host and once disconnected (which you are) it's impossible for the script to switch to another vhost; the default vhost is used always.

demond · Post by **demond** » Sun May 29, 2005 3:59 pm

Alchera wrote:In a nutshell, no! The ban is enforced before your bot can ever get the needed info to swap the host and once disconnected (which you are) it's impossible for the script to switch to another vhost; the default vhost is used always.

that is not correct... you get an ERROR ("Closing link" etc.) message from the server upon disconnect because of a K-line/G-line, so you can bind to it and do the vhost hopping

of course, this is not the case when you are D-lined - the server doesn't notify you and simply drops the connection

Thunderdome · Post by **Thunderdome** » Sun May 29, 2005 6:35 pm

so, how do I know which error I have so I can make a bind?
the ban is usually temporary to that network... by the next day, one can connect....

How can I make it using the script above?

Alchera · Post by **Alchera** » Sun May 29, 2005 8:03 pm

The following refer to K-Line/G-Line/Server Notice:

216 (rfc1459) RPL_STATSKLINE
223 (rfc1459) RPL_STATSGLINE

SNOTICE Incoming notice from a server.

@ demond: Haven't got a "trick" to get past this stupid DALnet release command have you? It's been a thorn in not only my side for ages but awyeah's as well and neither of us seem to able to find a solution. lol

demond · Post by **demond** » Mon May 30, 2005 1:13 am

Code: Select all

set next 0
set yourIPs {1.2.3.4 5.6.7.8}
bind raw - ERROR goterror
proc goterror {from keyword text} {
  if [string match -nocase *banned* $text] {
    if {[incr ::next] == [llength $::yourIPs]} {set ::next 0}
    set ::my-ip [lindex $::yourIPs $::next]
  }
}

of course, yourIPs list can/should be automatically populated by parsing the output of ifconfig

@Alchera: what's the problem with it? I presume you meant NickServ's RELEASE

Alchera · Post by **Alchera** » Mon May 30, 2005 9:33 am

demond wrote:@Alchera: what's the problem with it? I presume you meant NickServ's RELEASE

Yup, the very one.. lol

Need the bot to switch from its normal main nick if the nick is being held to an alternative nick (as per conf) and then issue the release command so it can switch back to it's normal nick.I've tried a few approaches (and came close) but failed in all efforts.

BTW: Nice avatar.

demond · Post by **demond** » Mon May 30, 2005 11:53 am

Alchera wrote:
demond wrote:@Alchera: what's the problem with it? I presume you meant NickServ's RELEASE
Yup, the very one.. lol

Need the bot to switch from its normal main nick if the nick is being held to an alternative nick (as per conf) and then issue the release command so it can switch back to it's normal nick.I've tried a few approaches (and came close) but failed in all efforts.

BTW: Nice avatar.

why not do a USERHOST on the main nick and if the answer is something like enforcer@services, issue a RELEASE?

Alchera · Post by **Alchera** » Mon May 30, 2005 12:21 pm

Tried something similar; instant disconnect to DALnet when a nick is held therefore making it (apparently) impossible to issue the command.

Switching to the alternate nick (when the error is received) to issue the command and then allowing the bot to recover it's main nick (as normal) seems to be the only way.

Thunderdome · Post by **Thunderdome** » Mon May 30, 2005 12:25 pm

what about in PTnet? .... the ideia would just be... on disconnect, change vhost and reconnect... Perhaps it is easy to do it for any disconnect.

demond · Post by **demond** » Mon May 30, 2005 12:46 pm

@Alchera: you might want to try what I posted, setting ::nick instead of ::my-ip (and once connected, do the USERHOST and RELEASE stuff and then set ::nick back)

@Thunderdome: that code should work on any RFC1459 (IRC protocol standard spec) compliant network (I've never been to PTnet)