> > thank you Earl. seems i hav to change the plan. I'll check it .
thusith. > > > Message: 2 > Date: Sat, 11 Oct 2008 21:33:10 +0000 > From: "Earl" <[EMAIL PROTECTED]> > Subject: Re: [Honeywall] modify honeywall for 4 interfaces. > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="UTF-8" > > I certainly don't intend to discourage innovation or new direction > but the Honeywall is already a very complex beast. I recommend > isolating the "routing" decision (BAD_STUFF_ROUTER) upstream from > the Honeywall and letting the Honeywall remain focused on what it > does best. > > WAN---BAD_STUFF_ROUTER----LAN > | > | > Honeywall---Management > | > Honeynet > > Just a thought. > > Earl > > > On Sat, 11 Oct 2008 05:58:10 +0000 Thusith Abeykoon > <[EMAIL PROTECTED]> wrote: > >Hi all, > > im implementing a honeynet for my university project. what i > >want to do > >is ; > > I have 4 NICs in the honeywall. WAN, Honeynet, Management, > >LAN. > > I need to enable snort-inline for WAN and LAN interfaces. > > If any suspecious traffic found in WAN and LAN, forward them > >to the > >honeypot. > > > > I installed the honeywall and tested it for 3 interfaces as > >in the > >guide. Please help me to implement the LAN interface. > > > > Thank you, > > Thusith. > > > > ------------------------------ > > _______________________________________________ > Honeywall mailing list > [email protected] > https://public.honeynet.org/mailman/listinfo/honeywall > > > End of Honeywall Digest, Vol 17, Issue 4 > **************************************** >
_______________________________________________ Honeywall mailing list [email protected] https://public.honeynet.org/mailman/listinfo/honeywall
