I had to fix it again just now: petzi:~# arpspoof -i eth1 78.40.125.81 0:e0:81:5a:60:3f ff:ff:ff:ff:ff:ff 0806 42: arp reply 78.40.125.81 is-at 0:e0:81:5a:60:3f ^C0:0:0:0:0:0 ff:ff:ff:ff:ff:ff 0806 42: arp reply 78.40.125.81 is-at 0:0:0:0:0:0 0:0:0:0:0:0 ff:ff:ff:ff:ff:ff 0806 42: arp reply 78.40.125.81 is-at 0:0:0:0:0:0 0:0:0:0:0:0 ff:ff:ff:ff:ff:ff 0806 42: arp reply 78.40.125.81 is-at 0:0:0:0:0:0
Apparently it was reset to 0:0:0:0:0:0 during the night? - Sylvain On Sat, Jun 26, 2010 at 05:54:03PM +0200, Sylvain Beucler wrote: > Hi, > > I had to use the 'arpspoof' trick several times today: for example > traffic for 78.40.125.81 was sent to eth0 instead of eth1. > > There's no special setup on petzi anymore now: I finished moving all > chroot-based setup to vserver, and there's no vserver with special > network privileges anymore. > > Vincent, is there a way this issue could be tracked down? > > -- > Sylvain _______________________________________________ Project mailing list [email protected] https://mail.gna.org/listinfo/project
