I've encountered a strange problem logging into my local Wifi.
There are 2 services I can use : (1) the household service,
part of my landlord's home-office system ; (2) my cell-phone's hotspot.
(2) is ok, but trying to use (1) has been offering challenges.

First, there's no problem with my hardware or that of my landlord
nor with 'wpa_supplicant' installed on my Gentoo system AFAIK.
The problem aros when I tried to log into (1)
after a power outage caused my landlord to restart his box,
at which time he renamed the service with a slightly different password ;
he's intelligent + friendly, but not upto fine-tuning it.
I have updated the config file below to match the new strings.

Earlier in the year, it was straightforward. I have a config file :

#wpa_supplicant-gr.conf : 241207

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel

network={
ssid="<name of landlord's service>"
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="<password>"
priority=5
}

This hasn't changed : it used to log me in when I rebooted.
Now it doesn't : for some reason, it scans, but finds nothing.
The config file for my cell-phone hotspot is the same & also unchanged.

However, I can use 'wpa_gui' with a bit of fussing & editing.
Currently, it shows the correct adapter + service name & below it lists :

Status : completed (station)
Last message : <blank>
Authentication : WPA2-PSK
Encryption : CCMP + TKIP
SSID : <service name>
BSSID : < 12 hex digits >
IP address : < 11 digits >

I can't see any difference between the 2 lists of config items.
I do have to reset it via an 'edit' menu after rebooting,
esp to restate the password, which is a nuisance,
but it succeeds in getting thro' to the service.

Can anyone suggest what mb wrong with the 1st method ?

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatcadotinterdotnet

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Philip,

On Monday 23 December 2024 23:35:21 GMT Philip Webb wrote:

I've encountered a strange problem logging into my local Wifi.
There are 2 services I can use : (1) the household service,
part of my landlord's home-office system ; (2) my cell-phone's hotspot.
(2) is ok, but trying to use (1) has been offering challenges.

First, there's no problem with my hardware or that of my landlord
nor with 'wpa_supplicant' installed on my Gentoo system AFAIK.
The problem aros when I tried to log into (1)
after a power outage caused my landlord to restart his box,
at which time he renamed the service with a slightly different password ; he's intelligent + friendly, but not upto fine-tuning it.
I have updated the config file below to match the new strings.

Did he *only* change the SSID and password, or did he also change the encryption and key management method?

Earlier in the year, it was straightforward. I have a config file :

#wpa_supplicant-gr.conf : 241207

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel

network={
ssid="<name of landlord's service>"
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="<password>"
priority=5
}

This hasn't changed : it used to log me in when I rebooted.
Now it doesn't : for some reason, it scans, but finds nothing.
The config file for my cell-phone hotspot is the same & also unchanged.

Check there are no empty spaces left at the end of the strings in any entries you edited in your wpa_supplicant.conf.

Check you have not altered the access rights of the file:

chmod -v 600 /etc/wpa_supplicant/wpa_supplicant.conf

However, I can use 'wpa_gui' with a bit of fussing & editing.
Currently, it shows the correct adapter + service name & below it lists :

Status : completed (station)
Last message : <blank>
Authentication : WPA2-PSK
Encryption : CCMP + TKIP
SSID : <service name>
BSSID : < 12 hex digits >
IP address : < 11 digits >

I can't see any difference between the 2 lists of config items.
I do have to reset it via an 'edit' menu after rebooting,
esp to restate the password, which is a nuisance,
but it succeeds in getting thro' to the service.

Can anyone suggest what mb wrong with the 1st method ?

The first method looks good to me, beyond the points I mentioned above.

You can check what the landlord's AP wants to use by running wpa_cli in a terminal:

scan

will start scanning for APs. A few seconds ago you will have some results to peruse:

scan_results

The landlord's BSSID will list what encryption his AP has been configured to use; e.g.:

01:23:45:67:89:01 2427 0 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP] LL's-SSID

Enter 'quit' to exit the wpa_cli once you made a note of the above. You'll need to reflect what the wpa_cli results revealed in your wpa_supplicant.conf.

If you want to be able to edit the AP configuration and save the results using your wpa_gui directly, you have to add in your wpa_supplicant.conf: ====================================================

# Whether to allow wpa_supplicant to update (overwrite) configuration
#
# This option can be used to allow wpa_supplicant to overwrite configuration
# file whenever configuration is changed (e.g., new network block is added
# with wpa_cli or wpa_gui, or a password is changed). This is required for
# wpa_cli/wpa_gui to be able to store the configuration changes permanently.
# Please note that overwriting configuration file will remove the comments
# from it.

update_config=1

===============

Please heed the above warning regarding commented sections in your wpa_supplicant.conf being removed.

HTH.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmdqkq4ACgkQseqq9sKV ZxknQA//f5dfvzsq69n+lFhK1hUpSffSSOhYPhPbxCrVx70vnSsJL4ImxAzYbjD4 O2b5YDdAK6LO0xdZsjxmJ/QkaKhyMFBI22eHtG3CoNOIoC+G1R8a+pBEj5Ieh3Af ub3MmhXZOs21YeJmXj0ExokNZCRvFhIKEhGvfT3psDlu9C5DRhv7Nr0kxquorkhd Fk9T4LNFC6EiiPghclNrGeidG7JIJWmrCimINPXL5khP4yqUCFfs0tDW9eC9C00v 00pSYjpG8NAkI2okSlFi9jJVcriVCEuLbwtIqRplReh0ZmG4RaScMcbTToNIcuv1 rUuT0GCkLIvjC2ROkcEGK0CvygvLnoS62RtNNTD4O7eeMR4VjZd/wzjMYkt/ZLxU eABCRM/U2GiI3T48gQ+G9qsSUmqxvQK6wMMl6WDt6TLDRNJ65zoK1BSpATUeniWn EaBoaUMqUS7EurOf2ubOoE5Cg1JDr78nWoxy6SuOECaGPfuP5ihtwfDsTCTj7LDg DTVa1SoyNJNU1QZdqXECxOPd2+pRDhZqvg6IYdDcwvqA0LanyLOebIvZV5kH9F7e iTtcXMTStjovkK6TcggABLcyB1uccYueNOQYaa63OveuydmEOqhdQ3zWqXOOxnb+ g/weGJ9fFAyjBuwsvpJvKwXmg02fFx9Lr6NS28R02WxWp7hOqKs=
=kkvw
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

241224 Michael wrote:

On Monday 23 December 2024 23:35:21 GMT Philip Webb wrote:

I've encountered a strange problem logging into my local Wifi.
There are 2 services I can use : (1) the household service,
part of my landlord's home-office system ; (2) my cell-phone's hotspot.
(2) is ok, but trying to use (1) has been offering challenges.
First, there's no problem with my hardware or that of my landlord
nor with 'wpa_supplicant' installed on my Gentoo system AFAIK.
The problem arose when I tried to log into (1)
after a power outage caused my landlord to restart his box,
at which time he renamed the service with a slightly different password ;
he's intelligent + friendly, but not upto fine-tuning it.
I have updated the config file below to match the new strings.

Did he *only* change the SSID and password
or did he also change the encryption and key management method ?

Only the former : he's not skilled enough to do the latter.
I suspect that originally someone set it up for him
& altered some default setting(s), then when he restarted it,
the default setting(s) returned & that's not working with my software.

Check there are no empty spaces left at the end of the strings
in any entries you edited in your wpa_supplicant.conf.

There are none.

Check you have not altered the access rights of the file :
chmod -v 600 /etc/wpa_supplicant/wpa_supplicant.conf

The permission is '644', which is ok for my cellpbone's hotspot.

I can use 'wpa_gui' with a bit of fussing & editing.

Currently, it shows the correct adapter + service name & below it lists :

Status : completed (station)
Last message : <blank>
Authentication : WPA2-PSK
Encryption : CCMP + TKIP
SSID : <service name>
BSSID : < 12 hex digits >
IP address : < 11 digits >

The first method looks good to me, beyond the points I mentioned above.
Check what the landlord's AP wants to use by running wpa_cli in a terminal:
> scan
will start scanning for APs. after few secs, you will have some results :
> scan_results

It shows nothing : see output below.

The landlord's BSSID will list
what encryption his AP has been configured to use; e.g.:

01:23:45:67:89:01 2427 0 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP]

LL's-SSID

You'll need to reflect what the wpa_cli results revealed
in your wpa_supplicant.conf.
If you want to be able to edit the AP configuration
and save the results using your wpa_gui directly,
you have to add in your wpa_supplicant.conf: ====================================================
# Whether to allow wpa_supplicant to update (overwrite) configuration
# This option can be used to allow wpa_supplicant
# to overwrite configuration file whenever configuration is changed
# (e.g., new network block is added with wpa_cli or wpa_gui
# or a password is changed). This is required for wpa_cli/wpa_gui
# to be able to store the configuration changes permanently.
# Please note that overwriting configuration file will remove comments.
update_config=1
HTH.

Thanks for your usually very helpful suggestions (smile).
Here is the output via 'wpa_cli' as I start & stop Wifi.
I connect & disconnect with my cell-phone 'Athene' + landlord's service,
whose name is 'Watch Iovedocs ... ',
& which I have to access via 'wpa_gui' (I used 2 terminals).

output of 'wpa_cli' as I wake up Athene's service :

<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-NETWORK-NOT-FOUND
... these lines occur frequently : duplicates deleted ...
<3>CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
<3>CTRL-EVENT-SCAN-RESULTS
<3>SME: Trying to authenticate with 16:c4:a5:6b:1e:6e (SSID='Athenes Hot Spot' freq=5745 MHz)
<3>Trying to associate with 16:c4:a5:6b:1e:6e (SSID='Athenes Hot Spot' freq=5745 MHz)
<3>Associated with 16:c4:a5:6b:1e:6e
<3>CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
<3>WPA: Key negotiation completed with 16:c4:a5:6b:1e:6e [PTK=CCMP GTK=CCMP]
<3>CTRL-EVENT-CONNECTED - Connection to 16:c4:a5:6b:1e:6e completed [id=0 id_str=]
<3>CTRL-EVENT-DISCONNECTED bssid=16:c4:a5:6b:1e:6e reason=1
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-NETWORK-NOT-FOUND

I tried queries :

> status
wpa_state=SCANNING
address=f8:89:d2:7a:26:9b
> ifname
wlp5s0
> set
Invalid SET command - at least 2 arguments are required.
> pmksa
Index / AA / PMKID / expiration (in seconds) / opportunistic
> list_networks
network id / ssid / bssid / flags
0 watch iovedocs on YouTube any

using wpa_gui to start/stop landlord's 'Watch ... ' :

<3>WNM: Preferred List Available
<3>SME: Trying to authenticate with 68:ff:7b:47:c9:13 (SSID='watch iovedocs on YouTube ' freq=5200 MHz)
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>Trying to associate with 68:ff:7b:47:c9:13 (SSID='watch iovedocs on YouTube ' freq=5200 MHz)
<3>Associated with 68:ff:7b:47:c9:13
<3>CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
<3>CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
<3>WPA: Key negotiation completed with 68:ff:7b:47:c9:13 [PTK=CCMP GTK=TKIP]
<3>CTRL-EVENT-CONNECTED - Connection to 68:ff:7b:47:c9:13 completed [id=1 id_str=]
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>WNM: Preferred List Available
<3>SME: Trying to authenticate with 7a:ff:7b:47:c8:7f (SSID='watch iovedocs on YouTube ' freq=5200 MHz)
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>Trying to associate with 7a:ff:7b:47:c8:7f (SSID='watch iovedocs on YouTube ' freq=5200 MHz)
<3>Associated with 7a:ff:7b:47:c8:7f
<3>CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
<3>WPA: Key negotiation completed with 7a:ff:7b:47:c8:7f [PTK=CCMP GTK=TKIP]
<3>CTRL-EVENT-CONNECTED - Connection to 7a:ff:7b:47:c8:7f completed [id=1 id_str=]
<3>CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-DISCONNECTED bssid=7a:ff:7b:47:c8:7f reason=3 locally_generated=1
<3>CTRL-EVENT-DSCP-POLICY clear_all
<3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

-- end of output --

I've had difficulty determining the exact sequence of commands with wpa_gui.
It seems to be : 'manage networks' -- 'edit' to add password -- 'save' --
'scan' : a list of services is offered, a '5200' is double-clicked --
back to 'current status' -- 'connect' & it fills in the details
& takes another 15 sec to get an IP address & I/net cb accessed.

Any further suggestions very welcome.

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatcadotinterdotnet

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 25/12/24 10:01, Philip Webb wrote:

<3>WPA: Key negotiation completed with 16:c4:a5:6b:1e:6e [PTK=CCMP GTK=CCMP]

and

<3>WPA: Key negotiation completed with 68:ff:7b:47:c9:13 [PTK=CCMP GTK=TKIP]


The above differs between the two ...

Modern wpa-supplicant auto detects sane defaults so you may get away
with removing them from the conf file if you are specifying them
(apologies if this has been covered as I didnt read the back thread)

BillK

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wednesday 25 December 2024 02:01:43 GMT Philip Webb wrote:

241224 Michael wrote:

Did he *only* change the SSID and password
or did he also change the encryption and key management method ?

Only the former : he's not skilled enough to do the latter.
I suspect that originally someone set it up for him
& altered some default setting(s), then when he restarted it,
the default setting(s) returned & that's not working with my software.

In this case you may only have to edit the SSID entry in your wpa_supplicant.conf and leave the rest as is. Since you can connect using the wpa_gui with the same password, let's start by paying attention to the SSID.

Check there are no empty spaces left at the end of the strings
in any entries you edited in your wpa_supplicant.conf.

There are none.

I think you'll find there is at least one within the SSID - see below.

Check you have not altered the access rights of the file :
chmod -v 600 /etc/wpa_supplicant/wpa_supplicant.conf

The permission is '644', which is ok for my cellpbone's hotspot.

This is a security issue for your WiFi password details being exposed in your filesystem and to stop non-root users altering your settings. It is recommended only root has access to this file, but in any case it is not affecting the problem you are experiencing.

I can use 'wpa_gui' with a bit of fussing & editing.

Currently, it shows the correct adapter + service name & below it lists :

Status : completed (station)
Last message : <blank>
Authentication : WPA2-PSK
Encryption : CCMP + TKIP
SSID : <service name>
BSSID : < 12 hex digits >
IP address : < 11 digits >

The first method looks good to me, beyond the points I mentioned above.

Check what the landlord's AP wants to use by running wpa_cli in a
terminal:
> scan

will start scanning for APs. after few secs, you will have some results :
> scan_results

It shows nothing : see output below.

It does provide some useful info, although you do not show the scan_results output provided by wpa_cli.

Thanks for your usually very helpful suggestions (smile).
Here is the output via 'wpa_cli' as I start & stop Wifi.
I connect & disconnect with my cell-phone 'Athene' + landlord's service, whose name is 'Watch Iovedocs ... ',
& which I have to access via 'wpa_gui' (I used 2 terminals).

[snip ...]

using wpa_gui to start/stop landlord's 'Watch ... ' :

<3>WNM: Preferred List Available
<3>SME: Trying to authenticate with 68:ff:7b:47:c9:13 (SSID='watch
iovedocs on YouTube ' freq=5200 MHz) <3>CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
<3>Trying to associate with 68:ff:7b:47:c9:13
(SSID='watch iovedocs on YouTube ' freq=5200 MHz)

Please check the space character shown at the end of the SSID string above.
You will need to include this in your wpa_supplicant.conf; e.g.:

ssid="watch iovedocs on YouTube "

-- end of output --

I've had difficulty determining the exact sequence of commands with wpa_gui. It seems to be : 'manage networks' -- 'edit' to add password -- 'save' -- 'scan' : a list of services is offered, a '5200' is double-clicked -- back
to 'current status' -- 'connect' & it fills in the details
& takes another 15 sec to get an IP address & I/net cb accessed.

Any further suggestions very welcome.

After I launch the wpa_gui I press scan, double click the preferred AP, add credentials and if necessary change the authentication method, and 'save'. It should pick it up thereafter, but if already associated with another AP, I may have to select from the "Network" drop down my preferred AP.

I expect when you edit the SSID as suggested above you will be able to connect without using the GUI.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmdr4ZIACgkQseqq9sKV ZxlBwBAA3bLoGmugEQf66umIyJaEJj4kzWzMu/aVCuCluQkOqL1VpQprgeuZnk5t coZAt8w+PvIBW0+vfqv5n3AlUVfNdZFeilUTE5Elujn+yvlqkioq1fBtlya8gfTz SYVfuqxxY+4sy5HiCtQIGVthrXM8nqdE8nLV9ZoKl7EaqQ34Sr0gVXBXac4P1uzF 6hT0cJe2QhBcKv7IY9l4q3+chb3wuMDsjT58yJEbdZ4KpoWWkKElynq0xFJWGNYc F3yyZAZ+8CNT0Kw/mX9/BzaJgIt8qx2z6ivCjXTuvB38XNqjhS0TcEA+LGiQ6b22 Tr02FBaweGziNtzzuOeS0quG7WDAVgc0eI2XSckjLP1cBQA3XnEw7FCjUjzcWsXP olwY/PL5tzfa8iHGHeY5z0OLD3zwXaI+u+kq+muEV/R40cJuZdAwjpMEm91bfUal Mm//2s1JOyxeNihz8ANaxFidZVVL8E+xo+Apq7z5auA07Gb7TJj6RFIORFqNiVOR VWvKXxfxcet3jsk/92nGQnFObQ1LM9IY6Mo+KzXwDf3h2Jf2k5iEfnVj03mmH0Ar mAKYhcdpoDr5g8UulfciuOC5dIVr9+sI0thGH9IUZrsnrtyTlsh5jBnzQmBCfuK6 EHSDw+rUAy/leezgA8Z7+amw7O71j2a7pXZTZr6HB5cyCw3FgMk=
=KZhM
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

241225 Michael wrote:

Check there are no empty spaces left at the end of the strings

in any entries you edited in your wpa_supplicant.conf.

There are none.

I think you'll find there is at least one within the SSID - see below.

using wpa_gui to start/stop landlord's 'Watch ... ' :

<3>WNM: Preferred List Available
<3>SME: Trying to authenticate with 68:ff:7b:47:c9:13 (SSID='watch
iovedocs on YouTube ' freq=5200 MHz) <3>CTRL-EVENT-REGDOM-CHANGE init=CORE >> type=WORLD
<3>Trying to associate with 68:ff:7b:47:c9:13
(SSID='watch iovedocs on YouTube ' freq=5200 MHz)

Please check the space character shown at the end of the SSID string above.

You will need to include this in your wpa_supplicant.conf; e.g.:
ssid="watch iovedocs on YouTube "
I expect when you edit the SSID as suggested above
you will be able to connect without using the GUI.

Indeed ! -- that was the problem.
I've added the space & commented the 3 extra lines re keys/security
& there's no problem connecting via 'rc-service -v wpa_supplicant start'
I keep copies of the config files for both services
& overwrite 'wpa_supplicant.conf' when necessary
(of course, I use a Bash aliases).

Thanks for all the advice : what a strange problem.

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatcadotinterdotnet

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Friday 27 December 2024 01:12:39 GMT Philip Webb wrote:

241225 Michael wrote:

I expect when you edit the SSID as suggested above
you will be able to connect without using the GUI.

Indeed ! -- that was the problem.
I've added the space & commented the 3 extra lines re keys/security
& there's no problem connecting via 'rc-service -v wpa_supplicant start'
I keep copies of the config files for both services
& overwrite 'wpa_supplicant.conf' when necessary
(of course, I use a Bash aliases).

Thanks for all the advice : what a strange problem.

I've learned the hard way it's easy to press the space bar inadvertently and not notice a space character at the end of a string. In this case it would be noticeable when you run 'scan_results' with wpa_cli, because the SSID is enclosed in single quotes.

Alternatively, you can use the BSSID to connect to an AP. The BSSID won't change when the AP owner alters the SSID. This may be less desirable if you are connecting to a mesh network with multiple APs, or you move around in a building with more than one AP.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmdueMAACgkQseqq9sKV ZxnigQ/8Cf6ivOi1fBmfNM1UP+FzQ+8z2JKDXkwfSnJwREo7c4O+ODreDec0QT/C eXB6kIHC2i/lg0mOw0WJWX9GGjDrDlPxXgay0ChUTlYPpJDopv+jUhDO9mfQPoYo lbvPT05gGfyqIICXGItuWjb3/FfhCtnlwV/OUC5lgDS1P5a6ZSu2uC/6ITmg8MLd fzRDAzY1juEURQF8ptsvN4TDqojBRz7IFv2F40Qlz2DKNb/3VH8DMIXn5tIXOBdP 2czP5s42Wj8EE2IGTcus3zDL3KsPEno9e7rUor7OPFS1bbjMyGjgSkKS5wLMl9Iw vOZjswa/sZfrK4zi2kFZyiArmTI0NI2Cos+nMXPvNzBiXuaqE8fcz4p7dDTqzdvx krj3gdzIbTadmVbZNuQe8XX1TGz99tuzhPplBXpGRF250tDfVQ1A2jz4DJNs6Dw/ mVZH5QaGkF2Ut65W3VzLeJ0e1uPVLWx11DYWK0+Tw1ghOjAvkt51IU0eZ2sjxlWj ROR5i/F4Ngo18ouwWkd4EOc/dl6k0DenDef4zlFi94VSHcas0pFCbReZ866G5UUt EEdUtzJkLetv1QZmoZwLGCfWf5tuwKbo3fAEe2LafwqVFsOFnE1v1Qu3/bF18+nY HJo4Ark8uflgIZ4VpzI1o6uDs/Uq0PSjRpckP6Egx+gaCzRBm7w=
=GjDh
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)