Next: SOCKS Configuration
Up: SOCKS Configuration Guide
Previous: Client Rules
Contents
| |
Action |
From |
To |
Port |
Auth? |
| [4] |
block |
1.2.3.20/32 |
209.11.107.14/32 |
Any |
- |
| [5] |
block |
1.2.3.10/32 |
Any |
Any |
- |
| [6] |
pass |
1.2.3.0/32 |
Any |
Any |
Yes |
| [7] |
pass |
1.2.4.0/24 |
Any |
Any |
- |
| [8] |
block |
Any |
Any |
Any |
- |
Rules 1 - 3 are Client rules and client 4 - 8 are SOCKS rules. Below
is a narrative explaining how these rules would be evaluated.
- When a connection is first established...
- If the client is on either the 1.2.3.0/24 or the 1.2.4.0/24 subnet,
access will be granted.
- Otherwise the connection will be dropped immediately (the client will
get a 'Connection refused' message).
- Once the connection is established the SOCKS server processes the
SOCKS rules.
- If the client is 1.2.3.20 and she is trying to access
209.11.107.14, access is denied.
- If the client is 1.2.3.10, access is denied.
- If the client is on the 1.2.3.0/24 subnet then access is denied unless
authentication credentials are sent by the client and they are successfully
validated.
- If the client is on the 1.2.4.0/24 subnet then access is granted.
- Otherwise the connection will be dropped gracefully.
I hope this guide has been helpful for you. If you still have questions
on how to configure SOCKS access control rules after you have read
this (and your user's manual), please contact Guardian Digital Support.
Next: SOCKS Configuration
Up: SOCKS Configuration Guide
Previous: Client Rules
Contents
docs@guardiandigital.com
2003-09-09