I have an eggdrop running on a server. This works fine. It can join channels etc. But when i use dcc togive it commands i have the following problem.
Commands like ´.say blablabla´ work fine, but when i want to op myself it doesn´t respond. It says ´gave ops to arcadis´, but nothing happens. The same when i want to kick, ban, deop someone.
I´m sure i type the nicknames and the channel correctly, but i can´t figure out what´s wrong.
Any help is greatly appreciated.
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
bot can join channel, but commands don't work.
-
aarcadis
Ok, i've changed it to IRCNet, which is the network the bot is on, but now when it 'doesn't connect to the irc server. 
When i log in via telnet i get the following messages:
[15:52] Trying server irc.nl.uu.net:6664
[15:52] Connected to irc.nl.uu.net
[15:52] NICK IN USE: Trying '[botnick]'
[15:52] (irc.nl.uu.net claims to be irc.uunet.nl; updating server list)
[15:52] irc.nl.uu.net has me i-lined (jumping)
[15:52] Trying server irc.sci.kun.nl:6665
What does this i-lined mean and why is the bot jumping to another server? This happens with all the servers in the list, so it is some sort of network restriction it seems.
When i log in via telnet i get the following messages:
[15:52] Trying server irc.nl.uu.net:6664
[15:52] Connected to irc.nl.uu.net
[15:52] NICK IN USE: Trying '[botnick]'
[15:52] (irc.nl.uu.net claims to be irc.uunet.nl; updating server list)
[15:52] irc.nl.uu.net has me i-lined (jumping)
[15:52] Trying server irc.sci.kun.nl:6665
What does this i-lined mean and why is the bot jumping to another server? This happens with all the servers in the list, so it is some sort of network restriction it seems.
IRCnet uses restricted connections. These are called i-lines.
TO know if your connections restricted, your usermode will include an "r" in it.
When restricted, you do not have full channle managment abilities. IE, you can't deop OPs, you can't kick OPS. This defeats the purpose of eggdrop, so it skips that server, and locates one that doesn't present an issue.
If you so wish to join the server anyhow, and put up with reduced abilities, then you can change a config settings, which will prevent this.
See the config file for details.
TO know if your connections restricted, your usermode will include an "r" in it.
When restricted, you do not have full channle managment abilities. IE, you can't deop OPs, you can't kick OPS. This defeats the purpose of eggdrop, so it skips that server, and locates one that doesn't present an issue.
If you so wish to join the server anyhow, and put up with reduced abilities, then you can change a config settings, which will prevent this.
See the config file for details.
-
aarcadis
With most networks, they serve you in a connection priority fasion.
Just like there are serveral levels of server bans, it is possible to have several levels of server connections.
Each connections that comes in, is defined a class.
This class defines different characteristics of the connection.
These can include
1: How often the server sends a ping to your connection.
2: The time limit before your connection times out (after not replying to a ping).
3: If pings are sent during idle periods, or all the time.
4: How many channels you may join.
ALong with these, the class can also define the default user-flags given/forced by the server.
In the case of a restricted connection (or class as it's called), you are forced the +r flag.
On IRCnet, there are a few reasons for this, these include, but are not limited to:
1: No ident reply
2: Hostname not resolving fully
3: Non-local server
In the case of number 3, more priority is given to clinet connecting near to them. Admins usualy collect these based on ping/tracroutes.
In the case of number 2, you will well know if this is the case. After changing the setting in the config file, and your bot is now on IRC, do a whois. If you see an IP, then your need to contact the shell admin, and get the DNS and rDNS records straight.
In the case of number 1, you will need ot contact the admin, and make sure that identd is running, and that there is no port-clocking in operation.
As for it being a configuration issue. No, this is not true. A restricted connections, is based on the rules/classes defined by the IRC admin.
Just like there are serveral levels of server bans, it is possible to have several levels of server connections.
Each connections that comes in, is defined a class.
This class defines different characteristics of the connection.
These can include
1: How often the server sends a ping to your connection.
2: The time limit before your connection times out (after not replying to a ping).
3: If pings are sent during idle periods, or all the time.
4: How many channels you may join.
ALong with these, the class can also define the default user-flags given/forced by the server.
In the case of a restricted connection (or class as it's called), you are forced the +r flag.
On IRCnet, there are a few reasons for this, these include, but are not limited to:
1: No ident reply
2: Hostname not resolving fully
3: Non-local server
In the case of number 3, more priority is given to clinet connecting near to them. Admins usualy collect these based on ping/tracroutes.
In the case of number 2, you will well know if this is the case. After changing the setting in the config file, and your bot is now on IRC, do a whois. If you see an IP, then your need to contact the shell admin, and get the DNS and rDNS records straight.
In the case of number 1, you will need ot contact the admin, and make sure that identd is running, and that there is no port-clocking in operation.
As for it being a configuration issue. No, this is not true. A restricted connections, is based on the rules/classes defined by the IRC admin.