|
List Info
Thread: Connecting P1i to FreeBSD
|
|
| Connecting P1i to FreeBSD |
|
2008-04-24 18:41:11 |
HI,
I'D LIKE TO CONNECT SE P1I (A "SMARTPHONE" DEVICE)
TO FREEBSD, IN ANY
POSSIBLE WAY, VIA WIRELESS (WLAN). THE SYMPTOMS ARE THAT IT
JUST REPORTS
"CONNECTION FAILED" NO MATTER WHAT I DO.
ACQUIRED DATA SO FAR:
0) I'M TRYING ADHOC MODE WITHOUT ANY AUTHORIZATION, FOR NOW,
JUST TO GET
IT WORKING
1) THE SAME WIFI ADAPTER (USB, D-LINK DWL-G122) WORKS OK
WITH WINDOWS XP
WITH ADHOC MODE (I.E. THE DEVICE CONNECTS/ASSOCIATES TO THE
COMPUTER,
CAN EXCHANGE NETWORK TRAFFIC, ETC; IN WINDOWS I CAN BRIDGE
THE WIFI
DEVICE TO THE NETWORK CARD, ETC. - IN EFFECT, NO PROBLEMS)
2) THERE'S NO WAY THE SAME DEVICES SUCCEEDS IN TALKING WHEN
THE WIFI
ADAPTER IS ON FREEBSD. THE ADAPTER IS RUN VIA THE RUM
DRIVER.
2A) THE "SCAN NETWORK" ACTION ON THE DEVICE LISTS
THE WLAN SSID ON THE
COMPUTER; ALSO "IFCONFIG RUM0 LIST STA" ON FREEBSD
SHOWS THE DEVICE'S MAC.
3) A THIRD MACHINE, A LAPTOP, CAN CONNECT TO THE FREEBSD
MACHINE,
EVERYTHING WORKS.
3A) APPARENTLY SE P1I IS QUIRKY WITH ITS WLAN SUPPORT, BUT
SOMEHOW IT
KNOWS HOW TO TALK TO WINDOWS.
HERE'S A DEBUG TRACE FROM THE FREEBSD MACHINE (WLANDEBUG -I
RUM0 +DEBUG
+SCAN +ASSOC +NODE +XRATE +RATE +INPUT +OUTPUT +AUTH) DURING
THE
UNSUCCESSFUL CONNECTION ATTEMPT. THE "...1D" MAC
IS FROM THE P1I.
RUM0: RECEIVED PROBE_REQ FROM 00:1C:A4:75:63:1D RSSI 27
RUM0: [00:1C:A4:75:63:1D] RECV PROBE REQ
RUM0: IEEE80211_REF_NODE (IEEE80211_SEND_MGMT:1574)
0XC250B000<00:1C:A4:75:63:1D> REFCNT 3
[00:1C:A4:75:63:1D] SEND PROBE_RESP ON CHANNEL 6
RUM0: RECEIVED PROBE_REQ FROM 00:1C:A4:75:63:1D RSSI 27
RUM0: [00:1C:A4:75:63:1D] RECV PROBE REQ
RUM0: IEEE80211_REF_NODE (IEEE80211_SEND_MGMT:1574)
0XC250B000<00:1C:A4:75:63:1D> REFCNT 3
[00:1C:A4:75:63:1D] SEND PROBE_RESP ON CHANNEL 6
RUM0: RECEIVED PROBE_REQ FROM 00:1C:A4:75:63:1D RSSI 25
RUM0: [00:1C:A4:75:63:1D] RECV PROBE REQ
RUM0: IEEE80211_REF_NODE (IEEE80211_SEND_MGMT:1574)
0XC250B000<00:1C:A4:75:63:1D> REFCNT 3
[00:1C:A4:75:63:1D] SEND PROBE_RESP ON CHANNEL 6
RUM0: RECEIVED PROBE_REQ FROM 00:1C:A4:75:63:1D RSSI 25
RUM0: [00:1C:A4:75:63:1D] RECV PROBE REQ
RUM0: IEEE80211_REF_NODE (IEEE80211_SEND_MGMT:1574)
0XC250B000<00:1C:A4:75:63:1D> REFCNT 3
[00:1C:A4:75:63:1D] SEND PROBE_RESP ON CHANNEL 6
RUM0: RECEIVED PROBE_REQ FROM 00:1C:A4:75:63:1D RSSI 25
RUM0: [00:1C:A4:75:63:1D] RECV PROBE REQ
RUM0: IEEE80211_REF_NODE (IEEE80211_SEND_MGMT:1574)
0XC250B000<00:1C:A4:75:63:1D> REFCNT 3
[00:1C:A4:75:63:1D] SEND PROBE_RESP ON CHANNEL 6
RUM0: RECEIVED PROBE_REQ FROM 00:1C:A4:75:63:1D RSSI 25
RUM0: [00:1C:A4:75:63:1D] RECV PROBE REQ
RUM0: IEEE80211_REF_NODE (IEEE80211_SEND_MGMT:1574)
0XC250B000<00:1C:A4:75:63:1D> REFCNT 3
[00:1C:A4:75:63:1D] SEND PROBE_RESP ON CHANNEL 6
RUM0: RECEIVED PROBE_REQ FROM 00:1C:A4:75:63:1D RSSI 25
RUM0: [00:1C:A4:75:63:1D] RECV PROBE REQ
RUM0: IEEE80211_REF_NODE (IEEE80211_SEND_MGMT:1574)
0XC250B000<00:1C:A4:75:63:1D> REFCNT 3
[00:1C:A4:75:63:1D] SEND PROBE_RESP ON CHANNEL 6
RUM0: RECEIVED PROBE_REQ FROM 00:1C:A4:75:63:1D RSSI 25
RUM0: [00:1C:A4:75:63:1D] RECV PROBE REQ
RUM0: IEEE80211_REF_NODE (IEEE80211_SEND_MGMT:1574)
0XC250B000<00:1C:A4:75:63:1D> REFCNT 3
[00:1C:A4:75:63:1D] SEND PROBE_RESP ON CHANNEL 6
RUM0: [00:1C:A4:75:63:1D] PROBE STATION DUE TO INACTIVITY
RUM0: [00:1C:A4:75:63:1D] SEND NULL DATA FRAME ON CHANNEL 6,
PWR MGT DIS
RUM0: [00:1C:A4:75:63:1D] PROBE STATION DUE TO INACTIVITY
RUM0: [00:1C:A4:75:63:1D] SEND NULL DATA FRAME ON CHANNEL 6,
PWR MGT DIS
RUM0: [00:1C:A4:75:63:1D] STATION TIMED OUT DUE TO
INACTIVITY (REFCNT 1)
RUM0: [00:1C:A4:75:63:1D] STATION WITH AID 0 LEAVES
RUM0: NODE_RECLAIM: REMOVE
0XC250B000<00:1C:A4:75:63:1D> FROM NEIGHBOR
TABLE, REFCNT 1
RUM0: _IEEE80211_FREE_NODE
0XC250B000<00:1C:A4:75:63:1D> IN <GONE> TABLE
THE LAST 8 MESSAGES APPEAR LONG AFTER THE DEVICE ITSELF HAS
STOPPED
TRYING AND DECLARED IT UNCONNECTABLE.
I DON'T KNOW ENOUGH OF WIFI IMPLEMENTATION TO DRAW SOLID
CONCLUSIONS BUT
THIS SEEMS TO ME LIKE THE DEVICE IS IGNORING INFORMATION
GIVEN TO IT BY
THE FREEBSD-RUN ADAPTER AND IS RETRYING SEVERAL TIMES UNTIL
IT GIVES UP.
HERE'S IFCONFIG FOR RUM0:
RUM0:
FLAGS=108843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NEEDS
GIANT>
METRIC 0 MTU 1500
ETHER 00:1C:F0:9D:08:B3
INET 10.0.0.3 NETMASK 0XFFFFFF00 BROADCAST
10.0.0.255
MEDIA: IEEE 802.11 WIRELESS ETHERNET AUTOSELECT
<ADHOC>
(AUTOSELECT <ADHOC>)
STATUS: ASSOCIATED
SSID C1 CHANNEL 6 (2437 MHZ 11G) BSSID
9A:04:A0:16:24:54
AUTHMODE OPEN PRIVACY OFF TXPOWER 50 SCANVALID 60
BGSCAN
BGSCANINTVL 300 BGSCANIDLE 250 ROAM:RSSI11G 7
ROAM:RATE11G 5
PROTMODE CTS
HERE'S "IFCONFIG RUM0 LIST STA":
ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ
CAPS FLAG
00:1C:F0:9D:08:B3 0 6 1M 15.5 0 0 80 I
A
00:1C:A4:75:63:1D 0 6 1M 14.5 0 2 96
A
IS THE DIFFERENCE IN CAPS SIGNIFICANT? OBVIOUSLY, I CAN'T
INFLUENCE THE
DEVICE IN ANY WAY TO CONFIGURE ITSELF, BUT WHEN IT SCANS THE
AVAILABLE
SSIDS, IT KNOWS THIS ONE IS IN "AD-HOC" MODE AND
HAS THE CORRECT CHANNEL
LISTED.
ANY IDEAS WHAT TO TRY NEXT? FIDDLING WITH ADHOC/HOSTAP
MODES, 11B AND
11G MODES, AUTHENTICATION, ETC. DOESN'T WORK. EVEN LONG
SHOTS ARE
APPRECIATED. THIS IS ON RELENG_7.
|
|
| Re: Connecting P1i to FreeBSD |
|
2008-04-25 01:54:23 |
On Fri, Apr 25, 2008 at 7:41 AM, Ivan Voras <ivoras freebsd.org> wrote:
> Hi,
>
> I'd like to connect SE P1i (a "smartphone"
device) to FreeBSD, in any
> possible way, via wireless (WLAN). The symptoms are
that it just reports
> "Connection failed" no matter what I do.
>
> Acquired data so far:
>
> 0) I'm trying adhoc mode without any authorization,
for now, just to get it
> working
> 1) The same wifi adapter (USB, D-Link DWL-G122) works
ok with Windows XP
> with adhoc mode (i.e. the device connects/associates to
the computer, can
> exchange network traffic, etc; in Windows I can bridge
the wifi device to
> the network card, etc. - in effect, no problems)
> 2) There's no way the same devices succeeds in talking
when the wifi
> adapter is on FreeBSD. The adapter is run via the rum
driver.
> 2a) The "scan network" action on the device
lists the WLAN SSID on the
> computer; also "ifconfig rum0 list sta" on
FreeBSD shows the device's MAC.
> 3) A third machine, a laptop, can connect to the
FreeBSD machine,
> everything works.
> 3a) Apparently SE P1i is quirky with its WLAN support,
but somehow it knows
> how to talk to Windows.
>
> Here's a debug trace from the FreeBSD machine
(wlandebug -i rum0 +debug
> +scan +assoc +node +xrate +rate +input +output +auth)
during the
> unsuccessful connection attempt. The "...1d"
MAC is from the P1i.
>
> rum0: received probe_req from 00:1c:a4:75:63:1d rssi
27
> rum0: [00:1c:a4:75:63:1d] recv probe req
> rum0: ieee80211_ref_node (ieee80211_send_mgmt:1574)
> 0xc250b000<00:1c:a4:75:63:1d> refcnt 3
> [00:1c:a4:75:63:1d] send probe_resp on channel 6
> rum0: received probe_req from 00:1c:a4:75:63:1d rssi
27
> rum0: [00:1c:a4:75:63:1d] recv probe req
> rum0: ieee80211_ref_node (ieee80211_send_mgmt:1574)
> 0xc250b000<00:1c:a4:75:63:1d> refcnt 3
> [00:1c:a4:75:63:1d] send probe_resp on channel 6
> rum0: received probe_req from 00:1c:a4:75:63:1d rssi
25
> rum0: [00:1c:a4:75:63:1d] recv probe req
> rum0: ieee80211_ref_node (ieee80211_send_mgmt:1574)
> 0xc250b000<00:1c:a4:75:63:1d> refcnt 3
> [00:1c:a4:75:63:1d] send probe_resp on channel 6
> rum0: received probe_req from 00:1c:a4:75:63:1d rssi
25
> rum0: [00:1c:a4:75:63:1d] recv probe req
> rum0: ieee80211_ref_node (ieee80211_send_mgmt:1574)
> 0xc250b000<00:1c:a4:75:63:1d> refcnt 3
> [00:1c:a4:75:63:1d] send probe_resp on channel 6
> rum0: received probe_req from 00:1c:a4:75:63:1d rssi
25
> rum0: [00:1c:a4:75:63:1d] recv probe req
> rum0: ieee80211_ref_node (ieee80211_send_mgmt:1574)
> 0xc250b000<00:1c:a4:75:63:1d> refcnt 3
> [00:1c:a4:75:63:1d] send probe_resp on channel 6
> rum0: received probe_req from 00:1c:a4:75:63:1d rssi
25
> rum0: [00:1c:a4:75:63:1d] recv probe req
> rum0: ieee80211_ref_node (ieee80211_send_mgmt:1574)
> 0xc250b000<00:1c:a4:75:63:1d> refcnt 3
> [00:1c:a4:75:63:1d] send probe_resp on channel 6
> rum0: received probe_req from 00:1c:a4:75:63:1d rssi
25
> rum0: [00:1c:a4:75:63:1d] recv probe req
> rum0: ieee80211_ref_node (ieee80211_send_mgmt:1574)
> 0xc250b000<00:1c:a4:75:63:1d> refcnt 3
> [00:1c:a4:75:63:1d] send probe_resp on channel 6
> rum0: received probe_req from 00:1c:a4:75:63:1d rssi
25
> rum0: [00:1c:a4:75:63:1d] recv probe req
> rum0: ieee80211_ref_node (ieee80211_send_mgmt:1574)
> 0xc250b000<00:1c:a4:75:63:1d> refcnt 3
> [00:1c:a4:75:63:1d] send probe_resp on channel 6
> rum0: [00:1c:a4:75:63:1d] probe station due to
inactivity
> rum0: [00:1c:a4:75:63:1d] send null data frame on
channel 6, pwr mgt dis
> rum0: [00:1c:a4:75:63:1d] probe station due to
inactivity
> rum0: [00:1c:a4:75:63:1d] send null data frame on
channel 6, pwr mgt dis
> rum0: [00:1c:a4:75:63:1d] station timed out due to
inactivity (refcnt 1)
> rum0: [00:1c:a4:75:63:1d] station with aid 0 leaves
> rum0: node_reclaim: remove
0xc250b000<00:1c:a4:75:63:1d> from neighbor
> table, refcnt 1
> rum0: _ieee80211_free_node
0xc250b000<00:1c:a4:75:63:1d> in <gone> table
>
> The last 8 messages appear long after the device
itself has stopped trying
> and declared it unconnectable.
>
> I don't know enough of wifi implementation to draw
solid conclusions but
> this seems to me like the device is ignoring
information given to it by the
> FreeBSD-run adapter and is retrying several times until
it gives up.
>
> Here's ifconfig for rum0:
>
> rum0:
flags=108843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NEEDS
GIANT>
> metric 0 mtu 1500
> ether 00:1c:f0:9d:08:b3
> inet 10.0.0.3 netmask 0xffffff00 broadcast
10.0.0.255
> media: IEEE 802.11 Wireless Ethernet autoselect
<adhoc> (autoselect
> <adhoc>)
> status: associated
> ssid C1 channel 6 (2437 Mhz 11g) bssid
9a:04:a0:16:24:54
> authmode OPEN privacy OFF txpower 50 scanvalid
60 bgscan
> bgscanintvl 300 bgscanidle 250 roam:rssi11g 7
roam:rate11g 5
> protmode CTS
>
> here's "ifconfig rum0 list sta":
>
> ADDR AID CHAN RATE RSSI IDLE TXSEQ
RXSEQ CAPS FLAG
> 00:1c:f0:9d:08:b3 0 6 1M 15.5 0 0
80 I A
> 00:1c:a4:75:63:1d 0 6 1M 14.5 0 2
96 A
Are you sure that your device works under IBSS mode?
BTW, it looks like you have third machine that is equipped
with
wireless device, so would you please grab a 802_11 tap when
your
device tries to connect to rum on your freebsd box:
tcpdump -ni your_third_wlan_iface -y ieee802_11 -w dump.bin
Best Regards,
sephe
--
Live Free or Die
_______________________________________________
freebsd-netfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscribefreebsd.org"
|
|
| Re: Connecting P1i to FreeBSD |
|
2008-04-26 18:26:08 |
SEPHEROSA ZIEHAU WROTE:
> ARE YOU SURE THAT YOUR DEVICE WORKS UNDER IBSS MODE?
YES, SINCE WINDOWS DOESN'T SUPPORT CREATING AN AP FROM THE
CARD, AND IT
CONNECTS TO WINDOWS. UNLESS THERE ARE OTHER MODES THAT CAN
DO THE SAME
THING...
> BTW, IT LOOKS LIKE YOU HAVE THIRD MACHINE THAT IS
EQUIPPED WITH
> WIRELESS DEVICE, SO WOULD YOU PLEASE GRAB A 802_11 TAP
WHEN YOUR
> DEVICE TRIES TO CONNECT TO RUM ON YOUR FREEBSD BOX:
> TCPDUMP -NI YOUR_THIRD_WLAN_IFACE -Y IEEE802_11 -W
DUMP.BIN
[NOMENCLATURE: LET'S CALL THE FREEBSD MACHINE WITH THE RUM
INTERFACE,
THE ONE I WISH TO ASSOCIATE THE DEVICE WITH, THE
"GATEWAY" AND THE OTHER
ONE THE "LAPTOP"].
I HAVE A SCAN FROM THE THE LAPTOP, BUT APPARENTLY IT DOESN'T
RECORD ALL
- ONLY BEACONS AND PROBE RESPONSES ARE IN THE DUMP AND ONLY
FROM TWO
NODES - MY OWN AND ONE OF THE NEIGHBOURS' (BUT IT'S A NOISY
NEIGBOURHOOD
AND THE DEVICE FINDS AT LEAST THREE MORE APS.
HERE'S A SAMPLE:
23:08:30.832242 PROBE RESPONSE (SPEEDTOUCH425488) [1.0* 2.0*
5.5* 11.0*
18.0 24.0 36.0 54.0 MBIT] CH: 6, PRIVACY
23:08:30.844990 BEACON (SPEEDTOUCH425488) [1.0* 2.0* 5.5*
11.0* 18.0
24.0 36.0 54.0 MBIT] ESS CH: 6, PRIVACY
23:08:31.011276 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
23:08:31.461225 PROBE RESPONSE (SPEEDTOUCH425488) [1.0* 2.0*
5.5* 11.0*
18.0 24.0 36.0 54.0 MBIT] CH: 6, PRIVACY
23:08:31.641185 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
23:08:32.272083 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
23:08:32.721339 PROBE RESPONSE (SPEEDTOUCH425488) [1.0* 2.0*
5.5* 11.0*
18.0 24.0 36.0 54.0 MBIT] CH: 6, PRIVACY
23:08:32.902988 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
23:08:33.351839 PROBE RESPONSE (SPEEDTOUCH425488) [1.0* 2.0*
5.5* 11.0*
18.0 24.0 36.0 54.0 MBIT] CH: 6, PRIVACY
23:08:33.533886 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
23:08:33.938823 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
23:08:33.940424 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
23:08:33.942064 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
23:08:33.944436 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
23:08:33.949696 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
23:08:33.953018 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
23:08:33.955180 PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0* 5.5*
11.0* 6.0 9.0
12.0 18.0 MBIT] CH: 2
ADDITIONALLY, I'VE RECORDED FROM THE GATEWAY MACHINE:
01:13:53.812038 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:13:53.812072 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:13:54.442969 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:13:54.442993 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:13:55.073911 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:13:55.073931 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:13:55.705028 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:13:55.705049 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:13:56.335801 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:13:56.335821 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:13:56.966747 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:13:56.966767 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:13:57.597697 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:13:57.597721 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:13:58.228636 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:13:58.228656 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:13:58.859586 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:13:58.859607 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:13:59.490529 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:13:59.490550 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:14:00.120474 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:14:00.120495 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:14:00.713427 0US PROBE REQUEST (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* MBIT]
01:14:00.713446 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:14:00.751416 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:14:00.751435 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:14:01.383364 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:14:01.383384 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:14:02.014315 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:14:02.014338 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:14:02.644945 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:14:02.644970 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:14:02.790241 0US PROBE REQUEST (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* MBIT]
01:14:02.790255 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
01:14:03.275200 0US PROBE REQUEST () [1.0* 2.0* 5.5* 11.0*
6.0 9.0 12.0
18.0 MBIT]
01:14:03.275219 0US PROBE RESPONSE (BSD7ADHOC) [1.0* 2.0*
5.5* 11.0* 6.0
9.0 12.0 18.0 MBIT] CH: 2
RAW SCANS ARE HERE:
HTTP://IVORAS.SHARANET.ORG/STUFF/SCANS.TGZ
|
|
| Re: Connecting P1i to FreeBSD |
|
2008-04-26 22:51:20 |
On Sun, Apr 27, 2008 at 7:52 AM, Ivan Voras <ivorasfreebsd.org> wrote:
> Ivan Voras wrote:
>
> > Sepherosa Ziehau wrote:
> >
> >
> > > Are you sure that your device works under
IBSS mode?
> > >
> >
> > Yes, since Windows doesn't support creating an AP
from the card, and it
> connects to Windows. Unless there are other modes that
can do the same
> thing...
> >
>
> Actually there is a difference; here's a dump from
laptop where the device
> connects to the Windows machine:
>
> 23:49:18.013539 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:18.045340 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
> 23:49:18.148408 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:18.374477 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:18.377198 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:18.379066 Probe Response (SpeedTouch425488)
[1.0* 2.0* 5.5* 11.0*
> 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY
> 23:49:18.659907 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
> 23:49:18.734842 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:18.762218 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
> 23:49:19.005423 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:19.008301 Probe Response (SpeedTouch425488)
[1.0* 2.0* 5.5* 11.0*
> 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY
> 23:49:19.026747 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:19.366882 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:19.376645 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
> 23:49:19.411652 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:19.636460 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:19.637575 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:19.888667 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
> 23:49:19.990770 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
> 23:49:19.997530 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:20.268038 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:20.269293 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:20.271670 Probe Response (SpeedTouch425488)
[1.0* 2.0* 5.5* 11.0*
> 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY
> 23:49:20.274467 Beacon (SpeedTouch425488) [1.0* 2.0*
5.5* 11.0* 18.0 24.0
> 36.0 54.0 Mbit] ESS CH: 6, PRIVACY
> 23:49:20.297986 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
> 23:49:20.492967 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:20.502751 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
> 23:49:20.629491 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:20.707738 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
> 23:49:20.899123 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:20.901458 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:20.989459 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:21.124700 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:21.219413 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
> 23:49:21.259747 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:21.321793 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
> 23:49:21.530624 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:21.531691 Probe Response (A2) [1.0* 2.0* 5.5*
11.0* Mbit] CH: 6,
> PRIVACY
> 23:49:21.533326 Probe Response (SpeedTouch425488)
[1.0* 2.0* 5.5* 11.0*
> 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY
> 23:49:21.833759 Beacon (A2) [1.0* 2.0* 5.5* 11.0*
Mbit] IBSS CH: 6, PRIVACY
>
> I didn't get the "Beacon" entries before. I
expected to see actual data
> packets in tcpdump, but I assume they are not in the
dump because we're only
> looking at the 802.11 events with -y ieee802_11?
>
I think you are using iwi to do the tap, could you put iwi
into
monitor mode, since iwi is "smart" device which
may filter certain
type of frames in non-monitor mode?
I tested my rum: the beacon template set in the hardware is
trashed in
a strange a pattern
What I got in the air; fc duration and certain part of mac
address is trashed:
11:04:57.256700 Assoc Request (sephe-adhoc) [1.0* 2.0* 5.5*
11.0* 6.0
9.0 12.0 18.0 Mbit]
0x0000: 0000 2a01 0032 0430 4860 6c18 f32f 077a
0x0010: 4e9c 3b6a eb9f b01d afbe e402 0000 0000
0x0020: 6400 2200 000b 7365 7068 652d 6164 686f
0x0030: 6301 0882 848b 960c 1218 2403 0101 0602
0x0040: 9056 e96b 88d0 f6ef 5cc9 1d
The actual beacon mbuf content:
80 00 00 00 ff ff ff ff ff ff 00 18 f3 2f 07 7a
4e 9c 3b 6a eb 9f 00 00 00 00 00 00 00 00 00 00
64 00 22 00 00 0b 73 65 70 68 65 2d 61 64 68 6f
63 01 08 82 84 8b 96 0c 12 18 24 03 01 01 06 02
00 00 2a 01 00 32 04 30 48 60 6c
After several small code change, I found that beacon
template size
can't exceeds 64bytes. Small template space means you could
only use
rum IBSS in 11b mode. I have tried to setup BEACON_BASE1
but without
result. If it is not a hardware design flaw then we will
need data
sheet to make it correct.
Best Regards,
sephe
--
Live Free or Die
_______________________________________________
freebsd-netfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscribefreebsd.org"
|
|
| Re: Connecting P1i to FreeBSD |
|
2008-04-26 22:52:58 |
On Sun, Apr 27, 2008 at 11:51 AM, Sepherosa Ziehau
<sepherosagmail.com> wrote:
>
> On Sun, Apr 27, 2008 at 7:52 AM, Ivan Voras
<ivorasfreebsd.org> wrote:
> > Ivan Voras wrote:
> >
> > > Sepherosa Ziehau wrote:
> > >
> > >
> > > > Are you sure that your device works
under IBSS mode?
> > > >
> > >
> > > Yes, since Windows doesn't support creating
an AP from the card, and it
> > connects to Windows. Unless there are other modes
that can do the same
> > thing...
> > >
> >
> > Actually there is a difference; here's a dump
from laptop where the device
> > connects to the Windows machine:
> >
> > 23:49:18.013539 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:18.045340 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> > 23:49:18.148408 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:18.374477 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:18.377198 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:18.379066 Probe Response
(SpeedTouch425488) [1.0* 2.0* 5.5* 11.0*
> > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY
> > 23:49:18.659907 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> > 23:49:18.734842 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:18.762218 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> > 23:49:19.005423 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:19.008301 Probe Response
(SpeedTouch425488) [1.0* 2.0* 5.5* 11.0*
> > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY
> > 23:49:19.026747 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:19.366882 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:19.376645 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> > 23:49:19.411652 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:19.636460 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:19.637575 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:19.888667 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> > 23:49:19.990770 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> > 23:49:19.997530 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:20.268038 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:20.269293 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:20.271670 Probe Response
(SpeedTouch425488) [1.0* 2.0* 5.5* 11.0*
> > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY
> > 23:49:20.274467 Beacon (SpeedTouch425488) [1.0*
2.0* 5.5* 11.0* 18.0 24.0
> > 36.0 54.0 Mbit] ESS CH: 6, PRIVACY
> > 23:49:20.297986 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> > 23:49:20.492967 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:20.502751 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> > 23:49:20.629491 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:20.707738 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> > 23:49:20.899123 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:20.901458 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:20.989459 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:21.124700 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:21.219413 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> > 23:49:21.259747 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:21.321793 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> > 23:49:21.530624 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:21.531691 Probe Response (A2) [1.0* 2.0*
5.5* 11.0* Mbit] CH: 6,
> > PRIVACY
> > 23:49:21.533326 Probe Response
(SpeedTouch425488) [1.0* 2.0* 5.5* 11.0*
> > 18.0 24.0 36.0 54.0 Mbit] CH: 6, PRIVACY
> > 23:49:21.833759 Beacon (A2) [1.0* 2.0* 5.5*
11.0* Mbit] IBSS CH: 6, PRIVACY
> >
> > I didn't get the "Beacon" entries
before. I expected to see actual data
> > packets in tcpdump, but I assume they are not in
the dump because we're only
> > looking at the 802.11 events with -y ieee802_11?
> >
>
> I think you are using iwi to do the tap, could you put
iwi into
> monitor mode, since iwi is "smart" device
which may filter certain
> type of frames in non-monitor mode?
>
> I tested my rum: the beacon template set in the
hardware is trashed in
> a strange a pattern
BTW, the pattern is anything beyond 64bytes will be wrapped.
See the
dump and the beacon content.
>
> What I got in the air; fc duration and certain part of
mac address is trashed:
> 11:04:57.256700 Assoc Request (sephe-adhoc) [1.0* 2.0*
5.5* 11.0* 6.0
>
> 9.0 12.0 18.0 Mbit]
> 0x0000: 0000 2a01 0032 0430 4860 6c18 f32f
077a
> 0x0010: 4e9c 3b6a eb9f b01d afbe e402 0000
0000
> 0x0020: 6400 2200 000b 7365 7068 652d 6164
686f
> 0x0030: 6301 0882 848b 960c 1218 2403 0101
0602
> 0x0040: 9056 e96b 88d0 f6ef 5cc9 1d
>
> The actual beacon mbuf content:
> 80 00 00 00 ff ff ff ff ff ff 00 18 f3 2f 07 7a
> 4e 9c 3b 6a eb 9f 00 00 00 00 00 00 00 00 00 00
> 64 00 22 00 00 0b 73 65 70 68 65 2d 61 64 68 6f
> 63 01 08 82 84 8b 96 0c 12 18 24 03 01 01 06 02
> 00 00 2a 01 00 32 04 30 48 60 6c
>
> After several small code change, I found that beacon
template size
> can't exceeds 64bytes. Small template space means you
could only use
> rum IBSS in 11b mode. I have tried to setup
BEACON_BASE1 but without
> result. If it is not a hardware design flaw then we
will need data
> sheet to make it correct.
>
>
>
> Best Regards,
> sephe
>
> --
> Live Free or Die
>
--
Live Free or Die
_______________________________________________
freebsd-netfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscribefreebsd.org"
|
|
| Re: Connecting P1i to FreeBSD |
|
2008-04-28 03:16:54 |
On Mon, Apr 28, 2008 at 7:22 AM, Ivan Voras <ivorasfreebsd.org> wrote:
> Sepherosa Ziehau wrote:
>
>
> >
> > > I think you are using iwi to do the tap,
could you put iwi into
> > > monitor mode, since iwi is "smart"
device which may filter certain
> > > type of frames in non-monitor mode?
> > >
> >
>
> Do you still need these tests since you did your own
with the rum device?
> Apparently my iwi device causes kernel panic when
switching modes or some
> related activity, so it's difficult to work with.
I just wanted to see whether the cause of your problem is
the same as mine.
Will iwi panic if you set "mediaopt monitor"
before bringing it up?
>
>
>
> >
> > > I tested my rum: the beacon template set in
the hardware is trashed in
> > > a strange a pattern
> > >
> > BTW, the pattern is anything beyond 64bytes will
be wrapped. See the
> > dump and the beacon content.
> >
>
> Yes, I see what you mean...
>
>
>
> >
...
> > >
> > > After several small code change, I found
that beacon template size
> > > can't exceeds 64bytes. Small template space
means you could only use
> > > rum IBSS in 11b mode. I have tried to setup
BEACON_BASE1 but without
> > >
> >
>
> I tried, and I can't run rum in IBSS in 11b (at least
the device in
> question ignores it as always). Can you?
On old system, before you bring rum up:
ifconfig rum0 mode 11b
It works fine for me; beacon size is less than 64bytes, if I
choose
short essid (short essid will not make 11g work, since even
one char
essid would make beacon size go beyond 64bytes)
But one thing I noticed, is that once you operate rum as
IBSS starter,
it always tries to sending beacons even if you set its
operation mode
back into STA, i.e. IBSS operation mode is
"sticky" o_O. I suspect
this is a driver bug.
>
>
>
> >
> > > result. If it is not a hardware design flaw
then we will need data
> > > sheet to make it correct.
> > >
> >
>
> I don't think it's a hardware fault since it
"just works" in Windows
> without any special configuration.
Nah, Windows puts rum into 11b mode and uses short essid
when working
as IBSS starter (see the tap you posted in the previous
email), could
you set essid to a 32 char string under Windows instead of
"A2"?
>
> Btw. what hardware revision is your rum device? Mine
is C1 (found on the
> label before the firmware version).
I do not have the hardware at hand now; Will take a look at
it when I
come back home.
>
> I don't know about data sheets, but the Linux driver
(rum-equivalent) is
> available from the chips' vendor:
> http://www.ralinktech.com/ralink/Home/Support/Linux.html
> It should be the one for RT2500USB.
I took a look at it yesterday, when I tried to program
BEACON_BASE1 
I don't think 11g IBSS operation mode will work under Linux.
That's
why data sheet will be necessary to make it correct.
Best Regards,
sephe
--
Live Free or Die
_______________________________________________
freebsd-netfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscribefreebsd.org"
|
|
[1-6]
|
|