- From: Flavio Figorilli <
>
- To:
- Subject: Re: [reti-accesso] Porta client DHCP - caccia al tesoro
- Date: Tue, 10 Jun 2008 01:03:36 +0200
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=pVCe5+lIwbm2UyAcBmPqx9OMs27wc0HGFpw2yfaButATwatHupTvsW61BD6wJP9115 vc/XyLNi0aW85+BnaTHDud9BN0wtw0ddk9CQdUHCI7/aQzphOtelcHS6900iJD8lUoIY 6OS1gnNQ7cMOi1JDnJdKr84l9V+u515kwWLS0=
- Openpgp: url=pool.sks-keyservers.net
Lorenzo Bracciale ha scritto:
>
Ricordo il quesito per la "caccia al tesoro":
>
Trovare il perchè nel protocollo dhcp viene definita una porta specifica
>
*anche* per il client, a differenza ad esempio di http (e della maggior
>
parte degli altri protocolli) dove l'unica porta definita è quella
>
server (ad es. la 80 per http).
>
>
Mandate la risposta (e la fonte) il mailing list.
>
Ciao,
>
>
Lorenzo
>
Mi sa che prima ho detto una caz.....olata...
Lo standard dice:
The reason TWO reserved ports
are used, is to avoid 'waking up' and scheduling the BOOTP server
daemons, when a bootreply must be broadcast to a client. Since the
server and other hosts won't be listening on the 'BOOTP client' port,
any such incoming broadcasts will be filtered out at the kernel
level. We could not simply allow the client to pick a 'random' port
number for the UDP source port field; since the server reply may be
broadcast, a randomly chosen port number could confuse other hosts
that happened to be listening on that port.
buona notte a tutti.............
Archivio con motore MhonArc 2.6.16.