Hi,
On Sun, 25 Jan 2015 18:52:45 + (UTC)
Kostya Berger wrote:
> Updates: I've set up a guest network on that router, now it connects
> OK.
[...]
> On Sunday, 25 January 2015, 20:14, Adrian Chadd
> wrote:
> On 25 January 2015 at 10:12, Kostya Berger
> wrote:
> > Yes, it says WPA2-PER
Updates: I've set up a guest network on that router, now it connects OK. Could
the problem be in my configured WPA key containing characters like "@", "$" }}
~~ and the like?
Because now I set up a key without those chars, just for experiment's sake, and
it works. With kindest regards,
Kostya B
On 25 January 2015 at 10:17, Kostya Berger wrote:
> MyHOME-Net e0:3f:49:22:6d:946 54M -56:-95 100
> EP SSID RATES DSPARMS<6> ERP<0x0>
> ???<2f0100> RSN XRATES<12,18,24,96>
> HTCAP
> HTINFO ???<4a0e14000a002c01c800140005001900>
> ???<7f0101> WPS uuid-e:40-f9-c0-57-1b-
MyHOME-Net e0:3f:49:22:6d:94 6 54M -56:-95 100 EP
SSID RATES DSPARMS<6> ERP<0x0>
???<2f0100> RSN XRATES<12,18,24,96>
HTCAP
HTINFO ???<4a0e14000a002c01c800140005001900>
???<7f0101> WPS
VEN WME
NGTS9 28:31:52:2c:af:5f 11 54M -81:-95
On 25 January 2015 at 10:12, Kostya Berger wrote:
> Yes, it says WPA2-PERSONAL with AES encryption. And I connect to it using my
> tablet and other devices.
>
What's the result of "ifconfig -v wlan0 list scan" and in wpa_cli,
"scan_results" ?
There's something about the SSID that has wpa_supplic
quot;my passphrase"
>>> }
>>>
>>> and here my /var/log/messages part to the point (not much):
>>> Jan 25 05:49:45 kostya-home kernel: wlan0:
>>> Jan 25 05:49:45 kostya-home kernel: Ethernet address: 60:6c:66:4d:28:a3
>>> Jan 25 05:49:45 ko
27;/etc/pccard_ether wlan0
>> start'
>> Jan 25 05:49:45 kostya-home wpa_supplicant[83148]: Successfully
>> initialized wpa_supplicant
>> Jan 25 05:49:45 kostya-home kernel: iwn0: iwn_read_firmware: ucode
>> rev=0x12a80601
>> Jan 25 05:49:56 kostya-home
; Jan 25 05:49:45 kostya-home wpa_supplicant[83148]: Successfully
>> initialized wpa_supplicant
>> Jan 25 05:49:45 kostya-home kernel: iwn0: iwn_read_firmware: ucode
>> rev=0x12a80601
>> Jan 25 05:49:56 kostya-home root: /etc/rc.d/dhclient: WARNING: failed to
>> sta
Saturday, 24 January 2015, 1:51, Kostya Berger
> wrote:
>
>
>
> Hello everyone,
> glad to meet you. I subscribed to this list in order to get my above
> mentioned card to work.Currently, the situation is as follows:It's Intel
> Centrino wireless-N 2230 Mini PCIe
Saturday, 24 January 2015, 1:51, Kostya Berger
wrote:
Hello everyone,
glad to meet you. I subscribed to this list in order to get my above mentioned
card to work.Currently, the situation is as follows:It's Intel Centrino
wireless-N 2230 Mini PCIe that came pre-installed on my GA-Z77
Hello everyone,
glad to meet you. I subscribed to this list in order to get my above mentioned
card to work.Currently, the situation is as follows:It's Intel Centrino
wireless-N 2230 Mini PCIe that came pre-installed on my GA-Z77N-wifi
motherboard.I'm running 11.0-CURRENT, down
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196279
Bug ID: 196279
Summary: [iwn] [patch]: Backport Intel Centrino Wireless-N 2230
to 9-STABLE
Product: Base System
Version: 9.3-RELEASE
Hardware: Any
OS
The channel 3 was the least used channel in the house; I'm able to
change the regdomain on route, eg. to ETSI or some US or AU domain. :)
Tomorrow will do.
Thanks,
Oliver
On 9/9/14, Adrian Chadd wrote:
> I'm not sure why yours is misbehaving. I don't ahve anything channel 3
> though, that's for
I'm not sure why yours is misbehaving. I don't ahve anything channel 3
though, that's for sure. I don't also run it in the HU
country/regdomain. :)
Can you try updating to the latest -HEAD and retrying?
-a
___
freebsd-wireless@freebsd.org mailing list
I think no. I'm running with this settings:
iwn0: flags=8843 metric 0 mtu 2290
ether 60:6c:66:7b:af:75
nd6 options=21
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
status: associated
wlan0: flags=8843 metric 0 mtu 1500
ether 60:6c:66:7b:af:75
Also, do you run this with -bgscan ?
-a
On 5 September 2014 12:26, Adrian Chadd wrote:
> Hi!
>
> This is just an iwn panic. Did your actual -HEAD kernel panic?
>
> Try doing this with sysctl dev.iwn.0.debug=0xff; let's see what
> happens just before the firmware loses its mind.
>
> Thanks!
>
>
Hi!
This is just an iwn panic. Did your actual -HEAD kernel panic?
Try doing this with sysctl dev.iwn.0.debug=0xff; let's see what
happens just before the firmware loses its mind.
Thanks!
-a
On 5 September 2014 12:22, Oliver Pinter wrote:
> I got the attached iwn panic, even if running in -
I got the attached iwn panic, even if running in -ht mode. In between
I have a working connection.
I set up now a serial console and try to enable the ht mode with debugging.
On 9/3/14, Oliver Pinter wrote:
> Or not, I forgot the -ht option in rc.conf.
>
> G STA + G AP = ok
> G STA + N AP = ok
>
Or not, I forgot the -ht option in rc.conf.
G STA + G AP = ok
G STA + N AP = ok
N STA + N AP = fail
On 9/3/14, Oliver Pinter wrote:
> Hi!
>
> Small status update:
> The mode N works too, I mistyped the other AP's passwork.
> So both mode G and mode N working after the backports.
>
> BTW, can yo
Hi!
Small status update:
The mode N works too, I mistyped the other AP's passwork.
So both mode G and mode N working after the backports.
BTW, can you MFC the same changes to 10.1?
On 9/2/14, Adrian Chadd wrote:
> Hi,
>
> Compile it with IWN_DEBUG, then
>
> sysctl dev.iwn.0.debug=0x1
>
>
> -a
>
Hi,
Compile it with IWN_DEBUG, then
sysctl dev.iwn.0.debug=0x1
-a
On 2 September 2014 12:41, Oliver Pinter wrote:
> I not tried freebsd-head yet, but I'm able today. In mode N seems like
> the NIC sends only one frame, and no more.
>
> With tcpdump and/or wlandebug I see only rx packets and
I not tried freebsd-head yet, but I'm able today. In mode N seems like
the NIC sends only one frame, and no more.
With tcpdump and/or wlandebug I see only rx packets and no tx.
If you add some pointer what changes must I create to easier debug, or
what concrete information required, feel free to
Cool! Have you tried freebsd-head? Does it work there?
How's it failing in association state? What's it saying?
-a
On 2 September 2014 12:30, Oliver Pinter wrote:
> Hi All!
>
> After I backported all of the net80211 and iwn changes from 11-CURRENT
> to 10-STABLE the wireless NIC in subject wo
Hi All!
After I backported all of the net80211 and iwn changes from 11-CURRENT
to 10-STABLE the wireless NIC in subject working on mode G. If I try
to use with mode N (ht20, ht40) it failed in association state.
All of the backports are in this github repo:
https://github.com/opntr/opBSD/commits
24 matches
Mail list logo
