q re network stuffs & FC5

[Gene Heskett]

Ed Greshko wrote:
> Gene Heskett wrote:
>   
>> Wandering around in the /etc/sysconfig tree, I find that there seem to
>> be a minimum of 3 each of all the ifcfg-xxxx scripts scattered around. 
>> And while I don't seem to be able to see any links, if I update one of
>> them, the other 2 will appear to have been updated at the same time.
>>
>> No damned wonder I can edit the /etc/sysconfig/network-scripts version
>> of ifcfg-wlan0, restart that interface and then see that iwconfig nor
>> ifconfig appear to reflect the changes I've made.
>>
>> So which is the master version of these files, and how many of the
>> friggin dupes can I actually nuke to get rid of the effect of trying to
>> make a change and having that change ignored?
>>
>> Right now there are:
>> root at diablo sysconfig]# ls -lL `locate ifcfg-wlan0`
>> -rw-r--r-- 3 root root 314 May 10 21:21
>> /etc/sysconfig/networking/devices/ifcfg-wlan0
>> -rw-r--r-- 3 root root 314 May 10 21:21
>> /etc/sysconfig/networking/profiles/default/ifcfg-wlan0
>> -rw-r--r-- 3 root root 314 May 10 21:21
>> /etc/sysconfig/network-scripts/ifcfg-wlan0
>>
>> Can anyone explain just what the heck is going on here?  This is driving
>> me to drink, which I don't mind all that much within limits (2 beers,
>> I'm diabetic), but its making me buy the gas too!
>>
>>     
>
> 2 words "Hard Link".
>
> Do an "ls -i" on the files and you will see they all have the same inode.
>
> Ed
>
>   
Which says that I should be able to edit any one of them and have that 
change be taken globally.  In which case, note this ESSID setting:
[root at diablo etc]# cat `locate ifcfg-wlan0` |grep ESSID
ESSID=MountainHost
ESSID=MountainHost
ESSID=MountainHost

Which s/b fine BUT:

[root at diablo etc]# iwconfig wlan0
wlan0     IEEE 802.11g  ESSID:off/any  Nickname:"diablo.coyote.den"
          Mode:Managed  Frequency:2.457 GHz  Access Point: Not-Associated
          Bit Rate=54 Mb/s   Tx-Power:25 dBm
          RTS thr=2347 B   Fragment thr=2346 B
          Encryption key:4495-9916-B297-EB54-9C26-9592-6F   Security 
mode:restricted
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Kwifimanager can also find the access point by its ESSID, but as you can 
see the key is on and wep, supposed to be off/open.

[root at diablo etc]# cat `locate ifcfg-wlan0` |grep KEY
KEY=open
KEY=open
KEY=open

and an iwlist wlan0 scan shows this:
[root at diablo etc]# iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:14:BF:D5:F8:F6
                    ESSID:"MountainHost"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.457 GHz (Channel 10)
                    Quality:0/100  Signal level:-60 dBm  Noise 
level:-256 dBm
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0
          Cell 02 - Address: 00:0F:66:77:73:A0
                    ESSID:"MountainHost"
                    Protocol:IEEE 802.11g
                    Mode:Managed
                    Frequency:2.417 GHz (Channel 2)
                    Quality:0/100  Signal level:-83 dBm  Noise 
level:-256 dBm
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
                              12 Mb/s; 48 Mb/s
                    Extra:bcn_int=100
                    Extra:atim=0

for the two access points located in this motel building.  There is no 
possibility of a connection until I can convince wlan0 that the fscking 
key is off or open.  That SEEMS like the next step in this little dance 
unless someone more experienced than I can see something else wrong above.



-- 
Cheers, Gene