Encountered an error configuring arpwatch: Invalid Arguments. Terminating...

[GoogleCodeExporter]

When I try to run sudo subterfuge it starts, but gives this one error message:

"Encountered an error configuring arpwatch: Invalid Arguments. Terminating..."

Launching attack with standard configuration options.
Automatically Configuring Subterfuge...
[01/Aug/2012 13:15:06] "GET / HTTP/1.1" 200 438
[01/Aug/2012 13:15:07] "GET / HTTP/1.1" 200 438
Iptables Prerouting Configured

Configuring System...
net.ipv4.ip_forward = 1
IP Forwarding Enabled.
Initiating ARP Poison With ARPMITM...
Starting up SSLstrip...
Harvesting Credentials...
Poisoning the entire subnet...

[01/Aug/2012 13:15:09] "GET / HTTP/1.1" 200 437

sslstrip 0.9 by Moxie Marlinspike running...
[01/Aug/2012 13:15:10] "GET / HTTP/1.1" 200 437

I am running:

sudo subterfuge
Validating models...

0 errors found
Django version 1.3.1, using settings 'subterfuge.settings'
Development server is running at http://127.0.0.1:80/

I have attempted to visit sites requiring credentials on both my host system 
and systems on the same subnet/vlan but it doesn't appear to be arp spoofing or 
doing anything for that matter.

Any suggestions?

Thanks

Original issue reported on code.google.com by 09Spa...@gmail.com on 1 Aug 2012 at 6:24

[GoogleCodeExporter]

Additional Note:

Running Ubuntu 12.04
Arpwatch Version: 2.1a15

Original comment by 09Spa...@gmail.com on 1 Aug 2012 at 7:05

[GoogleCodeExporter]

Yep ARPWATCH does not auto configure yet. This is fine. The feature you miss 
out on is called dynamic host retention, but it will not prevent your attack 
from being successful. If you would like to you can edit the conf file to 
manually set this up, but it's not a terribly big deal unless extreme stealth 
of the attack is a must. Otherwise just wait for Version 4.1. In 4.1 ARPWATCH 
will include automatic configuration.

Original comment by Mtoussain@gmail.com on 1 Aug 2012 at 8:10

[GoogleCodeExporter]

Original comment by topher.s...@gmail.com on 7 Aug 2012 at 7:02

[GoogleCodeExporter]

Fix implemented in Version 4.1

Original comment by Mtoussain@gmail.com on 13 Aug 2012 at 7:29

• Changed state: Fixed