Show TOC

Example documentationExample of a Route Permission Table

 

A route permission table could appear as follows:

D

host1

host2

serviceX

D

host3

P

*

*

3200.3298

P

155.56.*.*

155.56.*.*

P

155.57.1011xxxx.*

P

host4

host5

*

pass

S

host6

P

host7

host8

telnet

P*,0

*

*

gui

This means:

  • Do not allow routes from host1 to host2, service serviceX

  • Do not allow routes starting from host3

  • Allow all routes to server processes that use a service in area 3200 to 3298

  • Allow all routes within subnetwork 155.56.0.0/16

  • Allow all routes starting from subnetwork 155.57.1011xxxx (the last byte is written as a binary number; each x stands for 0 or 1).

  • Allow all routes from host4 to host5 if password pass is correct

  • All routes from host6, but only SAP protocol

  • Native protocol routes (TCP/IP) from host7 to host8 for the non-SAP service telnet on telnet

  • All connections to non-SAProuters (no more SAProuters allowed on this route) if password gui is correct

In the above example in Entering Route Strings the route permission table of host saprouter must have the entry:

P sappc your_rout

and the route permission table of host yoursaprouter must contain the entry

P saprouter yourapp sapsrv pass_to_app

It can contain parentheses, signs and the following operators:

More Information

Example of a Route Permission Table with SNC

Route Permission Table