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

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

Open
askz opened this issue Jul 31, 2017 · 4 comments
Open

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

askz opened this issue Jul 31, 2017 · 4 comments

Comments

@askz
Copy link

askz commented Jul 31, 2017

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
Copy link
Owner

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:

  • sudo iptables --list
  • sudo iptables -t nat --list

Thanks!

@brannondorsey
Copy link
Owner

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
Copy link

rbakaou commented Jul 30, 2018

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 brannondorsey reopened this Jul 30, 2018
@brannondorsey
Copy link
Owner

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.

  • iptables: No chain/target/match by that name. is the output of the iptables -C check to see if a rule already exists (it isn't an error, it is actually useful for the BASH logic).
  • iptables: Bad rule (does a matching rule exist in that chain?). I can't remember off hand rn what this error message means, but I see it regularly even when mitm-router is working correctly.

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

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