Results 1 to 6 of 6
  1. #1
    Untangler
    Join Date
    May 2009
    Location
    Rochester area, New York, USA
    Posts
    31

    Default Protocol Control mistakenly blocking AIM Ports?

    I was looking through the logs at traffic and noticed that my Protocol Control has been blocking traffic from my DNS Server on Port 53 as AIM. Can anyone provide some ideas about what's going on? Perhaps I'm misinterpreting something?

  2. #2
    Untanglit
    Join Date
    Apr 2009
    Posts
    18

    Default

    Yes I'm also experiencing the same and looking for a better way to arrange the rules.

    I expect because the Client Source Port (on your DNS Server) is using a similar port to which AIM uses it is getting blocked.

    My rules allow access to any with a source of any and destination port of 53 but they are also getting blocked by a variety of protocol filters including AIM, Socks Version 5.

    What is the best way to address this ?
    Eg Do you configure an alternate Rack just for your servers and not have the Protocol Layer enabled?

  3. #3
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,747

    Default

    protocol control just matches based on regex (not source port) so its probably just a false positive.
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  4. #4
    Untanglit
    Join Date
    Apr 2009
    Posts
    18

    Default

    That may be the case but shouldn't it be carrying the check on on the destination port address as that is the protocol you are trying access?

    Could you advise on a workaround?

  5. #5
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,747

    Default

    you could add a bypass rule (or a no rack rule) for all traffic from that IP with a dest port of 53 so it won't be scanned.
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  6. #6
    Untangler
    Join Date
    May 2009
    Location
    Rochester area, New York, USA
    Posts
    31

    Default Monitor, but not blocking for AOL

    I just went back to monitoring for AIM but not blocking it. I don't think my server is starting any AIM sessions.

    I see no other AIM activity on my network.

    Thanks!

Posting Permissions

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

SEO by vBSEO 3.6.0 PL2