Hi!
First of all: Thanks for the great job you are doing!!!
But I've got 2 remaining problems:
- If I enable WEP before setting my ESSID (it is hidden, thus I need to set it
manually) association to the AP fails.
- If I get disassociated from the AP (which currently happens due to config
Hi everybody!I'm testing today's snapshot, and found a couple of weird things.First is that #iwlist eth1 scanning(and the rest of funtionality) don't work untill 4 cores are enabled.To enable all four cores I had to modprobe/rmmod several times:
Dec 31 12:04:43 localhost kernel: [17180580.104000]
On Sat, 2005-12-31 at 02:37 +, David Woodhouse wrote:
At that point I can use dhclient successfully and Legacy IP works.
Hm, almost. If I leave a ping running, I see an occasional TX timeout,
followed by a reset -- and then I have to manually set the ESSID again
before it'll work any more.
