Re: Naming s0-s29 (fwd)

Julian Cowley (julian@pixi.com)
Fri, 22 Mar 1996 20:17:53 -1000 (HST)

On Thu, 21 Mar 1996, MegaZone wrote:
> Once upon a time Infinet's Admin shaped the electrons to say...
> >I was wondering, due to the lack of documentation, does any one out there
> >know how to name a port.
> >Say port s0 is dialup-1.domain.name
> >and port s1 as dialup-2.domain.name
>
> The name part would be mapping an IP to DNS.
>
> The hitch is that there is no built in way to link an IP to a port.
> You would have to hack RADIUS to do a psuedo-fixed IP for the ports.

Is there a good reason for that? Having an "assigned pool" of addresses
only adds an additional level of indirection which is unnecessary.

The way it seems to work now is that the first connection to *any* port is
assigned the first address in the pool. The second connection, again on
any port, is assigned the next address (if it is available, of course).
The third, the same, and so on.

Why do it that way? If each port had its own assigned address, such that
the port number could be directly determinable by subtracting the IP
address from the base address for the pool, then it would be easier to
determine the port a user is currently logged in on.

An example. Our terminal servers' ports are named by the base name of the
terminal server plus two digits. Given the terminal server "godzilla",
for instance, the base address of the pool is "godzilla00". Currently, if
I know a user is logged in on godzilla00, I still have to search through
the user list on the terminal server to find out which port he is on,
instead of immediately knowing he is on S0.

Seems unnecessary to me at least.

-=- julian