On Wed, 22 Nov 2006 00:15:24 +0100, Christian Langanke wrote:
>Chris Clayton wrote:
>> I have not been able to get WPA to work between my TP T41 internal wifi
>> and an Actiontec DSL gateway. WEP is working without problems.
>>
>
>Chris, sorry to read that you are having problems.
Christian,
There is no reason to apologize, you and Willibald have done a
fantastic effort getting us to this point! There's always a few
growing pains to wade through as you will see below.
>
>> I copied the profile for WEP to another WPA profile and changed the
>> security settings only to 'WiFi Protected Access (WPA2-PSK)' and
>> entered a preshared key. I then changed the DLS gateway to WPA with
>> the same key. When I try to activate the WPA profile I usually get an
>> icon with red bars indicating that it is connected but out of range.
>> The T41 is 2 feet from the DSL gateway. Occasionally I get an icon
>> with green bars indicating a strong signal. In either case, I cannot
>> communicate over wifi with WPA enabled even though the routing and IP
>> addresses are correctly assigned.
>>
>
>Hmm, cannot think of a reason for that. The signal should be identical.
>Can you test the WPA encryption with a notebook running linux or Windows ?
Believe it or not, my Window box refuses to connect with anything!
Rather than mess up my working Actiontec DSL system with WEP wifi, I
uncrated from storage a Linksys WRT54g I had when I was contemplating
using a cable setup. (When I decided to go to DSL, I needed a new box
since Qwest use PPPoA and the Linksys only support PPPoE). The Linksys
box has a WPA option to use TKIP (WPA) or AES (WPA2). When I tried the
AES option I had the same problems I had with the Actiontec box.
However, with TKIP enabled and changing the the XWLAN option from WPA2
to WPA, I was able to connect and had a working network! All of leads
me to believe that we have the usual "standards" problem!
>
>> I did try 'WiFi Protected Access (WPA-PSK)' but just got a 'searching
>> for connection' icon.
>>
>
>I am confused:didn't you say you get red bars on this ?
No, the red bars were for WPA2. There is minimal documentation, but my
understanding is that the Actiontec gateway I was initially using only
uses AES for its WPA-PSK operation. There is no option available to
switch between TKIP and AES.
>
>
>> Other issues:
>> 1) I am occasionally getting a trap e when trying to activate the WPA
>> profiles. This may or may not be related to the fact that I have
>> Object Desktop installed as, once, the system trapped when I opened the
>> Tab Launchbar with the WEP profile active.
>>
>
>This should be a driver issue. Please post that to the genmac mailing list.
Will do once I do a little further investigation. I need to disable
Object Desktop, possibly Norman AV, C-A-D Commander ... to narrow
things down. BTW, there were no problems with Genmac 1+.
>
>> 2) I still need to use a script when switching between a wifi and a
>> wired connection. This is because when using the method described in
>> the manual, the configuration for lan0(1) are not completely deleted
>> when switching to lan1(0)
>>
>V3.01 will come soon to fix a problem when switching back to cabled
>while using DHCP. Switching from cabled to wireless should already work.
>please use radio on/off for switching only (docs will be adapted to that
>for 3.01)
I am using fixed IPs only and I do use the radio on/off technique.
This is not a big problem since the script technique is working well.
>
>
>> 3) Netbios over TCP/IP does not start is I follow the instructions for
>> configuring setup.cmd for networks that switch between a wifi and wired
>> connection. The instructions state that the wifi lan configuration
>> should not be in setup.cmd, rather left to XWLAN. I have found that I
>> need both LAN0 (wifi) and LAN1 (wired) configured. I put in a 'dummy'
>> ip address for LAN1, so that both subnets are present when the system
>> starts. This may be needed because, in config.sys, a tcpbeui protocol
>> is run after the call to run setup.cmd:
>>
>> CALL=E:\OS2\CMD.EXE /Q /C E:\MPTN\BIN\MPTSTART.CMD >NUL
>> RUN=E:\IBMCOM\PROTOCOL\NBTCP.EXE
>>
>> Note: once the system is running, then lan0(1) can be deleted when
>> switching between lan1(0).
>>
>>
>
>Chris, I am verry sorry, but I never tested to integrate NetBios over
>TCP/IP. This may work, but I cannot say that there will be no side
>effect by this.
Thats, ok. I have found that NetBIOS over TCPIP can be very finicky
about configuration and caches being properly cleared. I once tried to
clone two machines from a backup file and change the network settings
(IP, name, etc) for the second machine. TCPBEIU complained for quite
awhile that I had two systems with the same name on the network! It
took a painstaking clearing of the caches of ALL the computers to clear
that up.
Cheers,
Chis
>
>thanx, Christian
>
>-------------------------------------------------
>
>Christian Langanke
>COS2E & CWSE
>Team OS/2 Ruhr e.V.
>cla@clanganke.de
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>This message is sent to you because you are subscribed to
> the mailing list <os2-wireless_users@2rosenthals.com>.
>To unsubscribe, E-mail to: <os2-wireless_users-off@2rosenthals.com>
>To switch to the DIGEST mode, E-mail to <os2-wireless_users-digest@2rosenthals.com>
>To switch to the INDEX mode, E-mail to <os2-wireless_users-index@2rosenthals.com>
>Send administrative queries to <os2-wireless_users-request@2rosenthals.com>
>To subscribe (new addresses), E-mail to: <os2-wireless_users-on@2rosenthals.com> and reply to the confirmation email.
>
>This list is hosted by Rosenthal & Rosenthal
>P.O. Box 281, Deer Park, NY 11729-0281. Non-
>electronic communications related to content
>contained in these messages should be directed
>to the above address. (CAN-SPAM Act of 2003)
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>
back to list