> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-iseries-en/proxy/onesait-editran-proxy-on-unix-and-windows/ip-addresses-without-trace.md).

# IP addresses without trace

There may be network monitoring tools within an organization (such as *HP* *Openview*, *Service Monitoring Daemon*, *LANsurveyor*, *ipMonitor*...). These systems periodically attempt to connect to a service on some networked machine to check whether it is still active and accepting connections.

To prevent the file from becoming full *ediproxyth.out* of information we do not want about these systems, there is the possibility of creating a file with a series of TCP/IP addresses whose activity we do not want to appear in the editran/PX trace.

In this way, we can include in a file all the TCP/IP addresses where we have monitoring systems and avoid filling the file with *ediproxyth.out* lines lacking useful information.

The TCP/IP addresses for which tracing is not desired must each be entered on a separate line in the file *ipnotraza.cfg* in the directory where editran/PX is installed. The file may not exist *ipnotraza.cfg* in this case the file *ediproxyth.out* will contain all the information.

The following shows the contents of a file *ipnotraza.cfg* that contains two IPs (172.22.168.23 and 172.22.168.24) for which tracing is not desired in the file *ediproxyth.out*::

*172.22.168.23*

*172.22.168.24*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-iseries-en/proxy/onesait-editran-proxy-on-unix-and-windows/ip-addresses-without-trace.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.