Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
88 user(s) are online (53 user(s) are browsing Forums)

Members: 2
Guests: 86

kas1e, Hypex, more...

Headlines
Recent files - OS4Depot - Your one stop for AmigaOS4 files

Forum Index

Board index » All Posts (pjs)


« 1 ... 9 10 11 (12) 13 14 15 ... 17 »


pjs
Microsloth winmail.dat (TNEF) file decoding?
Posted on: 2013/12/3 13:33    #221
Not too shy to talk
Not too shy to talk
Hi All,

I'm just wondering what luck or clues anyone might have for
decoding "windmail.dat" TNEF files from microsoft email
clients on AmigaOS.

A bit of background (if you need), these TNEF files (named
"winmail.dat" are proprietary attachments microsoft cooked
up to lock out foreign platforms...

http://en.wikipedia.org/w/index.php?s ... n=&title=Special%3ASearch

There are a couple ways for getting into these TNEF files
on AmigaOS that I've found: Unarc has a very out of date
MS-TNEF decoder and there's an old decoder on OS4Depot:

http://os4depot.net/index.php?functio ... =utility/archive/tnef.lha

Unfortunately, I'm finding the unarc plugin almost never
shows anything and the decoder util doesn't decode ICS
(calendar invites).

Anyone have any suggestions?

So far the only way I've found to get into the attachments
has been to forward messages into my gmail acct and (only)
open it in webmail.

Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: AmigaOS and web browsing in 2013
Posted on: 2013/10/28 14:51    #222
Not too shy to talk
Not too shy to talk
@vox

/me confused....

http://www.amigans.net/modules/xforum ... t_id=83755#forumpost83755

What happened to departing and leaving amigans free of
whining for a year?

:/

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/9/25 16:04    #223
Not too shy to talk
Not too shy to talk
Another bit of good news for the drivers... It's been
24 hours and the prism's connection is still up and
running on my A1-XE with ping running continuously.

Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/9/24 16:48    #224
Not too shy to talk
Not too shy to talk
Just to provide some more test results, I've replaced the
WPN311 card with my Amigakit wifi card in my A1-XE to see
how it worked.

Using the v2.4 prism driver, I started WM manually and it
looks like everything fired up OK and my system is online.
Here's the WM output:

Quote:
Initializing interface 'prism2.device:0' conf 'ENV:Sys/Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Sys/Wireless.prefs' -> 'ENV:Sys/Wireless.prefs'
Reading configuration file 'ENV:Sys/Wireless.prefs'
Line: 15 - start of a new network block
ssid - hexdump_ascii(len=14):
50 4a 53 77 69 72 65 6c 65 73 73 4e 65 74 PJSwirelessNet
key_mgmt: 0x4
wep_key0 - hexdump(len=13): [REMOVED]
wep_tx_keyidx=0 (0x0)
Priority group 0
id=0 ssid='PJSwirelessNet'
*** [wpa_sm_init] sm->pmksa=0x66f26814 ***
Own MAC address: 00:0e:6a:7a:e8:8c
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface prism2.device:0
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
BSS: Start scan result update 1
BSS: Add new id 0 BSSID 00:04:e2:ad:1e:40 SSID 'PJSwirelessNet'
BSS: Add new id 1 BSSID 0a:90:7f:8a:c7:24 SSID 'FR'
BSS: Add new id 2 BSSID c0:3f:0e:76:c4:f3 SSID 'Ellens Network'
BSS: Add new id 3 BSSID 1c:af:f7:dc:ad:29 SSID 'pewettco'
BSS: Add new id 4 BSSID f8:e4:fb:d9:f1:b1 SSID 'MLN7Q'
BSS: Add new id 5 BSSID 00:7f:28:99:51:13 SSID 'LFZ7J'
New scan results available
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:04:e2:ad:1e:40 ssid='PJSwirelessNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - no WPA/RSN IE
1: 0a:90:7f:8a:c7:24 ssid='FR' wpa_ie_len=0 rsn_ie_len=0 caps=0x411
skip - no WPA/RSN IE
2: c0:3f:0e:76:c4:f3 ssid='Ellens Network' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - no WPA/RSN IE
3: 1c:af:f7:dc:ad:29 ssid='pewettco' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - no WPA/RSN IE
4: f8:e4:fb:d9:f1:b1 ssid='MLN7Q' wpa_ie_len=0 rsn_ie_len=0 caps=0x411
skip - no WPA/RSN IE
5: 00:7f:28:99:51:13 ssid='LFZ7J' wpa_ie_len=0 rsn_ie_len=0 caps=0x411
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:04:e2:ad:1e:40 ssid='PJSwirelessNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
selected non-WPA AP 00:04:e2:ad:1e:40 ssid='PJSwirelessNet'
Trying to associate with 00:04:e2:ad:1e:40 (SSID='PJSwirelessNet' freq=2452 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
State: SCANNING -> ASSOCIATING
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=ForceAuthorized
EAPOL: Supplicant port status: Unauthorized
Association info event
req_ies - hexdump(len=2): 00 00
WPA: clearing own WPA/RSN IE
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:04:e2:ad:1e:40
Associated with 00:04:e2:ad:1e:40
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state S_FORCE_AUTH
EAPOL: Supplicant port status: Authorized
EAPOL: SUPP_BE entering state IDLE
Cancelling authentication timeout
State: ASSOCIATED -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:04:e2:ad:1e:40 completed (auth) [id=0 id_str=]
Cancelling scan request
EAPOL: disable timer tick
BSS: Expire BSS 1 due to age
BSS: Remove id 1 BSSID 0a:90:7f:8a:c7:24 SSID 'FR'
BSS: Expire BSS 2 due to age
BSS: Remove id 2 BSSID c0:3f:0e:76:c4:f3 SSID 'Ellens Network'
BSS: Expire BSS 3 due to age
BSS: Remove id 3 BSSID 1c:af:f7:dc:ad:29 SSID 'pewettco'
BSS: Expire BSS 4 due to age
BSS: Remove id 4 BSSID f8:e4:fb:d9:f1:b1 SSID 'MLN7Q'
BSS: Expire BS

Hopefully, the Amigakit card stays online longer here than
it does on my SAM. I'll keep a shell pinging the router
and see what happens.

I hope this helps with your development.

Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/9/23 15:41    #225
Not too shy to talk
Not too shy to talk
An update on the A1-XE:

Last week I got the WPN311 installed and running on my
A1-XE and thought I'd leave it online and pinging overnight
to see how things go...

Instead it got a bit longer term test... I never got back
to the office last week and my Amiga ran all weekend with
the WPN311 up & pinging away.

I'm glad to report everything is still working today
(~96 hours later), my Amiga is still online and ping still
running. I'm looking forward to seeing this on my SAM
and X1K!

:)

Thanks ncafferkey!

PJS
Go to top
Topic | Forum


pjs
Re: Sheepshaver (MacOS PPC 9): any coder interested?
Posted on: 2013/9/21 17:29    #226
Not too shy to talk
Not too shy to talk
Hi LiveForIt,
Quote:
LiveForIt wrote:
Thats a hard one

If this helps any, the trick I used to use with Shapeshifter
was this "virtual SANA" driver that would let the Mac
side see the network on the Amiga side:

http://aminet.net/package/comm/tcp/vlink

I wonder whether something like that might still be usable
with anything you might try to do with Basilisk?

Anyone know if the dev (Chris Brenner) is still around?

Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: Sheepshaver (MacOS PPC 9): any coder interested?
Posted on: 2013/9/20 13:39    #227
Not too shy to talk
Not too shy to talk
Hi LiveForIt,
Quote:

LiveForIt wrote:

There is probably a bunch of stuff that can be fixed in the GUI, but it depends on you people, how interested you are, I see few people interested but no feature requests.

I just wanted to say I've also been watching this thread
with great interest. I used to use Shapeshifter a lot in
the old days and would love to see Basilisk be as useful.

Can't say I had any great issues with the GUI, I just found
past instances of Basilisk not as compatible with apps as
the Shapeshifter used to be and I really missed network
access in Basilisk.

I'm hoping your new versions might help these things.

In any case, keep up the great work! Looking forward
to your results!

THANKS,

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/9/19 18:36    #228
Not too shy to talk
Not too shy to talk
Hi ncafferkey,

Quote:
ncafferkey wrote:
But the problem in the X1000 appears to be different, as it partially works for you.


Agreed, yes it is.

FWIW, I took the atheros card to my office, plugged it into
my A1-XE and it's mostly working here. This is with the
v15 driver from OS4Depot.

The only drawback is that I have to cold boot and then warm
boot to get the machine started with the card in, but I
think this may be a problem with UBoot variables.

If it helps any, I started the network manually and here's
the feedback I got from WM:
Quote:

Initializing interface 'atheros5000.device:0' conf 'ENV:Sys/Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Sys/Wireless.prefs' -> 'ENV:Sys/Wireless.prefs'
Reading configuration file 'ENV:Sys/Wireless.prefs'
Line: 15 - start of a new network block
ssid - hexdump_ascii(len=14):
50 4a 53 77 69 72 65 6c 65 73 73 4e 65 74 PJSwirelessNet
key_mgmt: 0x4
wep_key0 - hexdump(len=13): [REMOVED]
wep_tx_keyidx=0 (0x0)
Priority group 0
id=0 ssid='PJSwirelessNet'
*** [wpa_sm_init] sm->pmksa=0x64396824 ***
Own MAC address: 00:1b:2f:cf:ba:a7
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface atheros5000.device:0
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
MLME: starting scan
MLME: scan channel 1 (2412 MHz)
sana2: sending MLME frame
unknown vendor specific information element ignored (vendor OUI 00:03:93 len=7)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=14)
MLME: scan channel 2 (2417 MHz)
sana2: sending MLME frame
MLME: scan channel 3 (2422 MHz)
sana2: sending MLME frame
Unknown Broadcom information element ignored (type=52 len=26)

unknown vendor specific information element ignored (vendor OUI 00:03:7f len=9)
unknown vendor specific information element ignored (vendor OUI 00:03:7f len=10)
MLME: scan channel 4 (2427 MHz)
sana2: sending MLME frame
Unknown Broadcom information element ignored (type=52 len=26)

unknown vendor specific information element ignored (vendor OUI 00:03:7f len=9)
unknown vendor specific information element ignored (vendor OUI 00:03:7f len=10)
Unknown Broadcom information element ignored (type=52 len=26)

unknown vendor specific information element ignored (vendor OUI 00:03:7f len=9)
unknown vendor specific information element ignored (vendor OUI 00:03:7f len=10)
MLME: scan channel 5 (2432 MHz)
sana2: sending MLME frame
MLME: scan channel 6 (2437 MHz)
sana2: sending MLME frame
Unknown Broadcom information element ignored (type=52 len=26)

unknown vendor specific information element ignored (vendor OUI 00:03:7f len=9)
unknown vendor specific information element ignored (vendor OUI 00:03:7f len=10)
unknown vendor specific information element ignored (vendor OUI 00:10:18 len=9)
MLME: scan channel 7 (2442 MHz)
sana2: sending MLME frame
MLME: scan channel 8 (2447 MHz)
sana2: sending MLME frame
MLME: scan channel 9 (2452 MHz)
sana2: sending MLME frame
MLME: scan channel 10 (2457 MHz)
sana2: sending MLME frame
unknown vendor specific information element ignored (vendor OUI 00:10:18 len=6)
MLME: scan channel 11 (2462 MHz)
sana2: sending MLME frame
MLME: scan channel 12 (2467 MHz)
sana2: sending MLME frame
unknown vendor specific information element ignored (vendor OUI 00:03:93 len=7)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=14)
MLME: scan channel 13 (2472 MHz)
sana2: sending MLME frame
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
unknown vendor specific information element ignored (vendor OUI 00:03:93 len=7)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=14)
MLME: scan channel 14 (2484 MHz)
sana2: sending MLME frame
unknown vendor specific information element ignored (vendor OUI 00:03:93 len=7)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=14)
unknown vendor specific information element ignored (vendor OUI 00:10:18 len=9)
Unknown Broadcom information element ignored (type=52 len=26)

MLME: scan channel 1 (2412 MHz)
sana2: sending MLME frame
unknown vendor specific information element ignored (vendor OUI 00:03:93 len=7)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=14)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=11)
MLME: scan channel 2 (2417 MHz)
sana2: sending MLME frame
unknown vendor specific information element ignored (vendor OUI 00:03:93 len=7)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=14)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=11)
Unknown Broadcom information element ignored (type=52 len=26)

unknown vendor specific information element ignored (vendor OUI 00:03:7f len=9)
unknown vendor specific information element ignored (vendor OUI 00:03:7f len=10)
MLME: scan channel 3 (2422 MHz)
sana2: sending MLME frame
Unknown Broadcom information element ignored (type=52 len=26)

unknown vendor specific information element ignored (vendor OUI 00:03:7f len=9)
unknown vendor specific information element ignored (vendor OUI 00:03:7f len=10)
MLME: scan channel 4 (2427 MHz)
sana2: sending MLME frame
MLME: scan channel 5 (2432 MHz)
sana2: sending MLME frame
MLME: scan channel 6 (2437 MHz)
sana2: sending MLME frame
Unknown Broadcom information element ignored (type=52 len=26)

unknown vendor specific information element ignored (vendor OUI 00:03:7f len=9)
unknown vendor specific information element ignored (vendor OUI 00:03:7f len=10)
unknown vendor specific information element ignored (vendor OUI 00:10:18 len=9)
unknown vendor specific information element ignored (vendor OUI 00:10:18 len=9)
MLME: scan channel 7 (2442 MHz)
sana2: sending MLME frame
MLME: scan channel 8 (2447 MHz)
sana2: sending MLME frame
MLME: scan channel 9 (2452 MHz)
sana2: sending MLME frame
MLME: scan channel 10 (2457 MHz)
sana2: sending MLME frame
MLME: scan channel 11 (2462 MHz)
sana2: sending MLME frame
MLME: scan channel 12 (2467 MHz)
sana2: sending MLME frame
unknown vendor specific information element ignored (vendor OUI 00:03:93 len=7)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=14)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=11)
unknown vendor specific information element ignored (vendor OUI 00:10:18 len=9)
Unknown Broadcom information element ignored (type=52 len=26)

MLME: scan channel 13 (2472 MHz)
sana2: sending MLME frame
unknown vendor specific information element ignored (vendor OUI 00:03:93 len=7)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=14)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=11)
unknown vendor specific information element ignored (vendor OUI 00:03:93 len=7)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=14)
unknown vendor specific information element ignored (vendor OUI 00:17:f2 len=11)
MLME: scan completed
BSS: Start scan result update 1
BSS: Add new id 0 BSSID 00:7f:28:99:51:13 SSID 'LFZ7J'
BSS: Add new id 1 BSSID 7c:d1:c3:d1:51:d8 SSID 'METE Network'
BSS: Add new id 2 BSSID 1c:af:f7:dc:ad:29 SSID 'pewettco'
BSS: Add new id 3 BSSID c0:3f:0e:76:c4:f3 SSID 'Ellens Network'
BSS: Add new id 4 BSSID 68:7f:74:21:43:d5 SSID 'equallevel3'
BSS: Add new id 5 BSSID c0:3f:0e:8e:bc:5c SSID 'CTP'
BSS: Add new id 6 BSSID 0a:90:7f:8a:c7:24 SSID 'FR'
BSS: Add new id 7 BSSID 00:12:17:19:39:ee SSID 'ABS'
BSS: Add new id 8 BSSID 00:04:e2:ad:1e:40 SSID 'PJSwirelessNet'
New scan results available
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:7f:28:99:51:13 ssid='LFZ7J' wpa_ie_len=0 rsn_ie_len=24 caps=0x411
skip - SSID mismatch
1: 7c:d1:c3:d1:51:d8 ssid='METE Network' wpa_ie_len=0 rsn_ie_len=20 caps=0x1431
skip - SSID mismatch
2: 1c:af:f7:dc:ad:29 ssid='pewettco' wpa_ie_len=26 rsn_ie_len=24 caps=0x431
skip - SSID mismatch
3: c0:3f:0e:76:c4:f3 ssid='Ellens Network' wpa_ie_len=26 rsn_ie_len=24 caps=0x431
skip - SSID mismatch
4: 68:7f:74:21:43:d5 ssid='equallevel3' wpa_ie_len=28 rsn_ie_len=24 caps=0x411
skip - SSID mismatch
5: c0:3f:0e:8e:bc:5c ssid='CTP' wpa_ie_len=0 rsn_ie_len=20 caps=0x431
skip - SSID mismatch
6: 0a:90:7f:8a:c7:24 ssid='FR' wpa_ie_len=26 rsn_ie_len=0 caps=0x411
skip - SSID mismatch
7: 00:12:17:19:39:ee ssid='ABS' wpa_ie_len=24 rsn_ie_len=0 caps=0x411
skip - SSID mismatch
8: 00:04:e2:ad:1e:40 ssid='PJSwirelessNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:7f:28:99:51:13 ssid='LFZ7J' wpa_ie_len=0 rsn_ie_len=24 caps=0x411
skip - SSID mismatch
1: 7c:d1:c3:d1:51:d8 ssid='METE Network' wpa_ie_len=0 rsn_ie_len=20 caps=0x1431
skip - SSID mismatch
2: 1c:af:f7:dc:ad:29 ssid='pewettco' wpa_ie_len=26 rsn_ie_len=24 caps=0x431
skip - SSID mismatch
3: c0:3f:0e:76:c4:f3 ssid='Ellens Network' wpa_ie_len=26 rsn_ie_len=24 caps=0x431
skip - SSID mismatch
4: 68:7f:74:21:43:d5 ssid='equallevel3' wpa_ie_len=28 rsn_ie_len=24 caps=0x411
skip - SSID mismatch
5: c0:3f:0e:8e:bc:5c ssid='CTP' wpa_ie_len=0 rsn_ie_len=20 caps=0x431
skip - SSID mismatch
6: 0a:90:7f:8a:c7:24 ssid='FR' wpa_ie_len=26 rsn_ie_len=0 caps=0x411
skip - SSID mismatch
7: 00:12:17:19:39:ee ssid='ABS' wpa_ie_len=24 rsn_ie_len=0 caps=0x411
skip - SSID mismatch
8: 00:04:e2:ad:1e:40 ssid='PJSwirelessNet' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
selected non-WPA AP 00:04:e2:ad:1e:40 ssid='PJSwirelessNet'
Trying to associate with 00:04:e2:ad:1e:40 (SSID='PJSwirelessNet' freq=2452 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
State: SCANNING -> ASSOCIATING
MLME: Initial auth_alg=0
MLME: authenticate with AP 00:04:e2:ad:1e:40
sana2: sending MLME frame
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=ForceAuthorized
EAPOL: Supplicant port status: Unauthorized
MLME: RX authentication from 00:04:e2:ad:1e:40 (alg=0 transaction=2 status=0)
MLME: authenticated
MLME: associate with AP 00:04:e2:ad:1e:40
sana2: sending MLME frame
MLME: RX AssocResp from 00:04:e2:ad:1e:40 (capab=0x431 status=0 aid=2)
MLME: associated
Association info event
req_ies - hexdump(len=32): 00 0e 50 4a 53 77 69 72 65 6c 65 73 73 4e 65 74 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c
resp_ies - hexdump(len=16): 01 04 82 84 8b 96 32 08 0c 12 18 24 30 48 60 6c
freq=2452 MHz
WPA: clearing own WPA/RSN IE
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:04:e2:ad:1e:40
Associated with 00:04:e2:ad:1e:40
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state S_FORCE_AUTH
EAPOL: Supplicant port status: Authorized
EAPOL: SUPP_BE entering state IDLE
Cancelling authentication timeout
State: ASSOCIATED -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:04:e2:ad:1e:40 completed (auth) [id=0 id_str=]
Cancelling scan request
sana2: setting negotiate


As I said, the network is working and I've got a continuous
ping running to my router. The only running hickup I see
is the occasional "(DUP!)" in the ping returns.

Thanks & I hope this helps,

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/9/18 4:36    #229
Not too shy to talk
Not too shy to talk
Linux???


Wassat???

;)

Sorry, no. Only AmigaOS on my Amigas.

Bear in mind, this isn't a SAM specific problem - the
atheros driver wasn't working in my X1K either.

Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/9/16 13:53    #230
Not too shy to talk
Not too shy to talk
Hi ncafferkey,
Quote:
ncafferkey wrote:

Do other cards work in that PCI slot?
E.g. an old RTL8139 or SoundBlaster. If so, do they get the same interrupt number?
Also, what range are the interrupts for other PCI devices in?
Yes, indeed other PCI cards work in my SAM... The Amigakit prism card, even.
Just for not very long. It typically dies after a while (0.5-6 hours). My
experience with that was reported in this thread:

http://www.amigans.net/modules/xforum ... t_id=76630#forumpost76630

FWIW, I'm posting this via the prism card.

I looked at the prism card in Ranger and if this is the right item, this is what I saw:
Quote:
vendor: 0x1260 (N/A)
Cacheline Size: 32 bytes
Line: 0x32 Pin: A Number: 66
Resource Ranges: # = 0, Base = 0xa0023000, Physical = 0xa0023000, Size = 4096, Flags = PreFetch Mem
Just for the sake of testing, I ran WM manually on the prism and got this:
Quote:
5.aSYS:> c:WirelessManager prism2.device VERBOSE
Initializing interface 'prism2.device:0' conf 'ENV:Sys/Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Sys/Wireless.prefs' -> 'ENV:Sys/Wireless.prefs'
Reading configuration file 'ENV:Sys/Wireless.prefs'
Line: 10 - start of a new network block
ssid - hexdump_ascii(len=11):
50 4a 53 77 69 72 65 6c 65 73 73 PJSwireless
key_mgmt: 0x4
Priority group 0
id=0 ssid='PJSwireless'
*** [wpa_sm_init] sm->pmksa=0x58f91814 ***
Own MAC address: 00:0e:6a:7a:e8:8c
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface prism2.device:0
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
BSS: Start scan result update 1
BSS: Add new id 0 BSSID 68:7f:74:92:6f:a7 SSID 'myfreedom'
BSS: Add new id 1 BSSID 28:c6:8e:a7:4b:10 SSID '87S4EOO9'
BSS: Add new id 2 BSSID 94:44:52:5e:f3:42 SSID 'REAL'
BSS: Add new id 3 BSSID b8:8d:12:60:c8:23 SSID 'Apachejoel'
BSS: Add new id 4 BSSID e2:91:f5:05:c9:94 SSID 'NETGEAR_EXT'
BSS: Add new id 5 BSSID 20:e5:2a:f4:0c:8c SSID 'RED27'
BSS: Add new id 6 BSSID 00:24:b2:1e:10:24 SSID 'zRocket'
BSS: Add new id 7 BSSID 00:1c:10:20:b2:0e SSID 'linksys_SES_12386'
BSS: Add new id 8 BSSID 00:18:e7:f5:74:ea SSID 'PJSwireless'
BSS: Add new id 9 BSSID 00:1f:f3:c2:42:7d SSID 'Network'
New scan results available
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 68:7f:74:92:6f:a7 ssid='myfreedom' wpa_ie_len=0 rsn_ie_len=0 caps=0x411
skip - no WPA/RSN IE
1: 28:c6:8e:a7:4b:10 ssid='87S4EOO9' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - no WPA/RSN IE
2: 94:44:52:5e:f3:42 ssid='REAL' wpa_ie_len=0 rsn_ie_len=0 caps=0x411
skip - no WPA/RSN IE
3: b8:8d:12:60:c8:23 ssid='Apachejoel' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - no WPA/RSN IE
4: e2:91:f5:05:c9:94 ssid='NETGEAR_EXT' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - no WPA/RSN IE
5: 20:e5:2a:f4:0c:8c ssid='RED27' wpa_ie_len=0 rsn_ie_len=0 caps=0x411
skip - no WPA/RSN IE
6: 00:24:b2:1e:10:24 ssid='zRocket' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - no WPA/RSN IE
7: 00:1c:10:20:b2:0e ssid='linksys_SES_12386' wpa_ie_len=0 rsn_ie_len=0 caps=0x411
skip - no WPA/RSN IE
8: 00:18:e7:f5:74:ea ssid='PJSwireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x421
skip - no WPA/RSN IE
9: 00:1f:f3:c2:42:7d ssid='Network' wpa_ie_len=0 rsn_ie_len=0 caps=0x421
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 68:7f:74:92:6f:a7 ssid='myfreedom' wpa_ie_len=0 rsn_ie_len=0 caps=0x411
skip - SSID mismatch
1: 28:c6:8e:a7:4b:10 ssid='87S4EOO9' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - SSID mismatch
2: 94:44:52:5e:f3:42 ssid='REAL' wpa_ie_len=0 rsn_ie_len=0 caps=0x411
skip - SSID mismatch
3: b8:8d:12:60:c8:23 ssid='Apachejoel' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - SSID mismatch
4: e2:91:f5:05:c9:94 ssid='NETGEAR_EXT' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - SSID mismatch
5: 20:e5:2a:f4:0c:8c ssid='RED27' wpa_ie_len=0 rsn_ie_len=0 caps=0x411
skip - SSID mismatch
6: 00:24:b2:1e:10:24 ssid='zRocket' wpa_ie_len=0 rsn_ie_len=0 caps=0x431
skip - SSID mismatch
7: 00:1c:10:20:b2:0e ssid='linksys_SES_12386' wpa_ie_len=0 rsn_ie_len=0 caps=0x411
skip - SSID mismatch
8: 00:18:e7:f5:74:ea ssid='PJSwireless' wpa_ie_len=0 rsn_ie_len=0 caps=0x421
selected non-WPA AP 00:18:e7:f5:74:ea ssid='PJSwireless'
Trying to associate with 00:18:e7:f5:74:ea (SSID='PJSwireless' freq=2412 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
State: SCANNING -> ASSOCIATING
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=ForceAuthorized
EAPOL: Supplicant port status: Unauthorized
Association info event
req_ies - hexdump(len=2): 00 00
WPA: clearing own WPA/RSN IE
State: ASSOCIATING -> ASSOCIATED
Associated to a new BSS: BSSID=00:18:e7:f5:74:ea
Associated with 00:18:e7:f5:74:ea
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state S_FORCE_AUTH
EAPOL: Supplicant port status: Authorized
EAPOL: SUPP_BE entering state IDLE
Cancelling authentication timeout
State: ASSOCIATED -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:18:e7:f5:74:ea completed (auth) [id=0 id_str=]
Cancelling scan request
EAPOL: disable timer tick


Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/9/15 17:36    #231
Not too shy to talk
Not too shy to talk
Hi all,

Finally got some time to get the WPN311 card back into the
SAM440-mini and to try manually & verbosely starting the
WirelessManager and AddNetInterfaces...

Sorry for a long post, but here's what happened:

First, I continued trying with the atheros5000.device.debug4
(090313) version, I get:
Quote:
5.aSYS:> c:WirelessManager atheros5000.device VERBOSE
Initializing interface 'atheros5000.device:0' conf 'ENV:Sys/Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Sys/Wireless.prefs' -> 'ENV:Sys/Wireless.prefs'
Reading configuration file 'ENV:Sys/Wireless.prefs'
Line: 10 - start of a new network block
ssid - hexdump_ascii(len=11):
50 4a 53 77 69 72 65 6c 65 73 73 PJSwireless
key_mgmt: 0x4
Priority group 0
id=0 ssid='PJSwireless'
*** [wpa_sm_init] sm->pmksa=0x55e2d824 ***
Own MAC address: 00:1b:2f:cf:ba:a7
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface atheros5000.device:0
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
MLME: starting scan
MLME: scan channel 1 (2412 MHz)
sana2: sending MLME frame

When I tried starting the network, it times out like this:
Quote:
6.aSYS:> AddNetInterface DEVS:NetInterfaces/~(#?.info)
Interface "interface" added.
Trying interface "interface" configuration...
AddNetInterface: Interface "interface" configuration attempt timed out.
6.aSYS:>

This was the same result with all my tests... I have Internet Prefs
simply configured to use the atheros driver with a dynamic DHCP connection.

So I rebooted, installed the vanilla v15 driver (from OS4Depot), ran WM
again, and I got this:
Quote:
5.aSYS:> c:WirelessManager atheros5000.device VERBOSE
Initializing interface 'atheros5000.device:0' conf 'ENV:Sys/Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Sys/Wireless.prefs' -> 'ENV:Sys/Wireless.prefs'
Reading configuration file 'ENV:Sys/Wireless.prefs'
Line: 10 - start of a new network block
ssid - hexdump_ascii(len=11):
50 4a 53 77 69 72 65 6c 65 73 73 PJSwireless
key_mgmt: 0x4
Priority group 0
id=0 ssid='PJSwireless'
*** [wpa_sm_init] sm->pmksa=0x5af83824 ***
Own MAC address: 00:1b:2f:cf:ba:a7
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface atheros5000.device:0
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
MLME: starting scan
MLME: scan channel 1 (2412 MHz)
sana2: sending MLME frame

Finally, seeing the line above about "wpa" (my network is now open),
I thought maybe results might be different if I tried an encrypted
network. So I rebooted, changed the network to WEP and the
ENVARC:sys/wireless.prefs file. I tried WM again and got this:
Quote:
6.aSYS:> c:WirelessManager atheros5000.device VERBOSE
Initializing interface 'atheros5000.device:0' conf 'ENV:Sys/Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Sys/Wireless.prefs' -> 'ENV:Sys/Wireless.prefs'
Reading configuration file 'ENV:Sys/Wireless.prefs'
Line: 15 - start of a new network block
ssid - hexdump_ascii(len=11):
50 4a 53 77 69 72 65 6c 65 73 73 PJSwireless
key_mgmt: 0x4
wep_key0 - hexdump(len=13): [REMOVED]
wep_tx_keyidx=0 (0x0)
Priority group 0
id=0 ssid='PJSwireless'
*** [wpa_sm_init] sm->pmksa=0x581f9824 ***
Own MAC address: 00:1b:2f:cf:ba:a7
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface atheros5000.device:0
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
MLME: starting scan
MLME: scan channel 1 (2412 MHz)
sana2: sending MLME frame

As always, trying to AddNetInterface, things just timed out. In
all cases I rebooted before each test.

Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/9/8 17:28    #232
Not too shy to talk
Not too shy to talk
Well, FWIW, it looks like the lockups with the atheros
driver and the Netgear WPN311 card in my X1K are still
there.

Since my last post I've been running either the beta
driver (from this thread) or the v15 driver from OS4Depot
and have still encountered these lockups after a few
hours.

Most of the time and at the moment of every lockup, I
limited my use of the X1K to simply pinging, AmIRC and
streaming audio with AmigaAmp.

I'm running the beta kernel and I also kept kicking up the
debuglevel on the machine to see if I could provoke
anything to appear on the serial port. The last time
around, I had the debuglevel=10 and there was still
nothing.

In case it matters, I'm connecting to an open network
and that connection occurs quickly.

Next, I'll try things again in the SAM with various
drivers and manual startups.

Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/9/7 17:11    #233
Not too shy to talk
Not too shy to talk
@Quote:
ncafferkey wrote:
For initial testing, I'd recommend not enabling any TCP/IP interfaces. Just run "WirelessManager atheros5000.device VERBOSE" in a shell. If it connects, leave it running for a while to see if it's stable.

FWIW, I rebooted my X1K and it's been online and pinging
for 30+ minutes. Maybe the lockup was just the driver's
opening jitters?

I'll leave it pinging for a while more to see what
happens... then move the card back to the SAM to
try as you suggest:

Quote:
It's also important to disable WirelessManager from starting at boot if you want to test it in a shell: two copies running can cause problems.

The first driver version to try is the updated one on Aminet, before trying any debug versions.


Thanks!

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/9/7 16:29    #234
Not too shy to talk
Not too shy to talk
Hi all,

I spun the wheel again and the mailman brought me a new
wifi card to try: it's a Netgear WPN311 (version V1H2).

I installed the latest driver posted here in the thread
and reengaged the WirelessManager lines in the S-S of my
SAM440-mini. On cold reboot, I reconfigured Internet
prefs, it restarted the stack, but all I got was a timeout.

After shutting the net down, I ran...

run <>nil: c:WirelessManager atheros5000.device

...and nothing happens (no error msg). Then I execute
network-startup and after a while I get the console prompt
back but no net connection. Doing shownetstatus, I get:

8.RAM Disk:> ShowNetStatus
Network status summary
Local host address = 0.0.0.0 (on interface 'interface')
Default gateway address = (Not configured)
Domain name system servers = 192.168.1.1
8.RAM Disk:>

Then I ran the last DMATest2 app I saw in the thread and
this is what I got:

8.RAM Disk:> DMATest2
Virtual address: 0x5A83F040
Virtual block size: 64
Physical address: 0x18203040
Physical block size: 64
8.RAM Disk:>

I copied all the files (driver, WMgr, .prefs, etc) to my
X1K, I installed the card, selected the driver in Internet
prefs and everything started working straight away... for
about 5 minutes (pinging the router the whole time) and
then my X1K locked up. There was nothing on the serial
port (using the debug kernel).

Doing DMATest2 on the X1K, I get this:

9.RAM Disk:> DMATest2
Virtual address: 0x5AFE8240
Virtual block size: 64
Physical address: 0x17685240
Physical block size: 64
9.RAM Disk:>

Any thoughts?

Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/8/31 15:31    #235
Not too shy to talk
Not too shy to talk
Bummer this is the wrong card... when I saw most of its
name posted above with all the plusses, I thought I was
golden! ;)

Before I go shopping again, I thought I'd survey the
results here in the thread.

If I got it right, outside of ncafferkey and his DLink
DWL-G520 and Netgear WPN-311, the only person to report
success has been goos and his ABIT WPL-01...

ABIT WPL-01 = Works for goos, was DSI'ing for imagodespira
Alpha WMP-009 = DSI'd for billt a long time ago, no new news
Dlink DWL-G520 = Works for ncafferkey, hangs or times out for others
Netgear WG311T = Hangs for cara
Netgear WPN311 = Works for ncafferkey, times out for JurrasicC

Granted we haven't heard from billt and imagodespira in a
long time and only utri007 has reported testing with the
newest driver on OS4Depot.

Anyone else have new results? Anyone skip posting their
successes?

Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: Amigakits's wlan card
Posted on: 2013/8/24 17:12    #236
Not too shy to talk
Not too shy to talk

Hi Matt/Chris/Amigakit,

Can I suggest you guys post the best means for folks to
contact you for getting their wifi cards re-flashed?

I tried to get a PCtech friend to reflash mine, but the
listed software wouldn't recognize the card.

As it stands, my Amigakit card refuses to stay online for
more than an hour or so and I'm hoping reflashing might
help that (??).

Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: Timberwolf, Warp3D and ARMA
Posted on: 2013/8/24 15:28    #237
Not too shy to talk
Not too shy to talk
@tommysammy

Maybe if you're lucky, when they release the new Warp3D
and Timberworlf, your appreciation of their years of
hard work will be repaid with a "doesn't work on
tommysammy's machine" routine?

;)

Just saying... not recognizing or appreciating it can take
years of work to accomplish complex projects is simply
indecent (IMHO).

PJS
Go to top
Topic | Forum


pjs
Re: Atheros WLAN driver success/failures
Posted on: 2013/8/17 17:38    #238
Not too shy to talk
Not too shy to talk
Hi ncafferkey and all,

Given the unreliability of the prism driver & card, I bought the
D-Link DWL-520+ card and have been trying it out in my SAM440ep.
So far, it's been a no-go.

First, I tried using the May'13 atheros driver and then I installed
the July1st version posted in this thread. In all cases, the
WirelessManager (WM) fails when called (with this is the line in
the s-s):

run <>nil: c:WirelessManager atheros5000.device

Specifically, with the normal kernel I get this line in a console:

NIL::1: c:WirelessManager failed returncode 20

If I switch to using a debug kernel, then I get a DSI on the WM.
Crashlogs have been saved in this archive:

http://www.pjsa.net/WirelessManager-Crashlogs.lha

Just in case WM was somehow dependent on the config of Roadshow (RS),
I continued and configured RS to use the atheros device. When I
saved the config, RS restarted & I got this error in a console:

[error]: Could not open "atheros5000.device" unit 0 (Device/unit failed to open).

I also downloaded the DMA test app posted in this thread and this
is what I got when I ran it with the July1st driver in place (but
inactive):

Virtual address: 0x58BEE560
Virtual block size: 64
Physical address: 0x4428560
Physical block size: 64

Finally, I am noticing if I select either the prism or atheros
drivers in RS prefs' "Modify network interface" windows, the
driver type is listed as "unknown". Is this anything that
matters somehow?

ncafferkey, any thoughts on all this? Anything else to test?
Need any more data? Or should I continue on with the game of
wifi card roulette? ;)

Thanks,

PJS
Go to top
Topic | Forum


pjs
Re: New project - Mixer
Posted on: 2013/8/8 14:25    #239
Not too shy to talk
Not too shy to talk
Hi Jabirulo,

You have a PM! Nice work with Mixer! I'm fine with
you overwriting my version on OS4Depot.

Thanks!

PJS
Go to top
Topic | Forum


pjs
Re: Kryoflux software for AmigaOS?
Posted on: 2013/6/20 13:33    #240
Not too shy to talk
Not too shy to talk
It's my understanding the software for the KryoFlux is open
source and it's supposed to have been designed for
portability.

Here's the downloads page from the SPS:

http://www.softpres.org/download

Thanks,

PJS
Go to top
Topic | Forum



TopTop
« 1 ... 9 10 11 (12) 13 14 15 ... 17 »



[Advanced Search]


Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project