Re: WLAN (Linksys WPC111) + WEP

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: WLAN (Linksys WPC111) + WEP

Nikolaus Hiebaum
Hi,

A while ago I posted here for help with my WLAN card (Linksys WPC11 v3). Here is my setup ...
I have a built-in LAN card (rl0) through which I am usually connected to my network. The there
is the WLAN card (wi0) which would connect via an Access Point (AP). All of this is funneled
via a Router

rl0 usually has 192.168.0.2
Router 192.168.0.100
wi0 would get 192.168.0.21

This is my netstat -rn and ifconfig in the usual setup (just rl0 connected to router)

---snip---
Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use    Mtu  Interface
default            192.168.0.100      UGS         5    65505      -   rl0
127/8              127.0.0.1          UGRS        0        0  33224   lo0
127.0.0.1          127.0.0.1          UH          1      396  33224   lo0
192.168.0/24       link#1             UC          2        0      -   rl0
192.168.0.100      0:c:41:c6:1:75     UHLc        1     2180      -   rl0
192.168.0.255      link#1             UHLc        3      848      -   rl0
224/4              127.0.0.1          URS         0        0  33224   lo0

Encap:
Source             Port  Destination        Port  Proto SA(Address/Proto/Type/Direction)
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33224
        groups: lo
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:0a:e4:4a:13:0b
        groups: egress
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
        inet6 fe80::20a:e4ff:fe4a:130b%rl0 prefixlen 64 scopeid 0x1
pflog0: flags=0<> mtu 33224
pfsync0: flags=0<> mtu 1348
enc0: flags=0<> mtu 1536
---snap---

When I want to connect via the wi0, I down the rl0 and give it whole different IP. The chain
of commands is this:

ifconfig wi0 192.168.0.21 255.255.255.0 nwid scyld nwkey BACE8A21EA up

ifconfig rl0 10.0.0.0

route delete default

route add default 192.168.0.100

I need the nwkey for the WEP (64bit) encryption (open authentication). Both the AP, as well as
ifconfig, suggest that I am connected wireless, but I cannot ping anything.

---snip---
Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use    Mtu  Interface
default            192.168.0.100      UGS         4       72      -   wi0
10/8               link#1             UC          1        0      -   rl0
10.255.255.255     link#1             UHLc        2       42      -   rl0
127/8              127.0.0.1          UGRS        0        0  33224   lo0
127.0.0.1          127.0.0.1          UH          1      396  33224   lo0
192.168.0/24       link#6             UC          2        0      -   wi0
192.168.0.100      link#6             UHRLc       1        0      -   wi0
192.168.0.255      link#6             UHLc        3       21      -   wi0
224/4              127.0.0.1          URS         0        0  33224   lo0


lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33224
        groups: lo
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:0a:e4:4a:13:0b
        groups: egress
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
        inet6 fe80::20a:e4ff:fe4a:130b%rl0 prefixlen 64 scopeid 0x1
pflog0: flags=0<> mtu 33224
pfsync0: flags=0<> mtu 1348
enc0: flags=0<> mtu 1536
wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:06:25:2b:55:5c
        media: IEEE802.11 autoselect (DS2)
        status: active
        ieee80211: nwid scyld nwkey <not displayed> 5dBm (auto)
        inet6 fe80::206:25ff:fe2b:555c%wi0 prefixlen 64 scopeid 0x6
        inet 192.168.0.21 netmask 0xffffff00 broadcast 255.255.255.0
---snap---

And still I cannot ping anything. As soon as I turn off WEP and have an unencrypted AP, I can
ping. What am I missing out here? Both ifconfig and the AP tell me, that I am connected, and
netstat says the routes are fine. What's the problem here?

--
Beste Gr|_e / Best regards ,
Nikolaus Hiebaum

Reply | Threaded
Open this post in threaded view
|

Re: WLAN (Linksys WPC111) + WEP

Darrin Chandler
Nikolaus Hiebaum wrote:

>ifconfig wi0 192.168.0.21 255.255.255.0 nwid scyld nwkey BACE8A21EA up
>  
>
Not sure if it was just a typo in your email, but I think you want the
nwkey as hex, ... nwid 0xBACE8A21EA ...

--
Darrin Chandler
[hidden email]
http://www.stilyagin.com/

Reply | Threaded
Open this post in threaded view
|

Re: WLAN (Linksys WPC111) + WEP

Darrin Chandler
In reply to this post by Nikolaus Hiebaum
Typo in *my* last email. You want nwkey as hex, not nwid!

--
Darrin Chandler
[hidden email]
http://www.stilyagin.com/

Reply | Threaded
Open this post in threaded view
|

Re: WLAN (Linksys WPC111) + WEP

Nikolaus Hiebaum-2
* Darrin Chandler wrote on Nov 13, 2005 [08:16, -0700] :

> >ifconfig wi0 192.168.0.21 255.255.255.0 nwid scyld nwkey BACE8A21EA up
> >
> >
> Not sure if it was just a typo in your email, but I think you want the
> nwkey as hex, ... nwid 0xBACE8A21EA ...

* Darrin Chandler wrote on Nov 13, 2005 [08:19, -0700] :

> Typo in *my* last email. You want nwkey as hex, not nwid!

O.K., so I translated the whole BACE8A21EA into 0x42414345384132314541 and gave it a try.

Same thing as before. ifconfig, netstat and the AP tell me, I am all connected just fine, but
I cannot ping an IP (not even the router).

--
Beste Gr|_e / Best regards ,
Nikolaus Hiebaum

Reply | Threaded
Open this post in threaded view
|

Re: WLAN (Linksys WPC111) + WEP

Darrin Chandler
Nikolaus Hiebaum wrote:

>* Darrin Chandler wrote on Nov 13, 2005 [08:16, -0700] :
>
>  
>
>>>ifconfig wi0 192.168.0.21 255.255.255.0 nwid scyld nwkey BACE8A21EA up
>>>
>>>
>>>      
>>>
>>Not sure if it was just a typo in your email, but I think you want the
>>nwkey as hex, ... nwid 0xBACE8A21EA ...
>>    
>>
>
>* Darrin Chandler wrote on Nov 13, 2005 [08:19, -0700] :
>
>  
>
>>Typo in *my* last email. You want nwkey as hex, not nwid!
>>    
>>
>
>O.K., so I translated the whole BACE8A21EA into 0x42414345384132314541 and gave it a try.
>
>Same thing as before. ifconfig, netstat and the AP tell me, I am all connected just fine, but
>I cannot ping an IP (not even the router).
>
>  
>
wi(4) says: wi is capable of using both 40-bit (5 characters or 10
hexadecimal digits) or 104-bit (13 characters or 26 hexadecimal digits)
keys.

So you'll need either 0xBACE8A21EA as your *hex* key (for 40 bit), or
something else entirely is going with your keys.

--
Darrin Chandler
[hidden email]
http://www.stilyagin.com/

Reply | Threaded
Open this post in threaded view
|

Re: WLAN (Linksys WPC111) + WEP

Nikolaus Hiebaum
In reply to this post by Nikolaus Hiebaum
Darren wrote:

> wi(4) says: wi is capable of using both 40-bit (5 characters or 10
> hexadecimal digits) or 104-bit (13 characters or 26 hexadecimal digits)
> keys.
>
> So you'll need either 0xBACE8A21EA as your *hex* key (for 40 bit), or
> something else entirely is going with your keys.

Thank you! :) It works now! ;-) I thought the '0x' was only to be used for a hexadecimal
translation.

Do you know what the second type as mentioned by wi means resp. how the synatx would be

[...] or a set of keys of the form ``n:k1,k2,k3,k4'', where `n' specifies which of the keys
will be used for transmitted packets, and the four keys, ``k1'' through ``k4'', are configured
as WEP keys.  If a set of keys is specified, a comma (`,') [...]

n:BACE8A21EA ? Coz that didn't work.

--
Beste Gr|_e / Best regards ,
Nikolaus Hiebaum

Reply | Threaded
Open this post in threaded view
|

Re: WLAN (Linksys WPC111) + WEP

Nikolaus Hiebaum
* Nikolaus Hiebaum wrote on Nov 13, 2005 [17:35, +0100] :

> Thank you! :) It works now! ;-) I thought the '0x' was only to be used for a hexadecimal
> translation.

One last question: With which application can I measure the strength of the signal or if there
are other WLAN around, preferably a GUI.

--
Beste Gr|_e / Best regards ,
Nikolaus Hiebaum

Reply | Threaded
Open this post in threaded view
|

Re: WLAN (Linksys WPC111) + WEP

Darrin Chandler
In reply to this post by Nikolaus Hiebaum
Nikolaus Hiebaum wrote:

>Darren wrote:
>
>  
>
>>wi(4) says: wi is capable of using both 40-bit (5 characters or 10
>>hexadecimal digits) or 104-bit (13 characters or 26 hexadecimal digits)
>>keys.
>>
>>So you'll need either 0xBACE8A21EA as your *hex* key (for 40 bit), or
>>something else entirely is going with your keys.
>>    
>>
>
>Thank you! :) It works now! ;-) I thought the '0x' was only to be used for a hexadecimal
>translation.
>
>Do you know what the second type as mentioned by wi means resp. how the synatx would be
>
>[...] or a set of keys of the form ``n:k1,k2,k3,k4'', where `n' specifies which of the keys
>will be used for transmitted packets, and the four keys, ``k1'' through ``k4'', are configured
>as WEP keys.  If a set of keys is specified, a comma (`,') [...]
>
>n:BACE8A21EA ? Coz that didn't work.
>  
>
Really, it's a HEX KEY. First, "BACE8A21EA" should be "0xBACE8A21EA".
Second, it should be "1:0xBACE8A21EA" to specify the first key for
transmitting. Third, if you only have one key then why use the multikey
syntax at all? You can just stick with "0xBACE8A21EA" by itself.

--
Darrin Chandler
[hidden email]
http://www.stilyagin.com/