Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
bernhard_ertl
Explorer
Jump to solution

Security Gateway name cannot start with "in-"

Hi,

maybe it is written somewhere in the documentation I couldn't find.

It seems that a new gateway object can't start with the combination "in-".

The error message reads: "Token includes a reserved word".
Is there a specific reason for that?

I know it's just cosmetic but it kind breaks our naming concept.

 
0 Kudos
2 Solutions

Accepted Solutions
AkosBakos
Advisor
Advisor

@bernhard_ertl 

Here is the link of the banned words:

https://support.checkpoint.com/results/sk/sk40179

But I haven't found the "in-" prefix in the SK

Akos

----------------
\m/_(>_<)_\m/

View solution in original post

(1)
_Val_
Admin
Admin

From the same SK, in is a reserved word and cannot be used.

Screenshot 2024-09-16 at 11.59.38.png

View solution in original post

(1)
5 Replies
AkosBakos
Advisor
Advisor

@bernhard_ertl 

Here is the link of the banned words:

https://support.checkpoint.com/results/sk/sk40179

But I haven't found the "in-" prefix in the SK

Akos

----------------
\m/_(>_<)_\m/
(1)
_Val_
Admin
Admin

From the same SK, in is a reserved word and cannot be used.

Screenshot 2024-09-16 at 11.59.38.png

(1)
AkosBakos
Advisor
Advisor

ohh, I need to visit my optician 🙂

----------------
\m/_(>_<)_\m/
0 Kudos
bernhard_ertl
Explorer

Thank you Val,

it seems a bit inconsistent, because "in-" wasn't allowed but "in_" is allowed as prefix to a hostname.

but thanks for pointing out the proper SK.

cheers 

the_rock
Legend
Legend

Thats right, I just tested same in R82, exact same behavior.

Andy

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events