diff options
author | David Hankins <dhankins@isc.org> | 2006-02-24 23:16:32 +0000 |
---|---|---|
committer | David Hankins <dhankins@isc.org> | 2006-02-24 23:16:32 +0000 |
commit | 88cd8aca9efa1e5b867ac498b98e972638f7aee8 (patch) | |
tree | 8d3015eda99ca77265ed79d15b6e1f0200f6bab3 /README | |
parent | b43c87ad595026da002f7acca54bf24318d9fed2 (diff) | |
download | isc-dhcp-88cd8aca9efa1e5b867ac498b98e972638f7aee8.tar.gz |
- Merge changes between 3.0.3RC1 and 3.0.4-BETA-3 into HEAD (silence
robie).
Diffstat (limited to 'README')
-rw-r--r-- | README | 34 |
1 files changed, 26 insertions, 8 deletions
@@ -367,6 +367,18 @@ Linux 2.1 and later kernels do not use SO_BINDTODEVICE or require the broadcast address hack, but do support multiple interfaces, using the Linux Packet Filter. + LINUX: 802.1q VLAN INTERFACES + +If you're using 802.1q vlan interfaces on Linux, it is necessary to +vconfig the subinterface(s) to rewrite the 802.1q information out of +packets received by the dhcpd daemon via LPF: + + vconfig set_flag eth1.523 1 1 + +Note that this may affect the performance of your system, since the +Linux kernel must rewrite packets received via this interface. For +more information, consult the vconfig man pages. + SCO SCO has the same problem as Linux (described earlier). The thing is, @@ -446,18 +458,24 @@ systems, although it may occur with other systems as well. If you encounter this symptom, and you are running the DHCP server on a machine with a single broadcast network interface, you may wish to edit the includes/site.h file and uncomment the #define USE_SOCKETS -line. Then type ``make clean; make''. +line. Then type ``make clean; make''. As an alternative workaround, +it has been reported that running 'snoop' will cause the dhcp server +to start receiving packets. So the practice reported to us is to run +snoop at dhcpd startup time, with arguments to cause it to receive one +packet and exit. + + snoop -c 1 udp port 67 > /dev/null & The DHCP client on Solaris will only work with DLPI. If you run it and it just keeps saying it's sending DHCPREQUEST packets, but never gets a response, you may be having DLPI trouble as described above. -If so, we have no solution to offer at this time. Also, because -Solaris requires you to "plumb" an interface before it can be detected -by the DHCP client, you must either specify the name(s) of the -interface(s) you want to configure on the command line, or must plumb -the interfaces prior to invoking the DHCP client. This can be done -with ``ifconfig iface plumb'', where iface is the name of the -interface (e.g., ``ifconfig hme0 plumb''). +If so, we have no solution to offer at this time, aside from the above +workaround which should also work here. Also, because Solaris requires +you to "plumb" an interface before it can be detected by the DHCP client, +you must either specify the name(s) of the interface(s) you want to +configure on the command line, or must plumb the interfaces prior to +invoking the DHCP client. This can be done with ``ifconfig iface plumb'', +where iface is the name of the interface (e.g., ``ifconfig hme0 plumb''). It should be noted that Solaris versions from 2.6 onward include a DHCP client that you can run with ``/sbin/ifconfig iface dhcp start'' |