Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Built-In Wifi-Adapter in Docker Container #2

Closed
Emoe opened this issue Aug 27, 2018 · 6 comments
Closed

Built-In Wifi-Adapter in Docker Container #2

Emoe opened this issue Aug 27, 2018 · 6 comments

Comments

@Emoe
Copy link

Emoe commented Aug 27, 2018

Hi,

I have the following problem when using the shina-fi container. When I execurte airmon-ng, the output not only contains the mac80211_hwsim Wifi devices but also my built-in intel Wifi card, as wlan0.

PHY	Interface	Driver		Chipset

phy0	wlan0		iwlwifi		Intel Corporation Wireless 7260 (rev 83)
phy1	wlan1		mac80211_hwsim	Software simulator of 802.11 radio(s) for mac80211
phy2	wlan2		mac80211_hwsim	Software simulator of 802.11 radio(s) for mac80211

When i use airmon-ng to set wlan1 into Monitor Mode and execute airdodump, i don't recieve any Traffic from simulated Traffic.

Does anyone have similar problems running the container?

@kevthehermit
Copy link

Im still trying to get this working as well, so far the only error im seeing is Unsupported physical layer type 0x0323

root@shinai-fi:/opt/sensepost/bin# tcpreplay --stats=1 -i wlan0 --loop=0 /opt/sensepost/capture/sensepost.cap 
Warning in sendpacket.c:sendpacket_open_pf() line 936:
Unsupported physical layer type 0x0323 on wlan0.  Maybe it works, maybe it won't.  See tickets #123/318
Test start: 2018-10-07 19:12:22.245972 ...

After leaving for a few second it looks like no packets are being replayed

Actual: 0 packets (0 bytes) sent in 53.31 seconds
Rated: 0.0 Bps, 0.000 Mbps, 0.00 pps
Loop 863279...

This error is discussed - http://tcpreplay.synfin.net/ticket/123

@singe
Copy link
Contributor

singe commented Oct 24, 2018

Looking into this now. That ticket isn't the same thing as it's talking about 0x304 not 0x0323.

@singe
Copy link
Contributor

singe commented Oct 25, 2018

Two things:

  1. 0x304 (or 803 in decimal) is radiotap, according to include/uapi/linux/if_arp.h
    90 #define ARPHRD_IEEE80211_RADIOTAP 803 /* IEEE 802.11 + radiotap header */
    That shouldn't have changed in the last little while, and is a red herring.

  2. That warning isn't an exception, it's merely a warning and it doesn't break http://tcpreplay.synfin.net/browser/trunk/src/common/sendpacket.c?rev=2054#L638

So I'm still looking for why it doesn't replay anymore.

@singe
Copy link
Contributor

singe commented Oct 25, 2018

After rebuilding old kernels and kali docker images, I've narrowed the problem down to none of those :(

Looks like an issue with the .pcap, still not sure what specifically yet.

@singe
Copy link
Contributor

singe commented Oct 25, 2018

Oh my, it's the merged.cap, I merged two pcaps, one with a radiotap header, one without. Fix incoming.

@singe singe closed this as completed in fb77b12 Oct 25, 2018
@singe
Copy link
Contributor

singe commented Oct 25, 2018

Fixed in the last commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants