Login  •  Register


The time is now: Tue Jun 19, 2018 4:45 am

Emaculation wiki  •  Delete all board cookies



Post new topic  Reply to topic Page 2 of 2 [ 30 posts ]    Go to page Previous  1, 2
Print view Previous topic  |  Next topic
Author Message
PostPosted: Thu Apr 26, 2018 6:32 pm 
Offline
Student Driver

Joined: Tue Apr 10, 2018 7:24 pm
Posts: 14
No, the Raspberry Pi 3 onboard wifi driver definitely doesn't support monitor/promiscuous mode.

Proof: http://i.imgur.com/7tz6w81.png

Also, the sample capture program I'm using: https://opensourceforu.com/2011/02/capt ... m-libpcap/

Doesn't use the calls, pcap_set_rfmon() and pcap_set_promisc() that enable monitor/promiscuous modes.

Something else is going on here.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Thu Apr 26, 2018 6:59 pm 
Offline
Mac Mechanic
User avatar

Joined: Mon Sep 15, 2014 7:59 pm
Posts: 155
Sniffing packet on the network interface doesn't required to enable promiscuous mode on network interface. They are two different things.

The IP packet sent to/received from host OS network interface by sheep_net shares the same host OS NIC physical MAC address. The only difference is in IP address. You don't need to enable promiscuous mode.

I don't have any good recommendation to debug it further since wireshark seems to affect the outcome. Unless you want to debug this on Basilisk II side, otherwise be a happy ignorant and enjoy your gadget!

_________________
There is an App for that!
https://github.com/rickyzhang82


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Fri Apr 27, 2018 10:19 am 
Offline
Student Driver

Joined: Tue Apr 10, 2018 7:24 pm
Posts: 14
I'm not going to give up when I'm so close to what I need, which is a boot to Mac OS solution for
Raspberry Pi hardware, without Xorg. I'll recompile Basilisk with the debug option you highlighted
before and see if there is anything significant in the messages.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Fri Apr 27, 2018 8:38 pm 
Offline
Student Driver

Joined: Tue Apr 10, 2018 7:24 pm
Posts: 14
So I set DEBUG 1 and recompiled Basilisk. For each test I pinged 5 times to 192.168.1.1 then shut down.

First, just running Basilisk (ping FAILED)

Code:
pi@raspberrypi:~ $ BasiliskII
Basilisk II V1.0 by Christian Bauer et al.
Reading ROM file...
Ethernet address 76 72 9f 20 ec 82
Using SDL/alsa audio output
WARNING: RmvTime(0014a048): Descriptor not found
 packet received, triggering Ethernet interrupt
EtherIRQ
 header 76729f20ec82 c4ea1de8255c 0806
 calling protocol handler 000bb8c0, type 00000806, length 0000001c, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
 packet received, triggering Ethernet interrupt
EtherIRQ
 header ffffffffffff 08606ed76ecc 0800
 calling protocol handler 000bb8c0, type 00000800, length 000000e5, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
pi@raspberrypi:~ $


Second, running the libpcap demo program first, then Basilisk in a new terminal (ping SUCCESS)

Code:
pi@raspberrypi:~ $ BasiliskII
Basilisk II V1.0 by Christian Bauer et al.
Reading ROM file...
Ethernet address 76 72 42 ec ca 5d
Using SDL/alsa audio output
WARNING: RmvTime(0014a048): Descriptor not found
 packet received, triggering Ethernet interrupt
EtherIRQ
 header 767242ecca5d c4ea1de8255c 0806
 calling protocol handler 000bb8c0, type 00000806, length 0000001c, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
 packet received, triggering Ethernet interrupt
EtherIRQ
 header ffffffffffff c4ea1de8255c 0806
 calling protocol handler 000bb8c0, type 00000806, length 0000001c, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
 packet received, triggering Ethernet interrupt
EtherIRQ
 header 767242ecca5d c4ea1de8255c 0800
 calling protocol handler 000bb8c0, type 00000800, length 00000030, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
 packet received, triggering Ethernet interrupt
EtherIRQ
 header 767242ecca5d c4ea1de8255c 0800
 calling protocol handler 000bb8c0, type 00000800, length 00000030, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
 packet received, triggering Ethernet interrupt
EtherIRQ
 header 767242ecca5d c4ea1de8255c 0800
 calling protocol handler 000bb8c0, type 00000800, length 00000030, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
 packet received, triggering Ethernet interrupt
EtherIRQ
 header 767242ecca5d c4ea1de8255c 0800
 calling protocol handler 000bb8c0, type 00000800, length 00000030, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
 packet received, triggering Ethernet interrupt
EtherIRQ
 header 767242ecca5d c4ea1de8255c 0800
 calling protocol handler 000bb8c0, type 00000800, length 00000030, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
 packet received, triggering Ethernet interrupt
EtherIRQ
 header ffffffffffff 08606ed76ecc 0806
 calling protocol handler 000bb8c0, type 00000806, length 0000002e, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
 packet received, triggering Ethernet interrupt
EtherIRQ
 header ffffffffffff 9822ef92d659 0800
 calling protocol handler 000bb8c0, type 00000800, length 000000e5, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
 packet received, triggering Ethernet interrupt
EtherIRQ
 header ffffffffffff c6ea1de8255c 0800
 calling protocol handler 000bb8c0, type 00000800, length 000000f5, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
 packet received, triggering Ethernet interrupt
EtherIRQ
 header ffffffffffff c6ea1de8255c 0800
 calling protocol handler 000bb8c0, type 00000800, length 000000f1, data 003a988e, rha 0001ed44, read_packet 0001ed44
 EtherIRQ done
pi@raspberrypi:~ $


Please let me know what you think.


Top
 Profile  
Reply with quote Post a reply  
PostPosted: Mon Jun 11, 2018 10:41 am 
Offline
Mac Mechanic
User avatar

Joined: Mon Sep 15, 2014 7:59 pm
Posts: 155
Sorry to miss your thread.

It is hard for me to debug since I can't replicate your environment. If you are experienced in docker container or vagrant, how about we build BII in virtual env so that we have the same base line to start with?

I suspect the problem might related to your OS or network settings. By using virtual stuff, we can eliminate the OS difference. Then we only focus on networking.

_________________
There is an App for that!
https://github.com/rickyzhang82


Top
 Profile  
Reply with quote Post a reply  
Display posts from previous:  Sort by  
Post new topic  Reply to topic Page 2 of 2 [ 30 posts ]    Go to page Previous  1, 2


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
 

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group