| Deutsch English Français Italiano |
|
<uvvmnk$atsn$1@news1.tnib.de> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder8.news.weretis.net!news1.tnib.de!feed.news.tnib.de!news.tnib.de!.POSTED.torres.zugschlus.de!not-for-mail From: Marc Haber <mh+usenetspam1118@zugschl.us> Newsgroups: comp.os.linux.misc Subject: Re: I never thought of this scenario Date: Sat, 20 Apr 2024 08:18:28 +0200 Organization: private site, see http://www.zugschlus.de/ for details Message-ID: <uvvmnk$atsn$1@news1.tnib.de> References: <uuu39t$2pd0s$1@dont-email.me> <uuvblp$32mbm$1@dont-email.me> <uv06o4$3c5fm$2@dont-email.me> <uv09ad$3cnth$1@dont-email.me> <uv2e60$jin$1@dont-email.me> <uv3e7p$7nqq$3@dont-email.me> <uvcu20$2qdb0$3@dont-email.me> <uvd5rs$n3n$1@tncsrv09.home.tnetconsulting.net> <uvht5g$3th0n$3@dont-email.me> <uvhv3k$kq3$2@tncsrv09.home.tnetconsulting.net> <uvs640$2g9b9$6@dont-email.me> <uvtek0$2u6or$2@dont-email.me> <uvtuav$tkt$2@tncsrv09.home.tnetconsulting.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Date: Sat, 20 Apr 2024 06:18:28 -0000 (UTC) Injection-Info: news1.tnib.de; posting-host="torres.zugschlus.de:81.169.166.32"; logging-data="358295"; mail-complaints-to="abuse@tnib.de" X-Newsreader: Forte Agent 6.00/32.1186 Bytes: 3047 Lines: 38 Grant Taylor <gtaylor@tnetconsulting.net> wrote: >On 4/19/24 04:47, The Natural Philosopher wrote: >> DHCP servers can serve multiple local subnets > >Yes, DHCP servers can easily server multiple /locally/ /attached/ >subnets. As in multiple physical interfaces and / or multiple logical >VLAN interfaces. Wherein the DHCP server is in the same broadcast >domain as the DHCP client. The don't need to be if a DHCP agent is available. DHCP agents are considerably easier to implement AND don't need persistent state. They can just be implemented in "less intellgent" network devices. This also considerably eases exchange of defective devices since you don't lose state unless it's the DHCP server itself that is exchanged. >> The key is that the routers between each subnet and the DHCP machine >> need to be told to route DHCP in some way. > >I would consider those to be remote subnets as they are not /locally/ >/attached/ to the DHCP server. Meaning the DHCP server is not directly >participating in the broadcast domain. > >DHCP servers can easily serve multiple /remote/ subnets. > >Being in the layer 2 broadcast domain means that everybody smells it >when somebody farts for a browse maser election on the other side of the >room. That is unneccesarily confusing, DHCP has nothing to do with browse master elections. I surely hope that Windows doesn't do those any more. Greetings Marc -- ---------------------------------------------------------------------------- Marc Haber | " Questions are the | Mailadresse im Header Rhein-Neckar, DE | Beginning of Wisdom " | Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402