9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: [9fans] strange behavior with new Wavelan firmware + possible devmnt bug
Date: Fri, 24 May 2002 11:58:08 -0700	[thread overview]
Message-ID: <200205241858.g4OIw8S1032424@ducky.net> (raw)

The 8.10 firmware for Wavelan cards purports to fix WEP security holes.
However, I just discovered that the 8.10 firmware does not work with Plan 9.

It appears to work a little--ipconfig succeeds in getting an IP address
from a DHCP server.

Interactive ssh connections to a remote host work for awhile but then
get hung.  However "scp filename remotehost:" gets hung immediately.

Theory: the problem is large packets.

So, i tried:
term% echo -n mtu 576 > /net/ipifc/0/ctl

Now ssh logins work, and scp works.

However, attempts to run replica/pull from the sources.cs.bell-labs.com
repository don't work.  On further investigation, I found that it hangs
when attempting to cmp the last 1024 bytes of dist/replica/plan9.log.
Once again we're looking at large packets.  But in this case I had
already shrunk the MTU and other tcp services worked fine.

So there appear to be 2 problems here:

1.  Either the Wavelan driver is broken, or the 8.10 firmware is broken.
I am inclined to believe the firmware is at fault.  I downgraded to the
7.52 firmware and am having no trouble.

2.  devmnt appears to be not interacting well with network interfaces
configured with a smaller-than-normal MTU.  I confirmed this by trying
the same replica/pull, using the old 7.52 wavelan firmware, but setting
the mtu to 576 bytes.  Identical hang when attempting to cmp plan9.log,
so that problem is independent of the firmware version and depends only
on the MTU.


             reply	other threads:[~2002-05-24 18:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-24 18:58 Mike Haertel [this message]
2002-05-24 20:38 presotto
2002-05-24 21:48 Mike Haertel

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=200205241858.g4OIw8S1032424@ducky.net \
    --to=mike@ducky.net \
    --cc=9fans@cse.psu.edu \
    /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).