HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- IPfilter and TCP wrappers
Operating System - HP-UX
1833895
Members
2277
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2005 11:27 AM
03-31-2005 11:27 AM
IPfilter and TCP wrappers
I understand that IPFilter can be configured
to log allowed and blocked IPs and ports. TCP Wrappers can be configured to log allowed and blocked IPs.
What is the use for TCP Wrappers (other than customizing how to react to an attempt), if IPFilter already does the same?
Resource wise, is it less taxing on a system
to process an attempt using IPFilter than it is
with TCP Wrappers?
to log allowed and blocked IPs and ports. TCP Wrappers can be configured to log allowed and blocked IPs.
What is the use for TCP Wrappers (other than customizing how to react to an attempt), if IPFilter already does the same?
Resource wise, is it less taxing on a system
to process an attempt using IPFilter than it is
with TCP Wrappers?
I gave him his drink as usual. Some men can't hold their arsenic.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2005 12:33 PM
03-31-2005 12:33 PM
Re: IPfilter and TCP wrappers
IPFilter is a system firewall; so it does a lot more
than TCP wrapper.
I have not done any performance check comparison
between TCP wrapper and IPFilter. IPFilter goes in as
a streams module into the networking stack; so it
does have a little performance impact. Don't know
how it compares to TCP wrapper.
Another difference is, IPFilter is part of HP-UX and
hence supported by HP :-)
- Biswajit
than TCP wrapper.
I have not done any performance check comparison
between TCP wrapper and IPFilter. IPFilter goes in as
a streams module into the networking stack; so it
does have a little performance impact. Don't know
how it compares to TCP wrapper.
Another difference is, IPFilter is part of HP-UX and
hence supported by HP :-)
- Biswajit
:-)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP