发表文章

[Python] -iI 引发异常, 不知道原因 -iI raises exception with no known reason[wifiphisher]

Jinovas 2017-10-9 38

版本:
1。3
卡利4.9。0
wlan0 英特尔公司无线 7260 (转速 5b)
wlan1 rt2800usb Ralink 技术, Corp. RT2870/RT3070

描述: 在这里给出一个更具分析性的描述。iw listiwconfig 命令的输出可能会有帮助。

sudo iwconfig
lo        no wireless extensions.

wlan1     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=30 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
wlan0     IEEE 802.11  ESSID:" "  
          Mode:Managed  Frequency:2.452 GHz  Access Point: 6C:B0:CE:FC:3D:EA   
          Bit Rate=1 Mb/s   Tx-Power=22 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality=67/70  Signal level=-43 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:55   Missed beacon:0

脚本输出: 粘贴工具的输出, 包括任何堆栈跟踪。

我得到了一个例外, 但没有实际的原因给出。全新安装 wifiphisher 从这里, 确保所有的要求都正确安装。

此外, 我的 "wlan1" 接口不是由网络管理器管理的, 所以我把它与 ifconfig 在一个我使用的迷你脚本。然而, "wlan0" 是由网络管理器管理的, 但即使我停止网络管理器, 我仍然会得到同样的错误。

sudo wifiphisher -nJ -p firmeware_upgrade -iI wlan0 -aI wlan1 
[*] Starting Wifiphisher 1.3 at 2017-06-22 22:43
Traceback (most recent call last):
  File "/usr/local/bin/wifiphisher", line 11, in <module>
    load_entry_point('wifiphisher==1.3', 'console_scripts', 'wifiphisher')()
  File "/usr/local/lib/python2.7/dist-packages/wifiphisher/pywifiphisher.py", line 776, in run
    engine.start()
  File "/usr/local/lib/python2.7/dist-packages/wifiphisher/pywifiphisher.py", line 572, in start
    internet_interface = self.network_manager.set_internet_iface(args.internetinterface)
  File "/usr/local/lib/python2.7/dist-packages/wifiphisher/common/interfaces.py", line 367, in set_internet_iface
    raise Exception
Exception
原文:

Version:
1.3
kali 4.9.0
wlan0 Intel Corporation Wireless 7260 (rev 5b)
wlan1 rt2800usb Ralink Technology, Corp. RT2870/RT3070

Description: Give a more analytical description here. The output of the iw list and iwconfig commands may be helpful.

sudo iwconfig
lo        no wireless extensions.

wlan1     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=30 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
wlan0     IEEE 802.11  ESSID:" "  
          Mode:Managed  Frequency:2.452 GHz  Access Point: 6C:B0:CE:FC:3D:EA   
          Bit Rate=1 Mb/s   Tx-Power=22 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality=67/70  Signal level=-43 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:55   Missed beacon:0

Script output: Paste the output of the tool, including any stack traces.

I get an exception raised but no actual reason given. Fresh install of wifiphisher from here, made sure all requirements were installed correctly.

Also, my "wlan1" interface is not managed by network-manager so I bring it up with ifconfig in a mini script I use. "wlan0" is however managed by network-manager but even when I stop network-manager, I still get same error.

sudo wifiphisher -nJ -p firmeware_upgrade -iI wlan0 -aI wlan1 
[*] Starting Wifiphisher 1.3 at 2017-06-22 22:43
Traceback (most recent call last):
  File "/usr/local/bin/wifiphisher", line 11, in <module>
    load_entry_point('wifiphisher==1.3', 'console_scripts', 'wifiphisher')()
  File "/usr/local/lib/python2.7/dist-packages/wifiphisher/pywifiphisher.py", line 776, in run
    engine.start()
  File "/usr/local/lib/python2.7/dist-packages/wifiphisher/pywifiphisher.py", line 572, in start
    internet_interface = self.network_manager.set_internet_iface(args.internetinterface)
  File "/usr/local/lib/python2.7/dist-packages/wifiphisher/common/interfaces.py", line 367, in set_internet_iface
    raise Exception
Exception
相关推荐
最新评论 (21)
Jinovas 2017-10-9
1

刚刚尝试 "wifiphisher-aI wlan1-新泽西州", 我得到这个

forwifiphish

原文:

just tried "sudo wifiphisher -aI wlan1 -nJ" and I get this

forwifiphish

anakin1028 2017-10-9
2

关于第二个问题, 您能帮助我们使用 wireshark 来捕获数据包吗?
可以使用以下命令:

iwconfig wlan0 mode montor
ifconfig wlan0 up
#change 11 to the channel of target ap

我想问题是信标是畸形的, 我们不能正确处理它。

原文:

About the second issue, can you help us use wireshark to capture the packets?
You can use the following commands:

iwconfig wlan0 mode montor
ifconfig wlan0 up
iwconfig wlan0 channel 11 #change 11 to the channel of target ap

I guess the problem is beacon is malformed, and we don't handle it properly.

anakin1028 2017-10-9
3

我们应该解决这个问题我只是忘了您可以提取最新的提交, 然后重试吗?

原文:

we should have fixed this issue.I just forgot. Can you pull the latest commit and try again?

anakin1028 2017-10-9
4

关于第一个问题, 我们不支持通过无线接口为 V1.3 的互联网连接。但您可以使用此功能来提取最新的提交。

原文:

About the first issue, we don't support internet connection by wireless interface for V1.3. But you can pull the latest commit to use this feature.

Jinovas 2017-10-9
5

当然可以!我可以在下班后抓住他们只是去上班

原文:

Yeah for sure! I can capture them after work. Just headed into work.

anakin1028 2017-10-9
6

@mpkosewski 感谢:) 再次读取代码后, 我想您可能对最新版本有同样的问题。除了捕获, 您使用什么适配器作为干扰接口?

原文:

@mpkosewski thanks : ) After reading the code again, I guess you may have the same problem with the latest version. Besides from the capture, what adapter do you use as the jamming interface?

Jinovas 2017-10-9
7

嗯, 我有所有3的主要阿尔法卡哈哈, 但我最喜欢的是 awus036nh (我想) 是绿色的。我还没有得到足够的测试的干扰, 但该卡在 Github 的 wifi 干扰机应用程序体面。

原文:

Well I have all 3 of the main alfa cards lol but my favorite is the awus036nh (I think) it's the green one. I haven't gotten far enough to test the Jamming yet but that card does decent with the wifi jammer app on Github.

anakin1028 2017-10-9
8

是的。你的卡没有问题做干扰, 我有点误导虽然。我想说的是, 我们将使用适配器来嗅出信标并从信标帧中提取 RSSI。由于 RSSI 信息是特定于供应商的, 我们可能会为您捕获的信标提取错误的缓冲区位置。
让我们看看我们能否从你的捕获中挖出一些东西:)

原文:

Yes. There is no problem for your card to do jamming, I'm a little misleading though. What I want to say is that we'll use the adapter to sniff the beacons and extract the RSSI from the beacon frames. Since RSSI info is vendor specific, we may extract wrong position of the buffer for the beacon you captured.
Let's see if we can dig out something from your capture : )

Jinovas 2017-10-9
9

当然可以!乐意帮忙!这是一个分钟, 因为我已经与 scapy 的原始数据包和我自己的 "探头嗅探器" 大声笑, 但我不记得读过的 RSSI 是非常供应商具体?

边注: 我希望使用一个实际的等式在我的朋友谁是数学奇才的帮助下, 测量嗅到的信标, 并显示实际距离与只是一个功率水平估计他们是通过视觉分析环境和作出估计大声笑

原文:

ok for sure! happy to help! It's been a min since I've worked with raw packets with scapy and making my own "probe sniffer" lol but I don't remember reading that the RSSI was very vendor specific?

side note: I was hoping to use an actual equation with the help of my buddy who is a wiz at math, to measure the sniffed beacons and show an actual distance vs just a power level with estimating how far they are by visually analyzing the environment and making estimates lol

anakin1028 2017-10-9
10

您可以查看#478。我们有一个关于 rssi 问题的讨论。rssi 是在 radiotap 部件中定义的, 它是由供应商作为额外信息添加的, 因此供应商之间的位置可能有所不同。

原文:

you can have a look at #478. We have a discussion there about the rssi problem. rssi is defined in the radiotap part and it is added by the vendor as an extra information, so the position of this may be vary between vendors.

Jinovas 2017-10-9
11

我为米娅道歉没有感觉良好的周末和被淹没在工作, 没有线索跆拳道, 我做的工作仍然大声笑, 我会尝试得到这些日志和做一个更大的测试今天。我现在下班回家去了。

原文:

I apologize for being MIA. Wasn't feeling good most of the weekend and been swamped at work with no clue wtf i'm doing at work still lol I'll try to get those logs and do a lil more testing today. I headed home from work now.

Jinovas 2017-10-9
12

@anakin1028很高兴了解 RSSI 和供应商。我可能不得不协作与你的项目, 我一直在工作和关闭了一段时间 (我为自己做了太多的可恶的项目笑)。

原文:

@anakin1028 good to know about the RSSI and vendor. I might have to collab with you on a project I've been working on on and off for a while now(I make too many damn projects for myself lol).

Jinovas 2017-10-9
13

另外, 作为一个随机的问题, 你们不支持无线互联网连接, 因为你使用 airmon 或其他原因?我只问, 因为我已经遇到了多个流行的工具, 使用 airmon 明显打破了互联网连接。我有一个小的脚本, 实际工作一样好, 并不会打破互联网连接。它没有什么特别的或壮观的, 一旦你真的看到它大声笑, 但它的工作完美的一切, 我扔在它。

甚至得到法力工具箱的工作, 而不是 eth0。

只是好奇 =]

原文:

Also, as a random question, do you guys not support wireless Internet connection because you use airmon-ng or another reason? I only ask because I've run into multiple popular tools that use airmon-ng which obviously breaks internet connectivity. I have a little script that works practically just as well and WON'T break the internet connection. Its nothing special or spectacular once you actually see it lol but it's worked perfectly with everything I've thrown at it.

Even got mana-toolkit working with that instead of eth0.

Was just curious =]

anakin1028 2017-10-9
14

@mpkosewski

我可能不得不协作与你的项目, 我一直在工作和关闭了一段时间 (我为自己做了太多的可恶的项目笑)。

我们可以使用 wifiphisher 来了解 RSSI 的解码错误。我认为您可以使用 wifiphisher 重现此问题, 同时使用 wiresharktcpdump 嗅出帧并在该线程中发布捕获。如果您对此问题感兴趣, 可以通过 scapy 编写简单的脚本来侦听信标, 并将解码错误信标的原始数据包格式与您从 wireshark 获取的捕获进行比较。

你们不支持无线互联网连接, 因为你使用 airmon 或其他原因?

我们现在支持此功能。您可以提取最新的提交, 并提供 internet 接口作为 -iI wlan0 #wlan0 is the internet interface

wifiphisher V1.3 中, 我们使用 airmon-ng check kill 来杀死干扰过程, 因此, 为什么在那时我们不能使用无线接口作为互联网接口, 因为管理被杀害。现在, 在给定 -iI 时, 我们不使用它来杀死管理, 但用户必须在 NetworkManager.conf 中将 AP/Deauth 接口设置为 un-managed

原文:

@mpkosewski

I might have to collab with you on a project I've been working on on and off for a while now(I make too many damn projects for myself lol).

We may use wifiphisher to see why there is a decoding error for the RSSI. I think you can use wifiphisher to reproduce this problem and in the meantime use wireshark or tcpdump to sniff the frames and post the capture in this thread. If you are interested in this problem, you can write simple script to listen the beacons by scapy and compare the raw packet format of decoding error beacon to the capture you got from wireshark.

do you guys not support wireless Internet connection because you use airmon-ng or another reason?

We have supported this feature now. You can pull the latest commit and provide the internet interface as -iI wlan0 #wlan0 is the internet interface.

In the wifiphisher V1.3, we use airmon-ng check kill to kill the interfering processes, so that why at that time we cannot use wireless interface as internet interface since NetworkManager is being killed. For now, we don't use it to kill the NetworkManager when -iI is given, but users have to set the AP/Deauth interfaces as un-managed in the NetworkManager.conf.

Jinovas 2017-10-9
15

我们可以使用 wifiphisher 来了解 RSSI 的解码错误。我认为您可以使用 wifiphisher 重现此问题, 同时使用 wireshark 或 tcpdump 来嗅出帧并在该线程中发布捕获。如果您对此问题感兴趣, 您可以编写简单的脚本, 通过 scapy 来收听信标, 并将解码错误信标的原始数据包格式与您从 wireshark 获得的捕获进行比较。

我提到的项目太多了 (当我学习如何做每个部分, 然后把它们组合成一个更大更复杂的应用程序。我的方式试图建立我自己的版本, airodump, 但有更多的选择, 如寻找特定供应商 MAC 的, 并给予估计的 measuable 距离的基础上 "自由空间路径损失" 公式。

路径损耗 (dB) = 32.44 + 20日志 (F (MHz)) + 20日志 (D (公里))-Gtx (dBi)-Grx (dBi)

我到目前为止有一个1班轮做作为出发点 (没有触及它在一段时间)。这一个只是扫描的 wifi, 但同样的概念将适用于我的设备扫描仪。不知怎的, 我打破了我的设备嗅探哈哈。wifi 扫描仪与 scapy 和 RSSI 级别的 pic 连接:
sofarscapy

看起来像 im 要做一些刷我的 scapy 哈哈 xD

在 wifiphisher V1.3 中, 我们使用 airmon 检查杀死来杀死干扰过程, 因此, 为什么当时我们不能使用无线接口作为互联网接口, 因为管理是被杀害。现在, 我们不使用它来杀死管理时, 二是给定的, 但用户必须设置 AP/Deauth 接口作为未在管理. conf。

就这样是的, 我必须做同样的事情与法力。我还没有完全脚本的一切, 但我有所有3阿尔法 wifi 适配器保存和评论除了一个我不希望网络管理器管理。

我们现在支持此功能。您可以提取最新的提交, 并提供互联网接口作为第二 wlan0 #wlan0 是互联网接口。

哦甜!我刚才这样做, 我现在就玩它, 看看会发生什么事 =]

原文:

We may use wifiphisher to see why there is a decoding error for the RSSI. I think you can use wifiphisher to reproduce this problem and in the meantime use wireshark or tcpdump to sniff the frames and post the capture in this thread. If you are interested in this problem, you can write simple script to listen the beacons by scapy and compare the raw packet format of decoding error beacon to the capture you got from wireshark

Well the project I was referring too I'm building in pieces (as I learn how to do each part and then combine them into a much bigger more complex app. I am in a way trying to build my own version of airodump-ng but with more options like looking for specific vendor MAC's and giving an estimated measuable distance based of the "Free Space Path Loss" formula.

PATH LOSS(dB) = 32.44 + 20log(F(MHz)) + 20log(D(km)) - Gtx(dBi) - Grx(dBi)

I so far have a 1 liner done as a starting point (haven't touched it in a while). This one just scan's for wifi but same concept would apply for my device scanner. Somehow a while back I broke my device sniffer lol. pic attached of wifi scanner with scapy and RSSI levels:
sofarscapy

Looks like im gunna have to do some brushing up on my scapy haha xD

In the wifiphisher V1.3, we use airmon-ng check kill to kill the interfering processes, so that why at that time we cannot use wireless interface as internet interface since NetworkManager is being killed. For now, we don't use it to kill the NetworkManager when -iI is given, but users have to set the AP/Deauth interfaces as un-managed in the NetworkManager.conf.

Right on. Yeah I had to do the same thing with mana. I haven't fully scripted everything out yet but I have all 3 Alfa wifi adapters saved and commented out except the one I don't want network-manager to manage.

We have supported this feature now. You can pull the latest commit and provide the internet interface as -iI wlan0 #wlan0 is the internet interface.

Oh sweet! I just now did so I'll play with it now and see what all happens =]

Jinovas 2017-10-9
16

到目前为止仍然 =/一切看起来 ok, 虽然与 wlan1 (AP 适配器) 在 wireshark。
wifiphishererror2

原文:

so far still =/ everything looks ok though with wlan1 (AP adapter) in wireshark.
wifiphishererror2

Jinovas 2017-10-9
17

啊哈!它的工作, 它看起来像!我所做的只是添加第二个 wifi 适配器来完成 deauthing。这是我到目前为止

我使用的命令是:
sudo wifiphisher -aI wlan1 -iI wlan0 -jI wlan2 -p firmware_upgrade

wifiphisher_working

总之, 我有..。

  1. wlan0 (内置英特尔无线 7260) 运行互联网
  2. wlan1 (阿尔法 AWUS036NH) 运行 AP
  3. wlan2 (阿尔法 AWUS036NHA) 运行 Deauth
原文:

Ah ha! got it working it looks like! All I did was add a second wifi adapter to do the deauthing. This is as far as I got so far

the command I used was:
sudo wifiphisher -aI wlan1 -iI wlan0 -jI wlan2 -p firmware_upgrade

wifiphisher_working

So in short, I have...

  1. wlan0 (Built-in Intel wireless 7260) running internet
  2. wlan1 (Alfa AWUS036NH) running the AP
  3. wlan2 (Alfa AWUS036NHA) running the Deauth
anakin1028 2017-10-9
18

我到目前为止有一个1班轮做作为出发点 (没有触及它在一段时间)。这一个只是扫描的 wifi, 但同样的概念将适用于我的设备扫描仪。不知怎的, 我打破了我的设备嗅探哈哈。wifi 扫描仪与 scapy 和 RSSI 级别的 pic 连接:

我再次猜测您需要从捕获中观察并与 scapy 中的原始数据包格式进行比较。例如: 我们假定 RSSI 位于 wifiphisher 中的 non-decoded part [-4:-3] or [-2:-1] 中。

啊哈!它的工作, 它看起来像!我所做的只是添加第二个 wifi 适配器来完成 deauthing。这是我到目前为止

很高兴听到这个:)

原文:

I so far have a 1 liner done as a starting point (haven't touched it in a while). This one just scan's for wifi but same concept would apply for my device scanner. Somehow a while back I broke my device sniffer lol. pic attached of wifi scanner with scapy and RSSI levels:

Again I guessed you need to observe from the capture and compare with raw packet format in scapy. For example: we assume the RSSI is in the non-decoded part [-4:-3] or [-2:-1] in wifiphisher.

Ah ha! got it working it looks like! All I did was add a second wifi adapter to do the deauthing. This is as far as I got so far

Good to hear about that : )

Jinovas 2017-10-9
19

又坏了:(

wifiphisherbrokeagain

再次, 我猜你需要观察从捕获和比较原始包格式在 scapy。例如: 我们假设 RSSI 在 non-decoded 部分 [-4:-3] 或 [-2:-1] 在 wifiphisher。

好吧, 我明白你在说什么

原文:

it broke again :(

wifiphisherbrokeagain

Again I guessed you need to observe from the capture and compare with raw packet format in scapy. For example: we assume the RSSI is in the non-decoded part [-4:-3] or [-2:-1] in wifiphisher.

ahhh ok i see what you're saying

anakin1028 2017-10-9
20

是的, 我们在#608中已看到此问题, 并且目的公关#656应解决此问题。

原文:

yes we have seen this issue in #608 and the purpose PR #656 should solve this issue.

sophron 2017-10-9
21

我相信这个问题已经不复存在了。如有必要, 请随时重新开张。

原文:

I believe this issue no longer exists. Feel free to re-open if necessary.

返回
发表文章
Jinovas
文章数
1
评论数
11
注册排名
60759