[ previous ] [ next ] [ threads ]
 
 From:  Walter PC <walterpc at mchsi dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] m0n0wall behind m0n0wall
 Date:  Tue, 15 Aug 2006 14:27:06 -0500
Did you make sure to specify 192.168.222.1 as the default GW for the 
static IP of the WAN of mono(2) ?? assuming a 24 subnet.
Can you ping IPs in the 192.168.222.xxx range from the Test LAN with 
your static setup??
I'm guessing that #1 is the answer because DHCP would assign this 
automattically for you... unless your subnet masks don't match.
--Ken.

Don Munyak wrote:
> m0n0wall behind m0n0wall
>
> I have a test network setup within our LAN.
> the core firewall/gateway is m0n0(1)
> the test network has a second router, m0n0(2)
>
> ISP---m0n0(1)---LAN---m0n0(2)---TEST LAN
>
> m0n0(1) LAN nic/gateway is 192.168.222.1
>
> m0n0(2) WAN nic is 192.168.222.99
> m0n0(2) LAN nic is 192.168.18.1
> m0n0(2) DNS points to a DNS serer in 192.168.222.0 network
> m0n0(2) has block private IP's DISABLED (not checked)
>
> No static routes have been asigned in either box.
>
> With this configuration I can not get past the wan IP for m0n0(2),
> outbound from TEST LAN.
>
> If I remove the the static IP on m0n0(2) and make DHCP, everything 
> works fine.
> We have a DHCP server on the LAN network.
>
> -- What I am trying to accomplish....
>
> The equipment on the TEST LAN network behind the second m0n0wall(2)
> has equipment we will be moving to a data center. I want to access the
> servers in the TEST LAN (192.168.18.0) from the primary LAN network
> (192.168.222.0)
> I would like to configure m0n0(2) with a static WAN IP, so that I can
> create rules in the firewall for neccessary services to be hosted in
> the real world.
>
> ---------------------------------------------------------------------
> 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
>
>