|
Hmm... I'm looking for an easy way to stop some PC's (on an otherwise generally authorized subnet) to telnet to the 400. Is there no way to deny a (specific) tcp connection? Or put another way: if there's a route, connection is possible and 'undeniable'? Regards, Matthias David Gibbs wrote: > > I don't think so... the hosts.allow/deny functionality depend on a tcp > wrapper function (used here on midrange.com to keep people out of the unix > system)... and the tcp wrapper depends on a superserver internet daemon, > which the as/400 does not have. > > david > > At 02:12 PM 11/5/98 , Matthias Oertli wrote: > >Is there an equivalent to the unix hosts.allow and > >hosts.deny tcp/ip access control scheme available on the 400 > >(v3r7)? > >Regards, > >Matthias > > --------------------------------------------------------------------- Matthias Oertli <oertlim@s054.aone.net.au> +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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-2024 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.