Jump to content

OrangePi Pc Plus Monitor Mode Issues


doye

Recommended Posts

I'm trying Monitor Mode under an orangePi pc plus which use the RTL8189FTV chip, And under armbian, After I config it as Monitor Mode, it crash with segment fault

 

root@orangepipcplus:~# iwconfig wlan0 mode monitor

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.624651] Internal error: Oops: 5 [#1] SMP THUMB2

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.740200] Process iwconfig (pid: 9670, stack limit = 0xed9a4210)

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.746393] Stack: (0xed9a5d6c to 0xed9a6000)

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.750768] 5d60:                            ecb55e8a ed9a5d94 bf850f71 f13480b0 ffffffe2

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.758967] 5d80: 0000001e ffffffe6 0000001a bf8f1b2f 00000004 00000000 f13480b0 00000000

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.767173] 5da0: 0000001a ffffffe6 0000001e ffffffe2 00000000 00000000 00000000 00000000

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.775380] 5dc0: 00000000 00000000 00000000 b217e1d9 0000ec90 f1348000 00000005 ed9a5ecc

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.783588] 5de0: c09ac494 00000006 00008b06 bf8eebd9 f1348000 bf8c5407 f1348000 bf8ecb63

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.791795] 5e00: c09ac4dc bf8ecae1 c0d03f48 c0864289 ed865000 0000000c 00000000 00000091

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.800003] 5e20: b6e8e000 c0d03f48 00000040 c01d70d5 b6f1d000 c0200709 00000037 c0200709

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.808182] 5e40: 00000000 c04efd59 c0afe37c b217e1d9 ec023180 00008b06 c0d03f48 ed9a5ebc

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.816357] 5e60: c0dcca80 00000000 be921ae4 00000000 be921cd0 c0864811 bf8ecae1 00000000

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.824532] 5e80: 00008b06 b217e1d9 c0d03f48 00008b06 00000000 c0d03f48 be921ae4 c0dcca80

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.832707] 5ea0: 00000051 c079aadb 00000054 ec7eddf8 ec109780 c0110f39 014080c0 6e616c77

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.840881] 5ec0: 00000030 00000000 00000000 00000006 00000004 00000000 00000000 b217e1d9

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.849056] 5ee0: c0d096f4 c9cea840 00008b06 b217e1d9 ed260aa0 c0d03f48 be921ae4 00000000

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.857231] 5f00: be921cd0 c0237c35 00000020 c023ce2f 00000000 c0d050a4 00000003 ed9a5f40

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.865406] 5f20: 00000000 c022a98b ef16ba10 c0d050a4 00000000 c0d03f48 ed260a80 c076afd3

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.873580] 5f40: ef16ba10 c076c6c9 00000000 00000003 c0dd0e10 00000000 00000000 b217e1d9

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.881754] 5f60: 00000000 c9cea840 00000000 c9cea840 00008b06 be921ae4 00000003 00000000

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.889929] 5f80: be921cd0 c02382bf 6e616c77 be921ae4 b6f91f04 be921e05 00000036 c01067e4

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.898104] 5fa0: ed9a4000 c01065e1 be921ae4 b6f91f04 00000003 00008b06 be921ae4 6e616c77

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.906279] 5fc0: be921ae4 b6f91f04 be921e05 00000036 be921dfa b6fc7ce8 00000000 be921cd0

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63339.914454] 5fe0: b6f1d711 be921adc 00464617 b6f1d716 000c0030 00000003 00000000 00000000

Message from syslogd@localhost at Nov  6 03:13:37 ...
 kernel:[63340.025094] Code: bf18 f811 3b01 bf24 (f811) 4b01
Segmentation fault

 

Does anyone use Monitor mode on this board or with RTL8189FTV chip?

 

 

I've tried another supported system lubuntu, After it config, And then I open Wireshark, I could get some sniffer packages, But it seems to lack a lot of packages, I'm using a mobile try a http request under a no decrypt wifi, But after I tried many times, then It only showed several related packages, but seems broadcast like arp is fully captured, Instead under my MacBook Pro I could get all packages

 

My guessing is some package (tcp udp) was filtered by something,

 

 What I want to know is does RTL8189FTV not fully supported with Monitor Mode or the driver or this board have an issue with?

Or Did anyone try Monitor Mode on this board or likely board ? Did u face same issues

 

Thx

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines