HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Howto use wildcards in netfmt filters
Operating System - HP-UX
1832284
Members
1912
Online
110041
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-27-2006 12:03 AM
03-27-2006 12:03 AM
Howto use wildcards in netfmt filters
Hello,
I am inept to perform the trivial task of telling netfmt to filter for *any* (high range) local port of a client connection to a service running where I do run the nettl trace.
All these variants result in bad filter errors by netfmt.
filter connection 123.123.123.123:* 231.231.231.231:4444
filter connection 123.123.123.123: 231.231.231.231:4444
filter connection 123.123.123.123 231.231.231.231:4444
If there was a way to tell netfmt to logically AND filters per layer (in the manpage it says filters within layers are ORed and accross layers are ANDed)
then I would do something like
filter ip_daddr 231.231.231.231 && tcp_dport 4444 && filter ip_saddr 123.123.123.123
but that doesn't work either.
Thanks
Ralph
I am inept to perform the trivial task of telling netfmt to filter for *any* (high range) local port of a client connection to a service running where I do run the nettl trace.
All these variants result in bad filter errors by netfmt.
filter connection 123.123.123.123:* 231.231.231.231:4444
filter connection 123.123.123.123: 231.231.231.231:4444
filter connection 123.123.123.123 231.231.231.231:4444
If there was a way to tell netfmt to logically AND filters per layer (in the manpage it says filters within layers are ORed and accross layers are ANDed)
then I would do something like
filter ip_daddr 231.231.231.231 && tcp_dport 4444 && filter ip_saddr 123.123.123.123
but that doesn't work either.
Thanks
Ralph
Madness, thy name is system administration
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2006 05:49 PM
03-27-2006 05:49 PM
Re: Howto use wildcards in netfmt filters
How about
filter ip_saddr 123.123.123.123
filter ip_daddr 231.231.231.231
filter tcp_dport 4444
filter ip_saddr 123.123.123.123
filter ip_daddr 231.231.231.231
filter tcp_dport 4444
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2006 06:48 PM
03-27-2006 06:48 PM
Re: Howto use wildcards in netfmt filters
Hello Ermin,
your suggestion was of course my first filter.
But it didn't work as I expected,
and with it I was capturing every packet that at layer 3 that had the named IP source *or* destination address *and* at layer 4 the given destination port.
or to quote from netfmt manpage:
For a packet to make it through a filter layer which has a
filter specified, it must match the filter. Filters at each layer are
logically ``OR''ed. Filters between layers are logically ``AND''ed.
So the filter wasn't as restrictive as I would have wished, and I rather would want it to behave like what I am used to from tcpdump or snoop where you can intersperse logical operators between separate filters.
Well, as a last resort I still could install the libpcap together with tcpdump.
Besides, I started a new thread with a nettl netfmt question redarding accounting.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1014485
Regards
Ralph
your suggestion was of course my first filter.
But it didn't work as I expected,
and with it I was capturing every packet that at layer 3 that had the named IP source *or* destination address *and* at layer 4 the given destination port.
or to quote from netfmt manpage:
For a packet to make it through a filter layer which has a
filter specified, it must match the filter. Filters at each layer are
logically ``OR''ed. Filters between layers are logically ``AND''ed.
So the filter wasn't as restrictive as I would have wished, and I rather would want it to behave like what I am used to from tcpdump or snoop where you can intersperse logical operators between separate filters.
Well, as a last resort I still could install the libpcap together with tcpdump.
Besides, I started a new thread with a nettl netfmt question redarding accounting.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1014485
Regards
Ralph
Madness, thy name is system administration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2006 08:30 PM
03-27-2006 08:30 PM
Re: Howto use wildcards in netfmt filters
Hello Ralph,
Have you tried omitting ip_saddr filter? i.e just have
filter ip_daddr 231.231.231.231
filter tcp_dport 4444
It might be close to what you're after.
Have you tried omitting ip_saddr filter? i.e just have
filter ip_daddr 231.231.231.231
filter tcp_dport 4444
It might be close to what you're after.
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