Databases
StackOverflow2013
Postsdbo
POAccessing wireless interface (802.11) at MAC layer (Linux)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAccessing wireless interface (802.11) at MAC layer (Linux)
    primarykey
    data
    text
    <p>I spent the last days reading through man pages, documentations and anything else google brought up, but I suppose I'm even more confused now than I was at the beginning.</p> <p>Here is what I want to do: I want to send and receive data packets with my own layer 3-x protocol(s) via a wireless interface (802.11) on Linux systems with C/C++. So far, so good. I do not require beacons, association or any AP/SSID related stuff. However, for data transmissions I'd like the MAC layer to behave "as usual", meaning unicast packets are ACK'd, retransmissions, backoff etc. I'd also like to enjoy the extended QoS capabilites (802.11e with 4 queues and different access categories). Promiscuous mode on the other hand is not a concern, I require only broadcast packets and packets sent to the specific station.</p> <p>What would be the right way to go about it? Most of the documentation out there on raw socket access seems to be focused on network sniffing and that does not help. I've been playing around with the <strong>monitor mode</strong> for some time now, but from what I've read so far, received packets are not ACK'd in monitor mode etc. Without monitor mode, what would be the alternative? Using <strong>ad hoc mode</strong> and unix raw sockets? Or do I have to fiddle around with the drivers?</p> <p>I'm not looking for a complete solution, just some good ideas, where to start. I read through the man pages for socket(2), socket(7) and packet(7) but that did not help concerning the behaviour of the MAC layer in different modes.</p> <p>Thanks in advance.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USrocktale
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAccessing wireless interface (802.11) at MAC layer (Linux)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAccessing wireless interface (802.11) at MAC layer (Linux)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAccessing wireless interface (802.11) at MAC layer (Linux)
      1. USabb
      1. VTBountyStart
    1. COYou might look and see if there is an open source *software* solution for generating test traffic - ie, mix of valid and invalid packets in order to see how equipment on the other end handles that. Presumably, this would have the ability to both perform complete usual operations, but also arbitrary variations (in order to introduce the desired errors). If such exists you might be able to either use it or learn from it.
      singulars
      1. POAccessing wireless interface (802.11) at MAC layer (Linux)
      1. USChris Stratton
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload