Not connecting to the AP? about fluxion

[deltaxflux]

@TheProtocoler

Well yes this is a driver issue. I missed to look at your wireless card. The ALFA AWUS036H is unsupported for access points. So use another card.

I personally use the alfa AWUS036NH which support

Supported interface modes:

• IBSS
• managed
• AP
• AP/VLAN
• monitor
• mesh point

If you want a cheaper card I can recommend the TP-LINK TL-WN722N . Please not that only the TP-LINK TL-WN722N V1 Support monitor mode. The newer version V2 use another chipset and is not supported . If you have any trouble please let me know.

@vvbv
Do you use the same wireless card ?

EDIT:
First I thought that the variable $CHANNEL is negative but in this case its only a driver issue.

Cheers

[deltaxflux]

I will check it, thanks for your detailed issue.

[TheProtocoler]

@deltaxflux thank you so much, please do keep me updated.

[TheProtocoler]

@deltaxflux I might have found the problem. I tried using Linset, I got through the spanish menu, and I think the problem being is that when creating the evil twin, you have a new terminal opening up called "DHCP" in green, On linset, the Multiple interfaces which match the same subnet is eth0 and at0. While in fluxion, it's eth0 and wlan0. On Linset I can't really get redirected to the log in page everytime (although i got to the login page a few times and upon entering the pass, nothing happens and i just get redirected back). I think the problem is that maybe you have to change the multiple interfaces that match the same subnet and shared network from wlan0 TO at0? Thanks!

The picture below shows the linset DHCP terminal, this is what I mean about it being at0:

And here's the one from Fluxion:

Also, whenever I start my AP on fluxion I get this error:

Which I don't get in Linset.

Here's my dhcpd.conf file located in /etc/dhcp/dhcpd.conf:

authoritative;
default-lease-time 600;
max-lease-time 7200;
subnet 192.168.1.128 netmask 255.255.255.128 {
option subnet-mask 255.255.255.128;
option broadcast-address 192.168.1.255;
option routers 192.168.1.129;
option domain-name-servers 8.8.8.8;
range 192.168.1.130 192.168.1.140;
}

I'm so sorry for making this so long, I just want to provide you as much details as possible because I really want this to work, I'm about to pull my hairs out, again, I'm really sorry and thank you

[deltaxflux]

I don't think so I thought it is a hostapd bug. Now it woks again flawless for me. Please share results.

[TheProtocoler]

@deltaxflux okay, now I can get connected to the internet although it has that yellow triangle on windows and i don't get redirected whatsoever. This might be a problem from my wireless adapter.

Since I have the AWUS036H the driver is rtl8187

When I started the evil AP I saw something interesting.

First I get the error:

(unable to set resolver..)
I get this error on kali and not on Parrot Helium. So I tried on both kali and parrot but nothing worked.

Then on Kali, I noticed in the /tmp/TMPflux/hostapd.conf Of course I can only check while the evil AP is running because when it is not running TMPflux is empty (I suppose this only gets there when the evil AP has started running).

Anyway, I opened hostapd.conf while the evil ap was running and I saw this

It says that the driver is nl80211, so I searched more because I wanted more information and I got to know it's the new version that supports Hostapd. However, it only supports wireless cards with AP mode.

Here's a text from the official linuxwireless.org/en/users/Documentation/hostapd that says:

To communicate with a kernel driver hostapd has to use some interface. All new cfg80211 (and mac80211) based drivers that implement AP functionality are supported using nl80211 interface.

So i opened up a terminal and typed iw list_

max # scan SSIDs: 4
max scan IEs length: 2285 bytes
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* 00-0f-ac:10
* GCMP (00-0f-ac:8)
* 00-0f-ac:9
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* monitor

It doesnt really say that it supports AP mode.

Which led me to think that maybe it is my wireless adapter?

Do you know someone of whom uses the ALFA AWUS036H with fluxion?

May I know which wireless adapter you are using? Thank you again.

[vvbv]

I have the same problem. :(

[TheProtocoler]

@deltaxflux

I thought so. Thanks again! And yes, I thought that too at some point. I thought that the $Channel was negative, so I tried to change my wireless adapter's interface to my victim's channel. Still didn't work, so I thought this is a problem from my wireless adapter. Since AWUS036H is pretty outdated nowadays haha, thank you for the help again!

@vvbv

It looks like you have the same problem as me, maybe it's just your wireless network adapter.

Cheers!

[vvbv]

This is my hardware information @deltaxflux , sorry for the delay in responding. I have always used this card with fluxion.

root@router:~# lshw -C network
*-network
description: Ethernet interface
product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:08:00.0
logical name: enp8s0
version: 01
serial: 00:a0:d1:8c:77:d0
size: 10Mbit/s
capacity: 100Mbit/s
width: 64 bits
clock: 33MHz
capabilities: pm vpd msi pciexpress bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half latency=0 link=no multicast=yes port=MII speed=10Mbit/s
resources: irq:27 ioport:a000(size=256) memory:f8200000-f8200fff memory:f8220000-f823ffff
*-network
description: Wireless interface
physical id: 1
bus info: usb@1:6
logical name: wlx00164478ba7d
serial: 00:16:44:78:ba:7d
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=rtl8187 driverversion=4.8.0-58-generic firmware=N/A ip=192.168.1.2 link=yes multicast=yes wireless=IEEE 802.11

[deltaxflux]

@vvbv
Please do iw list

[vvbv]

@deltaxflux , I tried a previous version, and I no longer have channel -1 error, but the dns server does not start. What version of isc-dhcp-server do you use?.

router@router:~$ iw list
Wiphy phy6
max # scan SSIDs: 4
max scan IEs length: 2285 bytes
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* 00-0f-ac:10
* GCMP (00-0f-ac:8)
* 00-0f-ac:9
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* monitor
Band 1:
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps
* 5.5 Mbps
* 11.0 Mbps
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm)
* 2472 MHz [13] (20.0 dBm)
* 2484 MHz [14] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* Unknown command (104)
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
software interface modes (can always be added):
* monitor
interface combinations are not supported
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports low priority scan.
Device supports scan flush.
Device supports AP scan.
Device supports per-vif TX power setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM

[deltaxflux]

Your interface is not supported.

This is your output:
Supported interface modes:

• IBSS
• managed
• monitor

This is what it looks like

Supported interface modes:

• IBSS
• managed
• AP
• AP/VLAN
• monitor
• mesh point

[navyarm]

Hi, deltaflux. I have a problem like this, fluxion creates the fake AP with all Wi-Fi network except one. How can I solve this problem?. (It seems odd to me that it worked with this network before, but now do not work). I have this problem since my pc has turned off while the fake AP was on. Also from that time i see a Wi-Fi network without name and with a negative channel (see the picture)
. Sorry for my english bro

[behzad1k]

hi @deltaxflux
Im afraid I have the same problem as the others here
please check out my iw list :

z0b@z0b:~$ iw list
Wiphy phy1
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Device supports T-DLS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CCMP-256 (00-0f-ac:10)
* GCMP-128 (00-0f-ac:8)
* GCMP-256 (00-0f-ac:9)
* CMAC (00-0f-ac:6)
* CMAC-256 (00-0f-ac:13)
* GMAC-128 (00-0f-ac:11)
* GMAC-256 (00-0f-ac:12)
Available Antennas: TX 0x1 RX 0x3
Configured Antennas: TX 0x1 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
* P2P-client
* P2P-GO
* outside context of a BSS
Band 1:
Capabilities: 0x116e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (16.0 dBm)
* 2417 MHz [2] (16.0 dBm)
* 2422 MHz [3] (16.0 dBm)
* 2427 MHz [4] (16.0 dBm)
* 2432 MHz [5] (16.0 dBm)
* 2437 MHz [6] (16.0 dBm)
* 2442 MHz [7] (16.0 dBm)
* 2447 MHz [8] (16.0 dBm)
* 2452 MHz [9] (16.0 dBm)
* 2457 MHz [10] (16.0 dBm)
* 2462 MHz [11] (16.0 dBm)
* 2467 MHz [12] (16.0 dBm) (no IR)
* 2472 MHz [13] (16.0 dBm) (no IR)
* 2484 MHz [14] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* tdls_mgmt
* tdls_oper
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* connect
* disconnect
* channel_switch
* set_qos_map
* Unknown command (121)
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1,
total <= 2048, #channels <= 1, STA/AP BI must match
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports low priority scan.
Device supports scan flush.
Device supports AP scan.
Device supports per-vif TX power setting
P2P GO supports CT window setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Device supports active monitor (which will ACK incoming frames)
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
Device supports configuring vdev MAC-addr on create.

[deltaxflux]

@navanchauhan

Well, it is clear why it doesn't work. How should hostapd use a negative channel? This "bug" appears mostly because airodump-ng can't capture enough packages or they are invalid because you capture not the entire package. Airodump-ng signify this with -1. You could solve this if you capture longer, reduce the range or use a more powerfull wireless card.

@be-we
Looks like your wireless card is supported but I need more information about your environment. Can you please open a new issue with all details present including the diagnostic script.

[aqeel5user]

awus036h working smoothly in wifphisher. try it. i am using it.

[matic914]

@deltaxflux I use ALFA AWUS036NH. I follow all the steps and my problem is that at the moment of entering the language of the web interface (Spanish), everything is fine but the window of the twin web does not open and neither redirects me using the cell phone or another PC. Sorry for my english!!

[deltaxflux]

Summery

Well, debug this is pretty hard. It would be a pleasure if you could help me and share information.

Debugging lighttpd

First we make sure that you submodules are installed. While beeing in the fluxion directory do:
git submodule init && git submodule update

This clones all required submodules. To make sure that you have all required files but the main issue here is the lighttpd or the fakedns script.We try to figure out this.

1. We check if the lighttpd is working propertly.
2. Close the lighttpd window if any and try to run lighttpd manually
3. Use following command lighttpd -f <conf>

Note The lighttpd config is located inside the fluxion temp directory normally in /tmp/fluxspace

If some strange errors appear let me know

Debugging fakedns

1. Run the fakedns script python2 <script> Located inside the fluxion temp directory.

Final words

Please create a new issue with all required information and I will check it out as soon as possible.

Edit: I remove your screenshot because you could get doxed.

[zhienime]

I have problem like this...