Example of a Route Permission Table with SNC
A route permission table using SNC could look like this:
P |
* |
* |
* |
pass |
KT |
S:SR@host4 |
host4 |
3333 |
|
KT |
S:SR@host4 |
host9 |
* |
|
KD |
S:SR@host4 |
host9 |
* |
|
KP |
S:SR@host4 |
* |
* |
pass2 |
KS |
* |
host10 |
4444 |
|
KP |
* |
* |
* |
This means:
Allow all connections if password pass
is specified correctly.
Connections from this SAProuter to host4
(SNC name S:SR@host4
), service 3333
should be SNC connections.
Connections from host9 (SNC name s:SR@host9
) to this SAProuter should be SNC connections.
A SNC connection from SR@host4
to host9
through this SAProuter should not be set up.
A SNC connection from S:SR@host4
through this SAProuter (any target host) is allowed if the password pass2
is correct (unless the connection is to host9
, since this is not allowed according to the previous entry - the first entry which “matches” is decisive).
All SAP to SAP connections (NI protocols) to host10
, service 4444
, which come in as SNC connections are passed on as non-SNC connections to host10
(no SNC host).
All SNC connections (for which the previous entries are not suitable) are allowed.