From: "Miguel González Castaños" <mgc@tid.es>
To: linux-admin@vger.kernel.org
Subject: runt packets with HomePNA
Date: Wed, 12 Mar 2003 11:53:01 +0100 [thread overview]
Message-ID: <3E6F118D.534D6FB1@tid.es> (raw)
dear all,
I am configuring a router with Linux redhat 7.3. This router have 4
NICs.
One of it is a HomePNA NIC.
All NICs are detected, by something curious happen with the HomePNA
configuration. It is configured as the latest ethernet interface, and it
is the third NIC out of the 4 that I have. As this HomePNA NIC has three
interfaces: one RJ45 and two RJ11 I dont know how RedHat configures this
kind of NIC. BTW, the HomePNA card is a HPN100 from lynksys and the
driver is pcnet32.
Another strange thing is that right after restarting the network I
start getting the message "runt packet" which I never heard of before.
After reading around on the Internet I have realized that the runt
packets are packets that are too short and that could be dued to
problems on the NIC...
Can anyone give me any clue of what could be going on?
Many thanks
Miguel
reply other threads:[~2003-03-12 10:53 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=3E6F118D.534D6FB1@tid.es \
--to=mgc@tid.es \
--cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).