This is over-complicated, unless you can give a reason why you need to do
all this or need more than one router. You can just install a single
monowall with three interfaces and be done with it. Interface 1 for the
WAN connected straight to the cablemodem, interface 2 for LAN1 (.1.0) and
interface 3 for LAN2 (.2.0). You can keep each of the LANs completely
separate if you like, only making a few pinholes between them so users can
access shared printers between the lans.
This way you can manage everything from one router and eliminate a switch
or two. I have the same thing running at more than one location with great
From: maximkh at yahoo dot com [mailto:maximkh at yahoo dot com]
Sent: Tuesday, March 22, 2005 12:48 PM
To: m0n0wall at lists dot m0n0 dot ch
Subject: [m0n0wall] Help connecting two local subnets
Hi guys, having a bit of trouble with this and can't figure out why.
Basically my setup is this: cable modem connects to a switch, that switch
connects to two separate routers, one serves 192.168.1.0/24 network and
the other serves 192.168.2.0/24 network. The .1.0 router connects a LAN
interface to another switch to which all of its hosts are connected. The
.2.0 connects to a third switch on the LAN interface to which the .2.0
hosts is connected, and I also just installed an OPT1 interface which is
connected to the .1.0 switch.
Basically we have a number of devices (like network printers) on the .1.0
network that the .2.0 guys need to be able to access. I configured the
OPT1 interface with 192.168.1.254/24, set up a static route on the LAN
interface with destination 192.168.1.0/24 and gateway 192.168.1.254. At
this point it looks as though I should be able to access the other
network, but so far I can't ping anything over there.
The "Enable filtering bridge" is unchecked, so the firewall shouldn't be
blocking packets (and there's nothing in the firewall log about this).
Any ideas on what I'm missing? In the system log I'm getting this when I
try to ping anything over there:
kernel: arpresolve: can't allocate llinfo for 192.168.1.254rt
kernel: arplookup 192.168.1.254 failed: host is not on local network
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