mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Edward Wildgoose" <Ed@Wildgooses.com>
To: <linux-kernel@vger.kernel.org>
Subject: Curious problem with network driver on 2.6 (no UDP)
Date: Mon, 1 Sep 2003 10:30:25 +0100	[thread overview]
Message-ID: <00aa01c3706b$b054b9a0$cb40a8c0@FRiskMan.com> (raw)

I have tried most of the 2.6 test kernels with MM patches from test1 up to a
fairly recent test4.  In all of these I see a curious problem with sk98lin
net driver.

Basically, I am using an Asus P4P800 board (which is an i865 chipset) and it
has a 3Com gigabit lan which seems to be supported by the sk98lin net
driver.  What actually happens though is that the device seems to be
detected OK by the kernel, and in fact I can ping or otherwise make TCP
connections by IP address, but UDP seems to be failing.  The most obvious
problem is that name lookups are failing, and in fact if I run "nslookup
blah", this fails, however, if I add the flag to force lookup over TCP then
it runs fine.  Ping seems to work fine as well (by IP only of course)

The machine is pretty generic, there is no firewall installed, and in fact I
added a crummy old NE2000 10mbit card and if I simply unload and swap the
sk98lin driver for the ne2000 driver, then networking comes back up and
works perfectly (UDP name resolution is fine), so I'm pretty sure that this
is an issue with that net driver, rather than a config issue (the machine
obviously also works perfectly with a 2.4.22 kernel, although using the
3c2000 net driver in that case)

If this is interesting then can I send any more detailed info?  Is the
.config for the kernel interesting?  Just to stress that this testing has
only been done with the -mm patchset, I haven't tried the vanilla kernel
yet.

Thanks for listening

Ed W


                 reply	other threads:[~2003-09-01  9:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='00aa01c3706b$b054b9a0$cb40a8c0@FRiskMan.com' \
    --to=ed@wildgooses.com \
    --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®