On Fri, 16 May 2003 at 02:30:09PM +0200, Andreas Vitz wrote: > May 15 09:25:46 kai-router pppoe[180]: Bogus PPPoE length field (1262) > May 15 09:27:25 kai-router pppoe[180]: Bogus PPPoE length field (111) > May 15 09:27:33 kai-router pppoe[180]: Bogus PPPoE length field (111) > May 15 09:27:33 kai-router pppoe[180]: Bogus PPPoE length field (48) > May 15 09:27:33 kai-router pppoe[180]: Bogus PPPoE length field (111) > May 15 09:27:33 kai-router pppoe[180]: Bogus PPPoE length field (48) > May 15 09:28:37 kai-router pppoe[180]: Bogus PPPoE length field (111) > May 15 09:28:39 kai-router pppoe[180]: Bogus PPPoE length field (111) > May 15 09:29:42 kai-router pppoe[180]: Bogus PPPoE length field (50) > May 15 09:36:45 kai-router pppoe[180]: Bogus PPPoE length field (623) > May 15 09:36:48 kai-router pppoe[180]: Bogus PPPoE length field (111) > May 15 09:37:07 kai-router pppoe[180]: Bogus PPPoE length field (111) > May 15 09:47:18 kai-router pppoe[180]: Bogus PPPoE length field (172) The presence of error messages usually means the program has spotted an exception and handled it. There may have been abnormal traffic on your PPOE connection but pppd caught it. However, the possibility does exist that some problem traffic was not identified and handled. In addition to running chrootkit you may wish to start running tripwire (if you don't already). Tripwire usually helps greatly in spotting file system abnormalities... -- Phillip Hofmeister Network Administrator/Systems Engineer IP3 Inc. http://www.ip3security.com PGP/GPG Key: http://www.zionlth.org/~plhofmei/ wget -O - http://www.zionlth.org/~plhofmei/key.txt | gpg --import -- Excuse #124: Big to little endian conversion error
Attachment:
pgpTWf2V9GDuF.pgp
Description: PGP signature