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: ntpd drifts depsite pll state

[Manuel Bouyer]

On Fri, Feb 02, 2018 at 04:46:41AM +0100, Emmanuel Dreyfus wrote:
> Hello
> 
> I have a strange problem with ntpd: clock drifts while the daemon
> reports kernel status pll, which as I understand means NTP
> synchronisation is good:
> 
> # cat /etc/ntp.conf
> pidfile /var/run/ntpd.pid
> driftfile   /var/db/ntp.drift
> logconfig   -syncstatus
> server  192.0.2.20
> 
> # ntpq
> ntpq> kerninfo
> associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart,
> pll offset:0
> pll frequency: 0
> maximum error: 756.265
> estimated error:   1.6e-05
> kernel status: pll
> pll time constant: 3
> precision: 0
> frequency tolerance:   495.911
> pps frequency: 0
> pps stability: 0
> pps jitter:0
> calibration interval   0
> calibration cycles:0
> jitter exceeded:   0
> stability exceeded:0
> calibration errors:0

What does 'peer' shows ?

If you have only one server maybe you need:
tos minsane 1

-- 
Manuel Bouyer 
 NetBSD: 26 ans d'experience feront toujours la difference
--