> Also, consider the implications of roaming between AP's (and therefore,
> exitpoints to the Internet).  Any sessions in-progress will terminate,
> since any incoming packets for you will be going to the 1st AP (the 2nd AP
> on a 2nd broadband connection will have a different public IP).  And the
> 2nd AP won't have any existing NAT translations for you anyways (assuming
> the device is doing NAT, which it almost certainly would have to)
>I would therefore argue that #4 and #6 are mutually-exclusive.
> Adam Maloney

If you read the web page at the URL referenced in #6
6.) roaming: something like SOWN's TransparentMobility system would be very
very nice (http://www.sown.org.uk/index.php/TransparentMobility).  Then you
can roam between access points without losing your open connections.  This
is very important for things like VOIP or SSH sessions.
you will see that the method described involves handing off the roaming
by having the NEW access point tunnel to the OLD access point, which proxies
existing connection(s) in progress, thereby maintaining existing connections
changing the IP address. The end-user also maintains a consistent local IP
The software is available at sourceforge and they are asking people to use
it. One
caveat is that it appears that Win32 and WinCE users are not able to
at this time... Another caveat is that tunnelling consumes bandwidth from
access point to which a TCP connection was initiated, until that connection
is closed.