where is my WRAPPER

[GOTHBITES]

Bringing up interface wlan0: Line 963: Invalid PSK ''

This shows there is no psk in place.

Still has the issue

service -f network
Shutting down interface eth0:                                                                                [  OK  ]
Shutting down interface wlan0:                                                                               [  OK  ]
Shutting down loopback interface:                                                                            [  OK  ]
Bringing up loopback interface:                                                                              [  OK  ]
Configuring wireless regulatory domain                                                                       [  OK  ]
Bringing up interface eth0:                                                                                  [  OK  ]
Bringing up interface wlan0:  Line 963: Invalid PSK ''.
Line 963: failed to parse psk ''.
Line 966: WPA-PSK accepted for key management, but no PSK configured.
Line 966: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant.conf'.

So how do I correct this in reinstalling from scratch

btw thanks Hottie and DJ I wouldn't even have tried a nutty thing like if for you guys and the rest of the gang here on the Forum 

[Hootiegibbon]

try opening a terminal su to root and very carefully use

wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf

then append your wpa key into it

wpa_passphrase <ssid> [passphrase] >> /etc/wpa_supplicant.conf

be sure to use the >> as it will append your key as opposed to overwriting with >

then reboot again

If this fails to work post back with the result of these three lines

cat /etc/modprobe.d/blacklist
cat /etc/modprobe.d/blacklist-compat
cat /etc/modprobe.d/blacklist-pclos

Jase

[GOTHBITES]

cat /etc/modprobe.d/blacklist
blacklist ssb

cat /etc/modprobe.d/blacklist-compat
#
# Listing a module here prevents the hotplug scripts from loading it.
# Usually that'd be so that some other driver will bind it instead,
# no matter which driver happens to get probed first.  Sometimes user
# mode tools can also control driver binding.
#
# Syntax:  driver name alone (without any spaces) on a line. Other
# lines are ignored.
#

# watchdog drivers
blacklist i8xx_tco

# framebuffer drivers
blacklist aty128fb
blacklist atyfb
blacklist radeonfb
blacklist i810fb
blacklist cirrusfb
blacklist intelfb
blacklist kyrofb
blacklist i2c-matroxfb
blacklist hgafb
blacklist nvidiafb
blacklist rivafb
blacklist savagefb
blacklist sstfb
blacklist neofb
blacklist tridentfb
blacklist tdfxfb
blacklist virgefb
blacklist vga16fb
blacklist matroxfb_base

# ISDN - see bugs 154799, 159068
blacklist hisax
blacklist hisax_fcpcipnp

cat /etc/modprobe.d/blacklist-pclos

blacklist rivatv
blacklist i82875p_edac
blacklist usbkbd
blacklist usbmouse
blacklist pcspkr
blacklist snd-pcsp

Ok what does this mean please?

[Hootiegibbon]

Did the wpa_ commands not work?

The blacklists prevent the listed modules from loading completely

Jase

[GOTHBITES]

Did the wpa_ commands not work?

The blacklists prevent the listed modules from loading completely

Jase

N.o I think I may have appended it in the wrong spot, however I still need this to work at other locations without going through these steps, but if this happens again I would like to know how to do this right.

Here is the password is 12345 how would i append it to the wep account

[Hootiegibbon]

Did the wpa_ commands not work?

The blacklists prevent the listed modules from loading completely

Jase

N.o I think I may have appended it in the wrong spot, however I still need this to work at other locations without going through these steps, but if this happens again I would like to know how to do this right.

Here is the password is 12345 how would i append it to the wep account

its been an age since I personally used anything other than wpa, although a better way to check this out would be to check a couple more things

try using the following in a terminal su to root (take care)

ls /etc/sysconfig/network-scripts/wireless.d/<tab>

this will produce a resonce similar to
MA:CA:DD:RE:SS   essid_name

you need to use whatever teh essid_name is in teh following
cat /etc/sysconfig/network-scripts/wireless.d/essid_name

cat /etc/sysconfig/network-scripts/wireless.d/essid_name
BOOTPROTO=dhcp
METRIC=35
USERCTL=yes
DNS1=208.67.220.220
DNS2=208.67.222.222
RESOLV_MODS=yes
WIRELESS_MODE=Managed
WIRELESS_ESSID=essid_name
WIRELESS_ENC_KEY=s:12345
WIRELESS_WPA_DRIVER=wext
WIRELESS_WPA_REASSOCIATE=no
IPV6INIT=no
IPV6TO4INIT=no
ACCOUNTING=no
DHCP_CLIENT=dhclient
NEEDHOSTNAME=no
PEERDNS=no
PEERYP=yes
PEERNTPD=no

Some one may be kind enough to post an example for WEP

Jase

[GOTHBITES]

/etc/sysconfig/network-scripts/wireless.d/
*                     00:22:3f:31:f0:d4     0e:06:01:e6:83:7b
00:01:e6:ff:b4:43     00:23:69:91:8b:f0     0e:06:05:e6:83:7b     BigSpruce-guest     
00:0c:e6:02:5a:de     00:23:69:f3:9a:c8     12:06:01:e6:83:7b     c0:c1:c0:79:c4:8e     
00:0c:e6:a0:f4:7b     00:24:93:0a:c8:60     2WIRE077              c0:c1:c0:ac:65:9e   
00:0c:e6:fe:47:c0     00:3a:98:fa:79:60     63                    c0:c1:c0:d9:b4:fc     
00:13:10:35:ae:28     02:20:e0:a8:9b:a7     64:a0:e7:27:0a:f8     CHP Public            jimmyrcer
00:13:c3:59:35:70     06:06

this the output

cat /etc/sysconfig/network-scripts/wireless.d/CHP Public
cat: /etc/sysconfig/network-scripts/wireless.d/CHP: No such file or directory
cat: Public: No such file or directory