After applying the update on my servers, I got massive problems in the
stability of my network connections. I was running bond in mode 6, which
now seems not to work anymore.
auto bond0
iface bond0 inet static
hwaddress ether 00:30:88:88:88:88
address 192.168.111.5
netmask
Traditional dhcpd.conf
** Attachment added: dhcp.conf_traditional
https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/673427/+attachment/1730376/+files/dhcp.conf_traditional
--
DHCP with LDAP config should load class definitions first
https://bugs.launchpad.net/bugs/673427
You received
dhcpd.conf for LDAP saved configuration
** Attachment added: dhcpd.conf_with_LDAP
https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/673427/+attachment/1730377/+files/dhcpd.conf_with_LDAP
--
DHCP with LDAP config should load class definitions first
https://bugs.launchpad.net/bugs/673427
LDIF with DHCP configuration
** Attachment added: dhcp.ldif
https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/673427/+attachment/1730378/+files/dhcp.ldif
--
DHCP with LDAP config should load class definitions first
https://bugs.launchpad.net/bugs/673427
You received this bug notification
Traditional dhcpd.conf
** Attachment added: dhcp.conf_traditional
https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/673427/+attachment/1730376/+files/dhcp.conf_traditional
--
DHCP with LDAP config should load class definitions first
https://bugs.launchpad.net/bugs/673427
You received
dhcpd.conf for LDAP saved configuration
** Attachment added: dhcpd.conf_with_LDAP
https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/673427/+attachment/1730377/+files/dhcpd.conf_with_LDAP
--
DHCP with LDAP config should load class definitions first
https://bugs.launchpad.net/bugs/673427
LDIF with DHCP configuration
** Attachment added: dhcp.ldif
https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/673427/+attachment/1730378/+files/dhcp.ldif
--
DHCP with LDAP config should load class definitions first
https://bugs.launchpad.net/bugs/673427
You received this bug notification
As you can see in the LDIF, the classes are declared before the pools.
If you don't do that, DHCPD will throw an error.
To take care of the correct order is easy if you load the stuff
manually with LDIF files in the LDAP. But we use GoSA (www.gosa-
project.org) here, which provides a graphical
Public bug reported:
Binary package hint: dhcp3-server-ldap
Take as example the following dhcpd.conf (just as example, it's syntax
is not right):
global parameters...
class VoIP_Phones {
match if (substring (hardware,1,3)=00:04:13);
}
class Other_Clients {
match if not (substring
Uuups, of course it's
class Other_Clients {
match if not (substring (hardware,1,3)=00:04:13);
}
** Description changed:
Binary package hint: dhcp3-server-ldap
Take as example the following dhcpd.conf (just as example, it's syntax
is not right):
global parameters...
class
Public bug reported:
Binary package hint: dhcp3-server-ldap
Take as example the following dhcpd.conf (just as example, it's syntax
is not right):
global parameters...
class VoIP_Phones {
match if (substring (hardware,1,3)=00:04:13);
}
class Other_Clients {
match if not (substring
Uuups, of course it's
class Other_Clients {
match if not (substring (hardware,1,3)=00:04:13);
}
** Description changed:
Binary package hint: dhcp3-server-ldap
Take as example the following dhcpd.conf (just as example, it's syntax
is not right):
global parameters...
class
12 matches
Mail list logo
