Security

last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Expand all | Collapse all

ACL blocks UDP broadcast when specifying port

This thread has been viewed 1 times
  • 1.  ACL blocks UDP broadcast when specifying port

    Posted Feb 28, 2013 06:48 AM

    Hi.

     

    I am setting up a ACL rule which says

    SRC: any DST: any Service TCP / UDP *port* permit

    This works as long as the server and client device communicates directly to each others IP address.

    The server uses UDP broadcast on the specified port to discover devices. This does not work.

    The client device "data-LED" shows some activity when the broadcast is sent, so it looks like the broadcast gets through.

    The server never recieves the response tough.

     

    if I change the ACL rule to say:

    SRC: any DST: any Service: Any permit, the broadcast discovery works.

    When I check the wireshark logs the only specified is the same port that I spesify in the rule.

     

    Anyone know what might cause this?

     

    Thanks!



  • 2.  RE: ACL blocks UDP broadcast when specifying port

    EMPLOYEE
    Posted Mar 05, 2013 10:39 PM

    Type "show acl hits" to see if your traffic is hitting the firewall policy.



  • 3.  RE: ACL blocks UDP broadcast when specifying port
    Best Answer

    Posted Mar 06, 2013 07:36 AM

    Thanks.

     

    We just solved this case.

    Turned out that the equipment that the customer was using is work in progress, so the documentation was not complete.

    The broadcast was answered to the private/dynamic port that the broadcast was sent from. This way, the traffic was using a different destination port than what we defined in the acl. This was fixed so now everything works as expected :D



  • 4.  RE: ACL blocks UDP broadcast when specifying port

    EMPLOYEE
    Posted Mar 06, 2013 07:36 AM

    Awesome.