Configuring the Firewall for Terminal Services
33
If you need to log in remotely to the firewall, you must use netacl to start the proxies. In
this configuration, administrators on either inside or outside hosts initiate TELNET
requests to the firewall, which accesses the netacl daemon. The netacl daemon checks its
permissions, and determines that the host can use TELNET. The netacl daemon starts the
proxy. The proxy prompts the user for authentication. If it is successful, the proxy
prompts the user for the host and logs the transaction. When the user indicates a wish to
connect to the firewall itself (by specifying the destination “localhost”), the netacl
daemon reviews the destination and starts the actual IRIX TELNET daemon on the
firewall, thereby connecting the user to the firewall.
Using the TELNET and Rlogin Proxies Without Network Access
Control
In this scenario, the firewall runs the TELNET (tn-gw) or Rlogin (rlogin-gw) proxies as
daemons listening for requests on the standard TELNET port (23) and Rlogin port (513).
Common policies allow inside hosts to connect without authentication, and outside
hosts to connect with authentication.
This configuration using just the TELNET and Rlogin proxies (without the netacl
daemon) prohibits running either TELNET or Rlogin on the firewall itself (which would
allow you to login to the firewall remotely). Because the proxies are running on the
standard TELNET and Rlogin ports on the firewall, all requests start the proxy. There is
no way to start the TELNET and Rlogin daemons needed to service these requests on the
standard ports.
Configuring the Firewall for Terminal Services
Configuring the Gauntlet firewall involves planning, configuring the firewall, indicating
which daemons the system will run, configuring the proxies to enforce your policy, and
adding the users who will need to authenticate to the Gauntlet user authentication
database.
Planning
1.
Determine whether you wish to allow TELNET and TN3270 connections through
the firewall.
2. Determine whether you wish to allow rlogin connections through the firewall.
Summary of Contents for Gauntlet
Page 1: ...Gauntlet for IRIX Administrator s Guide Document Number 007 2826 004 ...
Page 16: ......
Page 26: ......
Page 27: ...PART ONE Understanding the Gauntlet Internet Firewall I ...
Page 28: ......
Page 43: ...PART TWO Configuring and Using Proxies II ...
Page 44: ......
Page 50: ......
Page 56: ......
Page 64: ......
Page 72: ......
Page 94: ......
Page 109: ...PART THREE Administering General Gauntlet Firewall Services III ...
Page 110: ......
Page 140: ......
Page 147: ...Introductory Management Form 121 Figure 17 4 Gauntlet Introductory Management Form 2 of 3 ...
Page 155: ...Routing Configuration Form 129 Figure 17 8 Routing Configuration Form ...
Page 163: ...Proxy Servers Configuration Form 137 Figure 17 11 Proxy Servers Configuration Form 2 of 3 ...
Page 170: ...144 Chapter 17 The Graphical Management Interface Figure 17 13 DNS Configuration Form 1 of 2 ...
Page 171: ...DNS Configuration Form 145 Figure 17 14 DNS Configuration Form 2 of 2 ...
Page 177: ...Sendmail on Gauntlet Servers 151 Figure 17 15 Sendmail Configuration Form ...
Page 187: ...Logfiles and Reports Configuration Form 161 Figure 17 20 Reports and Logfiles Form 1 of 2 ...
Page 191: ...Authorizing Users Form 165 Figure 17 22 Authorizing Users Form ...
Page 192: ...166 Chapter 17 The Graphical Management Interface Figure 17 23 Add User Form ...
Page 214: ......
Page 232: ......
Page 233: ...Appendixes IV ...
Page 234: ......
Page 294: ......
Page 305: ......