Rule Creation Query

Discussion in 'LnS English Forum' started by SimonW, Jun 15, 2004.

Thread Status:
Not open for further replies.
  1. SimonW

    SimonW Registered Member

    Joined:
    Feb 22, 2004
    Posts:
    115
    Location:
    Leicester, UK
    Can someone please clarify:

    When creating a new rule if, for arguments sake, I wanted to open port 9999 to receive connections would I:

    Set the direction to 'Inbounds'
    Set the Source/Destination (left hand side) group-box TCP section to 'Equals 9999'

    or

    Set the direction to 'Inbounds'
    Set the Destination/Source (right hand side) group-box TCP section to 'Equals 9999'

    or

    Set the direction to 'Inbounds and Outbounds'
    Set the Source/Destination group-box TCP section to 'Equals 9999'

    or

    Set the direction to 'Inbounds and Outbounds'
    Set the Destination/Source (right hand side) group-box TCP section to 'Equals 9999'



    I'm confused because it seems to me that 'Inbounds and Outbounds' allows control/restriction over both directions thus removing the need for them as unique options in their own right in the top section of the dialog


    I've looked on the LnS website and would still like the explaining in more detail - I think I've managed to confuse myself totally o_O .
    Many thanks.
     
  2. gkweb

    gkweb Expert Firewall Tester

    Joined:
    Aug 29, 2003
    Posts:
    1,932
    Location:
    FRANCE, Rouen (76)
    Hi,

    I would choose the first one, it should work, but doing that I'm not sure you could send information from your local port 9999 if it is not from an existing connection.
    I mean if someone connect to you r 9999, then data can come back to him, but if you try first it won't work.
    If you choose inbound/outbound then it will work.

    That's what I think, thought I can be wrong :)

    regards,

    gkweb.
     
  3. SimonW

    SimonW Registered Member

    Joined:
    Feb 22, 2004
    Posts:
    115
    Location:
    Leicester, UK
    Thanks for your help gkweb!!

    OK, I'll set the direction to 'Inbounds and Outbounds' and set the Source/Destination TCP field to 'equals' and the required port :) .

    I would therefore assume that if, instead I set a value in the Desctination/Source side then this would in fact allow anyone in but only if their outgoing port was 9999 then?
     
  4. redman

    redman Registered Member

    Joined:
    Apr 16, 2004
    Posts:
    41
    We could do with a rule creation wizard for performing these tasks (written in a way that those of us who are not firewall experts could easily follow). Perhaps a future version of this excellent firewall will be enhanced with such a feature if enough of us request it.
     
  5. SimonW

    SimonW Registered Member

    Joined:
    Feb 22, 2004
    Posts:
    115
    Location:
    Leicester, UK
    Agreed. A good straightforward rule entry dialog would really help.

    I believe a lot of the options ought to be under an advanced tab - things that firewall experts can go in and tweak to cover less common threats etc. but for everyone else a more verbose and easy to use basic gui for the more trivial things (like in my original example for opening and closing ports etc)

    As a registered user of 2.05 I wonder if any plans like this or any other changes are on the horizon ( I guess running as a service will be wrapped into the next release as well) ??
     
Thread Status:
Not open for further replies.