My current network setup:
2 Public IP's (cable modem), one of which goes to my linux box that my eggdrop is running on, and the other IP goes to my router that all of the windows box's are connected to.
The eggy is running fine, but i can't set up a password with it. I tried /msg <bot> <pass>
but i don't get a response. I can't DCC chat with the bot either because it doesn't respond...just sits at "waiting for acknowledgement." I can't telnet to the bot either because i don't have a password set yet and when i try to telnet to it i get "can't telnet until you set up a password" or something like that.
in the havoc i may have been retarded and not done /msg <bot> pass <password>, although i think i did. still the fact remains that i can't DCC chat with the bot.
the bot should respond to the DCC chat request though. it just waits for acknowledgement and does nothing else. doesn't even get to the point where it prompts me for a user name.
On 2002-03-12 14:06, optik wrote:
My current network setup:
2 Public IP's (cable modem), one of which goes to my linux box that my eggdrop is running on, and the other IP goes to my router that all of the windows box's are connected to.
The eggy is running fine, but i can't set up a password with it. I tried /msg <bot> <pass>
but i don't get a response. I can't DCC chat with the bot either because it doesn't respond...just sits at "waiting for acknowledgement." I can't telnet to the bot either because i don't have a password set yet and when i try to telnet to it i get "can't telnet until you set up a password" or something like that.
Umn... If the bot has been started from scratch, why not start with the beginning: /msg bot hello (or whatever "hello" word you've setup in your .conf file) ?
If there's already users in the userlist, verify for doubles. Example, you have two entries in the bot:
god
HOSTS: *!*@123.456.789.*
you
HOSTS: *!*@123.456.789.0
your IP is 123.456.789.0. Who is who? The password can be ignored in such case. I learned it the hard way using a take-over protection script...
<font size=-1>[ This Message was edited by: bleah on 2002-03-12 18:56 ]</font>
bleah, that's why people use ident (username) in their hostmasks. So it's harder to fake it. Also don't use any lame public commands script or autoop (ESPECIALY IF YOU ADDED YOUR HOST LIKE THAT).
On 2002-03-13 10:56, masskilla wrote:
bleah, that's why people use ident (username) in their hostmasks. So it's harder to fake it. Also don't use any lame public commands script or autoop (ESPECIALY IF YOU ADDED YOUR HOST LIKE THAT).
Errrr. I've omit the ident part to make my "point" look more apparent. I just tried to help here, but if I'm about to get blamed about something like that....
On 2002-03-13 15:36, masskilla wrote:
Blamed..? For what? Did I blame you for anything?
I was just making my "point" that those hostmasks are very insecure.
Alright, let me re-do it in some other way...
<you> .match *123.456.*
<bot> god
<bot> HOSTS: *!you@123.456.789.*
<bot>
<bot> you
<bot> HOSTS: *!you@123.456.*
So, who is you? Who is that other person/bot on the the same IP block as you?
Check for doubles.
Well in that case the bot wouldn't quite recognise you.. but there's still a password difference.. and if that's the problem (for auto-voice, or auto-op), you can add your nick (or part of it) to the hostmask. Or change your ident (if it's possible).