Blame SOURCES/dhcp-duidv4.patch

26a25c
diff -up dhcp-4.3.1b1/client/dhclient.8.KrJcIv dhcp-4.3.1b1/client/dhclient.8
26a25c
--- dhcp-4.3.1b1/client/dhclient.8.KrJcIv	2014-07-10 17:39:25.852763873 +0200
26a25c
+++ dhcp-4.3.1b1/client/dhclient.8	2014-07-10 17:54:26.841012988 +0200
26a25c
@@ -458,6 +458,9 @@ used to construct a RFC4361 style client
26a25c
 in the client's messages.  This client id can be overridden by
26a25c
 setting a client id in the configuration file.  Overridding the
26a25c
 client id in this fashion is discouraged.
26a25c
+This option is turned on by default, if you want to redefine or turn off
26a25c
+sending of client id, use send dhcp-client-identifier = "better identifier"
26a25c
+or send dhcp-client-identifier = "" in /etc/dhcp/dhclient.conf.
26a25c
 .TP
26a25c
 .BI \-I
26a25c
 Use the standard DDNS scheme from RFCs 4701 & 4702.  
26a25c
diff -up dhcp-4.3.1b1/client/dhclient.c.KrJcIv dhcp-4.3.1b1/client/dhclient.c
26a25c
--- dhcp-4.3.1b1/client/dhclient.c.KrJcIv	2014-07-10 17:54:26.829013157 +0200
26a25c
+++ dhcp-4.3.1b1/client/dhclient.c	2014-07-10 17:55:50.155835918 +0200
26a25c
@@ -73,7 +73,7 @@ struct sockaddr_in sockaddr_broadcast;
26a25c
 struct in_addr giaddr;
26a25c
 struct data_string default_duid;
26a25c
 int duid_type = 0;
26a25c
-int duid_v4 = 0;
26a25c
+int duid_v4 = 1;
26a25c
 int std_dhcid = 0;
26a25c
 
26a25c
 /* ASSERT_STATE() does nothing now; it used to be
26a25c
@@ -1301,7 +1301,7 @@ static void setup_ib_interface(struct in
26a25c
 	}
26a25c
 
26a25c
 	/* No client ID specified */
26a25c
-	log_fatal("dhcp-client-identifier must be specified for InfiniBand");
26a25c
+	//log_fatal("dhcp-client-identifier must be specified for InfiniBand");
26a25c
 }
26a25c
 
26a25c
 /* Individual States: