Giters

chef-cookbooks / iptables

Development repository for Chef Cookbook iptables

Home Page:https://supermarket.chef.io/cookbooks/iptables

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

iptables v1.8.2 (legacy): unknown option "--to-ports"

innateessence opened this issue · comments

commented

Cookbook version

[Version of the cookbook where you are encountering the issue]
I don't know what the 'cookbook' is referencing too

Chef-client version

[Version of chef-client in your environment]
iptables v1.8.2(legacy) [1:1.8.2-1 according to my pkg manager]

Platform Details

[Operating system distribution and release version. Cloud provider if running in the cloud]
ArchLinux - 5.1.7-arch1-1-ARCH

Scenario:

[What you are trying to achieve and you can't?]
NAT redirection for mitmproxy

Steps to Reproduce:

[If you are filing an issue what are the things we need to do in order to repro your problem? How are you using this cookbook or any resources it includes?]

  • use current version of iptables
  • use latest archlinx kernel (default kernel)
  • issue command such as: sudo iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8080

Expected Result:

[What are you expecting to happen as the consequence of above reproduction steps?]
putting my computer between the router and the server to view incoming and outgoing data on my device

Actual Result:

[What actually happens after the reproduction steps? Include the error output or a link to a gist if possible.]
iptables v1.8.2 (legacy): unknown option "--to-ports"
Try `iptables -h' or 'iptables --help' for more information.

I also can't find the '--to-port' option on the man page for my version of iptables

Just in case this needs to be clarified, this happens for '--to-port' and '--to-ports'

After some googling I did stumble accross this however leading me to believe the kernel I'm running may be to blame: sshuttle/sshuttle#286

commented

Hey There
It looks like this is the first issue you've filed against the chef-cookbooks project. I'm here to offer you a bit of extra help to make sure we can quickly get back to you.
Make sure you've filled out all the fields in our issue template. Make sure you've provided us with the version of chef-client you're running, your operating system and the version of the cookbook. If you're not using the most up to date version of the cookbook then please make sure to update first. Lots of things change between versions even if you're issue isn't listed in the changelog. Finally please give us a detailed description of the issue you're having. The more we know about what you're trying to do, what actually happens, and how you can reproduce the problem, the better.

If you're looking for more immediate troubleshooting help make sure to check out #general on the Chef Community Slack. There's plenty of folks there willing to lend a helping hand. Thanks for the first issue. We hope we can get back to you soon with a solution.

commented

fixed after a system update and reboot
Now @ 5.1.15-arch1-1-ARCH