Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: The Natural Philosopher <tnp@invalid.invalid>
Newsgroups: comp.os.linux.misc
Subject: Re: I never thought of this scenario
Date: Sun, 21 Apr 2024 11:17:28 +0100
Organization: A little, after lunch
Lines: 30
Message-ID: <v02p3o$894n$2@dont-email.me>
References: <uv2g3g$39k$1@tncsrv09.home.tnetconsulting.net>
 <uvhtft$3th0n$6@dont-email.me>
 <uvhv0m$kq3$1@tncsrv09.home.tnetconsulting.net>
 <uvs61u$2g9b9$5@dont-email.me> <uvsv4f$3cvv$1@news1.tnib.de>
 <uvv1qf$392q8$2@dont-email.me> <uvve26$3f4ea$1@dont-email.me>
 <wwvh6fwxy7q.fsf@LkoBDZeT.terraraq.uk> <v0108c$3q01h$1@dont-email.me>
 <v0111s$3q1fd$1@dont-email.me> <v013pv$3qmkf$1@dont-email.me>
 <v014gp$3qp0c$1@dont-email.me>
 <v017q3$td0$4@tncsrv09.home.tnetconsulting.net>
 <v018mo$3rj12$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 21 Apr 2024 12:17:29 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="e82ae113dc7ea49192f189c77debcc18";
	logging-data="271511"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX182XXEKZAYTy6OtVKrJfxQlN/tC3QioRGc="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:jDgPo2Em5SbOrRLlSXpwpqtVtVw=
Content-Language: en-GB
In-Reply-To: <v018mo$3rj12$1@dont-email.me>
Bytes: 2540

On 20/04/2024 21:31, Rich wrote:
> Exclusive of
> "deep packet inspection" a router is routing packets by looking at the
> IP header of that packet, not looking inside the IP packet's payload
> for HTTP/NNTP/DHCP/etc.  contents and routing based on those contents.

Not at all true in the case of address translation, routing protocols, 
traffic shaping and the like.

The only thing that caries is how *much* of the packet you inspect.

DHCP is similar in that the on;y thing a router has to do is determine 
its a UDP broadcast, and if it is, work out where to send it, and what 
return address to give it if any..

One would expect the router to simply spoof a MAC address on its 
interface, and relay responses to that MAC address back to the client 
network.
In short its acting like an ethernet switch or bridge

I am more curious as to how the DHCP server 'knows' which network 
address to give the client, but not interested enough to look it up. :-)




-- 
Climate is what you expect but weather is what you get.
Mark Twain