read register and proprietary frame
Home › Forums › Software › chibiArduino › read register and proprietary frame
Tagged: promiscuous, proprietary, register
This topic contains 3 replies, has 2 voices, and was last updated by akiba January 2, 2018 at 4:59 am.
-
AuthorPosts
-
November 1, 2017 at 1:32 pm #534
Hi
I need a little bit help with chibiarduino stack for exemple I awnt to check if promiscuous register is on but answer is little bit harzardous. I try to add this line in Wireshark Bridge sketch I have modify chibiUsrCfg.h file for define flag of promiscuous
byte registre_XAH_CTRL_1=chibiRegRead(0x17); //0x17 -> register XAH_CTRL_1 which you can find AACK_PROM_MODE
Serial.print(registre_XAH_CTRL_1);But in serial monitor of arduino appears registre_XAH_CTRL_1=0
For my application, I want to sniff a sensor with propritary frame so I think I need to modify some register and maybe I will find encryption payload but with wireshark will see frame, isn’t right?
Best regards
-
This topic was modified 5 months, 3 weeks ago by
yann-insa.
-
This topic was modified 5 months, 3 weeks ago by
yann-insa.
-
This topic was modified 5 months, 3 weeks ago by
-
November 1, 2017 at 2:06 pm #538
Hi Yann.
Setting XAH_CTRL_1 for the AACK_PROM_MODE enables promiscuous mode in the auto-ACK mode. When the chibiArduino stack sets promiscuous mode, it doesn’t use autoACK mode since there is no need for acknowledgements. Thats why that bit is 0.
When we go into promiscuous mode, I set it to receive frames manually with no automatic hardware processing (ie: no auto CRC check, no frame filtering based on address, etc). This allows you to get the completely raw data.Akiba
FreakLabs Open Source Wireless
Twitter: @freaklabs
Facebook: https://www.facebook.com/freaklabswireless -
November 1, 2017 at 3:36 pm #539
Akiba,
Now, I can check all register, so you right all bite of XAH_CTRL_1 are in low level. Okay, before i didn’t understand that promiscuous mode is only for acknowledge frame.
Do you know is we have any filtering enable that block received frame?But I don’t understand why I don’t see frame (proprietary frame protocol (MAC layer is not compliant with 802.15.4) in wireshark with sensniff.
Thanks in advance
regards-
This reply was modified 5 months, 3 weeks ago by
yann-insa.
-
This reply was modified 5 months, 3 weeks ago by
yann-insa.
-
This reply was modified 5 months, 3 weeks ago by
-
January 2, 2018 at 4:59 am #655
Hi Yann.
It sounds like the frames you’re trying to sniff are encrypted. That means, you’re likely getting something but it might be scrambled. Usually, the MAC layer would be compatible with 802.15.4 since it’s a standard. Then there would be other protocols on top of it.
AkibaAkiba
FreakLabs Open Source Wireless
Twitter: @freaklabs
Facebook: https://www.facebook.com/freaklabswireless -
AuthorPosts
You must be logged in to reply to this topic.