head	1.4;
access;
symbols
	RELEASE_8_3_0:1.4
	RELEASE_9_0_0:1.4
	RELEASE_7_4_0:1.3
	RELEASE_8_2_0:1.3
	RELEASE_6_EOL:1.3
	RELEASE_8_1_0:1.3
	RELEASE_7_3_0:1.3
	RELEASE_8_0_0:1.3
	RELEASE_7_2_0:1.3
	RELEASE_7_1_0:1.3
	RELEASE_6_4_0:1.3
	RELEASE_5_EOL:1.3
	RELEASE_7_0_0:1.3
	RELEASE_6_3_0:1.3
	PRE_XORG_7:1.3
	RELEASE_4_EOL:1.3
	RELEASE_6_2_0:1.3
	RELEASE_6_1_0:1.3
	RELEASE_5_5_0:1.3
	RELEASE_6_0_0:1.2;
locks; strict;
comment	@# @;


1.4
date	2011.07.03.14.03.37;	author ohauer;	state Exp;
branches;
next	1.3;

1.3
date	2006.01.24.01.03.25;	author edwin;	state Exp;
branches;
next	1.2;

1.2
date	2005.06.15.20.23.33;	author ahze;	state Exp;
branches;
next	1.1;

1.1
date	2005.06.15.06.57.10;	author ahze;	state Exp;
branches;
next	;


desc
@@


1.4
log
@-remove MD5
@
text
@SHA256 (sasp-0.1.tar.gz) = d186284a7e4991685f08d341f62f8632b0b66a81092949104f8f7ff7c27a91eb
SIZE (sasp-0.1.tar.gz) = 3674
@


1.3
log
@SHA256ify

Approved by: krion@@
@
text
@a0 1
MD5 (sasp-0.1.tar.gz) = 25f98a6853b0044d5d06b9cf57914934
@


1.2
log
@- Reroll tarball and mirror on MASTER_SITE_LOCAL, the orignal tarball
  was tared up and gzipped twice and gnutar does not like that.

Pointed out by:	krismail
@
text
@d2 1
@


1.1
log
@- Add sasp
This is a tool that uses ARP poisoning  to  have  a  scenario
like this: we have a LAN and we want offer connectivity to every-
one coming here with his laptop for example. It could happen that
our  customer  has  his  network parameters already configured to
work correctly in his own LAN, but not working here. We can  have
then this scenario:
Customer's  host (10.0.0.2/8 and default gateway set to 10.0.0.1)
Our LAN (192.168.0.0/24 with real gateway 192.168.0.254).
All that we want is that our customer plugs his laptop  and  joins
the  internet without changing nothing of his network parameters.
Here comes this tool installed in my real gw(192.168.0.254)  It's
a  sort  of sniffer, because it sniffs broadcast ARP requests for
the gateway and answers that the gateway is itself In our example
our  customer's  laptop  sends  this request: arp who-has 10.0.0.1
tell 10.0.0.2 Now our gateway does the following: 1)  Sends  back
this  reply to 10.0.0.2: arp reply 10.0.0.1 is-at his_mac_address
2)Create the alias 10.0.0.254 (ARP is not routable so we need one
alias  for each subnet that is not our one) 3)Sends itself an ARP
reply to refresh his ARP cache
It is different from proxy arp for two reasons: first it runs  in
user  space,  then in this case we can plug machines belonging to
whatever subnet, while proxy arp is used in the case of only  two
different ones.

PR:		ports/79676
Submitted by:	Luigi Pizzirani <sviat@@opengeeks.it>
@
text
@d1 2
a2 2
MD5 (sasp-0.1.tar.gz) = 01cdaf87a0ac27bc5d52a01e4e858c78
SIZE (sasp-0.1.tar.gz) = 3709
@

