[ previous ] [ next ] [ threads ]
 
 From:  Bill Hamel <billh at bugs dot hamel dot net>
 To:  Kyle Mott <kyle at xraided dot net>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] IPsec to WatchGuard v60
 Date:  Thu, 18 Nov 2004 11:12:04 -0500
Doing this from memory, but are you sure that you set up the "routes" on the
Watchguard side ? IOW - each end needs to know what the other ends Private IP
space is, so it knows how to route to it.

-b


Quoting Kyle Mott <kyle at xraided dot net>:

> 
> Hi all. I'm trying to setup an IPSec tunnel between my home m0n0wall
> firewall (on Comcast Cable), and a WatchGuard v60 (co-located nearby).
> 
> I actually have 90% of it setup correctly (or at least I think I do).
> The Tunnels are established, and on the Network behind the WatchGuard, I
> can ping the LAN IP of my m0n0wall system. However, I cannot ping any
> other systems in the m0n0wall's LAN subnet.
> 
> >From my m0n0wall network (LAN side), I cannot ping anything on the
> WatchGuard subnet (not even the WatchGuard's LAN IP). There's nothing
> special in the logs that's saying packets are denied for some reason. I
> feel like I am inches away from having it work, but I just can't wrap my
> brain around the last couple steps I need to take. Any suggestions would
> be much appreciated.
> 
> Also, is there any way to allow a VPN client from behind m0n0wall (on
> the LAN subnet) to VPN to a remote host?
> 
>  
>  
> -Kyle Mott
> 
> 
> 
> ---------------------------------------------------------------------
> 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
> 
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by the Bugs.Hamel.Net MailScanner, 
> and appears to be clean.
> 
> 




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

-- 
This message has been scanned for viruses and
dangerous content by the Bugs.Hamel.Net MailScanner, 
and appears to be clean.