Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #262472 > unrolled thread
| Started by | Pocket <pocket@columbus.rr.com> |
|---|---|
| First post | 2023-10-21 18:40 +0200 |
| Last post | 2023-10-22 02:30 +0200 |
| Articles | 20 on this page of 246 — 32 participants |
Back to article view | Back to linux.debian.user
Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 18:40 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 18:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 19:10 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 19:30 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 19:40 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 20:00 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:10 +0200
Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-22 10:10 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:30 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:50 +0200
Re: Bookworm: NetworkManager Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 15:20 +0200
Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-22 18:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:50 +0200
Re: Bookworm: NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-22 19:40 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 20:00 +0200
Re: Bookworm: NetworkManager Henning Follmann <hfollmann@itcfollmann.com> - 2023-10-22 17:10 +0200
Re: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-22 18:30 +0200
Re: Bookworm: NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 20:40 +0200
Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-24 18:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-24 19:30 +0200
Re: Bookworm: NetworkManager "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-24 19:40 +0200
Re: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-25 03:10 +0200
Re: Bookworm: NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-25 03:50 +0200
link-local 169.254.x.y addresses Max Nikulin <manikulin@gmail.com> - 2023-10-25 18:50 +0200
Re: Bookworm: NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-25 01:40 +0200
Alternative to NetworkManager on Debian 12 Alessandro Baggi <alessandro.baggi@gmail.com> - 2023-11-01 11:50 +0100
Re: Alternative to NetworkManager on Debian 12 Greg Wooledge <greg@wooledge.org> - 2023-11-01 12:20 +0100
Re: Alternative to NetworkManager on Debian 12 Nicolas George <george@nsup.org> - 2023-11-01 12:40 +0100
Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-01 17:10 +0100
Re: Alternative to NetworkManager on Debian 12 Nicolas George <george@nsup.org> - 2023-11-01 17:20 +0100
Re: Alternative to NetworkManager on Debian 12 yxcv@vienna.at - 2023-11-01 12:20 +0100
Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 12:20 +0100
Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 12:20 +0100
Re: Alternative to NetworkManager on Debian 12 Felix Miata <mrmazda@earthlink.net> - 2023-11-01 15:20 +0100
Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 15:40 +0100
Re: Alternative to NetworkManager on Debian 12 Alessandro Baggi <alessandro.baggi@gmail.com> - 2023-11-01 15:50 +0100
Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-01 16:10 +0100
Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-01 18:50 +0100
Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-02 16:50 +0100
Re: Alternative to NetworkManager on Debian 12 Jeffrey Walton <noloader@gmail.com> - 2023-11-02 18:00 +0100
Re: Alternative to NetworkManager on Debian 12 <tomas@tuxteam.de> - 2023-11-02 19:00 +0100
Re: Alternative to NetworkManager on Debian 12 Max Nikulin <manikulin@gmail.com> - 2023-11-03 16:50 +0100
Re: Alternative to NetworkManager on Debian 12 debian-user@howorth.org.uk - 2023-11-01 21:00 +0100
Re: Alternative to NetworkManager on Debian 12 "Marco M." <mm@dorfdsl.de> - 2023-11-01 12:30 +0100
Re: Alternative to NetworkManager on Debian 12 Joe <joe@jretrading.com> - 2023-11-01 13:20 +0100
Making resolv.conf immutable [was: Bookworm: NetworkManager] <tomas@tuxteam.de> - 2023-10-22 07:20 +0200
Re: Bookworm: NetworkManager Felix Miata <mrmazda@earthlink.net> - 2023-10-21 20:00 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:20 +0200
Re: Bookworm: NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-21 20:40 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:50 +0200
Re: Bookworm: NetworkManager Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-10-21 21:00 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 21:20 +0200
Re: Bookworm: NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-21 21:10 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 21:40 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 21:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 22:00 +0200
Re: Bookworm: NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-21 23:40 +0200
Re: Bookworm: NetworkManager <tomas@tuxteam.de> - 2023-10-22 07:30 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:40 +0200
Re: Bookworm: NetworkManager Charles Curley <charlescurley@charlescurley.com> - 2023-10-21 22:50 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 23:00 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 23:20 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 23:20 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 13:20 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:30 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-22 17:20 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-22 19:00 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager John Hasler <john@sugarbit.com> - 2023-10-22 20:20 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 20:40 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 00:10 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager John Hasler <john@sugarbit.com> - 2023-10-23 00:50 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 02:40 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-23 02:50 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager John Hasler <john@sugarbit.com> - 2023-10-23 04:40 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-23 05:10 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-23 09:20 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 17:20 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 18:00 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 04:40 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-23 22:40 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-24 02:00 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 20:40 +0200
Re: Domain name to use on home networks; was: Bookworm: NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-22 21:10 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-22 23:50 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager ghe2001 <ghe2001@protonmail.com> - 2023-10-23 02:00 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-23 07:40 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Christian Groessler <chris@groessler.org> - 2023-10-23 12:40 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-25 03:50 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager ghe2001 <ghe2001@protonmail.com> - 2023-10-25 05:50 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager "Marco M." <mm@dorfdsl.de> - 2023-10-25 07:40 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-25 11:10 +0200
Re: Domain name to use on home networks Joe <joe@jretrading.com> - 2023-10-25 13:20 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-25 14:20 +0200
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-25 16:50 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-25 13:30 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-25 14:20 +0200
Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-25 18:30 +0200
Re: Domain name to use on home networks Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-26 03:30 +0200
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-26 03:50 +0200
Re: Domain name to use on home networks Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-26 04:50 +0200
Re: Domain name to use on home networks David Wright <deblis@lionunicorn.co.uk> - 2023-10-27 05:20 +0200
Re: Domain name to use on home networks Stefan Monnier <monnier@iro.umontreal.ca> - 2023-10-27 06:50 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 12:10 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 13:20 +0200
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 13:30 +0200
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 14:00 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 15:10 +0200
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 15:40 +0200
Re: Domain name to use on home networks "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-27 16:10 +0200
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-27 16:20 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 17:50 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 16:30 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:10 +0200
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-29 17:30 +0100
Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-29 19:30 +0100
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-30 03:30 +0100
Re: Changing host name and domain name on Debian; was: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 16:20 +0200
Re: Changing host name and domain name on Debian; was: Domain nameto use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:10 +0200
Re: Changing host name and domain name on Debian; was: Domain nameto use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-29 17:10 +0100
Re: Changing host name and domain name on Debian; was: Domain nametouse on home networks gene heskett <gheskett@shentel.net> - 2023-10-29 18:10 +0100
Re: Changing host name and domain name on Debian; was: Domain nametouse on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-31 04:20 +0100
Re: Changing host name and domain name on Debian; was: Domain nametouse on home networks The Wanderer <wanderer@fastmail.fm> - 2023-10-31 10:20 +0100
Re: Changing host name and domain name on Debian; was: Domain nametouseon home networks gene heskett <gheskett@shentel.net> - 2023-10-31 15:30 +0100
Re: Changing host name and domain name on Debian; was: Domainnametouse on home networks gene heskett <gheskett@shentel.net> - 2023-10-31 15:30 +0100
Re: Changing host name and domain name on Debian; was: Domainnametouse on home networks John Hasler <john@sugarbit.com> - 2023-10-31 17:40 +0100
Re: Changing host name and domain name on Debian; was: Domainnametouse on home networks Felix Miata <mrmazda@earthlink.net> - 2023-11-01 22:10 +0100
Re: Changing host name and domain name on Debian; was:Domainnametouse on home networks gene heskett <gheskett@shentel.net> - 2023-11-02 00:30 +0100
Re: Changing host name and domain name on Debian; was:Domainnametouse on home networks Greg Wooledge <greg@wooledge.org> - 2023-11-02 00:40 +0100
Re: Changing host name and domain name on Debian;was:Domainnametouse on home networks gene heskett <gheskett@shentel.net> - 2023-11-02 01:20 +0100
Re: Changing host name and domain name on Debian;was:Domainnametouse on home networks Greg Wooledge <greg@wooledge.org> - 2023-11-02 01:40 +0100
Re: Changing host name and domain name on Debian;was:Domainnametouse on home networks Jeffrey Walton <noloader@gmail.com> - 2023-11-02 02:20 +0100
Re: Changing host name and domain name on Debian; was:Domainnametouse on home networks John Hasler <john@sugarbit.com> - 2023-11-02 00:40 +0100
Re: report a Debian bug (was: Changing host name and dom...) Felix Miata <mrmazda@earthlink.net> - 2023-11-02 01:00 +0100
Re: report a Debian bug gene heskett <gheskett@shentel.net> - 2023-11-02 02:40 +0100
Re: report a Debian bug David Christensen <dpchrist@holgerdanske.com> - 2023-11-02 06:50 +0100
Re: report a Debian bug gene heskett <gheskett@shentel.net> - 2023-11-02 09:10 +0100
Re: report a Debian bug David Christensen <dpchrist@holgerdanske.com> - 2023-11-02 22:20 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 17:30 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 17:50 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:40 +0200
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 18:50 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 19:10 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 19:20 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 14:00 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 17:20 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 17:50 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:30 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:50 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 19:30 +0200
Re: Domain name to use on home networks David Wright <deblis@lionunicorn.co.uk> - 2023-10-29 15:30 +0100
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-29 16:30 +0100
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-29 17:00 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-29 17:30 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-29 18:10 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-29 19:20 +0100
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-29 19:40 +0100
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-30 03:20 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 09:00 +0100
Re: Domain name to use on home networks Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-10-30 10:20 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:10 +0100
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-30 17:20 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 17:50 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:30 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 18:40 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 17:50 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:10 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 18:30 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:40 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 18:30 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 18:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:50 +0100
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-30 18:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 19:40 +0100
Re: Domain name to use on home networks "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-30 19:40 +0100
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-30 19:50 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 22:10 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 22:40 +0100
Re: Domain name to use on home networks Charles Curley <charlescurley@charlescurley.com> - 2023-10-31 02:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-31 15:10 +0100
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-31 04:10 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 19:50 +0100
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-31 04:00 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 13:20 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 13:30 +0100
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-30 13:30 +0100
Re: Domain name to use on home networks Pocket <pocket@columbus.rr.com> - 2023-10-30 13:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:20 +0100
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-30 16:00 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-30 17:40 +0100
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 16:40 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-27 16:50 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:10 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-27 21:30 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 16:50 +0200
Re: Domain name to use on home networks gene heskett <gheskett@shentel.net> - 2023-10-27 18:20 +0200
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 18:30 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 19:20 +0200
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 20:00 +0200
Re: Domain name to use on home networks Greg Wooledge <greg@wooledge.org> - 2023-10-27 20:10 +0200
Re: Domain name to use on home networks John Hasler <john@sugarbit.com> - 2023-10-27 21:00 +0200
Re: Domain name to use on home networks The Wanderer <wanderer@fastmail.fm> - 2023-10-27 21:10 +0200
Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-28 00:50 +0200
Re: Domain name to use on home networks Max Nikulin <manikulin@gmail.com> - 2023-10-28 07:40 +0200
Re: Domain name to use on home networks David Wright <deblis@lionunicorn.co.uk> - 2023-10-27 16:40 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-26 10:20 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-26 10:40 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-26 11:20 +0200
Re: Domain name to use on home networks Jeffrey Walton <noloader@gmail.com> - 2023-10-26 11:10 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-26 11:20 +0200
Re: Domain name to use on home networks Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-27 17:30 +0200
Re: Domain name to use on home networks "Marco M." <mm@dorfdsl.de> - 2023-10-26 10:30 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Jeffrey Walton <noloader@gmail.com> - 2023-10-25 22:10 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-26 01:30 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager jeremy ardley <jeremy.ardley@gmail.com> - 2023-10-26 02:00 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Dan Purgert <dan@djph.net> - 2023-10-26 02:20 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager David Wright <deblis@lionunicorn.co.uk> - 2023-10-27 05:30 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager ghe2001 <ghe2001@protonmail.com> - 2023-10-23 18:00 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-23 04:50 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 18:20 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-23 20:10 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-23 20:30 +0200
Re: Domain name to use on home networks; was: Bookworm:NetworkManager gene heskett <gheskett@shentel.net> - 2023-10-23 23:40 +0200
Re: Bookworm: NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 14:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 14:50 +0200
Re: example.org and other RFC 2606 domains; was: Bookworm: NetworkManager Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-10-22 15:20 +0200
Re: Bookworm: NetworkManager Dan Ritter <dsr@randomstring.org> - 2023-10-22 17:00 +0200
Re: Bookworm: NetworkManager Tixy <tixy@yxit.co.uk> - 2023-10-22 18:20 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:50 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-21 20:40 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 20:50 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-21 22:30 +0200
Re: Bookworm: NetworkManager "Andrew M.A. Cater" <amacater@einval.com> - 2023-10-21 22:40 +0200
Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-22 17:30 +0200
Re: Bookworm: NetworkManager <tomas@tuxteam.de> - 2023-10-22 17:30 +0200
Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-22 17:50 +0200
Re: Bookworm: NetworkManager Max Nikulin <manikulin@gmail.com> - 2023-10-25 19:00 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:40 +0200
Re: Bookworm: NetworkManager Greg Wooledge <greg@wooledge.org> - 2023-10-22 19:20 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 19:50 +0200
Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-23 00:40 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-23 01:20 +0200
Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-23 19:10 +0200
Re: Bookworm: NetworkManager Andy Smith <andy@strugglers.net> - 2023-10-23 22:30 +0200
Re: Bookworm: NetworkManager Lee <ler762@gmail.com> - 2023-10-27 21:40 +0200
Re: Bookworm: NetworkManager Pocket <pocket@columbus.rr.com> - 2023-10-22 02:30 +0200
Page 5 of 13 — ← Prev page 1 … 3 4 [5] 6 7 … 13 Next page →
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-24 02:00 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HscZX-ogz-5@gated-at.bofh.it> |
| In reply to | #262631 |
On 10/23/23 16:35, Andy Smith wrote: > Hello, > > On Sun, Oct 22, 2023 at 10:33:47PM -0400, gene heskett wrote: >> On 10/22/23 20:48, Greg Wooledge wrote: >>> Any issues you've encountered have been the result of misconfiguration. >>> You have repeatedly shown errors in your config files, and once those >>> have been corrected, everything has worked as expected. >> >> This is generally true, Greg, and I get that, but every new version, which >> should just continue what works, doesn't cuz somebody moved a config file > > I'm afraid that *you* are the person who has moved or broken your > config files with relation to name resolution in every case you've > ever described here. All of it has been user error. You've never yet > shown an example of any change designed to make hosts files work > less well (or not at all). That is just a belief you have and > continue to state as if it's fact, but at no time has it stood up to > scrutiny. > Then perhaps you can explain to me, why Ican fillout the data tonget online with a netinstall installer, download and instal 6 or 8 Gn of stuff, and when it is time to reboot the new snstall, it comes back up with a default route in the 169 block, locking me out of net access until I rm by brute root force any and everything to do with avahi for starters? At that point I'm locked out of net access even to the other still working machines on my home net. Explain to me how I've just pulled close to 8 GB in from the net, but the totally bogus avahi 169 address is the default route when its been thru the first reboot. Go ahead, But I'm listening for factual info, not the above innuendo and false accusations I did something wrong. I'm not doing anything the installer didn't ask me to do. 22 times before someone told me to unplug my weeping willow tree of usb stuff in order to get an install w/o orca and brltty which it installed and activated w/o asking me if I wanted it just because it was finding 2 usb-serial adapter's and assumed I was blind. Once that stuff is enabled and you rm it to get some peace and quiet, it won't reboot as it waits forever to bring them back up. So when I needed to reboot the only way to reboot was to reinstall. And I'm been catching hell ever since just because I wanted a working system, which even now I don't have. My /home is a raid10, but anything that wants to write to it, has to wait anywhere from 30 seconds to 5 minutes before the file requestor asking where to put this incoming file opens. Its /my/ raid, I own it all, why and what is getting in the way? A question I have asked several times without even the courtesy of a reply. A recent kernel update seemed to speed that up some, the wait is now a much more consistent 30 seconds but it is still there for the first access and now instant after that initial wait. Am I the only one on the planet using a quad of 1T Samsung 870 SSD's for a raid10 /home? > Those reading this later need to believe Greg's statements and not > Gene's. Thanks for the no confidence vote Andy but I'l stand by what I wrote. It has all happened to /me/. > Thanks, > Andy > Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2023-10-22 20:40 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm: NetworkManager |
| Message-ID | <HrLwJ-6xU-3@gated-at.bofh.it> |
| In reply to | #262542 |
gene heskett wrote: > On 10/22/23 11:19, Jeffrey Walton wrote: > > On Sun, Oct 22, 2023 at 7:13 AM Michael Kjörling <2695bd53d63c@ewoof.net> wrote: > > > > https://www.rfc-editor.org/info/rfc8375 > > > Chuckle. Looks like a solution looking for a problem. You can use whatever > domainname that tickles your fancy when your net is in an un-routeable > address block. Sure. Right up until the day that someone registers it on the Net at large. As of March 2021, the IANA root database includes 1589 TLDs. "den" is not currently one of them, but that could change at any point, and then there would be a high likelihood of "coyote.den" being registered by someone else. You might not have a specific problem with that, depending on how you do local DNS, and depending on what you want. But it's safer to either use a recognized internal domain (home.arpa, for instance) or a domain that you own, either with split views or unpublished internal subdomains (internal.randomstring.org, for example). -dsr-
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-10-22 21:10 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm: NetworkManager |
| Message-ID | <HrLZL-6XX-1@gated-at.bofh.it> |
| In reply to | #262560 |
On Sun, Oct 22, 2023 at 2:33 PM Dan Ritter <dsr@randomstring.org> wrote: > > gene heskett wrote: > > On 10/22/23 11:19, Jeffrey Walton wrote: > > > On Sun, Oct 22, 2023 at 7:13 AM Michael Kjörling <2695bd53d63c@ewoof.net> wrote: > > > > > > https://www.rfc-editor.org/info/rfc8375 > > > > > Chuckle. Looks like a solution looking for a problem. You can use whatever > > domainname that tickles your fancy when your net is in an un-routeable > > address block. > > > Sure. Right up until the day that someone registers it on the > Net at large. > > As of March 2021, the IANA root database includes 1589 TLDs. > "den" is not currently one of them, but that could change at any > point, and then there would be a high likelihood of "coyote.den" > being registered by someone else. > > You might not have a specific problem with that, depending on > how you do local DNS, and depending on what you want. But it's > safer to either use a recognized internal domain (home.arpa, for > instance) or a domain that you own, either with split views or > unpublished internal subdomains (internal.randomstring.org, for > example). +1. I've been using home.pvt and home.dmz since the late 1990s. I've been waiting for it to break since vanity domains/brand tlds are a thing now. <https://icannwiki.org/Brand_TLD>. Jeff
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-22 23:50 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HrOuB-8kK-3@gated-at.bofh.it> |
| In reply to | #262560 |
On 10/22/23 14:17, Dan Ritter wrote: > gene heskett wrote: >> On 10/22/23 11:19, Jeffrey Walton wrote: >>> On Sun, Oct 22, 2023 at 7:13 AM Michael Kjörling <2695bd53d63c@ewoof.net> wrote: >> >>>> https://www.rfc-editor.org/info/rfc8375 >>> >> Chuckle. Looks like a solution looking for a problem. You can use whatever >> domainname that tickles your fancy when your net is in an un-routeable >> address block. > > > Sure. Right up until the day that someone registers it on the > Net at large. > > As of March 2021, the IANA root database includes 1589 TLDs. > "den" is not currently one of them, but that could change at any > point, and then there would be a high likelihood of "coyote.den" > being registered by someone else. > > You might not have a specific problem with that, depending on > how you do local DNS, and depending on what you want. But it's > safer to either use a recognized internal domain (home.arpa, for > instance) or a domain that you own, either with split views or > unpublished internal subdomains (internal.randomstring.org, for > example). As I keep repeating Dan, there is not a local dns, its all a 15 entry hosts file atm. So that cannot bite /me/. Now If I should make a typu, fat fingering & miss-spelling an alias, I suppose that might resolve to someplace in the neighorhood of a yurt near Ulan Bator and they might not appreciate my trying to login in English. Until then I'm not inclined to lose much sleep over it. If it ever happens, its adjustable in any event. It will all die when this stuff gets turned off by the cleanup crew after I miss roll call. There's about 6 years left in the pacemaker battery and the average life of a TAVR heart valve is another 8 or so years. By then I will be 95 and might be napping in my morning cereal. Higher Powers have missed several chances to claim me, but they'd look ar the book and send me down, I'd fix the stoker, rewind the generators and open an air conditioned bar and neither of them could tolerate that. In the meantime ;o)> > > -dsr- > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | ghe2001 <ghe2001@protonmail.com> |
|---|---|
| Date | 2023-10-23 02:00 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HrQwp-9xU-1@gated-at.bofh.it> |
| In reply to | #262566 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 How about a /29 or so, named "here.<your initials>", hosts named 2 or 3 letter abbreviations of what you call the computers, with unroutable IPs, DNS'ed in /etc/hosts (with shortcuts). Works here... -- Glenn English -----BEGIN PGP SIGNATURE----- Version: ProtonMail wsBzBAEBCAAnBYJlNbcbCZCf14YxgqyMMhYhBCyicw9CUnAlY0ANl5/XhjGC rIwyAAC+WwgAuYZg79YPdVcffLcsYAKN5NVK4rl+q0NB1Bnmk8IyvuQ2AHo2 +zzA2C1wRb0266xJKVvBt+T/e4VxE6NVJbPb22UjYkVoFFoK8qDi73V0uhdm m7W+kNDSFsLMFmuzRqVipPQAHqSDml28DhwIAEzPI+9OWVGfQSzmayEl4XGK lca9+j3Dj/7Lu4vLCvuG8Aowhw4M5Xq7qtbj7JXe30fQ3I25c9DTu9Zd5FT4 VbfLMJHhCeeRakGzRcxRFEq8+BQAc9l/3Jip9rteYwzb03atoqSXHIcG6YQJ VqZofzElWCFZ//ahPa4vR8A51wmdf2mFVYyc13101u1BkSGCWEWFSQ== =VonO -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-10-23 07:40 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HrVPs-d4R-5@gated-at.bofh.it> |
| In reply to | #262572 |
On Mon, Oct 23, 2023 at 1:24 AM ghe2001 <ghe2001@protonmail.com> wrote: > > How about a /29 or so, named "here.<your initials>", hosts named 2 or 3 letter abbreviations of what you call the computers, with unroutable IPs, DNS'ed in /etc/hosts (with shortcuts). Whatever you come up with for <your initials>, ICANN can add to the gTLD namespace; see <https://icannwiki.org/Brand_TLD>. The DNS queries for fii.xy (a typo) will escape your homenet when you meant to type foo.xy (the target). Jeff
[toc] | [prev] | [next] | [standalone]
| From | Christian Groessler <chris@groessler.org> |
|---|---|
| Date | 2023-10-23 12:40 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <Hs0vL-fYM-7@gated-at.bofh.it> |
| In reply to | #262586 |
On 10/23/23 07:29, Jeffrey Walton wrote: > On Mon, Oct 23, 2023 at 1:24 AM ghe2001 <ghe2001@protonmail.com> wrote: >> >> How about a /29 or so, named "here.<your initials>", hosts named 2 or 3 letter abbreviations of what you call the computers, with unroutable IPs, DNS'ed in /etc/hosts (with shortcuts). > > Whatever you come up with for <your initials>, ICANN can add to the > gTLD namespace; see <https://icannwiki.org/Brand_TLD>. Just register a daomain and use that. regards, chris
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2023-10-25 03:50 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HsBbX-DSl-3@gated-at.bofh.it> |
| In reply to | #262591 |
On Mon 23 Oct 2023 at 12:06:05 (+0200), Christian Groessler wrote:
> On 10/23/23 07:29, Jeffrey Walton wrote:
> > On Mon, Oct 23, 2023 at 1:24 AM ghe2001 <ghe2001@protonmail.com> wrote:
> > >
> > > How about a /29 or so, named "here.<your initials>", hosts named 2 or 3 letter abbreviations of what you call the computers, with unroutable IPs, DNS'ed in /etc/hosts (with shortcuts).
> >
> > Whatever you come up with for <your initials>, ICANN can add to the
> > gTLD namespace; see <https://icannwiki.org/Brand_TLD>.
>
> Just register a daomain and use that.
That costs money, and I can't see the point when there are TLDs
that are perfectly safe already available, like .home.arpa, and
before that, .{corp,home,mail}.
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | ghe2001 <ghe2001@protonmail.com> |
|---|---|
| Date | 2023-10-25 05:50 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HsD45-F9F-1@gated-at.bofh.it> |
| In reply to | #262690 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
------- Original Message -------
On Tuesday, October 24th, 2023 at 7:47 PM, David Wright <deblis@lionunicorn.co.uk> wrote:
> On Mon 23 Oct 2023 at 12:06:05 (+0200), Christian Groessler wrote:
>
> > On 10/23/23 07:29, Jeffrey Walton wrote:
> >
> > Just register a daomain and use that.
>
>
> That costs money,
It's probably slower than the Ethernet cable (or modern WiFi) to the next room, too.
> and I can't see the point when there are TLDs
> that are perfectly safe already available, like .home.arpa, and
> before that, .{corp,home,mail}.
TLD '.lan' works. As best I can tell on the web, it doesn't exist.
--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
wsBzBAEBCAAnBYJlOI4jCZCf14YxgqyMMhYhBCyicw9CUnAlY0ANl5/XhjGC
rIwyAAA4aQgAg3ynKpks+IHyX+b6F6NVclPhRTQp6Pudv5Z88EyhnKtphx54
Mcp7uYIQE+ibwLo00qKKfGkrvhfUk16ClRLfB9yN1iGzhBEgL1FS5bsKYaaU
9klf/51ks+sECp5blLvBFERhfUrVg0yOKANr4t0nep6aRWYsqikk79SfQRMP
6walXOtoG+FOdSfLzV1SIlZzULCXk1BmH1ouoABRv7KkLRjYK4Yi5fsjhRdz
r4tTTXAP4MvF3bJs5odxf99uk9o94uUO5P3fKDSDGsjPZN3RULmieRkqAX4o
2VR/dICquHTWjaSVwOtq0rgNkppBzC9SgFPb3AaTPpwMvb1suEA0Rw==
=xpps
-----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | "Marco M." <mm@dorfdsl.de> |
|---|---|
| Date | 2023-10-25 07:40 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HsEMx-GmD-1@gated-at.bofh.it> |
| In reply to | #262695 |
Am 25.10.2023 um 03:40:46 Uhr schrieb ghe2001: > TLD '.lan' works. As best I can tell on the web, it doesn't exist. Is it intended for that? No? Then don't use it. It can be used in the future for public domains.
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-25 11:10 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HsI3L-IMP-1@gated-at.bofh.it> |
| In reply to | #262700 |
On 25 Oct 2023 07:32 +0200, from mm@dorfdsl.de (Marco M.): >> TLD '.lan' works. As best I can tell on the web, it doesn't exist. > > Is it intended for that? > No? > Then don't use it. It can be used in the future for public domains. Exactly. I see lots of people in this sub-thread arguing for cobbled-together, "it works for me for now and if it breaks I'll just fix it later" style solutions. "home.arpa" is _reserved specifically_ for almost exactly the purpose we're talking about: local (for example residential) use where one does not want to pay for a domain name and/or does not need globally unique names. If you have anyway, or are willing to pay for, a domain name that you can use for the purpose, great; all that power to you. But most home users aren't in that situation. For those people, "home.arpa" is _the official_ answer. It's not something I've made up. There's an RFC, there's a corresponding domain name reservation, it's specifically set up so that it won't break for example DNSSEC, and that RFC is a _PROPOSED STANDARD_ which is pretty much as officially sanctioned as things get on the public Internet. (I think IPv4 has the status of STANDARD.) Just like you shouldn't pick some IP address range at random for your LAN if you want hosts on that LAN to be able to communicate unimpeded with hosts on the Internet, you shouldn't randomly pick a domain name. Using a domain name (or IP address range) which is reserved for examples and documentation likely won't break anything important, but it _will_ cause confusion (as evidenced earlier in this thread). If you go with the domain name home.arpa and an IPv4 subnet sliced out of one of 192.168.0.0/16, 172.12.0.0/12 or 10.0.0.0/8, you can be _almost certain_ that nothing will break because of those choices, now _or_ in the future. None of the other alternatives I've seen proposed in this thread can offer anything like such guarantees. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2023-10-25 13:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HsK5z-K0b-1@gated-at.bofh.it> |
| In reply to | #262711 |
On Wed, 25 Oct 2023 09:01:18 +0000 Michael Kjörling <2695bd53d63c@ewoof.net> wrote: > > I see lots of people in this sub-thread arguing for cobbled-together, > "it works for me for now and if it breaks I'll just fix it later" > style solutions. > > Not arguing about anything else, but this situation you describe is how IT works, and will continue to work until it stabilises, maybe a century from now. I have web pages on my home intranet written anything up to twenty years ago. The versions of HTML, PHP, Perl etc that I used in many of them are long obsolete. To do things right, I ought to go over that code line by line every year or two, checking current documentation to see what's deprecated, find out how to workaround it and fix it. Life's too short. So when I use a page I haven't used for years, there's a good chance it won't work, and I'll have to fix it then. So be it. Scale that up, and it's how the whole of IT works. Inevitably, things will break, hardware and software won't work on new operating systems, and so on. We have to live with it. Yes, it's nice to do things exactly correctly, but they are only exactly correct today. Tomorrow, they may be deprecated, and eventually removed. The exact situation you address may be set in stone for all time. Or it may not: it can be changed on a whim. All we can do is make the best choice at the time, and even then we have to guess at how much time we need to spend researching it in order to have a better choice than we can see now, and whether it's worth doing that when we don't even know that there is a better choice possible. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | "Marco M." <mm@dorfdsl.de> |
|---|---|
| Date | 2023-10-25 14:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HsL1D-KGh-7@gated-at.bofh.it> |
| In reply to | #262712 |
Am 25.10.2023 um 12:17:40 Uhr schrieb Joe: > On Wed, 25 Oct 2023 09:01:18 +0000 > Michael Kjörling <2695bd53d63c@ewoof.net> wrote: > > > > > > I see lots of people in this sub-thread arguing for > > cobbled-together, "it works for me for now and if it breaks I'll > > just fix it later" style solutions. > > > > > > Not arguing about anything else, but this situation you describe is > how IT works, and will continue to work until it stabilises, maybe a > century from now. Avoiding mistakes by using it as designed is much better than repairing it years later.
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-25 16:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HsNmO-Mb8-9@gated-at.bofh.it> |
| In reply to | #262717 |
Sent from my iPad > On Oct 25, 2023, at 8:12 AM, Marco M. <mm@dorfdsl.de> wrote: > > Am 25.10.2023 um 12:17:40 Uhr schrieb Joe: > >>> On Wed, 25 Oct 2023 09:01:18 +0000 >>> Michael Kjörling <2695bd53d63c@ewoof.net> wrote: >>> >>> >>> >>> I see lots of people in this sub-thread arguing for >>> cobbled-together, "it works for me for now and if it breaks I'll >>> just fix it later" style solutions. >>> >>> >> >> Not arguing about anything else, but this situation you describe is >> how IT works, and will continue to work until it stabilises, maybe a >> century from now. > > Avoiding mistakes by using it as designed is much better than repairing > it years later. > Amen
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-25 13:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HsKff-K4Q-3@gated-at.bofh.it> |
| In reply to | #262711 |
On 10/25/23 05:01, Michael Kjörling wrote: > On 25 Oct 2023 07:32 +0200, from mm@dorfdsl.de (Marco M.): >>> TLD '.lan' works. As best I can tell on the web, it doesn't exist. >> >> Is it intended for that? >> No? >> Then don't use it. It can be used in the future for public domains. > > Exactly. > > I see lots of people in this sub-thread arguing for cobbled-together, > "it works for me for now and if it breaks I'll just fix it later" > style solutions. > > "home.arpa" is _reserved specifically_ for almost exactly the purpose > we're talking about: local (for example residential) use where one > does not want to pay for a domain name and/or does not need globally > unique names. > > If you have anyway, or are willing to pay for, a domain name that you > can use for the purpose, great; all that power to you. > > But most home users aren't in that situation. For those people, > "home.arpa" is _the official_ answer. It's not something I've made up. > There's an RFC, there's a corresponding domain name reservation, it's > specifically set up so that it won't break for example DNSSEC, and > that RFC is a _PROPOSED STANDARD_ which is pretty much as officially > sanctioned as things get on the public Internet. (I think IPv4 has the > status of STANDARD.) > > Just like you shouldn't pick some IP address range at random for your > LAN if you want hosts on that LAN to be able to communicate unimpeded > with hosts on the Internet, you shouldn't randomly pick a domain name. > Using a domain name (or IP address range) which is reserved for > examples and documentation likely won't break anything important, but > it _will_ cause confusion (as evidenced earlier in this thread). > > If you go with the domain name home.arpa and an IPv4 subnet sliced out > of one of 192.168.0.0/16, 172.12.0.0/12 or 10.0.0.0/8, you can be > _almost certain_ that nothing will break because of those choices, now > _or_ in the future. > This thread is the first I've heard of home.arpa as a domainname for internal lan's. It s/b easy enough to switch my local lan to that since only the domainname changes. The alias shouldn't need changed. Is there an RFC number for this already? > None of the other alternatives I've seen proposed in this thread can > offer anything like such guarantees. Thank you for this clarificaion. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | "Marco M." <mm@dorfdsl.de> |
|---|---|
| Date | 2023-10-25 14:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HsL1D-KGh-9@gated-at.bofh.it> |
| In reply to | #262713 |
Am 25.10.2023 um 07:25:45 Uhr schrieb gene heskett: > Is there an RFC number for this already? ftp://ftp.rfc-editor.org/in-notes/rfc8375.html
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-10-25 18:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HsOVz-Nds-1@gated-at.bofh.it> |
| In reply to | #262718 |
On Wed, Oct 25, 2023 at 8:14 AM Marco M. <mm@dorfdsl.de> wrote: > > Am 25.10.2023 um 07:25:45 Uhr schrieb gene heskett: > > > Is there an RFC number for this already? > > ftp://ftp.rfc-editor.org/in-notes/rfc8375.html This is so interesting (to me). I can't believe I missed that RFC... >From the Abstract: This document specifies the behavior that is expected from the Domain Name System with regard to DNS queries for names ending with '.home.arpa.' and designates this domain as a special-use domain name. 'home.arpa.' is designated for non-unique use in residential home networks. The Home Networking Control Protocol (HNCP) is updated to use the 'home.arpa.' domain instead of '.home'. Notice '.home.arpa.' is a fully qualified domain name (FQDN). FQDN's end in dot, and the dot denotes the top of the DNS tree. 'home' is not a FQDN. It is not a node from the top of the DNS tree. It is just a special label. One of my pet peeves is when someone conflates a hostname with a FQDN. Systemd does this all the time. Systemd's [unofficial] policy seems to be mDNS and its gossip is the source of truth for network names. Old admins will always consider DNS as the single source of truth for network names, not gossip-based protocols. Systemd networking probably has W Richard Stevens rolling over in his grave... Jeff
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2023-10-26 03:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HsXma-Spu-13@gated-at.bofh.it> |
| In reply to | #262711 |
> If you go with the domain name home.arpa and an IPv4 subnet sliced out
> of one of 192.168.0.0/16, 172.12.0.0/12 or 10.0.0.0/8, you can be
> _almost certain_ that nothing will break because of those choices, now
> _or_ in the future.
100% agreement.
It's just such a shame that they chose a name which refers to "arpa" in
it, which is not only US-centric but even belongs to the US's war
department, which I find rather unpalatable.
I understand ARPA was closely related to the beginnings of the Internet,
but... couldn't they choose something a bit more neutral?
Stefan
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-10-26 03:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HsXFv-Svu-1@gated-at.bofh.it> |
| In reply to | #262733 |
Stefan writes: > It's just such a shame that they chose a name which refers to "arpa" > in it, which is not only US-centric but even belongs to the US's war > department It belongs to the Internet Architecture Board and is administered by IANA which is why they chose it. It stands for "Address and Routing Parameter Area” <https://www.iana.org/domains/arpa>. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2023-10-26 04:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HsYBz-T94-1@gated-at.bofh.it> |
| In reply to | #262734 |
>> It's just such a shame that they chose a name which refers to "arpa"
>> in it, which is not only US-centric but even belongs to the US's war
>> department
>
> It belongs to the Internet Architecture Board and is administered by
> IANA which is why they chose it. It stands for "Address and Routing
> Parameter Area” <https://www.iana.org/domains/arpa>.
But that's a "backronym".
It originally referred to the US agency.
I totally understand the technical reasons why they decided to stick to
this naming, but it's still grating.
Stefan
[toc] | [prev] | [next] | [standalone]
Page 5 of 13 — ← Prev page 1 … 3 4 [5] 6 7 … 13 Next page →
Back to top | Article view | linux.debian.user
csiph-web