| | .. footer:: $Id: tperimeter.txt,v 1.114 2006/09/25 20:12:38 tundra Exp $ |
|---|
| | .. footer:: $Id: tperimeter.txt,v 1.115 2010/11/18 16:22:02 tundra Exp $ |
|---|
| | |
|---|
| | |
|---|
| | ===================================================== |
|---|
| | ``tperimeter`` - A Dynamic TCP Wrapper Control System |
|---|
| |
|---|
| | the ``tperimeter`` web interface. You also cannot specify |
|---|
| | the host from which you desire access by using its name, only |
|---|
| | its full IP quad address. |
|---|
| | |
|---|
| | 5) When initially logging into the ``tperimeter`` interface, |
|---|
| | the user probably does not know their "real" dynamic IP |
|---|
| | address - i.e., The address they need opened by ``tperimeter`` |
|---|
| | for the desired access. The dynamic IP addressing systems |
|---|
| | found in hotels, airports, and self-service kiosks vary |
|---|
| | considerably in their use of ``NAT`` and other address translation |
|---|
| | schemes. There is a trivial solution to this problem, however. |
|---|
| | Each time you log into the ``tperimeter`` system, simply |
|---|
| | submit the request without the address field filled in. |
|---|
| | ``tperimeter`` will report an error that includes the address |
|---|
| | the request came from. This is almost always the correct |
|---|
| | address to use. If you are in a given location for several |
|---|
| | days, be aware that many dynamic IP systems assign a new address |
|---|
| | each time you log in. So, the address you provided on your |
|---|
| | first day at a hotel may not be the same one the next day. |
|---|
| | For this reason, the "trick" described above should be done |
|---|
| | every time you log into ``tperimeter``. |
|---|
| | 5) When initially logging into the ``tperimeter`` interface, the |
|---|
| | user probably does not know their "real" dynamic IP address - |
|---|
| | i.e., The address they need opened by ``tperimeter`` for the |
|---|
| | desired access. The dynamic IP addressing systems found in |
|---|
| | hotels, airports, and self-service kiosks vary considerably in |
|---|
| | their use of ``NAT`` and other address translation schemes. |
|---|
| | |
|---|
| | There is a trivial solution to this problem, however. Each time |
|---|
| | you log into the ``tperimeter`` system, simply submit the request |
|---|
| | without the service or address fields filled in. ``tperimeter`` |
|---|
| | will automatically generate a request for ssh access at the |
|---|
| | current address through which you're connecting. (It determines |
|---|
| | the address from the http headers which is almost always the |
|---|
| | correct address to use.) This makes it simple to just hit ``Enter`` |
|---|
| | at the ``tperimeter`` entry screen and have the right thing happen. |
|---|
| | |
|---|
| | 6) If you are in a given location for several days, be aware that many |
|---|
| | dynamic IP systems assign a new address each time you log in. |
|---|
| | So, the address you provided on your first day at a hotel may not |
|---|
| | be the same one the next day. For this reason, the "trick" |
|---|
| | described above should be done every time you log into |
|---|
| | ``tperimeter``. |
|---|
| | |
|---|
| | |
|---|
| | |
|---|
| | SECURITY RISKS |
|---|
| |
|---|
| | |
tundra
authored
on 18 Nov 2010