> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/ipxe-ws/configuration/configuring-the-ipxe-web-service.md).

# Configuring the iPXE Web Service

### Using the iPXE Anywhere Web Service

The iPXE Anywhere Service is configured via the 2PXE Server Configuration File – which is covered in full in the 2PXE Server documentation.

There are 2 settings to consider within the 2PXE Configuration file:

**ENABLEIPXEANYWHEREWEBSERVICE**="0” \
Specifies to use iPXE Anywhere Web Service. 0 to disable, 1 to use reporting functionality only, 2 to move the entire request over to the web service + reporting. 3 is 1+2 and the ability to execute command line from iPXE WS in WinPE

 BootRequest = 1,

 Syslog = 2

Using the resolved IPv4 Addresss of the iPXE Anywhere Web Service unless overridden by adding the \<add key="iPXEAnywhereWebServiceIP" value="192.168.xxx.yyy"/> setting in this config.

&#x20;ReportBootConfiguration = 4,

&#x20;ReportDLStart = 8,

&#x20;ReportDLComplete = 16,

&#x20;ReportDLBoot = 32,

&#x20;RunCmdLineWinPE = 64

For example:

A value of 62 (2+4+8+16+32=62) gives you all but BootRequest and RunCmdLineWinPE. Therefore

for iPXE and StifleR Integration you would have to set it to a minimum of; 2+4+8+16+32 = 62

**IPXEANYWHEREWEBSERVICEURI**=[http://url:Port](http://url/:Port) Specifies the address and Port for the iPXE Anywhere Web Service

Pretty simple – but be sure to enter the FQDN of the server and Port number.

> IMPORTANT: After setting the above parameters, you will then need to restart the 2PXE service.


---

# 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://documentation.2pintsoftware.com/ipxe-ws/configuration/configuring-the-ipxe-web-service.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.