Subject: | |
From: | |
Reply To: | |
Date: | Sat, 9 Nov 2002 22:15:37 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Keven Miller wrote:
>
> Ok, I think I'm beginning to see some light
> (could be the on-coming engine)
>
> We have
> MASK 255.255.0.0
> DTC1 172.16.17.194 (172.16.17.11000010 $C2)
> DTC2 172.16.17.195 (172.16.17.11000011 $C3)
> LAN2 172.16.17.196 (172.16.17.11000100 $C4)
> LAN1 172.16.17.220 (172.16.17.11011100 $DC)
>
> Couldn't you subnet on the HP3K with a mask of
> 255.255.255.240 (255.255.255.11110000 $F0)?
Only unless that is the *real* subnet mask, as viewed by everything else
on the subnet, else you are asking for trouble.
A better scenario would be to create your own subnet with one LANIC
and the DTCs, assigning this LANIC to DTSLINK, and using the other LANIC
for LAN1 (or whatever the NI name is) and TCP/IP. The DTSLINK side
doesn't even need IP addresses at all unless you have a TAC in
the DTC, or are using the DTC as a terminal server over TCP (telnet).
The DTSLINK part will work perfectly well without IPs.
Jeff
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|