Thin

Security level already seems to be set to standard. I'll have a go at changing the charset

very small - 1.4GB

hi all Booted up the laptop this morning to find my shared partition completely misbehaving - this is a FAT32 partition shared between Mandriva and XP. its in FSTAB as /dev/hda6 /mnt/win_e vfat umask=0,iocharset=iso8859-15,codepage=850 0 0 If I try to create / delete a test file in the root initially - everything is fine and works as expected, however when I attempt to use / edit files in some directories below the whole thing seems to lose permission and go to read only or something. This is completlely reproducable in that if I unmount, mount again, it does exactly the same thing I don't have the first idea what to try to pin this one down - so any troubleshooting advice greatly appreciated. [moved from Terminal Shell Commands,etc by spinynorman]

Thread stealer! Well, seeing as my problem is solved. If you're running 2005 LE i'd try using the IPW2200 driver before resorting to NDIS wrapper. How did you install the firmware and WPA supplicant ? I used easy urpmi to setup source and then simple urpmi commands to get the firmware from PLF and the supplicant from main once you've made your /etc/wpa_supplicant.conf along the lines above try wpa_supplicant -i eth2 -c /etc/wpa_supplicant.conf -D ipw -w -dd where eth2 is your wireless interface you can make it wpa_supplicant -B -i eth2 -c /etc/wpa_supplicant.conf -D ipw -w -dd to run the command in the background (daemonize) You may wish to add ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 to the top of your wpa_supplicant.conf. the first line gives an interface for client programs to access - and the interface group lets you specify a group of users who can manage it (0 = root) HTH

Cheers, simplifying my config seems to have worked

Ok, a bit more reading - and this command Appears to work - as in it creates some output. then prints Daemonize.. and then returns to the prompt - and when using the network monitor you can see traffic spikes - however pings inward or outward do not work wpa_cli -i eth2 status shows the property wpa_state as scanning, handshaking or associating, and this seems to go round and round iwconfig eth2 = shows the access point mac address, so it is connecting. The state however remains as unassociated so I presume that although it can connect it cannot associate with the access point. Every 10 seconds or so iwconfig will show IEEE 802.11g rather than unassociated - but this doesnt last

Cheers - i'd missed adding a main to my urpmi sources Right, i've got it all installed and have made a basic config - but when I issue the command to associate wpa_supplicant -i eth2 -c /etc/wpa_supplicant.conf -d ipw When it gets to my access point it displays the following 1: 00:30:bd:f2:66:f0 ssid='myssid' wpa_ie_len=0 rsn_ie_len=0 skip - no WPA/RSN IE Its presumeably skipping it down to a missing config option ? I've had a read of the wpa_supplicant.conf.rpmnew which contains a hell of a lot of information - but can't made sense of half of it. Anyone got any tips? My access point is a Belkin 54g using wpa-psk and TKIP

Hi all Decided I wanted mandrake back on my laptop Downloaded the 2005 (10.2) download edition. Installed. My laptop uses an Intel 2200BG - my home network uses WPA-PSK with TKIP encryption. Added update and plf sources for easy urpmi, ran update - installed ipw2200 firmware necassery for driver to work that the silly configuration wizards make no mention of you needing to obtain. Reboot iwlist eth2 scan now reveals that the wireless card appears to be working and seeing things. Back to the control center - follow through the wizard - tick the box for WPA. No luck Decide to do it manually All tutorials / guides to WPA on linux seem to end up with wpa_supplicant. This command doesnt seem to exisit on my new system - but I do however have a wpa_supplicant.conf (presumeably created by the control centre?) Have tried searching in the control center for a wpa_supplicant package - and have also tried urpmi wpa-supplicant wpa_supplicant wpasupplicant None of which seem to exist And have completely run out of patience Does anyone know the secret to this? Please :woops:

You could well be right. I find it slightly maddening that it doesn't say on the site anywhere what the current feature list actually is

ok downloaded and placed the firmware into the appropriate folder and re ran the wizard. I now have the new interface showing in the control centre. Have tried putting the ssid and key into the wizard but i'm not ending up with a working connection. I get the impression its missing some connection info somewhere - i cant see an option to choose between WEP and WPA in the wizard Given that i'm try to connect to a WPA-PSK network should I be using wpa supplicant ? Is this already in 10.1 ? Sorry if these are dumb questions guys, but i'm a little confused on whether the wizard is supposed to do what i want it to do (WPA-PSK) or whether its just for 'standard' WEP... Thanks again for any help

hi all Have installed 10.1 community on my Centrino Laptop. Am largely very happy with the outcome although i have yet to start using it in anger due to the lack of network access. My laptop has a Intel Wireless Pro 2200BG mini card inside it, whilst Mandrake 10.1 appears to recognise this, i don't seem to be able to see an obvious way to connect it to my wireless network, which is a 54g affair secured with WPA-PSK. If i have noobishly missed the fields to enter my key and ssid then i apologise in advance. I remember reading a while back that neither NDIS wrapper nor the Intel drivers at http://ipw2200.sourceforge.net/ supported WPA-PSK but that it would be added in due course. Where i am slightly confused is what i already have on my system (ie bundled with 10.1 community) as opposed to what i actually need to achieve what i want. The control centre dialogues don't really give much away in this regard. I attach what the control centres hardware section is currently reporting Any help / suggestions highly appreciated as i am a tad lost. feel free to move this over to networking - may be more appropriate