This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
If I try to set an object to an invalid color, I get a list of all of the valid options. Where can I find a list of all of the protocols defined for protocol inspection purposes?
[Expert@LabSC1]# mgmt_cli -r true set service-tcp uid "97AEB3AB-9AEA-11D5-BD16-0090272CCB30" protocol "some value which does not exist" --format json
{
"code" : "generic_err_invalid_parameter",
"message" : "Invalid parameter for [protocol]. No such protocol : [ some value which does not exist ]"
}
Executed command failed. Changes are discarded.
While it would be amusing to see the FTP inspection module try to make sense of UDP traffic, I assume the list of acceptable protocols will differ between TCP and UDP. Are there any other constraints?
I believe they are listed in the UI when you edit a service of the relevant type. It refers to a specific low-level INSPECT handler, I believe. However, I wouldn’t edit this on a service unless you’ve received specific advice/documentation to suggest you should.
Sure, but is there a way for me to get that list short of opening a service object in SmartConsole and writing down each option?
I agree this isn't a commonly-used option, but I've had to set some service's protocol inspection to nothing enough times that I want to provide the ability to set the protocol on service objects. You know what I'm working on, and the level of functionality I want to provide. 😉
Yes, I'm aware of what you're building and I look forward to seeing it 😉 Unfortunately, I'm not aware of a way to get it short of opening SmartConsole.
Well, I just bit the bullet and manually typed out all the protocol inspection options as of SmartCenter R80.40 jumbo 91, SmartConsole R80.40 994000394. I found three categories of protocol inspections: TCP, UDP, and "other" (for IP protocols). The styling is wildly inconsistent. All-caps, camelCase, dashes, underscores, "Proto" versus "Protocol".
Also, there's a protocol inspection item which shows as "HTTPS" in SmartConsole, but which is "ENC-HTTP" in the object. That was an enormous pain to figure out.
I tested the TCP and UDP lists using a script like this:
Successful changes return 45 lines for TCP services, 46 lines for UDP services. Unsuccessful ones return four lines. I couldn't test the service-other list, as set service-other does not have a 'protocol' parameter. The lists are quite long, so I'm putting them in spoiler tags so they can be collapsed.
