[ previous ] [ next ] [ threads ]
 From:  Robert <robertedstrom at yahoo dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Getting m0n0wall up and running.
 Date:  Tue, 30 Aug 2005 23:20:03 -0700 (PDT)
I wasn't trying to bridge.  Both interfaces are not
connected to the same switch.  tl0 is connected to the
switch with my broadband router and the rest of the
live network.  de0 was connected to a completely
isolated switch and was configured with a static ip
address.  de0 will actually be connected to the wan. 
I set it to static to prevent it from constantly
trying to dhcp and to have an address on the other


--- Steve Yates <steve at teamITS dot com> wrote:

> 	Yes...a router routes between two different
> networks (subnets).  You
> are probably confusing m0n0wall by telling it both
> your NICs are on the same
> network.  If you want them to be on the same subnet
> - perhaps between your
> PCs and your broadband router - you should bridge
> the two sides together. 
> 	Unfortunately m0n0wall doesn't let us bridge a LAN
> and WAN interface,
> you must add a third NIC and bridge the WAN with
> OPT1.  You can still
> connect on the LAN interface if you plug it into
> another switch - i.e.,
> don't plug it into the same wired network as either
> WAN or OPT1.  Otherwise
> it gets confused about seeing packets from "itself."
>  Best thing is to stick
> a second NIC in another PC, or set up another box to
> connect only to the
> m0n0wall box.  Yes, you finally have a use for all
> those old NICs.
> 	Once you get bridging up, make sure you have added
> firewall rules to
> allow incoming and outgoing traffic on both the WAN
> and OPT1 sides.  Now you
> should be able to ping "across" your bridge.
> - Steve Yates
> - Out the 10Base-T, through the router, down the T1,
> over the leased line, off the bridge, past the
> firewall.... nothing but Net.
> ~ Taglines by Taglinator - www.srtware.com ~

Start your day with Yahoo! - make it your home page