Hi,
Unfortunately, there is no way to customize the applications listed under the host-inboud traffic settings. Fortunately, Junos 11.2 introduced a more flexible way to apply policies to host-bound traffic.
On the in ingress zone of your RPM server, allow any host-bound traffic as you have, but configure a host-bound security policy to restrict which traffic will be allowed. The order to evaluation is Zone-based setting followed by the host-policy setting.
The junos-host zone is a special predefined zone that is assigned as the destination zone for all host-inbound traffic (or source zone for host-outbound), allowing you to configure a normal security policy to control which traffic is allowed or denied.
For example, say that you are sending UDP probes to port 50000 and that the server is listening on an interface bound to the untrust zone. They configuration would be something like this
[edit applications]
application rpm {
protocol udp;
destination-port 50000;
}
[edit security policies from-zone untrust to-zone junos-host]
policy allow-RPM-probes {
match {
source-address any;
destination-address any;
application rpm;
}
then {
permit;
}
}
policy deny-other {
match {
source-address any;
destination-address any;
application any;
}
then {
deny;
}
}
I didn't test this config so It is possible that I made a mistake somewhere, but hopefully you get the idea.
As a byproduct of this, host-bound policies allow you to generate session logs for host-bound traffic, which is particularly useful when used in conjunction with a global policy (to log all host-bound packets, or all denied host-bound traffic).