|
> > FYI, we use the device names for a physical security scheme. With these > QPADEV* things, we use the new features of the QDCRDEVD API, format > DEVD0600 to get the IP address, which is as unique as the SNA device name > for non-TELNET sessions. Then we convert that address to an 8-char > hex-equivalent with a REXX procedure. E.g., 95.96.97.98 becomes 5F606162. > We use this 8-char string as the device name. > Please note: That if you are using PPP in anyway, or NAT with a Firewall product. IP means little other than a resolve route back to the location of the packet at that point in time. Unless you are a fixed internal IP user you may not be getting the security and audit trail you really want.. Jeff Silberberg CompuDesigns, Inc. root +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.