From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] wavelan config problems
Date: Tue, 10 Apr 2001 17:31:47 +0200 [thread overview]
Message-ID: <200104101531.RAA09755@polya.cs.utwente.nl> (raw)
I have been trying to get a wavelan/orinoco card working using the
driver in the March 27 distribution, without success.
(In the mean time I applied to portclock.c fix).
On the same laptop the card works without problems for win98 and linux.
I did not have a working plan9 network (card) on this laptop before, so I'm
configuring the network stuff at the same time. Could errors (or omissions)
made there explain my problems? I try to 'hardcode' the ip-gateway, ip-address
and network mask in the ip/ipconfig line in /rc/bin/termrc, but that doesn't
make much of a difference.
To sketch what is happening: say, our managed network name is OUR-NAME
(different, actually, but indeed all caps and including a hyphen)
Encryption keys shgo
In the plan9.ini I have:
ether0=type=wavelan
without anything else.
After booting, one green led on the card is on.
However, it seems that for each packet sent I get a transmit error.
At least, that is what I see in the stats window, and also in the
/net/ether0/0/ifstats and /net/ether0/0/stats status files.
However, stats reports one more packets sent than ifstats,
but the same number of errors. i.e.: stats: in=2 out=2 output-errors=1;
ifstats txpackets=0 rxpackets=0 txerrors=1 rxerrors=0 txrequests=1.
Does that mean that one packet got out without error?
/net/ether0/0/ifstats reports a.o. the following:
Current name: OUR-NAME\01
Net name: First WaveLAN II SSID
where the \01 represents hex 01. Wonder where the \01 comes from.
In attempt at debugging, I changed etherwavelan.c to check the return
value of the w_cmd call in w_outltv, in the same way as elsewhere
in the file, but this doesn't seem to give me much, becaue I get an
error message for each config command that I sent to the driver,
like: echo 'crypt on' > /net/ether0/0/ctl .
Earlier I tried to use a plan9.ini with
ether0=type=wavelan essid=OUR-NAME
which gives me in /net/ether0/0/ifstats
Current name: non-specified SSID!!
Net name: OUR-NAME
and the green led on the card is off.
Does this make sense to anyone?
I really have the feeling that I'm overlooking something simple...
Some things I could check/do to get more grip on the problem?
Regards,
Axel.
next reply other threads:[~2001-04-10 15:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 15:31 Axel Belinfante [this message]
2001-04-10 15:58 jmk
2001-04-11 14:37 ` Axel Belinfante
2001-04-11 20:47 jmk
2001-04-12 13:17 ` Axel Belinfante
2001-04-12 17:26 jmk
2001-04-17 12:56 ` Axel Belinfante
2001-04-17 7:17 nemo
2001-04-17 7:29 nemo
2001-04-17 8:35 ` Axel Belinfante
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=200104101531.RAA09755@polya.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).