Re: Unable to join open WEP wireless network

[Xianwen Chen (陈贤文)]

Dear Brett,
Thank you. I don't think I tried _ifconfig urtwn0 ssid "" down_. I will try
it next time I am in a similar situation.
Sincerely,
Xianwen

On Wed, Feb 7, 2018 at 9:11 PM, Brett Lymn  wrote:

> On Fri, Feb 02, 2018 at 07:34:22AM -0700, Andy Ruhl wrote:
> >
> > I was reading this from the context of "oh you have to use the old WEP
> > way" to connect to an open network using ifconfig. I remember doing
> > this many years ago.
> >
> > I have no idea if stuff changed since then, but the ifconfig command
> > still appears to support connecting to open networks and WEP
> > networks... Just need to figure out what is happening in this case.
> >
>
> I visited a hotel recently that had an "open" wireless network, the
> wireless had no auth itself but they redirected you to an authentication
> portal the first time you connected after which things Just Worked(tm)
> for the rest of our stay.  I did this to get connected:
>
> /etc/rc.d/wpa_supplicant stop  (assuming you have that running)
> ifconfig urtwn0 ssid "" down
> dhclient urtwn0
>
> Once I think I confused the wireless adaptor when messing around and I
> had to unplug/plug it again (it is a usb adaptor so that was easy) but
> most of the time it worked fine.
>
> --
> Brett Lymn
> Let go, or be dragged - Zen proverb.

Re: Unable to join open WEP wireless network

[Brett Lymn]

On Fri, Feb 02, 2018 at 07:34:22AM -0700, Andy Ruhl wrote:
> 
> I was reading this from the context of "oh you have to use the old WEP
> way" to connect to an open network using ifconfig. I remember doing
> this many years ago.
> 
> I have no idea if stuff changed since then, but the ifconfig command
> still appears to support connecting to open networks and WEP
> networks... Just need to figure out what is happening in this case.
> 

I visited a hotel recently that had an "open" wireless network, the
wireless had no auth itself but they redirected you to an authentication
portal the first time you connected after which things Just Worked(tm)
for the rest of our stay.  I did this to get connected:

/etc/rc.d/wpa_supplicant stop  (assuming you have that running)
ifconfig urtwn0 ssid "" down
dhclient urtwn0

Once I think I confused the wireless adaptor when messing around and I
had to unplug/plug it again (it is a usb adaptor so that was easy) but
most of the time it worked fine.

-- 
Brett Lymn
Let go, or be dragged - Zen proverb.

Re: Unable to join open WEP wireless network

[Xianwen Chen (陈贤文)]

Dear Edmond,
Thank you.
I am no longer at the site of the said network. I will try your suggestion
when I am back to the said network in the future.
Sincerely,
Xianwen

On Mon, Feb 5, 2018 at 11:51 PM, Edmond  wrote:

> Hi Xianwen Chen,
>
> > An open WEP network is a network that > does not require
> > password or key.
>
> I'm quite sure a Open-Key WEP connection is different from a Open Network
> (unprotected), since a Open WEP, despite not requesting authentication (as
> opposed to Shared-Key WEP), still holds a hexadecimal WEP key, which is
> required for data encryption after connection. If your network is truly
> Open WEP, then in my experience, wpa_supplicant needs that key in order to
> successfully attach to the network. So , in addition to what Scole Mail
> said, if you happened to find out you need a WEP key for real, you could
> make use of a similar configuration in /etc/wpa_supplicant.conf:
>
>
> network={
> ssid="x"
> key_mgmt=NONE
> wep_key0=$hex_key #(10 characters)
> wep_tx_keyidx=0
> priority=x
> }
>
> For Shared-Key WEP, simply add :
>
> auth_alg=SHARED
>
> And then try connecting:
>
> wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf
>
> You can also avoid using wpa_supplicant at all:
>
>
> ifconfig $interface ssid xx nwkey $wep_key
>
>
>
> Best whishes
>
>
> On 1 February 2018 22:34:48 CET, "Xianwen Chen (陈贤文)" <
> xianwen.c...@gmail.com> wrote:
>>
>> Dear Dave,
>> Thank you. An open WEP network is a network that does not require
>> password or key.
>> Sincerely,
>> Xianwen
>>
>> On Thu, Feb 1, 2018 at 6:34 PM, David Young  wrote:
>>
>>>  On Thu, Feb 01, 2018 at 11:25:21AM +, Chen, Xianwen (陈贤文) wrote:
>>>
  Dear NetBSD users,

  I am having trouble connecting NetBSD to an open WEP wireless network,
  called "ks-guest". Because my Android mobile phone is able to connect
  to "ks-guest", the network is functioning.

>>>
>>>  What do you mean by an "open WEP" network?  Seems like any WEP network
>>>  should have a key, but you're not configuring the interface with any
>>>  key.
>>>
>>>  Dave
>>>
>>>  --
>>>  David Young
>>>  dyo...@pobox.comUrbana, IL(217) 721-9981
>>>
>>
>>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>

Re: Unable to join open WEP wireless network

[Edmond]

Hi Xianwen Chen, 

> An open WEP network is a network that > does not require
> password or key.

I'm quite sure a Open-Key WEP connection is different from a Open Network 
(unprotected), since a Open WEP, despite not requesting authentication (as 
opposed to Shared-Key WEP), still holds a hexadecimal WEP key, which is 
required for data encryption after connection. If your network is truly Open 
WEP, then in my experience, wpa_supplicant needs that key in order to 
successfully attach to the network. So , in addition to what Scole Mail said, 
if you happened to find out you need a WEP key for real, you could make use of 
a similar configuration in /etc/wpa_supplicant.conf:


network={ 
ssid="x" 
key_mgmt=NONE 
wep_key0=$hex_key #(10 characters)
wep_tx_keyidx=0 
priority=x
}

For Shared-Key WEP, simply add :

auth_alg=SHARED

And then try connecting:

wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf

You can also avoid using wpa_supplicant at all:


ifconfig $interface ssid xx nwkey $wep_key



Best whishes

On 1 February 2018 22:34:48 CET, "Xianwen Chen (陈贤文)"  
wrote:
>Dear Dave,
>Thank you. An open WEP network is a network that does not require
>password or key.
>Sincerely,
>Xianwen
>
>On Thu, Feb 1, 2018 at 6:34 PM, David Young  wrote:
>> On Thu, Feb 01, 2018 at 11:25:21AM +, Chen, Xianwen (陈贤文) wrote:
>>> Dear NetBSD users,
>>>
>>> I am having trouble connecting NetBSD to an open WEP wireless
>network,
>>> called "ks-guest". Because my Android mobile phone is able to
>connect
>>> to "ks-guest", the network is functioning.
>>
>> What do you mean by an "open WEP" network?  Seems like any WEP
>network
>> should have a key, but you're not configuring the interface with any
>> key.
>>
>> Dave
>>
>> --
>> David Young
>> dyo...@pobox.comUrbana, IL(217) 721-9981

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: Unable to join open WEP wireless network

[陈贤文]

Dear Scole,

Thank you! I will try it out next time I am in the same situation!
Sincerely,
Xianwen



*From:* Scole Mail <scole_m...@gmx.com>
*Sent:* Friday, February 02, 2018 4:50PM
*To:* Netbsd-users <netbsd-users@netbsd.org>
*Cc:* Xianwen Chen <xianwen.c...@gmail.com>

*Subject:* Re: Unable to join open WEP wireless network




On 02/02/2018 04:50 PM, scole_mail wrote:

I'm not sure if you have a similar set up, but thought I'd share this
since it took me awhile to figure out.  This configuration worked for me
when trying to use a password-less wifi with an athn device.  I changed
athn0 to iwi0 below...

In /etc/rc.conf:
  dhcpcd=YES
  dhcpcd_flags="-g -4 -q -b -n iwi0"
  wpa_supplicant=YES
  wpa_supplicant_flags="-i iwi0 -c /etc/wpa_supplicant.conf"

In /etc/wpa_supplicant.conf:
  ctrl_interface=/var/run/wpa_supplicant/
  
  network={

 scan_ssid=1
 ssid="ks-guest"
 # or try this instead of ssid=,
 # I think the capital letters are required
 #bssid=10:BD:18:F0:26:F2
 key_mgmt=NONE
 }


and then running
  > /etc/rc.d/wpa_supplicant restart
  > /etc/rc.d/dhcpcd restart

I had a lot of trouble trying to backquote network names with
parentheses or quotes in the ssid field so I used the bssid instead.
I'm not sure if "-" will have the same issues.

Good luck

Re: Unable to join open WEP wireless network

[scole_mail]

I'm not sure if you have a similar set up, but thought I'd share this
since it took me awhile to figure out.  This configuration worked for me
when trying to use a password-less wifi with an athn device.  I changed
athn0 to iwi0 below...

In /etc/rc.conf:
 dhcpcd=YES
 dhcpcd_flags="-g -4 -q -b -n iwi0"
 wpa_supplicant=YES
 wpa_supplicant_flags="-i iwi0 -c /etc/wpa_supplicant.conf"

In /etc/wpa_supplicant.conf:
 ctrl_interface=/var/run/wpa_supplicant/
 
 network={
scan_ssid=1
ssid="ks-guest"
# or try this instead of ssid=,
# I think the capital letters are required 
#bssid=10:BD:18:F0:26:F2
key_mgmt=NONE
}


and then running
 > /etc/rc.d/wpa_supplicant restart
 > /etc/rc.d/dhcpcd restart

I had a lot of trouble trying to backquote network names with
parentheses or quotes in the ssid field so I used the bssid instead.
I'm not sure if "-" will have the same issues.

Good luck

Re: Unable to join open WEP wireless network

[Andy Ruhl]

On Fri, Feb 2, 2018 at 2:55 AM, Martin Husemann  wrote:
> On Thu, Feb 01, 2018 at 09:34:48PM +, Xianwen Chen (???) wrote:
>> Dear Dave,
>> Thank you. An open WEP network is a network that does not require
>> password or key.
>
> Dave's point is: technically that should not be possible, how do you
> encrypt the packets when there is no key?

I was reading this from the context of "oh you have to use the old WEP
way" to connect to an open network using ifconfig. I remember doing
this many years ago.

I have no idea if stuff changed since then, but the ifconfig command
still appears to support connecting to open networks and WEP
networks... Just need to figure out what is happening in this case.

Andy

Re: Unable to join open WEP wireless network

[Martin Husemann]

On Thu, Feb 01, 2018 at 09:34:48PM +, Xianwen Chen (???) wrote:
> Dear Dave,
> Thank you. An open WEP network is a network that does not require
> password or key.

Dave's point is: technically that should not be possible, how do you
encrypt the packets when there is no key?

Martin

Re: Unable to join open WEP wireless network

[Xianwen Chen (陈贤文)]

Dear Andy,

Thank you.

Unfortunately the trouble with the open WEP network happened while I
was in a conference earlier today. The conference ended and I no
longer have access to the particular network. I cannot tcydump.

Yes, I had tried without -nwkey. You gave a good tip about "mode 11g".
I will try it out next time when I am facing a similar problem!

Sincerely,
Xianwen


On Thu, Feb 1, 2018 at 5:54 PM, Andy Ruhl  wrote:
> On Thu, Feb 1, 2018 at 4:25 AM, Chen, Xianwen (陈贤文)
>  wrote:
>> Dear NetBSD users,
>>
>> I am having trouble connecting NetBSD to an open WEP wireless network,
>> called "ks-guest". Because my Android mobile phone is able to connect
>> to "ks-guest", the network is functioning.
>>
>> "ifconfig iwi0 list scan" gives the following output:
>> SSID  BSSID  CHAN RATE  S:N INT 
>> CAPS
>> ks-nett   24:01:c7:14:2a:601   54M  37:0
>>  102 EPS  RSN WME
>> ks-guest  10:bd:18:f0:26:f21   54M  69:0
>>  102 ES   WME
>> ks-mobil  10:bd:18:f0:26:f11   54M  69:0
>>  102 EPS  RSN WME
>> ks-mobil  24:01:c7:14:2a:611   54M  36:0
>>  102 EPS  RSN WME
>> ks-guest  24:01:c7:14:2d:d26   54M  55:0
>>  102 ES   WME
>> ks-guest  24:01:c7:14:27:326   54M  49:0
>>  102 ES   WME
>> GSS-KS30:b5:c2:3e:7b:d8   11   54M  51:0
>>  100 EPS  RSN WME
>> ks-nett   cc:d5:39:cc:61:a0   11   54M  52:0
>>  102 EPS  RSN WME
>> ks-guest  cc:d5:39:cc:61:a2   11   54M  53:0
>>  102 ES   WME
>> ks-mobil  cc:d5:39:cc:61:a1   11   54M  54:0
>>  102 EPS  RSN WME
>> KSA-Trakterietcc:d5:39:cc:61:a3   11   54M  50:0
>>  102 EPS  RSN WME
>>
>> I try to connect to "ks-guest" by "ifconfig iwi0 ssid ks-guest
>> -nwkey". When I run "ifconfig", the ssid is updated. However, the
>> status remains "no network":
>> iwi0: flags=8843 mtu 1500
>> ssid ks-guest
>> powersave off
>> bssid 10:bd:18:f0:26:f0
>> address: 00:12:f0:f2:14:c4
>> media: IEEE802.11 autoselect
>> status: no network
>> inet6 fe80::212:f0ff:fef2:14c4%iwi0 prefixlen 64 detached scopeid 0x3
>>
>> I tried to specify bssid and channel by for example "ifconfig -s iwi0
>> ssid ks-guest bssid 24:01:c7:14:2b:e2 chan 6 -nwke". However, the
>> status does not change.
>
> I might not be helping much but I will try.
>
> I haven't done this in a really long time, but I know for sure that
> this used to work. I would use an ifconfig command to connect to WEP
> networks. This was an 802.11b network though, not sure if that makes a
> difference.
>
> Did you try without -nwkey? Did you try specifically setting the media
> type (maybe "mode 11g" or whatever it is)?
>
> Maybe try to tcpdump the interface to see if it really is offline...
>
> Andy

Re: Unable to join open WEP wireless network

[Xianwen Chen (陈贤文)]

Dear Dave,
Thank you. An open WEP network is a network that does not require
password or key.
Sincerely,
Xianwen

On Thu, Feb 1, 2018 at 6:34 PM, David Young  wrote:
> On Thu, Feb 01, 2018 at 11:25:21AM +, Chen, Xianwen (陈贤文) wrote:
>> Dear NetBSD users,
>>
>> I am having trouble connecting NetBSD to an open WEP wireless network,
>> called "ks-guest". Because my Android mobile phone is able to connect
>> to "ks-guest", the network is functioning.
>
> What do you mean by an "open WEP" network?  Seems like any WEP network
> should have a key, but you're not configuring the interface with any
> key.
>
> Dave
>
> --
> David Young
> dyo...@pobox.comUrbana, IL(217) 721-9981

Re: Unable to join open WEP wireless network

[David Young]

On Thu, Feb 01, 2018 at 11:25:21AM +, Chen, Xianwen (陈贤文) wrote:
> Dear NetBSD users,
> 
> I am having trouble connecting NetBSD to an open WEP wireless network,
> called "ks-guest". Because my Android mobile phone is able to connect
> to "ks-guest", the network is functioning.

What do you mean by an "open WEP" network?  Seems like any WEP network
should have a key, but you're not configuring the interface with any
key.

Dave

-- 
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981

Re: Unable to join open WEP wireless network

[Andy Ruhl]

On Thu, Feb 1, 2018 at 4:25 AM, Chen, Xianwen (陈贤文)
 wrote:
> Dear NetBSD users,
>
> I am having trouble connecting NetBSD to an open WEP wireless network,
> called "ks-guest". Because my Android mobile phone is able to connect
> to "ks-guest", the network is functioning.
>
> "ifconfig iwi0 list scan" gives the following output:
> SSID  BSSID  CHAN RATE  S:N INT 
> CAPS
> ks-nett   24:01:c7:14:2a:601   54M  37:0
>  102 EPS  RSN WME
> ks-guest  10:bd:18:f0:26:f21   54M  69:0
>  102 ES   WME
> ks-mobil  10:bd:18:f0:26:f11   54M  69:0
>  102 EPS  RSN WME
> ks-mobil  24:01:c7:14:2a:611   54M  36:0
>  102 EPS  RSN WME
> ks-guest  24:01:c7:14:2d:d26   54M  55:0
>  102 ES   WME
> ks-guest  24:01:c7:14:27:326   54M  49:0
>  102 ES   WME
> GSS-KS30:b5:c2:3e:7b:d8   11   54M  51:0
>  100 EPS  RSN WME
> ks-nett   cc:d5:39:cc:61:a0   11   54M  52:0
>  102 EPS  RSN WME
> ks-guest  cc:d5:39:cc:61:a2   11   54M  53:0
>  102 ES   WME
> ks-mobil  cc:d5:39:cc:61:a1   11   54M  54:0
>  102 EPS  RSN WME
> KSA-Trakterietcc:d5:39:cc:61:a3   11   54M  50:0
>  102 EPS  RSN WME
>
> I try to connect to "ks-guest" by "ifconfig iwi0 ssid ks-guest
> -nwkey". When I run "ifconfig", the ssid is updated. However, the
> status remains "no network":
> iwi0: flags=8843 mtu 1500
> ssid ks-guest
> powersave off
> bssid 10:bd:18:f0:26:f0
> address: 00:12:f0:f2:14:c4
> media: IEEE802.11 autoselect
> status: no network
> inet6 fe80::212:f0ff:fef2:14c4%iwi0 prefixlen 64 detached scopeid 0x3
>
> I tried to specify bssid and channel by for example "ifconfig -s iwi0
> ssid ks-guest bssid 24:01:c7:14:2b:e2 chan 6 -nwke". However, the
> status does not change.

I might not be helping much but I will try.

I haven't done this in a really long time, but I know for sure that
this used to work. I would use an ifconfig command to connect to WEP
networks. This was an 802.11b network though, not sure if that makes a
difference.

Did you try without -nwkey? Did you try specifically setting the media
type (maybe "mode 11g" or whatever it is)?

Maybe try to tcpdump the interface to see if it really is offline...

Andy