From: Chris Leishman <masklin@debian.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: airport woes?
Date: Tue, 24 Oct 2000 15:16:44 +1100 [thread overview]
Message-ID: <20001024151644.A660@nina.dev.fol> (raw)
Hi all,
Something appears to be odd with the airport under PPC.
Unfortunatly I've been stuck behind a fairly awful link recently, and have
had to open interactive connections to remote hosts. The quality of the link
is terrible with average ping times of up to 1sec, and packet loss between 12
and 25 percent.
I've been using ssh to connect to remote hosts, and needless to say the
response time is shocking.
However, I've also had problems where the session totally locks up - I type at
the terminal as much as I like, but nothing reaches the other end. At first I
put this down to the crappy network link. However I've also noticed more
recently that only _half_ the connection craps out - I can still receive data
from the remote server. Weird.
Then today I switched to use ethernet instead of the airport (I was
transfering some large files and wanted to use 100Mb), and I noticed that I
wasn't getting the lockup problems with the remote hosts.
I'm using benh's latest kernel and airport driver. Now I can't think what
would be causing this, but I thought you'd like to know. Anyone else seen
this problem?
Regards,
Chris
--
----------------------------------------------------------------------
Knuth: premature optimization is the root of all evil.
----------------------------------------------------------------------
Reply with subject 'request key' for GPG public key. KeyID 0xB4E24219
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-10-24 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 4:16 Chris Leishman [this message]
2000-10-24 15:33 ` airport woes? Rob
2000-10-24 15:36 ` Chris Leishman
2000-11-02 20:15 ` Rod Stewart
2000-10-26 10:34 ` Topi Kanerva
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=20001024151644.A660@nina.dev.fol \
--to=masklin@debian.org \
--cc=linuxppc-dev@lists.linuxppc.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).