May I know how To keep things simple quicker and shorter route to server, from the bots machine? My eggdrop keeps ping timeout when try to connect to the server and if it connect (maybe once a day), it will ping timeout again very fast.
What type of IRC server is it, and when you connect to the same server with an IRC client, do you have to type any special commands, before you are fully connected.
You also state it is your own machine, are you on *nix fr widnows?
I got Eggdrop 1.6.8 running on my Debian stabele 3.0 something
and every tenth minute it pings out
17:44 --> Bottolf (eggdrop@localhost.) has joined #Roterommet
18:03 <-- Bottolf has quit (Ping timeout: 182 seconds)
18:04 --> Bottolf (eggdrop@localhost.) has joined #Roterommet
18:14 <-- Bottolf has quit (Ping timeout: 181 seconds)
18:14 --> Bottolf (eggdrop@localhost.) has joined #Roterommet
This happens after +/- 10 minutes all the time and i don't get it at all.
I've set up 127.0.0.1 and 192.168.1.6 as servers in the serverlist
Any ideas why this is happening?
And is there something i can do to change that?
This is on my own box and i'm the only one connected to it.
There's no other on my machine.
I got Shorewall installed and then it's shutdown.
There's no problem connecting (still on the same box) with regular users.
And i've also no problems connecting from work.
webmin check of firewall
"
Checking configuration ..
Processing /etc/shorewall/shorewall.conf ...
Processing /etc/shorewall/params ...
Verifying Configuration...
Determining Zones...
Zones: net loc dmz
Validating interfaces file...
Validating hosts file...
Determining Hosts in Zones...
Net Zone: eth0:0.0.0.0/0
Warning: Zone loc is empty
Warning: Zone dmz is empty
Validating rules file...
Rule "ACCEPT loc fw tcp ssh" validated.
Rule "ACCEPT net fw tcp ssh,auth" validated.
Rule "ACCEPT fw net udp ntp" validated.
Validating policy file...
Policy "loc net ACCEPT " Validated
Policy "net all DROP info" Validated
Policy "all all REJECT info" Validated
Configuration Validated
"
All addressess are allowed through when the firewall is stopped.
So i don't think that's the problem
I'm starting to wonder if it's the crond scheduling that is the problem