wicd-devel — wicd

[Wicd-devel] [PATCH] CURSES_REVNO not defined in wicd-1.6.1

[Robby W. <rwo...@sl...>]

I think all the major distribution packagers are already aware of this
from IRC, but I figure it might not hurt to put this out there on the
mail list archives for users who run into it on their own.

If you get this error when pressing 'h' in the curses interface:
  NameError: global name 'CURSES_REVNO' is not defined

then you need to apply the attached patch.

-RW

Re: [Wicd-devel] Bug ? in wicd v1.5.9 -> wicd 1.6.0

[Steve N. <nahn@MIT.EDU>]

Encryption test results - beyond my parsing ability, but looks like my 
target ap gets blacklisted, don't know why -

Dan O'Reilly wrote:
> On Tue, Jun 16, 2009 at 7:58 AM, Steve Nahn<na...@mi...> wrote:
>   
>> ...

>> 2) However, I cannot connect to a WEP encrypted network.  The odd thing
>> here is the iwconfig parameters are set correctly, including the WEP key
>> (using the external tools and wext driver) so after wicd fails with "bad
>> password" I can start dhclient by hand and connect immediately.
>>
>> [nahn@sammy ~]$ sudo iwconfig ra0
>> ra0       Ralink STA  ESSID:"TG374"  Nickname:"RT2860STA"
>>          Mode:Managed  Frequency=2.437 GHz  Access Point: 00:1F:90:D4:A7:90
>>          Bit Rate=54 Mb/s
>>          RTS thr:off   Fragment thr:off
>>          Encryption key:DEAD-BEEF-AD
>>          Link Quality=100/100  Signal level:-52 dBm  Noise level:-81 dBm
>>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>>          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>>
>> So, something in the wpa_supplicant is failing, but I am not exactly
>> sure how to test this.  Any ideas?  I tried using the RALINK legacy
>> driver but it didn't really work, and I've browsed a fair amount of
>> forums but haven't come up with any hints for debugging.  Could it be
>> that wicd just doesn't work for my hardware?
>>     
>
> It sounds like your driver is behaving strangely.  You can try running
> the commands you see in the log by hand to debug, with some minor
> adjustments:
> /sbin/dhclient -v -r eth0
> ifconfig eth0 0.0.0.0
> /sbin/ip route flush dev eth0
> ifconfig eth0 down
> ifconfig eth0 up
> ifconfig ra0 down
> /sbin/dhclient -v -r ra0
> ifconfig ra0 0.0.0.0
> wpa_cli -i ra0 terminate
> /sbin/ip route flush dev ra0
> iwconfig ra0 mode Managed
> ifconfig ra0 up
> wpa_supplicant -i ra0 -c /var/lib/wicd/configurations/001f90d4a790 -D
> wext (run this in its own window, also note the -B option has been
> removed, which causes wpa_supplicant to fork into the background)
> iwconfig ra0 essid TG374
> iwconfig ra0 channel 6
> iwconfig ra0 ap 00:1F:90:D4:A7:90
>
> Then watch the wpa_supplicant window for stuff that looks like an error.
>
>   

Did this, in fact did

 wpa_supplicant -i ra0 -c /var/lib/wicd/configurations/001f90d4a790 -D wext -ddKf wpa_debug2.txt



contents of  debug file:

Initializing interface 'ra0' conf '/var/lib/wicd/configurations/001f90d4a790' dr
iver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/var/lib/wicd/configurations/001f90d4a790' -> '/var/lib/wicd
/configurations/001f90d4a790'
Reading configuration file '/var/lib/wicd/configurations/001f90d4a790'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 3 - start of a new network block
ssid - hexdump_ascii(len=5):
     54 47 33 37 34                                    TG374           
scan_ssid=0 (0x0)
key_mgmt: 0x4
wep_key0 - hexdump(len=5): 84 90 d2 ca ba
wep_tx_keyidx=0 (0x0)
priority=5 (0x5)
Priority group 5
   id=0 ssid='TG374'
Initializing interface (2) 'ra0'
SIOCGIWRANGE: WE(compiled)=22 WE(source)=14 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:22:43:95:c3:99
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface ra0
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
State: DISCONNECTED -> SCANNINGStarting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed 
up initial association
Received 511 bytes of scan results (5 BSSes)
CTRL-EVENT-SCAN-RESULTS 
Selecting BSS from priority group 5
Try to find WPA-enabled AP
0: 00:1f:90:d4:a7:90 ssid='TG374' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
1: 00:1f:33:38:7a:e8 ssid='Parthum' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:18:01:ed:34:57 ssid='0G7D2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
3: 00:1a:70:67:a5:2f ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
4: 00:23:69:33:d5:26 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1f:90:d4:a7:90 ssid='TG374' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   selected non-WPA AP 00:1f:90:d4:a7:90 ssid='TG374'
Trying to associate with 00:1f:90:d4:a7:90 (SSID='TG374' freq=2437 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=5
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 20 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8b04 len=12
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8b04 len=12
Authentication with 00:1f:90:d4:a7:90 timed out.
Added BSSID 00:1f:90:d4:a7:90 into blacklist
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
Scan timeout - try to get results
Received 612 bytes of scan results (6 BSSes)
CTRL-EVENT-SCAN-RESULTS 
Selecting BSS from priority group 5
Try to find WPA-enabled AP
0: 00:1f:90:d4:a7:90 ssid='TG374' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
1: 00:1f:33:38:7a:e8 ssid='Parthum' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:18:01:ed:34:57 ssid='0G7D2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
3: 00:1f:90:ee:bd:81 ssid='54CC2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
4: 00:1a:70:67:a5:2f ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
5: 00:23:69:33:d5:26 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1f:90:d4:a7:90 ssid='TG374' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   selected non-WPA AP 00:1f:90:d4:a7:90 ssid='TG374'
Trying to associate with 00:1f:90:d4:a7:90 (SSID='TG374' freq=2437 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=5
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 20 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8b04 len=12
Authentication with 00:1f:90:d4:a7:90 timed out.
BSSID 00:1f:90:d4:a7:90 blacklist count incremented to 2
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
Scan timeout - try to get results
Received 511 bytes of scan results (5 BSSes)
CTRL-EVENT-SCAN-RESULTS 
Selecting BSS from priority group 5
Try to find WPA-enabled AP0: 00:1f:90:d4:a7:90 ssid='TG374' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - blacklisted
1: 00:1f:33:38:7a:e8 ssid='Parthum' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:18:01:ed:34:57 ssid='0G7D2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
3: 00:1a:70:67:a5:2f ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
4: 00:23:69:33:d5:26 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1f:90:d4:a7:90 ssid='TG374' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - blacklisted
1: 00:1f:33:38:7a:e8 ssid='Parthum' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
2: 00:18:01:ed:34:57 ssid='0G7D2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - SSID mismatch
3: 00:1a:70:67:a5:2f ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - SSID mismatch
4: 00:23:69:33:d5:26 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - SSID mismatch
No APs found - clear blacklist and try again
Removed BSSID 00:1f:90:d4:a7:90 from blacklist (clear)
Selecting BSS from priority group 5
Try to find WPA-enabled AP
0: 00:1f:90:d4:a7:90 ssid='TG374' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
1: 00:1f:33:38:7a:e8 ssid='Parthum' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
2: 00:18:01:ed:34:57 ssid='0G7D2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   skip - no WPA/RSN IE
3: 00:1a:70:67:a5:2f ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
4: 00:23:69:33:d5:26 ssid='linksys' wpa_ie_len=0 rsn_ie_len=0 caps=0x1
   skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:1f:90:d4:a7:90 ssid='TG374' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
   selected non-WPA AP 00:1f:90:d4:a7:90 ssid='TG374'
Trying to associate with 00:1f:90:d4:a7:90 (SSID='TG374' freq=2437 MHz)
Cancelling scan request


and this seems to repeat forever...any insights?

Steve

Re: [Wicd-devel] Bug ? in wicd v1.5.9 -> wicd 1.6.0

[Steve N. <nahn@MIT.EDU>]

Hi Dan et al
  Thanks for the response.  I have two out of three answers requested, 
inline

Dan O'Reilly wrote:
> On Tue, Jun 16, 2009 at 7:58 AM, Steve Nahn<na...@mi...> wrote:
>   
>> 1) Although the Associate method in wnettools.py has changed, I still
>> have the same problem - trying to set the Access point doesn't work -
>> commenting out the Misc.Run() command for this action and I can connect
>> to any open wifi network
>>     
>
> Does iwconfig give you an error if you try to do this by hand?
>
>   
No - I can execute the same commands by hand using iwconfig and 
everything works fine.
>> 2) However, I cannot connect to a WEP encrypted network.  The odd thing
>> here is the iwconfig parameters are set correctly, including the WEP key
>> (using the external tools and wext driver) so after wicd fails with "bad
>> password" I can start dhclient by hand and connect immediately.
>>
>> [nahn@sammy ~]$ sudo iwconfig ra0
>> ra0       Ralink STA  ESSID:"TG374"  Nickname:"RT2860STA"
>>          Mode:Managed  Frequency=2.437 GHz  Access Point: 00:1F:90:D4:A7:90
>>          Bit Rate=54 Mb/s
>>          RTS thr:off   Fragment thr:off
>>          Encryption key:DEAD-BEEF-AD
>>          Link Quality=100/100  Signal level:-52 dBm  Noise level:-81 dBm
>>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>>          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>>
>> So, something in the wpa_supplicant is failing, but I am not exactly
>> sure how to test this.  Any ideas?  I tried using the RALINK legacy
>> driver but it didn't really work, and I've browsed a fair amount of
>> forums but haven't come up with any hints for debugging.  Could it be
>> that wicd just doesn't work for my hardware?
>>     
>
> It sounds like your driver is behaving strangely.  You can try running
> the commands you see in the log by hand to debug, with some minor
> adjustments:
> /sbin/dhclient -v -r eth0
> ifconfig eth0 0.0.0.0
> /sbin/ip route flush dev eth0
> ifconfig eth0 down
> ifconfig eth0 up
> ifconfig ra0 down
> /sbin/dhclient -v -r ra0
> ifconfig ra0 0.0.0.0
> wpa_cli -i ra0 terminate
> /sbin/ip route flush dev ra0
> iwconfig ra0 mode Managed
> ifconfig ra0 up
> wpa_supplicant -i ra0 -c /var/lib/wicd/configurations/001f90d4a790 -D
> wext (run this in its own window, also note the -B option has been
> removed, which causes wpa_supplicant to fork into the background)
> iwconfig ra0 essid TG374
> iwconfig ra0 channel 6
> iwconfig ra0 ap 00:1F:90:D4:A7:90
>
> Then watch the wpa_supplicant window for stuff that looks like an error.
>
>   
Will try this this evening.

> Also, does the encryption key in iwconfig actually show up as DEAD-BEEF-AD?
>   
No - DEAD-BEEF-AD was just a over-paranoid security measure on my part.  
The actual WEP Key is reported correctly by iwconfig

Thanks

Steve

Re: [Wicd-devel] Bug ? in wicd v1.5.9 -> wicd 1.6.0

[Dan O'R. <ore...@gm...>]

On Tue, Jun 16, 2009 at 7:58 AM, Steve Nahn<na...@mi...> wrote:
> 1) Although the Associate method in wnettools.py has changed, I still
> have the same problem - trying to set the Access point doesn't work -
> commenting out the Misc.Run() command for this action and I can connect
> to any open wifi network

Does iwconfig give you an error if you try to do this by hand?

> 2) However, I cannot connect to a WEP encrypted network.  The odd thing
> here is the iwconfig parameters are set correctly, including the WEP key
> (using the external tools and wext driver) so after wicd fails with "bad
> password" I can start dhclient by hand and connect immediately.
>
> [nahn@sammy ~]$ sudo iwconfig ra0
> ra0       Ralink STA  ESSID:"TG374"  Nickname:"RT2860STA"
>          Mode:Managed  Frequency=2.437 GHz  Access Point: 00:1F:90:D4:A7:90
>          Bit Rate=54 Mb/s
>          RTS thr:off   Fragment thr:off
>          Encryption key:DEAD-BEEF-AD
>          Link Quality=100/100  Signal level:-52 dBm  Noise level:-81 dBm
>          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>
> So, something in the wpa_supplicant is failing, but I am not exactly
> sure how to test this.  Any ideas?  I tried using the RALINK legacy
> driver but it didn't really work, and I've browsed a fair amount of
> forums but haven't come up with any hints for debugging.  Could it be
> that wicd just doesn't work for my hardware?

It sounds like your driver is behaving strangely.  You can try running
the commands you see in the log by hand to debug, with some minor
adjustments:
/sbin/dhclient -v -r eth0
ifconfig eth0 0.0.0.0
/sbin/ip route flush dev eth0
ifconfig eth0 down
ifconfig eth0 up
ifconfig ra0 down
/sbin/dhclient -v -r ra0
ifconfig ra0 0.0.0.0
wpa_cli -i ra0 terminate
/sbin/ip route flush dev ra0
iwconfig ra0 mode Managed
ifconfig ra0 up
wpa_supplicant -i ra0 -c /var/lib/wicd/configurations/001f90d4a790 -D
wext (run this in its own window, also note the -B option has been
removed, which causes wpa_supplicant to fork into the background)
iwconfig ra0 essid TG374
iwconfig ra0 channel 6
iwconfig ra0 ap 00:1F:90:D4:A7:90

Then watch the wpa_supplicant window for stuff that looks like an error.

Also, does the encryption key in iwconfig actually show up as DEAD-BEEF-AD?

Re: [Wicd-devel] Bug ? in wicd v1.5.9 -> wicd 1.6.0

[Steve N. <nahn@MIT.EDU>]

Followup, using newly released wicd 1.6.0 on Fedora 10 with RaLink 
RT2860 on ASUS EeePC 1000 HE


1) Although the Associate method in wnettools.py has changed, I still 
have the same problem - trying to set the Access point doesn't work - 
commenting out the Misc.Run() command for this action and I can connect 
to any open wifi network

2) However, I cannot connect to a WEP encrypted network.  The odd thing 
here is the iwconfig parameters are set correctly, including the WEP key 
(using the external tools and wext driver) so after wicd fails with "bad 
password" I can start dhclient by hand and connect immediately.  Here is 
a dump of the debug -

2009/06/16 06:48:54 :: Connecting to wireless network TG374
2009/06/16 06:48:54 :: /sbin/dhclient -v -r eth0
2009/06/16 06:48:54 :: ifconfig eth0 0.0.0.0 
2009/06/16 06:48:54 :: /sbin/ip route flush dev eth0
2009/06/16 06:48:54 :: ifconfig eth0 down
2009/06/16 06:48:54 :: ifconfig eth0 up
2009/06/16 06:48:54 :: Putting interface down
2009/06/16 06:48:54 :: ifconfig ra0 down
2009/06/16 06:48:54 :: Releasing DHCP leases...
2009/06/16 06:48:54 :: /sbin/dhclient -v -r ra0
2009/06/16 06:48:54 :: iwconfig ra0
2009/06/16 06:48:54 :: Setting false IP...
2009/06/16 06:48:54 :: ifconfig ra0 0.0.0.0 
2009/06/16 06:48:54 :: Stopping wpa_supplicant
2009/06/16 06:48:54 :: wpa_cli -i ra0 terminate
2009/06/16 06:48:54 :: Flushing the routing table...
2009/06/16 06:48:54 :: /sbin/ip route flush dev ra0
2009/06/16 06:48:54 :: iwconfig ra0 mode Managed
2009/06/16 06:48:54 :: Putting interface up...
2009/06/16 06:48:54 :: ifconfig ra0 up
2009/06/16 06:48:54 :: enctype is wep-hex
2009/06/16 06:48:54 :: Attempting to authenticate...
2009/06/16 06:48:54 :: ['wpa_supplicant', '-B', '-i', 'ra0', '-c', '/var/lib/wicd/configurations/001f90d4a790', '-D', 'wext']
2009/06/16 06:48:54 :: ['iwconfig', 'ra0', 'essid', 'TG374']
2009/06/16 06:48:54 :: iwconfig ra0 channel 6
2009/06/16 06:48:54 :: iwconfig ra0 ap 00:1F:90:D4:A7:90
2009/06/16 06:48:54 :: WPA_CLI RESULT IS DISCONNECTED
2009/06/16 06:48:55 :: WPA_CLI RESULT IS SCANNING
2009/06/16 06:48:56 :: WPA_CLI RESULT IS SCANNING
2009/06/16 06:48:57 :: WPA_CLI RESULT IS SCANNING
2009/06/16 06:48:58 :: WPA_CLI RESULT IS SCANNING
2009/06/16 06:48:59 :: WPA_CLI RESULT IS SCANNING
2009/06/16 06:49:00 :: found backend in configuration external
2009/06/16 06:49:00 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:01 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:02 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:03 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:04 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:05 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:06 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:08 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:09 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:10 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:11 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:12 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:13 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:14 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:15 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:16 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:17 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:18 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:19 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:20 :: WPA_CLI RESULT IS SCANNING
2009/06/16 06:49:21 :: WPA_CLI RESULT IS SCANNING
2009/06/16 06:49:22 :: WPA_CLI RESULT IS SCANNING
2009/06/16 06:49:23 :: WPA_CLI RESULT IS SCANNING
2009/06/16 06:49:24 :: WPA_CLI RESULT IS SCANNING
2009/06/16 06:49:25 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:26 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:27 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:28 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:29 :: WPA_CLI RESULT IS ASSOCIATING
2009/06/16 06:49:30 :: wpa_supplicant authentication may have failed.
2009/06/16 06:49:30 :: exiting connection thread
2009/06/16 06:49:30 :: Sending connection attempt result bad_pass
2009/06/16 06:49:30 :: ifconfig eth0
...


[nahn@sammy ~]$ sudo iwconfig ra0
ra0       Ralink STA  ESSID:"TG374"  Nickname:"RT2860STA"
          Mode:Managed  Frequency=2.437 GHz  Access Point: 00:1F:90:D4:A7:90   
          Bit Rate=54 Mb/s   
          RTS thr:off   Fragment thr:off
          Encryption key:DEAD-BEEF-AD
          Link Quality=100/100  Signal level:-52 dBm  Noise level:-81 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

[nahn@sammy ~]$ sudo dhclient -v ra0
Internet Systems Consortium DHCP Client 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/ra0/00:22:43:95:c3:99
Sending on   LPF/ra0/00:22:43:95:c3:99
Sending on   Socket/fallback
DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 5
DHCPOFFER from 192.168.1.1
DHCPREQUEST on ra0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.4 -- renewal in 38931 seconds.


So, something in the wpa_supplicant is failing, but I am not exactly 
sure how to test this.  Any ideas?  I tried using the RALINK legacy 
driver but it didn't really work, and I've browsed a fair amount of 
forums but haven't come up with any hints for debugging.  Could it be 
that wicd just doesn't work for my hardware?

Thanks

Steve

Steve Nahn wrote:
> Hi
>   I just downloaded the stable version of wcid for my ASUS 1000HE 
> running Fedora 10.  I find when trying to connect to some wireless 
> (with essid MIT for instance) wcdi erases the current essid a,d never 
> executes the command to associate the correct essid.  The status text 
> is ":Obtaining an IP address" but by executing iwconfig by hand I can 
> see the parameters are not set.  In addition, if I set the parameters 
> by hand using iwconfig, suddenly the text changes to "MIT:Obtaining an 
> IP address"  where MIT is the essid I set by hand, and the connection 
> succeeds.
>
> I believe this is because of a problem with the Associate method in 
> the wnettools.py class, or possibly in the Run() method of the misc.py 
> class.  If I look at the log, I see
>
> 2009/05/29 18:05:19 :: Connecting to wireless network MIT
> 2009/05/29 18:05:19 :: Executing pre-connection script
> 2009/05/29 18:05:19 :: Putting interface down
> 2009/05/29 18:05:19 :: ifconfig ra0 down
> 2009/05/29 18:05:19 :: Releasing DHCP leases...
> 2009/05/29 18:05:19 :: Setting false IP...
> 2009/05/29 18:05:19 :: ifconfig ra0 0.0.0.0 
> 2009/05/29 18:05:19 :: ifconfig eth0 0.0.0.0 
> 2009/05/29 18:05:19 :: Stopping wpa_supplicant and any DHCP clients
> 2009/05/29 18:05:19 :: killall wpa_supplicant
> 2009/05/29 18:05:19 :: Flushing the routing table...
> 2009/05/29 18:05:19 :: ip route flush dev ra0
> 2009/05/29 18:05:19 :: ip route flush dev eth0
> 2009/05/29 18:05:19 :: Putting interface up...
> 2009/05/29 18:05:19 :: ifconfig ra0 up
> 2009/05/29 18:05:19 :: iwconfig ra0 mode Managed
> 2009/05/29 18:05:19 :: ['iwconfig', 'ra0', 'essid', 'MIT', 'channel', '11', 'ap', '00:0F:66:75:18:46']
> 2009/05/29 18:05:19 :: Running DHCP
> 2009/05/29 18:05:19 :: /sbin/dhclient ra0
> 2009/05/29 18:05:23 :: iwconfig ra0
>
>   
> The line
> 2009/05/29 18:05:19 :: ['iwconfig', 'ra0', 'essid', 'MIT', 'channel', '11', 'ap', '00:0F:66:75:18:46']
>
>   
> should really translate to
>
> 2009/05/29 18:05:19 :: iwconfig ra0 essid MIT channel 11 ap 00:0F:66:75:18:46
>
> The offending code is in the Associate method of wnettools.py
>
> """
> if not self.iface: return False
> cmd = ['iwconfig', self.iface, 'essid', essid]
> if channel:
>  cmd.extend(['channel', str(channel)])
>  if bssid:
>   cmd.extend(['ap', bssid])
>  if self.verbose: print cmd
>  misc.Run(cmd)
>
>   
> It appears that if I just remove
>   cmd.extend(['ap', bssid])
> everything works fine, so I guess python is having some trouble there 
> - the Popen command is translating the colon-separated numbers in a 
> strange way.  If I do it from the command line, it works fine.
> I am running Python 2.5.2 and in fact I think it looks like this 
> should work so I don't really know why it fails yet, but I am not a 
> Python programmer.  The output of python subprocess.py looks like:
> [root@sammy wicd]# python ../../subprocess.py
> Process list:
>   PID TTY          TIME CMD
>  5440 pts/0    00:00:00 su
>  5451 pts/0    00:00:01 bash
>  8118 pts/0    00:00:00 python
>  8119 pts/0    00:00:00 ps
>
> uid=100 gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> Looking for 'hda'...
> 'hda_codec: Unknown model for ALC269, trying auto-probe from BIOS...\nALSA sound/pci/hda/hda_codec.c:3021: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0)\nALSA sound/pci/hda/hda_codec.c:3025:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)\nALSA sound/pci/hda/hda_codec.c:3029:    hp_outs=1 (0x15/0x0/0x0/0x0/0x0)\nALSA sound/pci/hda/hda_codec.c:3030:    mono: mono_out=0x0\nALSA sound/pci/hda/hda_codec.c:3038:    inputs: mic=0x12, fmic=0x18, line=0x0, fline=0x0, cd=0x0, aux=0x0\n'
>
> Trying a weird file...
> The file didn't exist.  I thought so...
> Child traceback:
> Traceback (most recent call last):
>   File "../../subprocess.py", line 1057, in _execute_child
>     os.execvp(executable, args)
>   File "/usr/lib/python2.5/os.py", line 353, in execvp
>     _execvpe(file, args)
>   File "/usr/lib/python2.5/os.py", line 377, in _execvpe
>     func(file, *argrest)
> OSError: [Errno 2] No such file or directory
>
> [root@sammy wicd]# 
>
>
>   
> Since I doubt I'll ever need to specify the access point, I'll leave 
> it as is for now but if someone knows the fix, that would be great.  I 
> also believe others might be suffering from the same bug so posting 
> this to the appropriate bug report is a good idea, but I am not 
> registered so I trust a developer  to do it.
>
> Be nice to know if this were fixed...
>
>
> Stev e

Re: [Wicd-devel] support for setting phase1/phase2 in wpa_supplicanf conf file

[Norbert P. <pre...@lo...>]

On Mo, 08 Jun 2009, Adam Blackburn wrote:
> I think what you want is to make a new encryption template. Please see
> http://wicd.sourceforge.net/templates.php for more information about
> that. If any part isn't clear, please don't hesitate to ask.

Thanks, that the perfect hint, I managed, the explanations are fine.

Thanks a lot

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <pre...@lo...>        Vienna University of Technology
Debian Developer <pre...@de...>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
BALLYCUMBER
One of the six half-read books lying somewhere in your bed.
			--- Douglas Adams, The Meaning of Liff

Re: [Wicd-devel] support for setting phase1/phase2 in wpa_supplicanf conf file

[Adam B. <com...@gm...>]

Hi,

I think what you want is to make a new encryption template. Please see
http://wicd.sourceforge.net/templates.php for more information about
that. If any part isn't clear, please don't hesitate to ask.

Regards,
Adam

On 6/8/09, Norbert Preining <pre...@lo...> wrote:
> Hi all,
>
> first of all, thanks for the great program, I have completely switched
> from hand maintained wpa_supplicant config file to wicd!
>
> One question I have is whether there is a way to configure phase1/phase2
> settings of the wpa_supplicant.conf file?
>
> I have to connect to an accesspoint with the following settings:
> network={
>    ssid="XXXXXXX"
>    scan_ssid=1
>    key_mgmt=WPA-EAP
>    eap=PEAP
>    identity="username"
>    password="pass"
>    phase1="peaplabel=0"
>    phase2="auth=MSCHAPV2"
> }
>
> I use "PEAP with GTC" and get mostly the right thing, but not really.
>
> Is there anything else I can do to get something like the above?
>
> Thanks a lot and all the best
>
> Norbert
>
> -------------------------------------------------------------------------------
> Dr. Norbert Preining <pre...@lo...>        Vienna University of
> Technology
> Debian Developer <pre...@de...>                         Debian TeX
> Group
> gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5
> B094
> -------------------------------------------------------------------------------
> Pages one and two [of Zaphod's presidential speech] had
> been salvaged by a Damogran Frond Crested Eagle and had
> already become incorporated into an extraordinary new form
> of nest which the eagle had invented. It was constructed
> largely of papier mache and it was virtually impossible for
> a newly hatched baby eagle to break out of it. The Damogran
> Frond Crested Eagle had heard of the notion of survival of
> the species but wanted no truck with it.
>                  --- An example of Damogran wildlife.
>                  --- Douglas Adams, The Hitchhikers Guide to the Galaxy
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> wicd-devel mailing list
> wic...@li...
> https://lists.sourceforge.net/lists/listinfo/wicd-devel
>

[Wicd-devel] support for setting phase1/phase2 in wpa_supplicanf conf file

[Norbert P. <pre...@lo...>]

Hi all,

first of all, thanks for the great program, I have completely switched
from hand maintained wpa_supplicant config file to wicd!

One question I have is whether there is a way to configure phase1/phase2
settings of the wpa_supplicant.conf file?

I have to connect to an accesspoint with the following settings:
network={   
   ssid="XXXXXXX"
   scan_ssid=1
   key_mgmt=WPA-EAP
   eap=PEAP
   identity="username"
   password="pass"
   phase1="peaplabel=0"
   phase2="auth=MSCHAPV2"
}

I use "PEAP with GTC" and get mostly the right thing, but not really.

Is there anything else I can do to get something like the above?

Thanks a lot and all the best

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <pre...@lo...>        Vienna University of Technology
Debian Developer <pre...@de...>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
Pages one and two [of Zaphod's presidential speech] had
been salvaged by a Damogran Frond Crested Eagle and had
already become incorporated into an extraordinary new form
of nest which the eagle had invented. It was constructed
largely of papier mache and it was virtually impossible for
a newly hatched baby eagle to break out of it. The Damogran
Frond Crested Eagle had heard of the notion of survival of
the species but wanted no truck with it.
                 --- An example of Damogran wildlife.
                 --- Douglas Adams, The Hitchhikers Guide to the Galaxy

Re: [Wicd-devel] Problems with suspend.py

[Robby W. <rwo...@sl...>]

On Mon, 26 Jan 2009 23:58:42 +0000
ore...@gm... wrote:

> I just made a commit to the mainline experimental branch that I think
> will fix this issue. You can grab it and try that out or wait for
> Robby to rebase his branch.


Done; in the usual place:
http://slackware.com/~rworkman/wicd/

-RW

Re: [Wicd-devel] Problems with suspend.py

[<ore...@gm...>]

I just made a commit to the mainline experimental branch that I think will  
fix this issue. You can grab it and try that out or wait for Robby to  
rebase his branch.

On Jan 26, 2009 4:52pm, alkos333 <me...@al...> wrote:
> I have installed r253_rworkman and getting the following when I run  
suspend.py:
>
>
>
>
>
> root@tpt60:~# /usr/lib/wicd/suspend.py
>
> Exception caught: org.freedesktop.DBus.Python.TypeError: Traceback
>
> (most recent call last):
>
> File "/usr/lib/python2.5/site-packages/dbus/service.py", line 702,
>
> in _message_cb
>
> retval = candidate_method(self, *args, **keywords)
>
> File "/usr/lib/wicd/wicd-daemon.py", line 290, in Disconnect
>
> self.wifi.Disconnect()
>
> File "/usr/lib/python2.5/site-packages/wicd/networking.py", line
>
> 688, in Disconnect
>
> Controller.Disconnect(self)
>
> File "/usr/lib/python2.5/site-packages/wicd/networking.py", line
>
> 184, in Disconnect
>
> self.wiface.GetBSSID( iwconfig ),
>
> TypeError: GetBSSID() takes exactly 1 argument (2 given)
>
>
>
> Error setting suspend.
>
>
>
>
>
>
>
>
>
> Any ideas?
>
>
>
> --
>
>
>
> Bill Cosby - "A word to the wise ain't necessary - it's the stupid
>
> ones that need the advice."
>
>
>
>  
------------------------------------------------------------------------------
>
> This SF.net email is sponsored by:
>
> SourcForge Community
>
> SourceForge wants to tell your story.
>
> http://p.sf.net/sfu/sf-spreadtheword
>
> _______________________________________________
>
> wicd-devel mailing list
>
> wic...@li...
>
> https://lists.sourceforge.net/lists/listinfo/wicd-devel
>

[Wicd-devel] Problems with suspend.py

[alkos333 <me...@al...>]

I have installed r253_rworkman and getting the following when I run suspend.py:


root@tpt60:~# /usr/lib/wicd/suspend.py
Exception caught: org.freedesktop.DBus.Python.TypeError: Traceback
(most recent call last):
  File "/usr/lib/python2.5/site-packages/dbus/service.py", line 702,
in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/wicd/wicd-daemon.py", line 290, in Disconnect
    self.wifi.Disconnect()
  File "/usr/lib/python2.5/site-packages/wicd/networking.py", line
688, in Disconnect
    Controller.Disconnect(self)
  File "/usr/lib/python2.5/site-packages/wicd/networking.py", line
184, in Disconnect
    self.wiface.GetBSSID( iwconfig ),
TypeError: GetBSSID() takes exactly 1 argument (2 given)

Error setting suspend.




Any ideas?

-- 

Bill Cosby  - "A word to the wise ain't necessary - it's the stupid
ones that need the advice."

Re: [Wicd-devel] [RESEND] [Wicd-1.5.8]Unknown distribution, no init file installed

[Predrag I. <pre...@na...>]

On Wed, 21 Jan 2009 13:04:15 -0600
Robby Workman wrote:
>
>Does this look right for you?
>
>=== modified file 'setup.py'
>--- setup.py	2009-01-04 02:47:35 +0000
>+++ setup.py	2009-01-21 18:55:10 +0000
>@@ -148,6 +148,8 @@
>         elif os.access('/etc/pld-release', os.F_OK):
>             self.init = '/etc/rc.d/init.d/'
>             self.initfile = 'init/pld/wicd'
>+        elif os.access('/usr/bin/crux', os.F_OK):
>+            self.init = '/etc/rc.d/'
>         else:
>             self.init = 'FAIL'
>             self.initfile = 'FAIL'
>
>
>-RW

Works fine here.

[...]
python setup.py configure --mandir=/usr/man --no-install-kde --no-install-docs
[...]
initfile is init/default/wicd
initfilename is wicd
[...]
python setup.py build
Using init file ('/etc/rc.d/', 'init/default/wicd')

Pedja
-- 
Come to the dark side, my child. There is nutella. -Samwise

Re: [Wicd-devel] [RESEND] [Wicd-1.5.8]Unknown distribution, no init file installed

[Robby W. <rwo...@sl...>]

On Wed, 21 Jan 2009 18:19:23 +0100
Predrag Ivanovic <pre...@na...> wrote:

> Dan wrote:  
> > Does Crux have a file in /etc/ that identifies it as the distro
> > being
> >used? Something like /etc/crux-release? I'll add it to the list of
> >distros we check for.  
> 
> No, it doesn't have a file to identify itself, but the output of
> '/usr/bin/crux', which is   "CRUX version 2.5" Maybe you could use
> that?  


Does this look right for you?

=== modified file 'setup.py'
--- setup.py	2009-01-04 02:47:35 +0000
+++ setup.py	2009-01-21 18:55:10 +0000
@@ -148,6 +148,8 @@
         elif os.access('/etc/pld-release', os.F_OK):
             self.init = '/etc/rc.d/init.d/'
             self.initfile = 'init/pld/wicd'
+        elif os.access('/usr/bin/crux', os.F_OK):
+            self.init = '/etc/rc.d/'
         else:
             self.init = 'FAIL'
             self.initfile = 'FAIL'


-RW

[Wicd-devel] [RESEND] [Wicd-1.5.8]Unknown distribution, no init file installed

[Predrag I. <pre...@na...>]

[I apologize in advance, but I wasn't subscribed to this list when I sent the message[1], and I forgot to  set ReplyTo: field to 
my mail adress, so i didn't get followup by Dan O'Reilly, and this is reply to it.Sorry ]

Dan wrote:
> Does Crux have a file in /etc/ that identifies it as the distro being
>used? Something like /etc/crux-release? I'll add it to the list of
>distros we check for.

No, it doesn't have a file to identify itself, but the output of '/usr/bin/crux', which is   "CRUX version 2.5" 
Maybe you could use that?

[1][http://sourceforge.net/mailarchive/forum.php?thread_name=20090112150827.15490fd8%40deus.prime.one&forum_name=wicd-devel]

Pedja

Re: [Wicd-devel] [Wicd-1.5.8]Unknown distribution, no init file installed

[Dan O'R. <ore...@gm...>]

Does Crux have a file in /etc/ that identifies it as the distro being
used? Something like /etc/crux-release?  I'll add it to the list of
distros we check for.

I'll take a look at the setup.py initfile issues as well.

On Mon, Jan 12, 2009 at 9:08 AM, Predrag Ivanovic <pre...@na...> wrote:
>
> Hi.
> I made a port of Wicd-1.5.8 for Crux(www.crux.nu), distribution that I use.
> When I ran configure:
> 'python setup.py configure --init=/etc/rc.d --initfile=wicd --initfilename=wicd
> --mandir=/usr/man --no-install-kde --no-install-docs'
>
> this warning occured:
> "WARNING: Unable to detect the distribution in use.  If you have specified
> --init and --initfile, configure will continue.  Please report this warning,
> along with the name of your distribution, to the wicd developers.
> "
> so here I am :)
>
> Default init file is fine to use with Crux, so I added it manually, since it doesn't get installed.
> btw, configure --help states  --initfilename switch as 'do not use', but if it's
> not defined, throws a FAIL.
>
> Great work with Wicd ,btw, I like it better than NetworkManager.
> It looks cleaner and more elegant, imho.
>
> Pedja
> --
>  Think of Linux security as a sort of "wedding cake".
>  The two figures at the top are the root account.
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> wicd-devel mailing list
> wic...@li...
> https://lists.sourceforge.net/lists/listinfo/wicd-devel
>

[Wicd-devel] [Wicd-1.5.8]Unknown distribution, no init file installed

[Predrag I. <pre...@na...>]

Hi.
I made a port of Wicd-1.5.8 for Crux(www.crux.nu), distribution that I use.
When I ran configure:
'python setup.py configure --init=/etc/rc.d --initfile=wicd --initfilename=wicd 
--mandir=/usr/man --no-install-kde --no-install-docs'

this warning occured:
"WARNING: Unable to detect the distribution in use.  If you have specified
--init and --initfile, configure will continue.  Please report this warning,
along with the name of your distribution, to the wicd developers.
"
so here I am :) 

Default init file is fine to use with Crux, so I added it manually, since it doesn't get installed.
btw, configure --help states  --initfilename switch as 'do not use', but if it's 
not defined, throws a FAIL.

Great work with Wicd ,btw, I like it better than NetworkManager.
It looks cleaner and more elegant, imho.  

Pedja
-- 
 Think of Linux security as a sort of "wedding cake".
 The two figures at the top are the root account.

[Wicd-devel] Now, Wicd is in Pardus!

[Gökmen G. <gkm...@gm...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi all,<br>
Can we update the <a href="cid:par...@gm..."
 moz-do-not-send="false">download page</a> for Pardus?<br>
<br>
--------------------------------------&gt;&gt;<br>
<b>Installing Wicd in Pardus<br>
</b>Wicd exists in <a href="cid:par...@gm..."
 moz-do-not-send="false"><b>contrib</b> repository</a>. After you have
added contrib repository, all you need to do is:<br>
<font face="Bitstream Vera Sans Mono">    sudo pisi it wicd</font><br>
You can also install the package by using Pisi Package Manager.<br>
--------------------------------------&gt;&gt;<br>
<br>
Kind Regards..<br>
</body>
</html>

[Wicd-devel] Solid Wicd Backend

[Dario F. <drf...@gm...>]

Hello List,

Let me introduce myself: my name is Dario, I am a KDE hacker. I am writing you 
since I'm attempting to write a Wicd Backend for Solid.

I don't know if you already know what Solid is: in case you don't, it's the 
hardware abstraction framework of KDE4. It has a networking part too, that (at 
the moment) has networkmanager as its unique backend. I use Wicd since ages, 
and given the fact I consider it superior to NM, I thought Solid definitely 
should give users a wider choice of backends.

So, what does that mean? The most visible example would be that the upcoming 
network manager applet will be able to use Wicd as its backend through Solid. 
This would mean you'll get another client fully integrated with KDE4. 
Moreover, all applications using network calls will interface with Wicd.

I have already started coding something. I am using C++, so I'm relying on the 
DBus API only. You can find first bits of code here: 
http://github.com/drf/wicd-solid/tree/master

At the moment, I am looking mostly at gui.py and wicd_client.py to find my way 
through the API, though I could surely use some more help. I'd like to know if 
you documented somehow your DBus API, or if you would be willing to give a 
small amount of help, at least on getting me started with your code :)

I am already on #wicd, my nick is drf__. I'm screening IRC remotely, so you'll 
always find me in; feel free to ping me any time.

Cheers
Dario

[Wicd-devel] Patch against trunk - only one DNS entry may be accepted with it.

[Mateusz K. <mat...@an...>]

I am using only one dns server - 127.0.0.1.
Regards,

-- 
Mateusz Korniak

Re: [Wicd-devel] Minor problems

[Robby W. <rwo...@sl...>]

Disclaimer: I'm not a wicd developer, so nothing I say should be
construed as definitive.

mark damerell wrote:
> In general I am very happy with wicd, especially after other wireless
> S-ware failed. Please could you kindly consider the following?
> 
> 
> 1. Installing tray icon. In the download page,
> 
> http://wicd.sourceforge.net/download.php
> 
> section
> 
> Installing Wicd in Ubuntu
> 
> it says:
> 
> go to System > Preferences > Sessions
> 
> which does not exist (xubuntu 8.04). The correct
> place is
> 
> Applications > settings >
> settings manager > autostarted Apps


This should not be an issue in the "soon to be released" 1.5.0
version of wicd.  It will install the proper file(s) to have the
tray startup for all users on the system, even regardless of what
desktop environment they choose.


> 2. Is there any way for the sudoer to
> install the tray icon for all users
> instead of one at a time?


See above.  :)


> 3. Clicking right on the tray icon and "about"
> tells you it is icon version 0.2.  Please could
> it also display the version of wicd?


Hmm, interesting.  I'd never noticed the (possible) discrepancy there
with the daemon and the actual client.


> 4. You probably already know that
> early in July there were some updates for Ubuntu
> that caused wireless networking to fail. I think this
> is now fixed, but it revealed what I believe to be a
> problem in WICD. To show this:
> 
> start with wireless working; shutdown the PC; switch
> off wireless card and reboot.
> 
> The Wicd manager gives the error "no wireless network
> found" which I believe is misleading. I think it ought
> to say something like "wireless card not working".


I think Dan put something in the daemon to return a (hopefully)
more useful error message, but I may be wrong.


Can you try the latest 1.5.0_rc10 release and verify that it works
as expected on your system?   http://wicd.net/latest

-RW

[Wicd-devel] Minor problems

[mark d. <mar...@go...>]

In general I am very happy with wicd, especially after other wireless
S-ware failed. Please could you kindly consider the following?


1. Installing tray icon. In the download page,

http://wicd.sourceforge.net/download.php

section

Installing Wicd in Ubuntu

it says:

go to System > Preferences > Sessions

which does not exist (xubuntu 8.04). The correct
place is

Applications > settings >
settings manager > autostarted Apps

2. Is there any way for the sudoer to
install the tray icon for all users
instead of one at a time?

3. Clicking right on the tray icon and "about"
tells you it is icon version 0.2.  Please could
it also display the version of wicd?

4. You probably already know that
early in July there were some updates for Ubuntu
that caused wireless networking to fail. I think this
is now fixed, but it revealed what I believe to be a
problem in WICD. To show this:

start with wireless working; shutdown the PC; switch
off wireless card and reboot.

The Wicd manager gives the error "no wireless network
found" which I believe is misleading. I think it ought
to say something like "wireless card not working".

Thank you, Mark

[Wicd-devel] [PATCH] Test for some files in postinst

[Robby W. <rwo...@sl...>]

The attached patch tests for the existence of some things
that are not present on all distributions (at least not
Slackware) to prevent seeing error messages on install.

This is really a sub-optimal solution in the long term,
as any later changes for easier packaging will ideally make
this file unnecessary, but for now, here you are :)

[Wicd-devel] [PATCH] Add restart() and rewrite init script

[Robby W. <rwo...@sl...>]

The attached patch adds a restart function to wicd's init script
and rewrites the script to use "case $1 in..." logic instead of
individual if [ ... ] tests.

Re: [Wicd-devel] wich.py patch

[Dan O'R. <ore...@gm...>]

Thanks, I forgot we were renaming that too.

On Thu, May 8, 2008 at 1:48 PM, Helber Maciel Guerra <hel...@gm...> wrote:
> This file continues without patch...
>
> Helber Maciel Guerra
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> wicd-devel mailing list
> wic...@li...
> https://lists.sourceforge.net/lists/listinfo/wicd-devel
>
>

[Wicd-devel] wich.py patch

[Helber M. G. <hel...@gm...>]

This file continues without patch...

Helber Maciel Guerra