egghelp/eggheads community

crond

2003-11-13T15:37:58-04:00

Just took a check and made cron run the botcheck task every fifth minute.
No change in the bot's behaviour.
It comes and leaves every tenth minute.

*is totally baffled*

Statistics: Posted by Guest — Thu Nov 13, 2003 3:37 pm

Shorewall

2003-11-13T14:30:59-04:00

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

Statistics: Posted by Guest — Thu Nov 13, 2003 2:30 pm

ping timeout

2003-11-13T13:35:45-04:00

You maybe have firewall "on" ?

Statistics: Posted by ]Kami[ — Thu Nov 13, 2003 1:35 pm

Same problem

2003-11-13T13:23:43-04:00

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.

Statistics: Posted by Guest — Thu Nov 13, 2003 1:23 pm

ping timeout

2002-01-15T13:31:00-04:00

Undernet server.. no commands required to connect. It's a *nix box.

Statistics: Posted by Guest — Tue Jan 15, 2002 1:31 pm

ping timeout

2002-01-15T11:25:00-04:00

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?

Statistics: Posted by ppslim — Tue Jan 15, 2002 11:25 am

ping timeout

2002-01-15T04:02:00-04:00

It's my own server... not a free shell from other provider.

Statistics: Posted by Guest — Tue Jan 15, 2002 4:02 am

ping timeout

2002-01-15T02:36:00-04:00

The trick is to shift to a faster shell which are usually not free (I assume you are using a shell thats free)

goto the shells page on http://www.egghelp.org

Statistics: Posted by Yourname — Tue Jan 15, 2002 2:36 am

ping timeout

2002-01-15T02:16:00-04:00

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.

Statistics: Posted by Guest — Tue Jan 15, 2002 2:16 am

ping timeout

2001-11-05T06:20:00-04:00

k thnx

Statistics: Posted by JensB — Mon Nov 05, 2001 6:20 am

ping timeout

2001-11-04T21:59:00-04:00

To keep things simple quicker and shorter route to server, from the bots machine.

Statistics: Posted by ppslim — Sun Nov 04, 2001 9:59 pm

ping timeout

2001-11-04T13:17:00-04:00

peering ?

Statistics: Posted by JensB — Sun Nov 04, 2001 1:17 pm

ping timeout

2001-11-04T12:33:00-04:00

not really. its caused by lag between the bot and the server. only way to fix it properly is to get better peering

Statistics: Posted by Petersen — Sun Nov 04, 2001 12:33 pm

ping timeout

2001-11-04T08:34:00-04:00

[14:14] -ERROR from server- Closing Link: Bot[bot@100.100.100.100] (Ping timeout: 180 seconds)

any setting I can use to try and prevent this ?

Statistics: Posted by JensB — Sun Nov 04, 2001 8:34 am