halo... i am using fedora core 4,2.6.11 and ndiswrapper-1.1 and my wireless card is
Intel Pro/Wireless 2100 3B ....
I am trying to build up a ad-hoc mode to try to communicate with others laptop.
i am having problem on setting essid of ndiswrapper....dunno why the status is keep on "on/off"
when i did tried to use command to set it "iwconfig wlan0 essid test" and also go to network configuration there to set it, but also cannot.

Before that, I did faced the same problem. After my lecturer set the ad-hoc to "test" on his laptop, then i only able set essid to "test" on my laptop. I did feel weird why like that. Then my lecturer off his wlan0 interface, then i did off also and on again, my essid still is "test".

Then after the next day, when i check my essid status, it is "on/off" again. I tried to set it to "test" together with my fren pc, we cannot set it.

Is that got related to any firewall setting ???


Did anyone have face the same problem as me ??
Please drop your messages if you have any ideas... Thanks!!!

sorry..forgot to mention that I did increase my stack size to 16K due to window driver might have 8K stack size or bigger than that...so my fedora core 4 only got 4K and i have to change it.

Is that got possible due to kernel version problem??

Instead of ndiswrapper, why don't you use the native linux ipw2100 drivers? Fedora has never been particularly ndiswrapper friendly, and a native linux driver might work a lot better. If ipw2100 isn't included in a stock Fedora install, my guess is that there are RPM's out there.

when I tried to do a similar setup at home I had basically the same problems as you...trick was too set the ssid on the other wlan nic first and with some luck worked..only used it a couple of days then bought a AP..way less problems

Is there have any patches that needed to solve the problem which i can set essid on myself in ad-hoc mode ??
I only can set the essid when there is a network existed in ad-hoc, but if i want to set a new network name, then i cannot do so. Dunno why (

Usually when you have these sorts of troubles, it is some conflict between ndiswrapper and the Windows driver. You might check Intel's site and see if you have the latest Windows driver. But as I said earlier, the native linux driver is likely to be a superior solution.