SRX generator creates two terms when source and destination port is defined

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Create an SRX policy like this:
term accept-dhcp-access {
  source-port:: DHCP
  destination-port:: DHCP
  protocol:: udp
  action:: accept
}
2. Generate ACLs and check the application that has been generated.

What is the expected output?

    application accept-dhcp-access-app {
        term t1 protocol udp source-port 67-67 destination-port 67-67;
    }

What do you see instead?

    application accept-dhcp-access-app {
        term t1 protocol udp source-port 67-68;
        term t2 protocol udp destination-port 67-68;
    }

Original issue reported on code.google.com by m...@google.com on 4 May 2012 at 1:47

[GoogleCodeExporter]

Thanks for reporting this issue.  Looking into it.

Original comment by watson on 6 Jun 2012 at 4:37

• Changed state: Accepted

[GoogleCodeExporter]

Fixed at rev 186.

Original comment by watson on 6 Jun 2012 at 9:13

• Changed state: Fixed