From: "Keith Gagne" <keithgagne@home.com>
To: <linux-kernel@vger.kernel.org>
Subject: nic problems
Date: Wed, 27 Dec 2000 01:10:15 -0800 [thread overview]
Message-ID: <004801c06fe4$d3464bc0$60d77318@surrey1.bc.wave.home.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 485 bytes --]
hi, i'm new to this list, but i searched around and i've been having troubles getting my nic to work in the 2.2.18 kernel. when i try to ping something, i get no responce, as i sniff eth0 i can see the inital arp and arp reply for whatever ip on my local subnet. i also see an arp cache entry, i also see the icmp echo and echo reply. i'm looking for any ideas. i've tried this with a 3com 3c509b isa card and a intel 100mb eepro pci nic.
thanx alot, apreciate any help
keith
[-- Attachment #2: Type: text/html, Size: 936 bytes --]
reply other threads:[~2000-12-27 9:41 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='004801c06fe4$d3464bc0$60d77318@surrey1.bc.wave.home.com' \
--to=keithgagne@home.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®