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

ufw returns errors #2042

Closed
ghost opened this issue May 1, 2017 · 2 comments
Closed

ufw returns errors #2042

ghost opened this issue May 1, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented May 1, 2017

  • Your Windows build number: (Type ver at a Windows Command Prompt)

15063

  • What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)

Typing the command "ufw status" returns the following error:
"ERROR: problem running iptables: iptables v1.6.0: can't initialize iptables table 'filter': Table does not exist (or do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded."

  • What's wrong / what should be happening instead:

Command should be returning "Status: inactive" instead. The ufw enable and disable commands don't work either.

  • Strace of the failing command, if applicable: (If <cmd> is failing, then run strace -o strace.txt -ff <cmd>, and post the strace.txt output here)

Running "strace -o strace.txt -ff ufw status" produces the following files (renamed to be uploadable):
strace.366.txt
strace.367.txt
strace.368.txt

@fpqc
Copy link

fpqc commented May 1, 2017

iptables has both userspace and kernelspace components. The kernel module part of iptables does not exist in WSL (which is why it asks you to run insmod, since it's not detecting the expected module). I think it will be neat if MS decides to support something like IPtables though.

@therealkenc
Copy link
Collaborator

#767

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants