diff options
| author | root <root@frank.tg14.gathering.org> | 2014-04-20 02:46:46 +0200 |
|---|---|---|
| committer | root <root@frank.tg14.gathering.org> | 2014-04-20 02:46:46 +0200 |
| commit | 66426aeac27af5793d388cea7b1078fb871fc5ad (patch) | |
| tree | 66e847f4de9b8ff7b8fa0bd942fb8b9e04bfd904 /examples/old-patches/README | |
| parent | b231e372681e6bfc499fd2aadda840e0b607278f (diff) | |
Moved files, re-organized a bit.
Diffstat (limited to 'examples/old-patches/README')
| -rw-r--r-- | examples/old-patches/README | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/examples/old-patches/README b/examples/old-patches/README new file mode 100644 index 0000000..bc6a962 --- /dev/null +++ b/examples/old-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. |