[ previous ] [ next ] [ threads ]
 
 From:  Michael DeMan <michael at staff dot openaccess dot org>
 To:  "Adam Wilks" <adam dot wilks at weymouthwireless dot co dot uk>
 Cc:  "Monowall Mailing List" <m0n0wall at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall] IPSec Tunnel to 128.0.0.0
 Date:  Tue, 11 Jan 2005 13:11:21 -0800
Yes, being able to setup VPNs to 0.0.0.0/0 would be helpful for us also.

We use IPSec to 0.0.0.0/0 to create tunnels on wireless.  Its not so 
much a office<->office VPN but actually a client<->internet tunnel to 
prevent 802.11 eavesdropping.

- mike

On Jan 11, 2005, at 1:07 PM, Adam Wilks wrote:

> Just to make it general knowledge... anyone trying to route internet
> traffic via an IPSec tunnel. If you follow my last post you will know I
> used a remote network of 128.0.0.0/1. This won't work, at least not for
> every conceivable internet address. See this post...
>
> www.m0n0.ch/wall/list/?action=show_msg&actionargs[]=90&actionargs[]=04
>
> To solve this I used a remote network of 0.0.0.0/0 to specify a route
> for 'all' networks but had to modify the tunnel config manually in the
> configuration xml as m0n0wall's web gui does not let you input this 
> mask
> as a remote net (but does let you put it as the local net).
>
> I believe this is a bug, either you should be able to use a netmask of 
> 0
> in both local and remote net's or none at all right?
>
>
> Regards,
>
> Adam.
>
> -- 
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.6.10 - Release Date: 10/01/2005
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>
>