Fix time_offset to be int to match RFC-2132

https://datatracker.ietf.org/doc/html/rfc2132#section-3.4

time_offset (dhcp v4 option 2) should be int32, not uint32, as it can
indicate a time offset east (positive) or west (negative) of zero
meridian.

diff --git a/src/dhcpcd-definitions.conf b/src/dhcpcd-definitions.conf
index ad8efd3f2c1e96b1b585f6e15901a1cf01d95002..37ae9744037b78e3b4b3fe3a0994a80e0e6d8514 100644 (file)
--- a/src/dhcpcd-definitions.conf
+++ b/src/dhcpcd-definitions.conf
@@ -12,7 +12,7 @@ define 1      request ipaddress       subnet_mask
 # RFC3442 states that the CSR has to come before all other routes
 # For completeness we also specify static routes then routers
 define 121     rfc3442                 classless_static_routes
-define 2       uint32                  time_offset
+define 2       int32                   time_offset
 define 3       request array ipaddress routers
 define 4       array ipaddress         time_servers
 define 5       array ipaddress         ien116_name_servers