-
-
Notifications
You must be signed in to change notification settings - Fork 318
Open
Description
The mobile device is connected normally, but there is no network and the Protal authentication page cannot be popped up. Manually accessing version 1.0.0.1 can enter the authentication page. Is there any setting that caused DNS hijacking failure
(移动设备连接正常,但是无网络,而且无法弹出 Protal 认证页面,手动访问 10.0.0.1 可以进入认证页面,是否哪里设置导致DNS劫持失败)
The startup configuration is as follows(启动配置如下):
wp3 --xpulp " \
set ssid 401; \
set interface wlan0; \
set proxy captiveflask; \
set captiveflask.WifiLogin true; \
set captiveflask.force_redirect_https_connection true; \
set captiveflask.force_redirect_to_url http://10.0.0.1; \
ignore pydns_server; \
set mode docker; \
start
无法劫持 HTTPS 流量,HTTP 的正常
wp3 > start
[+] enable forwarding in iptables...
[*] sharing internet connection with NAT...
[*] settings for captive portal:
[*] allow FORWARD UDP DNS
[*] allow traffic to captive portal
[*] block all other traffic in access point
[*] redirecting HTTP traffic to captive portal
[*] redirecting HTTPS traffic to captive portal
[+] starting hostpad pid: [108692]
wp3 > [+] hostapd is running
[*] starting pydhcp_server
[+] starting captiveflask pid: [108718]
[*] starting sniffkin3 port: [80, 8080]
[+] sniffkin3 -> httpCap activated
[+] sniffkin3 -> hexdump activated
[+] sniffkin3 -> emails activated
[+] sniffkin3 -> ftp activated
[+] sniffkin3 -> kerberos activated
[ captiveflask ] 04:50:08 - [*] CaptiveFlask v1.0.2 - subtool from wifipumpkin3
* Serving Flask app 'wifipumpkin3.plugins.bin.captiveflask'
* Debug mode: off
WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
* Running on http://10.0.0.1:80
Press CTRL+C to quit
Metadata
Metadata
Assignees
Labels
No labels