egghelp/eggheads community

Problems with NickServ identify on IRCNet

2009-10-04T06:37:33-04:00

add these line anywhere in conf file.

###identify###

bind evnt - init-server evnt:init_server

proc evnt:init_server {type} {
global botnick
putquick "PRIVMSG NICKSERV@services.icq.com :IDENTIFY yourbotnick yourbotnickpassword" }

note: do /nickserv help, you will get more info about nickserv and its mask.

example of dalnet

.:13:33:45:. -NickServ- ***** NickServ Help *****
.:13:33:45:. -NickServ- NickServ permits users to 'register' a nickname, and stop
.:13:33:45:. -NickServ- others from using that nick. NickServ allows the owner of a
.:13:33:45:. -NickServ- nick to disconnect a user using the owners registered nick.
.:13:33:45:. -NickServ- If a registered nick is not used by the owner for 30 days,
.:13:33:45:. -NickServ- NickServ will drop it, leaving it up for grabs by another user.
.:13:33:45:. -NickServ- Please do NOT register more nicks than you will actively use! =)
.:13:33:45:. -NickServ-
.:13:33:45:. -NickServ- For more information on a command, type
.:13:33:45:. -NickServ- /msg NickServ@services.dal.net help
.:13:33:45:. -NickServ-
.:13:33:45:. -NickServ- Core Commands:

some IRCD's will not show it. in that case do /whois nickserv
and find the hostmasks

NickServ is service@dal.net Nick Registration Service (Internic Network)
NickServ using services.dal.net DALnet services home base

that will be your hostmask, ie nickserv@services.dal.net

hope this one helps

Statistics: Posted by gogers — Sun Oct 04, 2009 6:37 am

Problems with NickServ identify on IRCNet

2009-08-09T08:55:23-04:00

hi deejayb, have you even looked in the tcl archive? there are a load of id scripts in there for many services types. I use the dalnet ones myself and tweak the scripts to fix any differences between the services. You have not really given enough info either, what is the services challenge? how does it ask for id ? is this your own ircd/services? need loads more info. Also listen to what these guys say, they been doing this long enough. And if the whole concept of ircd/services/eggdrops leave you confused? give up and join someone elses network.
Good luck

Statistics: Posted by Callisto — Sun Aug 09, 2009 8:55 am

Re: I've resolved the problem!!!!!!!! (we can mark as "

2009-08-09T01:04:40-04:00

proc evnt:init_server {type} {
global botnick
adduser services *!*services@icq.com
chattr services +f
putquick "MODE $botnick +i-ws"
utimer 8 putserv "/ns identify montagna"
}

This shows you cannot listen to advice and probably are a bad candidate for actual help. You've used / in your putserv again clearly thinking eggdrop behaves as mIRC does. You should just create an mIRC bot for your projects and give up ever trying to get eggdrop to work. Clearly since you can't listen to the help already given, then repeating it several times causing this thread to span 15 pages won't do much good either (expect bump my post count higher which is irrelevant anyways). My advice to you is to seriously re-read this entire thread from front to back several hundred times until you figure it out. All the advice you need is already here.

Statistics: Posted by speechles — Sun Aug 09, 2009 1:04 am

I've resolved the problem!!!!!!!! (we can mark as "SOLV

2009-08-09T00:05:26-04:00

Here we are the modify to the eggdrop.conf file:

# This is a Tcl script to be run immediately after connecting to a server.
bind evnt - init-server evnt:init_server

proc evnt:init_server {type} {
global botnick
adduser services *!*services@icq.com
chattr services +f
putquick "MODE $botnick +i-ws"
utimer 8 putserv "/ns identify montagna"
}

.....

# This line loads script.tcl from the scripts directory inside your Eggdrop's
# directory. All scripts should be put there, although you can place them where
# you like as long as you can supply a fully qualified path to them.
#
# source scripts/script.tcl
source scripts/identify.tcl
source scripts/alltools.tcl
source scripts/action.fix.tcl

........

# Ident script for Windrop by FireEgl@EFnet <FireEgl@LinuxFan.com>
# uses username value for ident name by default
# read the start of script for more documentation
# uncomment (remove # in front of line) next line to activate
#source scripts/winident1.2.tcl
source scripts/identify.tcl

And here the identify.tcl script:

###########################################################
#
# Identify 1.0 tcl for eggdrop (20/01/2005)
# by lnx85 at #lnxlabs on AzzurraNet (irc.azzurra.org)
# E-mail: lnx85@lnxlabs.it
#
# Impostare la password del nick nella variabile identify(pass) (vedi GLOBALS)
# Lo script è pensato per Azzurra ma, con qualche piccola modifica, è adattabile
# anche ad altri Network
#
###########################################################

### GLOBALS ###
set identify(pass) "montagna"
set identify(ns) "NickServ!service@icq.com"
set identify(cs) "ChanServ!service@icq.com"
### END GLOBALS ###

### BINDS ###
bind evnt - init-server identify:identify
bind notc - *nick*registrato*altro*utente* identify:notice
bind notc - *rimangono*secondi*cambiare*automaticamente* identify:notice
### END BINDS ###

### PROCS ###
proc identify:identify { type } {
set ns [ lindex [ split $::identify(ns) "!" ] 0 ]
putserv "PRIVMSG $ns :IDENTIFY $::identify(pass)"
}

proc identify:notice { nick host handle text dest } {
set ns [ lindex [ split $::identify(ns) "!" ] 0 ]
putserv "PRIVMSG $ns :IDENTIFY $::identify(pass)"
}
### END PROCS ###

### INITIAL ###
if { ! [ validuser [ finduser $::identify(ns) ] ] } {
adduser NS [ lindex [ split $::identify(ns) "!" ] 1 ]
chattr NS +f
}
if { ! [ validuser [ finduser $::identify(cs) ] ] } {
adduser CS [ lindex [ split $::identify(cs) "!" ] 1 ]
chattr CS +f
}
putlog "\037IDENTIFY\037 \002::\002 \037LOADED\037 version 1.0 by lnx85

Statistics: Posted by deejayb — Sun Aug 09, 2009 12:05 am

Problems with NickServ identify on IRCNet

2009-08-08T22:46:34-04:00

Hi again!!!!!!!
Well...it's not change anything.....
The BOT enter without problems, but seems to don't identify itself to nickserv.....
Tnx so much!!!!!!!!!!

Statistics: Posted by deejayb — Sat Aug 08, 2009 10:46 pm

Problems with NickServ identify on IRCNet

2009-08-08T21:08:48-04:00

See the "check-mode-r" configuration setting. I believe your nickserv solution sets the usermode +r for registered nicks, which on most networks actually means "restricted connection". If this setting is set to 1, eggdrop will change the server whenever it detects usermode +r on itself to avoid "i-lines" (restricted connections).

As such, I would say that at least one of your scripts work (the one generating the Quit's).

Statistics: Posted by nml375 — Sat Aug 08, 2009 9:08 pm

Problems with NickServ identify on IRCNet

2009-08-08T16:01:55-04:00

None with this command exit.....
home.test.irc- *** Notice -- Client exiting: SitProperly (Bot@localhost) [Quit: i-lines suck]

I've try to put off the [ ] and now don't give me the error....but some problem.... when enter into the chan, Chanserv set it -o

Statistics: Posted by deejayb — Sat Aug 08, 2009 4:01 pm

Problems with NickServ identify on IRCNet

2009-08-08T15:58:05-04:00

putserv "/msg ns identify montagna" (I've change this)

Why? msg is an internal mIRC alias. You can tell by the / preceeding the command. Which in turn calls the proper "privmsg $target". Which in this case will actually be converted into "PRIVMSG NS :identify ". Now you have already said this wouldn't work and the proper way to do it was /ns identify password.

The problem now is eggdrop is not mIRC. /msg to it will actually go out to the ircd as "/msg" so what your doing of course will just go to oblivion/outerspace/hell/you-name-it it won't do anything. Eggdrop doesn't use / to preceed commands as mIRC does. Put it back to the way I had it for you and it should work as intended. If it doesn't, you may need to change this:

Code:

putserv "ns identify montagna"

to this:

Code:

utimer 8 [list putserv "ns identify montagna"]utimer 9 [list putserv "privmsg chanserv :op #mychan"]

This will give an 8 second delay which should be enough for your bot to join channels. Then it will attempt to authenticate itself which in turn should give you ownership of the nickname. After which 1 second later, at 9 seconds the bot will now msg chanserv to give it operator rights for #mychan.

Statistics: Posted by speechles — Sat Aug 08, 2009 3:58 pm

Problems with NickServ identify on IRCNet

2009-08-08T15:47:11-04:00

I don't know whether I am addressing your problem but I also used to identify my bots by this method. If services are a little lagged then the bot can enter its channels before services have reacted to the identify command and hence will not be op'd even if they are on the channels access list.

I now use a script that waits for nickserv to say something like 'this nick belongs to someone else etc etc' and sends the appropriate response. Then depending whether it is one of a preconfigured list of channels sends an OP command after a finite delay.

Statistics: Posted by arfer — Sat Aug 08, 2009 3:47 pm

Problems with NickServ identify on IRCNet

2009-08-08T15:32:37-04:00

Hi.
Now I don't receive any sort of errors....
But when my BOT enter into the Chan where is addes as Op, ChanServ don't op it....where can be the error?

# This is a Tcl script to be run immediately after connecting to a server.
bind evnt - init-server evnt:init_server

proc evnt:init_server {type} {
global botnick
adduser services *!*services@test.irc
chattr services +f
putquick "MODE $botnick +i-ws"
putserv "/msg ns identify montagna" (I've change this)
}

Tnx too much for the help that you give me!!!!!!!!

Statistics: Posted by deejayb — Sat Aug 08, 2009 3:32 pm

Problems with NickServ identify on IRCNet

2009-08-08T15:01:21-04:00

Code:

# This is a Tcl script to be run immediately after connecting to a server.bind evnt - init-server evnt:init_serverproc evnt:init_server {type} {  global botnick  adduser services *!*services@test.irc  chattr services +f   putquick "MODE $botnick +i-ws"  putserv "ns identify montagna"}

Change services@test.irc to the actual unique host (ident@host) that your services are actually using. Leave the *!* preceeding this in the adduser. This is all you should need to do.

Statistics: Posted by speechles — Sat Aug 08, 2009 3:01 pm

Problems with NickServ identify on IRCNet

2009-08-08T14:53:07-04:00

Same thing....
services continue to placing the BOT on ignore.....

Here is where I've put the script into the "eggdrop.conf" file:

# This is a Tcl script to be run immediately after connecting to a server.
bind evnt - init-server evnt:init_server
set init-server { putserv "ns identify montagna" }

proc evnt:init_server {type} {
global botnick
putquick "MODE $botnick +i-ws"
}

Statistics: Posted by deejayb — Sat Aug 08, 2009 2:53 pm

Problems with NickServ identify on IRCNet

2009-08-08T14:47:29-04:00

set init-server { putserv "ns identify " }

nml375 already said this awhile ago, some use the non-standard command "ns". Your also using this non-standard command in your question. So why not simply use the command?
But where I must put it into the identify.tcl file?!?!?
Tnx so much!!!!!!

Nowhere, that script is bloated, remove it. Just read the above reply by me again, and put these into your eggdrop.conf where they belong. The key to this is that you understand common sense. Do you?

Statistics: Posted by speechles — Sat Aug 08, 2009 2:47 pm

Problems with NickServ identify on IRCNet

2009-08-08T14:45:33-04:00

set init-server { putserv "ns identify " }

nml375 already said this awhile ago, some use the non-standard command "ns". Your also using this non-standard command in your question. So why not simply use the command?

But where I must put it into the identify.tcl file?!?!?
Tnx so much!!!!!!

Statistics: Posted by deejayb — Sat Aug 08, 2009 2:45 pm

Problems with NickServ identify on IRCNet

2009-08-08T14:48:15-04:00

set init-server { putserv "ns identify " }

nml375 already said this awhile ago, some use the non-standard command "ns". Your also using this non-standard command in your question. So why not simply use the command?

adduser services *!*services@test.irc
chattr services +f

According to your text, the above would put an end to the flooding message and subsequent ignores issued when connecting to the ircd. Change them of course to what should really be there.

Statistics: Posted by speechles — Sat Aug 08, 2009 2:38 pm