# Multi NIC and trunks implementations

Normal 2PXE operation involves several binding to local interfaces, primarily for the DHCP and TFTP threads. The "BindTo" configuration value is used for the DHCP threads, as Windows handles multicast/broadcast responds in a very uncontrolled way, it needs to know from which adapter to send the broadcast reply, this is done by specifying the address for the DHCP threads to use when creating the sockets.

In some cases TFTP might fail to send the data from the correct interface and the servers UDP replies to the TFTP read requests ends up being sent from the wrong adapter/IP. In this case, create a new configuration entry in the .config file (next to the BindToIp) setting preferably, name it: "ListenToTftpIp" and set the value to the correct IP you want to use, such as "10.10.11.30" (in most scenarios this IP is the same as the BindToIp value).


---

# Agent Instructions: 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:

```
GET https://documentation.2pintsoftware.com/2pxe-server/troubleshooting/multi-nic-and-trunks-implementations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
