1.265 connection 1.270 not connecting

[Bill Moss <bmoss clemson edu>]

1.265 connects to SMC AP/DHCP server, but 1.270 does not. Will try 
ethereal over the weekend. I am assuming that NM sends a discovery 
message that the DHCP server does not like and so does not reply.

Here is bit from the syslog for the version at changelog 1.265. This is 
a ACK reply from the DHCP server. Why are all the option numbers too low 
by 2? Are the options for the server and client numbered differently? I 
don't recall seeing that. The client option numbers can be found in 
dhcpcd.h. Are the discovery messages sent with a bogus option numbering 
scheme? 1.270 is no longer sending  dhcpClassIdentifier and 
dhcpClientIdentifier options or else they are nulled out.

Feb 11 09:27:23 localhost NetworkManager: Broadcasting DHCP_REQUEST for 
192.168.2.3
Feb 11 09:27:23 localhost NetworkManager: DHCP: Starting request loop
Feb 11 09:27:23 localhost NetworkManager: DHCP: Request sent, waiting 
for reply...
Feb 11 09:27:23 localhost NetworkManager: DHCP: Got some data of length 576.
Feb 11 09:27:23 localhost NetworkManager: Server replied with 11 DHCP 
options:
Feb 11 09:27:23 localhost NetworkManager:       i=1  (subnetMask)  
len=4   option = 255.255.255.0
Feb 11 09:27:23 localhost NetworkManager:       i=3  (routersOnSubnet)  
len=4   option = 192.168.2.1
Feb 11 09:27:23 localhost NetworkManager:       i=6  (dns)  len=4   
option = 192.168.2.1
Feb 11 09:27:23 localhost NetworkManager:       i=15 (domainName)  
len=9   option = "WorkGroup"
Feb 11 09:27:23 localhost NetworkManager:       i=28 (broadcastAddr)  
len=4   option = 255.255.255.255
Feb 11 09:27:23 localhost NetworkManager:       i=51 (dhcpMessageType)  
len=4   option = 7200
Feb 11 09:27:23 localhost NetworkManager:       i=52 
(dhcpServerIdentifier)  len=1   option = ""
Feb 11 09:27:23 localhost NetworkManager:       i=53 (dhcpParamRequest)  
len=1   option = 5
Feb 11 09:27:23 localhost NetworkManager:       i=54 (dhcpMsg)  len=4   
option = 192.168.2.1
Feb 11 09:27:23 localhost NetworkManager:       i=58 
(dhcpClassIdentifier)  len=4   option = 0
Feb 11 09:27:23 localhost NetworkManager:       i=59 
(dhcpClientIdentifier)  len=4   option = 0
Feb 11 09:27:23 localhost NetworkManager:       dhcp_msg->yiaddr  = 
192.168.2.3
Feb 11 09:27:23 localhost NetworkManager:       dhcp_msg->siaddr  = 0.0.0.0
Feb 11 09:27:23 localhost NetworkManager:       dhcp_msg->giaddr  = 0.0.0.0
Feb 11 09:27:23 localhost NetworkManager:       dhcp_msg->sname   = ""
Feb 11 09:27:23 localhost NetworkManager:       Server Hardware 
Address   = 00.04.E2.1E.55.C8
Feb 11 09:27:23 localhost NetworkManager: DHCP_ACK received from  
(192.168.2.1)

--
Bill Moss
Professor, Mathematical Sciences
Clemson University