|
||||||||
In your description, which makes sense, how do the current m0n0wall settings relate to the way you think it 'should read'? WAN-to-LAN: e.g. Wan Tab selected, LAN on SOURCE, ?? on DESTINATION etc WAN-to-Opti "" LAN-to-WAN "" Opti-to-WAN "" Opti-to-LAN "" LAN-to-Opti "" because its the 'get used to using m0n0' that i am having the hurdle with ~~~~~~~~~~~~~ ----- Original Message ----- From: "Ed Chatlos" <edchat at bellsouth dot net> To: "M0n0Wall" <m0n0wall at lists dot m0n0 dot ch> Sent: Friday, December 30, 2005 5:19 AM Subject: Re: [m0n0wall] Interface vs Source vs Destination > In my option the tabs you select, WAN/LAN/Opti, should read WAN-to-LAN, > WAN-to-Opti, LAN-to-WAN, Opti-to-WAN, Opti-to-LAN and LAN-to-Opti which > would make the direction the rule is to apply to a little more > descriptive. They could even be all on the same page with a drop down list > to select in which direction the packets are traveling. Although once you > get use to m0n0 it becomes clear. > > > Ed Chatlos > > > > ----- Original Message ----- > From: <tech at adaptive dot net> > To: "Chris Buechler" <cbuechler at gmail dot com> > Cc: <m0n0wall at lists dot m0n0 dot ch> > Sent: Friday, December 30, 2005 1:46 AM > Subject: Re: [m0n0wall] Interface vs Source vs Destination > > >> But wouldnt "coming into the defined interface" as you describe be the >> same thing as the "SOURCE" popup menu? As such, why am i selecting it >> from a menu if i'm already defining the rule for the interface in >> question. >> >> jeff >> >> ~~~~~~~~~~~~~ >> >> >> ----- Original Message ----- >> From: "Chris Buechler" <cbuechler at gmail dot com> >> Cc: <m0n0wall at lists dot m0n0 dot ch> >> Sent: Friday, December 30, 2005 1:37 AM >> Subject: Re: [m0n0wall] Interface vs Source vs Destination >> >> >> On 12/30/05, tech at adaptive dot net <tech at adaptive dot net> wrote: >>> In setting up Firewall rules, whats the specific reason that there are >>> separate rule lists for LAN, WAN, OPT1 interfaces? Afterall, aren't i >>> defining the interface implied when I specify the SOURCE and DESTINATION >>> interface in the rule itself? >>> >> >> firewall rules get applied as they're coming into the defined >> interface only, and the source and destination is used under that >> context, just like with basically every firewall. >> >> -Chris >> >> --------------------------------------------------------------------- >> 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 >> >> >> >> >> -- >> No virus found in this incoming message. >> Checked by AVG Free Edition. >> Version: 7.1.371 / Virus Database: 267.14.9/216 - Release Date: >> 12/29/2005 >> >> >> >> --------------------------------------------------------------------- >> 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 >> >> >> >> -- >> No virus found in this incoming message. >> Checked by AVG Anti-Virus. >> Version: 7.1.371 / Virus Database: 267.14.8/215 - Release Date: >> 12/27/2005 >> >> > > > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.1.371 / Virus Database: 267.14.8/215 - Release Date: 12/27/2005 > > > --------------------------------------------------------------------- > 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 > > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.371 / Virus Database: 267.14.9/216 - Release Date: 12/29/2005 > > |