bettercap doesn't work

[lfpnub]

Please use the following bug reporting template to help produce actionable and reproducible issues. Please try to ensure that the reproduction is minimal so that the team can go through more bugs!

• A brief description
  Title says it all. I'm trying to use bettercap, but it's not working. Would like help as soon as possible.
• Expected results
• Actual results (with terminal output if applicable)
  ... Cannot find logs.
• Your Windows build number
  I have no idea.
• Steps / All commands required to reproduce the error from a brand new installation
  sudo apt-get install bettercap
  sudo bettercap
• Strace of the failing command
  There's no /proc/sys/ file for ipv4
• Required packages and commands to install
  bettercap
  See our contributing instructions for assistance.

[therealkenc]

It appears he means bettercap here and gem install not apt-get install (bettercap isn't in Canonical's repositories). It needs proc/sys/net/ipv4/ip_forward, among other things I'm sure.

Same as #767 et al. User voice here.

[fpqc]

@therealkenc This one is in the works, and Alex Ionescu found the kernel-side interface in his investigations and even wrote a PoC driver. I asked him on Twitter if he thinks the interface will be general enough to expose CUDA to WSL.

[therealkenc]

Between the title "/proc/ is not in this" and fpqc's "this one is in the works", I'm afraid I'm one too many pronouns deep on this thread... If Ionescu is working on has a proof of concept /proc/net/ipv4/ip_forward that's...uh...awesome.

[benhillis]

@lfpnub Just to confirm, are you referring to /proc/net/ipv4/ip_forward ?

[therealkenc]

This is the CLI output from bettercap.

[E] Oooops, seems like something weird occurred, please copy paste the following output and open a new issue on https://github.com/evilsocket/bettercap/issues :

[E] Platform          : x86_64-linux-gnu
[E] Ruby Version      : 2.3.1
[E] BetterCap Version : 1.5.8
[E] Command Line      :
[E] Exception         : Errno::ENOENT
[E] Message           : No such file or directory @ rb_sysopen - /proc/sys/net/ipv4/ip_forward
[E] Backtrace         :

    /var/lib/gems/2.3.0/gems/bettercap-1.5.8/lib/bettercap/firewalls/linux.rb:31:in `initialize'
    /var/lib/gems/2.3.0/gems/bettercap-1.5.8/lib/bettercap/firewalls/linux.rb:31:in `open'
    /var/lib/gems/2.3.0/gems/bettercap-1.5.8/lib/bettercap/firewalls/linux.rb:31:in `forwarding_enabled?'
    /var/lib/gems/2.3.0/gems/bettercap-1.5.8/lib/bettercap/firewalls/base.rb:45:in `initialize'
    /var/lib/gems/2.3.0/gems/bettercap-1.5.8/lib/bettercap/firewalls/base.rb:28:in `new'
    /var/lib/gems/2.3.0/gems/bettercap-1.5.8/lib/bettercap/firewalls/base.rb:28:in `get'
    /var/lib/gems/2.3.0/gems/bettercap-1.5.8/lib/bettercap/context.rb:67:in `initialize'
    /var/lib/gems/2.3.0/gems/bettercap-1.5.8/lib/bettercap/context.rb:51:in `new'
    /var/lib/gems/2.3.0/gems/bettercap-1.5.8/lib/bettercap/context.rb:51:in `get'
    /var/lib/gems/2.3.0/gems/bettercap-1.5.8/lib/bettercap/options/options.rb:42:in `parse!'
    /var/lib/gems/2.3.0/gems/bettercap-1.5.8/bin/bettercap:27:in `<top (required)>'
    /usr/local/bin/bettercap:23:in `load'
    /usr/local/bin/bettercap:23:in `<main>'

[fpqc]

@therealkenc I mean that the WSL team has said that the network interface stuff is in the works, and maybe the driver interface that Alex found is how they are going to implement it (my speculation).

Look:
https://github.com/ionescu007/lxss/tree/master/lxdrv

It has code to add devices to the environment and associates vfs nodes. Plus it looks like you can make Windows devices actually show up if you programmed them to also make use of this interface, I think. I have never written a device driver, but this seems to be the "right" way to do it.

Don't know if the MS devs are going to document this directly for driver-writers, or if they are going to keep this interface private and then write generic shims between the Windows drivers and the interface.

[therealkenc]

Network interface stuff is always in the works. But I suspect people looking for Berkeley packet filtering or to turn their WSL session into a core IP router probably have a bit of a wait ahead.

[fpqc]

@therealkenc You might find this little Q&A pair interesting:

ionescu007/lxss#9

[benhillis]

This issue is quite old and also quite vague (procfs is implemented but incomplete). If you continue to experience issues on newer Windows builds, please reopen more specific issues. Thanks!

[therealkenc]

That was /proc/sys/net/ipv4/ip_forward as the initial fail. This is the same category as #767 and #1349 because bettercap does a bit of everything.