brannondorsey / mitm-router

☠ Man-in-the-middle wireless access point inside a docker container 🐳
Other
421 stars 81 forks source link

iptables: No chain/target/match by that name. #1

Open askz opened 6 years ago

askz commented 6 years ago

Hi, I am struggling to make iptables work with your config. Maybe my host machine (archlinux) isn't properly matching your iptables setup? Let me know if you want more informations ! Thanks!

$ docker run -it --net host --privileged -e AP_IFACE="xxxx" -e INTERNET_IFACE="xxxx" -e SSID="Public" -v "$(pwd)/data:/root/data" -t brannondorsey/mitm-router
using random MAC address
Current MAC:  :an:on:ym:o:us: (unknown)
Permanent MAC: :an:on:ym:o:us: (Intel Corporate)
New MAC:      :an:on:ym:o:us: (IEC)
[ ok ] Starting system message bus: dbus.
[ ok ] Starting DNS forwarder and DHCP server: dnsmasq.
[ ok ] Starting advanced IEEE 802.11 management: hostapd.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
Proxy server listening at http://0.0.0.0:1337
brannondorsey commented 6 years ago

Hey there! I've seen this before. Does the rouge access point still work despite the warnings? Also, would you mind including the output of:

Thanks!

brannondorsey commented 6 years ago

I still see this occasionally but it has never seemed to cause a problem. If it does in the future comment here and I will re-open.

rbakaou commented 5 years ago

Hi, got the same issue. Here are the iptable rules. can you repoen the issue ?

iptable.txt iptablenat.txt

Can this be the wireless usb driver. I used ralink card? Bus 002 Device 006: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter

brannondorsey commented 5 years ago

Hey there, so is this causing an error for you or are you just seeing this output? In my experience, this text is printed to the screen most every time I run the docker container, however it doesn't ever cause I problem for me. If my memory serves me correctly, it is coming from here.

I've never used the RT5370 Wireless Adapter, but I assume it support monitor mode, correct? Have you seen the troubleshooting guide?