From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: Jeff Sickel <jas@spamisham.corpus-callosum.com>
Message-ID: <102h10mso8o2a6c@corp.supernews.com>
Subject: [9fans] 802.11b oddities
Date: Tue, 10 Feb 2004 09:36:43 +0000
Topicbox-Message-UUID: dc3ac9b8-eacc-11e9-9e20-41e7f4b1d025

I've been using Plan 9 on my laptop for quite some time now (never even
booted the XP that came with it... unfortunately, neither IBM nor M$ will
reimburse me for the XP license I wouldn't sign or use).  From the very
first boot, I'd set up the plan9.ini file to have multiple configs to help
choose which network I would be using.

Everything was fine until someone nearby added another 802.11b network.
Now, even though my plan9.ini sets essid=string to my network name, the
other network now takes precidence and ends up messing up my net settings.

Luckily an echo 'essid string' > /net/ether0/0/ctl fixes the problem.

Is there a way to properly force the 802.11b network choice outside of
explicitely setting it in termrc?

jas
---
remove spamisham.