Results 1 to 20 of 23

Thread: Comodo blocking port forwarding

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    fred fleagle
    Guest

    Comodo blocking port forwarding

    Comodo blocks port forwarding from router, programs can't receive
    incoming connections.
    Can someone suggest a way to allow port forwarding?

    Thanks from
    fred fleagle



    --
    Posted via a free Usenet account from http://www.teranews.com


  2. #2
    Volker Birk
    Guest

    Re: Comodo blocking port forwarding

    fred fleagle <fgh@dot.net> wrote:
    > Comodo blocks port forwarding from router, programs can't receive
    > incoming connections.
    > Can someone suggest a way to allow port forwarding?


    Yes. Drop Comodo.

    Yours,
    VB.
    --
    The file name of an indirect node file is the string "iNode" immediately
    followed by the link reference converted to decimal text, with no leading
    zeroes. For example, an indirect node file with link reference 123 would
    have the name "iNode123". - HFS Plus Volume Format, MacOS X

  3. #3
    Mr. Arnold
    Guest

    Re: Comodo blocking port forwarding


    "fred fleagle" <fgh@dot.net> wrote in message
    news:47f15c4c$0$30486$88260bb3@free.teranews.com...
    > Comodo blocks port forwarding from router, programs can't receive
    > incoming connections.
    > Can someone suggest a way to allow port forwarding?
    >


    You go to the personal packet filter/personal firewall and you open the same
    ports on it as you did on the router.


  4. #4
    Poutnik
    Guest

    Re: Comodo blocking port forwarding

    Dne Tue, 01 Apr 2008 01:28:11 +0200 fred fleagle <fgh@dot.net> napsal/-a:

    > Comodo blocks port forwarding from router, programs can't receive
    > incoming connections.
    > Can someone suggest a way to allow port forwarding?
    >


    I have no problems with forwarded ports with Comodo.

    Especially at firewalls, all FW is as good as its configuration.
    Well, it can be worse, but never better.

    check proper forwarding at router, and incoming connections
    in comodo in both Application and Network monitor.

    Remember if there is not allowed incoming traffic in network layer,
    it does not matter what is allowed at application layer.

    First step in blaming is always my own hands,
    blaming product is next step.


  5. #5
    Sebastian G.
    Guest

    Re: Comodo blocking port forwarding

    Poutnik wrote:


    > I have no problems with forwarded ports with Comodo.
    >
    > Especially at firewalls, all FW is as good as its configuration.
    > Well, it can be worse, but never better.



    And Comodo is worse, since it doesn't even allow proper configuration even
    in the most simple scenarios.

    > Remember if there is not allowed incoming traffic in network layer,
    > it does not matter what is allowed at application layer.



    There is no matter to the latter anyway.


    > First step in blaming is always my own hands,
    > blaming product is next step.


    Unless you know what you're doing.

  6. #6
    Poutnik
    Guest

    Re: Comodo blocking port forwarding

    In article <65ort2F2h69r5U1@mid.dfncis.de>, seppi@seppig.de says...

    >
    > And Comodo is worse, since it doesn't even allow proper configuration even
    > in the most simple scenarios.


    As I have said, it is on your hands.

    My comodo works fine even at complex scenarios.
    But it can be out of your knowledge scope.

  7. #7
    Mr. Arnold
    Guest

    Re: Comodo blocking port forwarding


    "Poutnik" <me@privacy.net> wrote in message
    news:MPG.22618018491b0ac989680@127.0.0.1...
    > In article <65ort2F2h69r5U1@mid.dfncis.de>, seppi@seppig.de says...
    >
    >>
    >> And Comodo is worse, since it doesn't even allow proper configuration
    >> even
    >> in the most simple scenarios.

    >
    > As I have said, it is on your hands.
    >
    > My comodo works fine even at complex scenarios.
    > But it can be out of your knowledge scope.


    Your first mistake is that some 3rd party personal firewall you're even
    calling a FW. It's not a FW at best it's a machine level packet filter and
    some won't even call it that.

    A FW separates two networks. A FW sits at the junction point between two
    networks. A FW protects from the network it's protecting from usually the
    Internet, and it protects the network it's protecting the LAN. A FW must
    have two network interfaces or in the case of a FW running on a secured
    gateway computer, the computer must have two NIC(s). One network interface
    must face the WAN/Internet, and the other one must face the LAN.

    Because of the FW ability to segment networks, it reduces the risk of damage
    spreading from one network to another network, like a firewall or firedoor.


  8. #8
    Sebastian G.
    Guest

    Re: Comodo blocking port forwarding

    Mr. Arnold wrote:


    > Your first mistake is that some 3rd party personal firewall you're even
    > calling a FW. It's not a FW at best it's a machine level packet filter and
    > some won't even call it that.



    The latter would be idiots, since it is one, albeit a lousy one.

    > A FW separates two networks. A FW sits at the junction point between two
    > networks. A FW protects from the network it's protecting from usually the
    > Internet, and it protects the network it's protecting the LAN. A FW must
    > have two network interfaces or in the case of a FW running on a secured
    > gateway computer, the computer must have two NIC(s). One network interface
    > must face the WAN/Internet, and the other one must face the LAN.



    And the inability of Comodo to implement a routing firewall, which is the
    minimal strictly isolating firewall concept in scenarios where bridging
    firewalls are not applicable, is what makes it not a firewall.

    But: he hasn't claimed it to be a firewall. He only wrote that a firewall is
    only as good as its ruleset, and the same obviously also applies to pure
    host-based packet filters.

  9. #9
    Poutnik
    Guest

    Re: Comodo blocking port forwarding

    I do not need to learn what the hardware FWs are
    and how they are supposed to work.

    According to the fact
    Comodo is personal software firewall,
    I stayed at this topic.

    We can debate, if Pers SW FWs are proper term, but it is commonly used.
    And modern PSW are much more then plain packet filters.
    PF have no more chance against sofisticated malware.

    SW FW can be more easily compromized,
    but on the other hand, the have more chances
    to detect application hijacking
    and suspicious interprocess comunication.

    This field is closed to distant HW firewalls.

    HW and SW FWs have little different goals, purpose and usage.
    There is no use for their users fight each other.
    They have common enemy.

    be toughtIn article <D6adnbiCXr1v5WranZ2dnUVZ_jmdnZ2d@earthlink.com>,
    "Mr. Arnold" <MR. Arnold@Arnold.com> says...
    >
    > "Poutnik" <me@privacy.net> wrote in message
    > news:MPG.22618018491b0ac989680@127.0.0.1...
    > > In article <65ort2F2h69r5U1@mid.dfncis.de>, seppi@seppig.de says...
    > >
    > >>
    > >> And Comodo is worse, since it doesn't even allow proper configuration
    > >> even
    > >> in the most simple scenarios.

    > >
    > > As I have said, it is on your hands.
    > >
    > > My comodo works fine even at complex scenarios.
    > > But it can be out of your knowledge scope.

    >
    > Your first mistake is that some 3rd party personal firewall you're even
    > calling a FW. It's not a FW at best it's a machine level packet filter and
    > some won't even call it that.
    >
    > A FW separates two networks. A FW sits at the junction point between two
    > networks. A FW protects from the network it's protecting from usually the
    > Internet, and it protects the network it's protecting the LAN. A FW must
    > have two network interfaces or in the case of a FW running on a secured
    > gateway computer, the computer must have two NIC(s). One network interface
    > must face the WAN/Internet, and the other one must face the LAN.
    >
    > Because of the FW ability to segment networks, it reduces the risk of damage
    > spreading from one network to another network, like a firewall or firedoor.
    >
    >


  10. #10
    Sebastian G.
    Guest

    Re: Comodo blocking port forwarding

    Poutnik wrote:

    > In article <65ort2F2h69r5U1@mid.dfncis.de>, seppi@seppig.de says...
    >
    >> And Comodo is worse, since it doesn't even allow proper configuration even
    >> in the most simple scenarios.

    >
    > As I have said, it is on your hands.



    No, it isn't, since the software puts the limit. It's only in my hand to
    choose are not so insanely limited alternative host-based packet filter.

    > My comodo works fine even at complex scenarios.


    > But it can be out of your knowledge scope.



    This is a very simple ruleset that is part of essentially every sane
    configuration:

    check-state
    allow tcp from me to any out setup keep-state
    allow tcp from any to any established keep-state
    allow tcp from any to any frag keep-state
    deny tcp from any to me 1-1023 in setup
    skip tcp from any to me in setup keep-state

    Any stricter is horribly broken, any laxer is insecure. Yet it's impossible
    to implement in Comodo.

Similar Threads

  1. what the heck is all this on my logs?
    By Faction in forum Wireless Networks & Routers
    Replies: 13
    Last Post: 08-11-08, 08:03 PM
  2. A routing query
    By dileepviswa in forum Wireless Networks & Routers
    Replies: 1
    Last Post: 02-22-06, 11:26 PM
  3. Why Port Forwarding in Games Pisses me off
    By purecomedy in forum Gaming
    Replies: 11
    Last Post: 01-02-06, 12:11 PM
  4. port forwarding
    By corruptMonk in forum Wireless Networks & Routers
    Replies: 0
    Last Post: 12-21-05, 08:40 AM
  5. Nat Error, Port Forwarding w/ Putty
    By gearshifter in forum Software Forum
    Replies: 13
    Last Post: 12-07-05, 09:18 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •