simple QoS for dhcpd

[Shane Kerr]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In that case, the simplest solution would probably be to have a set of variables
like this:

time_t qos_discover_timestamp;	/* 0 means no discover received yet */
unsigned short qos_uid_len;	/* 0 means no client identifier, use hw_addr */
unsigned char *qos_uid;
struct hardware qos_hw_addr;

You set the appropriate variables when you get a new discover, and then can
check them in all other places. We use a timestamp so you can time out
eventually (in case the client goes away).

Good luck! :)

fadey wrote:
> Yes. It is for research, not production.
> 
>> You do realise that this gives yet another means for a DoS attack don't you ?
>>
>>
>> fadey wrote:
>>
>>> I'm interested in modifying dhcpd in a way that it serves one client at
>>> a time: takes a DISCOVER packet, serves OFFER, waits for the REQUEST and
>>> serves ACK, and only after that pays attantion to whats going on on port
>>> 67 again.

- --
Shane
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHPCLLMsfZxBO4kbQRAmQLAKCU0WZFe/4T7nilJ9JMHrA2jcCGvQCggqQL
h/ZtQhcpoEsM3M57jXzE3zo=
=QVKN
-----END PGP SIGNATURE-----