This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
fuss:networking [2018/08/03 09:11] – [Determining Open Outbound Ports] office | fuss:networking [2020/05/16 22:55] – [Determine ISP Address Blocks] office | ||
---|---|---|---|
Line 319: | Line 319: | ||
2a01: | 2a01: | ||
</ | </ | ||
+ | |||
+ | ====== Solving Issues with PXE Servers not Working with Network Bridges with Spanning Tree Protocol Enabled ====== | ||
+ | |||
+ | A typical scenario of a non-working PXE server is a PXE server that has been set up on a Linux server running virtual machines that automatically join an STP-enabled network bridge once the virtual machine boots. | ||
+ | |||
+ | The phenomenon is due to STP itself that runs through various stages ('' | ||
+ | |||
+ | Cisco routers have a (nasty) hack named '' | ||
+ | |||
+ | In order to resolve the issue, STP can be turned off for the entire bridge: | ||
+ | <code bash> | ||
+ | brctl stp br0 off | ||
+ | </ | ||
+ | but that means losing the extra benefits of having the STP protocol. | ||
+ | |||
+ | Instead, and even better than Cisco '' | ||
+ | |||
+ | <code bash> | ||
+ | brctl setfd br0 2 | ||
+ | </ | ||
+ | where: | ||
+ | * '' | ||
+ | |||
+ | On Debian, in case the bridge is configured via ''/ | ||
+ | < | ||
+ | auto br0 | ||
+ | iface br0 inet static | ||
+ | ... | ||
+ | # Enable STP | ||
+ | bridge_stp on | ||
+ | # Fix PXE with STP | ||
+ | bridge_fd 2 | ||
+ | ... | ||
+ | </ | ||
+ | |||
+ | |||
+ | |||