mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shish <shish@shishnet.org>
To: linux-kernel@vger.kernel.org
Subject: Weird network problems with 2.6.23-rc2
Date: Sat, 11 Aug 2007 08:39:59 +0100	[thread overview]
Message-ID: <20070811083959.305b0421.shish@shishnet.org> (raw)

Something seems to have broken in 2.6.23-rc2, and I'm not sure what, or
where I should look for further debugging. The info I have:

On my 2.6.23-rc2 desktop, things run fine.

On my test server, built from the same source tree, networking goes
strange every few minutes, with the following symptoms:

o) running ping against the server, the first ping goes through;
further pings go AWOL until about icmp_seq=30, when I get 4-5 icmp
replies (marked as DUP!), then no pings for a while, then dups, and so
on.

o) the server doesn't see ARP replies. According to tcpdump, the server
will send eg "who has 192.168.0.2? tell 192.168.0.1"; the client in
question will recieve the packet and send a response, but nothing shows
up in the server-side tcpdump.

o) after a few minutes of random network troubles, everything will work
fine again, (ping is normal, arp replies are seen, tcp sessions work)
for a few minutes.

o) The server's dmesg shows lots of "short udp packet" messages

o) ifdown then ifup'ing the interfaces fixes things, temporarily.

Reverting to 2.6.22, everything seems to be running fine (but no lguest,
which is what I came for :( )

I've also tried with the latest code from git, the behaviour is the same
as 2.6.23-rc2.

-- 
Shish

PS. First message to the list, please don't hurt me :P

             reply	other threads:[~2007-08-11  8:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-11  7:39 Shish [this message]
2007-08-11 21:55 ` Jiri Kosina
2007-11-13 16:03 ` Ray Lee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070811083959.305b0421.shish@shishnet.org \
    --to=shish@shishnet.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®