diff options
| author | Joachim Tingvold <joachim@tingvold.com> | 2015-03-21 14:48:22 +0100 |
|---|---|---|
| committer | Joachim Tingvold <joachim@tingvold.com> | 2015-03-21 14:48:22 +0100 |
| commit | 6875390524d606e23b23ab0a45239630ed49ba65 (patch) | |
| tree | 6e71411f41e3a7db379f69c17486ded35a75d053 /examples/historical/patches/README | |
| parent | 630f90f91cb5ef32d432314c9934a8ec5c3c7b05 (diff) | |
Re-add moved files.
Diffstat (limited to 'examples/historical/patches/README')
| -rw-r--r-- | examples/historical/patches/README | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/examples/historical/patches/README b/examples/historical/patches/README new file mode 100644 index 0000000..bc6a962 --- /dev/null +++ b/examples/historical/patches/README @@ -0,0 +1,17 @@ + +Patches from pre TG14. None of these patches were in use under TG14. + + +Includes various patch(es) we had to use. + +> dhcpd-never-broadcast.diff + +When using DHCP in routed networks, the router has to participate in rewriting +and sending DHCP replies on to the user. Unfortunately, some devices, +in particular Cisco's Nexus series of switches, drop such DHCP reply packets +with the broadcast bit in the flags field of the DHCP message header set. +Thi means that some operating systems, in particular Microsoft Windows Vista, +can have problems getting DHCP to work in such environments. If you enable +this flag, the DHCP server will never set the broadcast flags in the replies +it sends, even if the client set the broadcast flag. This flag overrides +the never-broadcast flag if both are set. |