diff options
| author | root <root@riffraff.tg14.gathering.org> | 2014-04-20 02:58:05 +0200 |
|---|---|---|
| committer | root <root@riffraff.tg14.gathering.org> | 2014-04-20 02:58:05 +0200 |
| commit | 8f4ae8e5833f0d26be5fad5160ae6ee0479b0712 (patch) | |
| tree | da5089e91fbe52fd7da57a1c431c9af64f6ac8af /patches/README | |
| parent | 37a3b5d6ed97367989aecc875f1db1e9eb0458df (diff) | |
| parent | 19cd0064816a577b72577b9f21a5a946eb746f64 (diff) | |
Merge branch 'master' of https://github.com/tech-server/tgmanage
Diffstat (limited to 'patches/README')
| -rw-r--r-- | patches/README | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/patches/README b/patches/README deleted file mode 100644 index c89deaf..0000000 --- a/patches/README +++ /dev/null @@ -1,13 +0,0 @@ -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. |