On Tue, 2013-12-10 at 18:48 +0100, Lennart Poettering wrote:
I agree with Zbigniew: this should probably be in
src/libsystemd-dhcp/, so that this is similar to libsystemd-bus/,
libsystemd-id128/ and so on...
Sent a patch for that, and in the process of creating an account on
freedesktop.org.
Hi Patrik,
I agree with Zbigniew: this should probably be in
src/libsystemd-dhcp/, so that this is similar to libsystemd-bus/,
libsystemd-id128/ and so on...
Sent a patch for that, and in the process of creating an account on
freedesktop.org. As that will most probably take some time,
On Tue, 2013-12-10 at 02:46 +0100, Lennart Poettering wrote:
+uint32_t ciaddr;
+uint32_t yiaddr;
+uint32_t siaddr;
+uint32_t giaddr;
Hmmm, why uin32_t? Shouldn't this be32_t? THis is network byte order,
right? which is just synoymous to big endian...
On 10 Dec 2013 17:45, Patrik Flykt patrik.fl...@linux.intel.com wrote:
On Tue, 2013-12-10 at 02:46 +0100, Lennart Poettering wrote:
+uint32_t ciaddr;
+uint32_t yiaddr;
+uint32_t siaddr;
+uint32_t giaddr;
Hmmm, why uin32_t? Shouldn't this be32_t?
On Tue, 10.12.13 14:15, Patrik Flykt (patrik.fl...@linux.intel.com) wrote:
On Tue, 2013-12-10 at 02:46 +0100, Lennart Poettering wrote:
+uint32_t ciaddr;
+uint32_t yiaddr;
+uint32_t siaddr;
+uint32_t giaddr;
Hmmm, why uin32_t? Shouldn't this
Hi Lennart,
+uint32_t ciaddr;
+uint32_t yiaddr;
+uint32_t siaddr;
+uint32_t giaddr;
Hmmm, why uin32_t? Shouldn't this be32_t? THis is network byte order,
right? which is just synoymous to big endian...
Or even, if you now use struct in_addr elsewhere
On Tue, 10.12.13 18:12, Marcel Holtmann (mar...@holtmann.org) wrote:
Hi Lennart,
+uint32_t ciaddr;
+uint32_t yiaddr;
+uint32_t siaddr;
+uint32_t giaddr;
Hmmm, why uin32_t? Shouldn't this be32_t? THis is network byte order,
right? which is just
On Mon, 09.12.13 23:43, Patrik Flykt (patrik.fl...@linux.intel.com) wrote:
+struct DHCPMessage {
+uint8_t op;
+uint8_t htype;
+uint8_t hlen;
+uint8_t hops;
+be32_t xid;
+be16_t secs;
+be16_t flags;
+uint32_t ciaddr;
+
