From: Jon B. <jon...@la...> - 2004-07-21 13:21:22
|
one of my windows xp users reports that he gets alot of Wed Jul 21 15:11:54 2004 Authenticate/Decrypt packet error: bad packet ID (may b e a replay): [ #1461 ] -- see the man page entry for --no-replay and --replay-wi ndow for more info Wed Jul 21 15:12:20 2004 Authenticate/Decrypt packet error: bad packet ID (may b e a replay): [ #1479 ] -- see the man page entry for --no-replay and --replay-wi ndow for more info Wed Jul 21 15:12:29 2004 Authenticate/Decrypt packet error: bad packet ID (may b e a replay): [ #1480 ] -- see the man page entry for --no-replay and --replay-wi ndow for more info Wed Jul 21 15:12:34 2004 Authenticate/Decrypt packet error: bad packet ID (may b e a replay): [ #1481 ] -- see the man page entry for --no-replay and --replay-wi ndow for more info Wed Jul 21 15:12:36 2004 Authenticate/Decrypt packet error: bad packet ID (may b e a replay): [ #1481 ] -- see the man page entry for --no-replay and --replay-wi ndow for more info Wed Jul 21 15:12:38 2004 Authenticate/Decrypt packet error: bad packet ID (may b e a replay): [ #1481 ] -- see the man page entry for --no-replay and --replay-wi ndow for more info Wed Jul 21 15:12:44 2004 Authenticate/Decrypt packet error: bad packet ID (may b e a replay): [ #1482 ] -- see the man page entry for --no-replay and --replay-wi ndow for more info he's connected through wifi to a internet and through that to the server, which is wired. It was something it just suddently started at, and it keeps doing it. Do i need to worry or something ? JonB |
From: James Y. <ji...@yo...> - 2004-07-21 19:59:01
|
On Wednesday 21 July 2004 08:20, Jon Bendtsen wrote: > one of my windows xp users reports that he gets alot of > > Wed Jul 21 15:11:54 2004 Authenticate/Decrypt packet error: bad packet > ID (may b > e a replay): [ #1461 ] -- see the man page entry for --no-replay and > --replay-wi > ndow for more info > Wed Jul 21 15:12:20 2004 Authenticate/Decrypt packet error: bad packet > ID (may b > e a replay): [ #1479 ] -- see the man page entry for --no-replay and > --replay-wi > ndow for more info > Wed Jul 21 15:12:29 2004 Authenticate/Decrypt packet error: bad packet > ID (may b > e a replay): [ #1480 ] -- see the man page entry for --no-replay and > --replay-wi > ndow for more info > Wed Jul 21 15:12:34 2004 Authenticate/Decrypt packet error: bad packet > ID (may b > e a replay): [ #1481 ] -- see the man page entry for --no-replay and > --replay-wi > ndow for more info > Wed Jul 21 15:12:36 2004 Authenticate/Decrypt packet error: bad packet > ID (may b > e a replay): [ #1481 ] -- see the man page entry for --no-replay and > --replay-wi > ndow for more info > Wed Jul 21 15:12:38 2004 Authenticate/Decrypt packet error: bad packet > ID (may b > e a replay): [ #1481 ] -- see the man page entry for --no-replay and > --replay-wi > ndow for more info > Wed Jul 21 15:12:44 2004 Authenticate/Decrypt packet error: bad packet > ID (may b > e a replay): [ #1482 ] -- see the man page entry for --no-replay and > --replay-wi > ndow for more info > > he's connected through wifi to a internet and through that to the > server, which is wired. > It was something it just suddently started at, and it keeps doing it. It means that either duplicate packets are being received or packets are arriving extremely out-of-order. It's more likely the former because in the output above, I see 3 messages concerning #1481. It's not uncommon to see duplication of packets on wireless links. If the link is working fine otherwise, I would just ignore the errors or mute them using --verb or --mute. James |
From: Jon B. <jon...@la...> - 2004-07-21 20:29:22
|
Den 21. jul 2004, kl. 21:59, skrev James Yonan: > On Wednesday 21 July 2004 08:20, Jon Bendtsen wrote: >> one of my windows xp users reports that he gets alot of >> >> Wed Jul 21 15:11:54 2004 Authenticate/Decrypt packet error: bad packet >> ID (may b >> e a replay): [ #1461 ] -- see the man page entry for --no-replay and >> --replay-wi >> ndow for more info >> Wed Jul 21 15:12:20 2004 Authenticate/Decrypt packet error: bad packet >> ID (may b >> e a replay): [ #1479 ] -- see the man page entry for --no-replay and >> --replay-wi >> ndow for more info >> Wed Jul 21 15:12:29 2004 Authenticate/Decrypt packet error: bad packet >> ID (may b >> e a replay): [ #1480 ] -- see the man page entry for --no-replay and >> --replay-wi >> ndow for more info >> Wed Jul 21 15:12:34 2004 Authenticate/Decrypt packet error: bad packet >> ID (may b >> e a replay): [ #1481 ] -- see the man page entry for --no-replay and >> --replay-wi >> ndow for more info >> Wed Jul 21 15:12:36 2004 Authenticate/Decrypt packet error: bad packet >> ID (may b >> e a replay): [ #1481 ] -- see the man page entry for --no-replay and >> --replay-wi >> ndow for more info >> Wed Jul 21 15:12:38 2004 Authenticate/Decrypt packet error: bad packet >> ID (may b >> e a replay): [ #1481 ] -- see the man page entry for --no-replay and >> --replay-wi >> ndow for more info >> Wed Jul 21 15:12:44 2004 Authenticate/Decrypt packet error: bad packet >> ID (may b >> e a replay): [ #1482 ] -- see the man page entry for --no-replay and >> --replay-wi >> ndow for more info >> >> he's connected through wifi to a internet and through that to the >> server, which is wired. >> It was something it just suddently started at, and it keeps doing it. > > It means that either duplicate packets are being received or packets > are > arriving extremely out-of-order. > > It's more likely the former because in the output above, I see 3 > messages > concerning #1481. It's not uncommon to see duplication of packets on > wireless links. > > If the link is working fine otherwise, I would just ignore the errors > or mute > them using --verb or --mute. okay, thanks. It is already --verb 1 though JonB |