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 11 of 13 — ← Prev page 1 … 9 10 [11] 12 13 Next page →
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-10-27 21:00 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtAdP-1hpK-3@gated-at.bofh.it> |
| In reply to | #262813 |
I wrote: > The NIS stuff should be evicted from the hostname man page. Greg writes: > Well... maybe? While the use of NIS hostname resolution is strongly > discouraged, it's not *forbidden*. A system admin might, in theory, > be using NIS to serve up hostname/IP mappings, in which case the NIS > commands and references might be needed. Evicted to a page of their own. I realize that it won't happen. > The part of hostname(1) that struck me as needing amendment was this: > The host name is usually set once at system startup in > /etc/init.d/hostname.sh (normally by reading the contents of a file > which contains the host name, e.g. /etc/hostname). > My Debian 12 system does not have an /etc/init.d/hostname.sh file, > or anything else that's close to it. My desktop, which has been upgraded many times, does have /etc/init.d/hostname.sh. However, a recently installed Bookworm does not. > Whatever's reading /etc/hostname comes from another location. systemd-hostnamed -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2023-10-27 21:10 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtAnw-1hIl-11@gated-at.bofh.it> |
| In reply to | #262817 |
[Multipart message — attachments visible in raw view] — view raw
On 2023-10-27 at 14:57, John Hasler wrote: > I wrote: > Greg writes: >> My Debian 12 system does not have an /etc/init.d/hostname.sh file, >> or anything else that's close to it. > > My desktop, which has been upgraded many times, does have > /etc/init.d/hostname.sh. However, a recently installed Bookworm does > not. Mine does: $ dlocate /etc/init.d/hostname.sh initscripts: /etc/init.d/hostname.sh $ apt-file search /etc/init.d/hostname.sh initscripts: /etc/init.d/hostname.sh At least in current testing+stable, it's contained exclusively in the 'initscripts' package. My guess is that a machine running systemd will not include that package, and therefore will not have this script. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-10-28 00:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtDOq-1jNn-7@gated-at.bofh.it> |
| In reply to | #262813 |
On Fri, Oct 27, 2023 at 2:04 PM Greg Wooledge <greg@wooledge.org> wrote: > > On Fri, Oct 27, 2023 at 12:53:40PM -0500, John Hasler wrote: > > The NIS stuff should be evicted from the hostname man page. > > Well... maybe? While the use of NIS hostname resolution is strongly > discouraged, it's not *forbidden*. A system admin might, in theory, > be using NIS to serve up hostname/IP mappings, in which case the NIS > commands and references might be needed. > > The part of hostname(1) that struck me as needing amendment was this: > > The host name is usually set once at system startup in > /etc/init.d/hostname.sh (normally by reading the contents of a file > which contains the host name, e.g. /etc/hostname). > > My Debian 12 system does not have an /etc/init.d/hostname.sh file, > or anything else that's close to it. > > unicorn:/etc/init.d$ grep hostname * > unicorn:/etc/init.d$ > > Whatever's reading /etc/hostname comes from another location. That could be Systemd. They used to recommend changing /etc/hostname directly: <https://systemd-devel.freedesktop.narkive.com/W2bL081i/how-do-you-set-the-machine-s-domain-name-with-systemd>. > In any case, this is clearly a man page *not* written by Debian, so > getting changes made to it is going to be like pulling teeth. Don't even > bother submitting Debian bug reports against upstream man pages, in > my experience. You can try your luck with upstream projects, but even > then it's really unlikely you'll ever get a documentation patch accepted. Yeah, just file a bug and let whomever else deal with it. Whatever text is proposed, it will be rejected in favor of what the person with check-in privileges wants. Or worse, the person with check-in privileges will torture the submitter with an endless stream of minute changes, as if the submitter is a personal secretary, in an effort "teach" the submitter for his/her benefit of expected volumes of future patches. Jeff
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-28 07:40 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtKdc-1nHE-3@gated-at.bofh.it> |
| In reply to | #262827 |
On 28/10/2023 05:48, Jeffrey Walton wrote: > > Yeah, just file a bug and let whomever else deal with it. Whatever > text is proposed, it will be rejected in favor of what the person with > check-in privileges wants. > > Or worse, the person with check-in privileges will torture the > submitter with an endless stream of minute changes, as if the > submitter is a personal secretary, in an effort "teach" the submitter > for his/her benefit of expected volumes of future patches. Be a bit more patient. A person may be busy with other tasks including patches from other people and has no time to explain why a suggested change may be confusing as well. They may be trying to preserve your authorship in git history. They may be unsure concerning proper wording and testing if alternatives may be interpreted incorrectly. It might help to express expectations explicitly. Finally it is reality that not all proposed patches are applied even if you invest your time preparing them.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2023-10-27 16:40 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htwad-1f4f-5@gated-at.bofh.it> |
| In reply to | #262773 |
On Fri 27 Oct 2023 at 07:12:48 (-0400), gene heskett wrote: > On 10/27/23 00:47, Stefan Monnier wrote: > > > I would have thought that techies understand its origins, and > > > non-techies are fairly unlikely ever to encounter it. > > > > That's the thing: if you use `home.arpa` for your home network, suddenly > > it's exposed to non-techies, like your friends and family, contrary to > > things like `in-addr.arpa`. You'll have to remind me where it is that your non-techie friends and family would see your domain name. As I start to compose this email, the only occurrence on the screen is in the quote above, and that goes for the other 19 virtual desktops (fvwm-parlance) as well. It's not as if you actually need a domain name—a non-techie home network will run perfectly well without one. > I tried to change just this machine to see how its done, and managed > to get all the right answers, which did not affect my local network > since I generally use the alias name for an ssh or sshfs login, but on > a reboot its all gone. So how the heck do we do that so it survives a > reboot? My domain name is corp, chosen to make the next step easier. # grep -r '\<corp\>' /etc/ |& less will show the configured occurrences. (Run this as a user and the & will show what missed being searched.) Here, the files hit are: /etc/hosts, /etc/aliases, /etc/mailname, /etc/exim4/update-exim4.conf.conf and /etc/exim4/hubbed_hosts. The last one is for my intra-LAN emails in the absence of any DNS service on my router(s). If you're setting up tunnels and things like that, there may be more occurrences. Then you need to check at least /var/lib in the same manner, which may remind you to rerun some configuration scripts. The obvious one above is dpkg-reconfigure exim4-config in order to rewrite /var/lib/exim4/config.autogenerated. Changing just one machine's domain name on a network may not make a lot of sense if other machines refer to it. BTW I have no idea why this thread has suddenly lurched onto hostnames (he writes, as he looks up at the Subject line). Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-26 10:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Ht3KV-WX0-1@gated-at.bofh.it> |
| In reply to | #262733 |
On 25 Oct 2023 21:23 -0400, from monnier@iro.umontreal.ca (Stefan Monnier): >> 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. Aside: I realized after sending the email quoted above that I'd made a mistake. The subnet is 172.16.0.0/12, not 172.12.0.0/12. Apologies. > 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? As already mentioned, it has been backronymed. Also, "arpa." already existed, and is well established for infrastructure names in DNS. For example both IPv4 and IPv6 reverse DNS are served under the arpa zone; in-addr.arpa and ip6.arpa respectively. To "choose something a bit more neutral", assuming such a name could be found (it seems likely that almost anything reasonable could match _some_ government agency _somewhere_ and therefore be, to borrow your phrasing, "unpalatable" to some) would mean having to register and maintain (or at the very least reserve) a new TLD just for the purpose, which was the problem from RFC 7788 that RFC 8375 aimed to solve. Certainly "local." would have been one possibility, but that is reserved _specifically_ for mDNS (RFC 6762) although is often incorrectly used for non-mDNS names. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | "Marco M." <mm@dorfdsl.de> |
|---|---|
| Date | 2023-10-26 10:40 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Ht44h-X4Y-5@gated-at.bofh.it> |
| In reply to | #262738 |
Am 26.10.2023 um 08:16:47 Uhr schrieb Michael Kjörling: > Certainly "local." would have been one possibility, but that is > reserved _specifically_ for mDNS (RFC 6762) although is often > incorrectly used for non-mDNS names. rfc6762 |Implementers MAY choose to look up such names concurrently via other |mechanisms (e.g., Unicast DNS) and coalesce the results in some |fashion. Although, querying mDNS is mandatory for it and MAY means there is no guarantee that unicast DNS is being used.
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-26 11:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Ht4H0-XAj-11@gated-at.bofh.it> |
| In reply to | #262740 |
On 26 Oct 2023 10:33 +0200, from mm@dorfdsl.de (Marco M.): >> Certainly "local." would have been one possibility, but that is >> reserved _specifically_ for mDNS (RFC 6762) although is often >> incorrectly used for non-mDNS names. > > rfc6762 >From section 3 of that RFC: > This document specifies that the DNS top-level domain ".local." is a > special domain with special semantics, namely that any fully > qualified name ending in ".local." is link-local, and names within > this domain are meaningful only on the link where they originate. [...] > > Any DNS query for a name ending with ".local." MUST be sent to the > mDNS IPv4 link-local multicast address 224.0.0.251 (or its IPv6 > equivalent FF02::FB). "Link local" is not the same thing as "site local". "Site local" seems a reasonable approximation of the scope of home.arpa names; it's certainly not implausible for a home network to have both wired and wireless parts, hosts on which would belong to different link local scopes. (Yes, it is possible to run a VPN or other type of tunnel between two geographically disparate sites both of which use home.arpa names in a coordinated fashion with non-routable IP addresses, such that hosts in one location are accessible from the other under their *.home.arpa names. But that only requires coordination between the sites involved, not global coordination.) -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-10-26 11:10 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Ht4xj-Xwm-1@gated-at.bofh.it> |
| In reply to | #262738 |
On Thu, Oct 26, 2023 at 4:17 AM Michael Kjörling <2695bd53d63c@ewoof.net> wrote: > > [...] > > > > 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? > > As already mentioned, it has been backronymed. Also, "arpa." already > existed, and is well established for infrastructure names in DNS. For > example both IPv4 and IPv6 reverse DNS are served under the arpa zone; > in-addr.arpa and ip6.arpa respectively. To "choose something a bit > more neutral", assuming such a name could be found (it seems likely > that almost anything reasonable could match _some_ government agency > _somewhere_ and therefore be, to borrow your phrasing, "unpalatable" > to some) would mean having to register and maintain (or at the very > least reserve) a new TLD just for the purpose, which was the problem > from RFC 7788 that RFC 8375 aimed to solve... I think the real unpalatable part of DNS is, most of the operators are US-based: <https://www.iana.org/domains/root/servers>. Most fall under US jurisdiction, and the system is mostly homogeneous and subject to political whims. Imagine if the US government denied service to Iran or Russia by fiat. Do you think Verisign or NASA would contravene a whitehouse order? Jon Postel was trying to fix that before he died. He wanted DNS to be truly global and outside the government's control. It's unfortunate he passed away before he accomplished that. Jeff
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-26 11:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Ht4H0-XAj-9@gated-at.bofh.it> |
| In reply to | #262741 |
On 26 Oct 2023 05:07 -0400, from noloader@gmail.com (Jeffrey Walton): > I think the real unpalatable part of DNS is, most of the operators are > US-based: Nothing about home.arpa requires or relies on the use of DNS, and most residential networks are probably small enough that a non-DNS setup (such as for example using exclusively /etc/hosts distributed among the computers involved) is entirely manageable. RFC 8375 section 3 specifically prohibits queries for anything under home.arpa leaking "outside the logical boundaries of the homenet". -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-27 17:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtwWB-1fzz-3@gated-at.bofh.it> |
| In reply to | #262738 |
On 27 Oct 2023 15:56 +0100, from mick.crane@gmail.com (mick.crane): > If remembering correctly the RFC was use "home" for a home network > Then that was changed to use "local" and then back to "home". > Is it now "home.arpa." with the dot at the end or without? RFC 6762 specifies that "local." is _specifically_ and _exclusively_ for use with mDNS. If you're not using mDNS, don't use that TLD; and if you're using mDNS, use that TLD _only_ for mDNS-managed names. End of that story. (Yes, people use it incorrectly. That doesn't mean you should, too.) RFC 7788 said "home." was for use in environments using the Home Networking Control Protocol. RFC 8375 reserves "home.arpa." and updates RFC 7788 to use "home.arpa." instead of "home." but _also_ specifies that the intended usage of "home.arpa." is broader; "home.arpa." is intended for almost any residential / home network use where a globally unique domain name is either unnecessary or undesirable. (It can, of course, also be used in a corporate context, if desired.) Bottom line: unless you have another actually registered domain name you want to use (in which case you are, of course, free to use that), the safe, officially recommended choice is to use "home.arpa.". The dot at the end of any fully qualified DNS name signifies the DNS root zone; it is often omitted and implied, but in some contexts, particularly DNS administration contexts, it's explicitly included to remove ambiguity. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | "Marco M." <mm@dorfdsl.de> |
|---|---|
| Date | 2023-10-26 10:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Ht3UB-X0Q-1@gated-at.bofh.it> |
| In reply to | #262733 |
Am 25.10.2023 um 21:23:41 Uhr schrieb Stefan Monnier: > I understand ARPA was closely related to the beginnings of the > Internet, but... couldn't they choose something a bit more neutral? I don't know the exact reason for that decision, but I assume they used it because it is already there, e.g. in-addr.arpa and ip6.arpa exist for reverse DNS. I dunno if DARPA still uses that domain for their own stuff.
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-10-25 22:10 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HsSmt-Pso-13@gated-at.bofh.it> |
| In reply to | #262700 |
On Wed, Oct 25, 2023 at 1:32 AM Marco M. <mm@dorfdsl.de> wrote:
>
> 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.
Many folks don't know about the IANA special-use domain names.
Even Linux documentation is bad (from Fedora):
$ cat /etc/hosts
# Loopback entries; do not change.
# For historical reasons, localhost precedes localhost.localdomain:
127.0.0.1 localhost localhost.localdomain localhost4
localhost4.localdomain4
::1 localhost localhost.localdomain localhost6
localhost6.localdomain6
# 127.0.1.1 is often used for the FQDN of the machine
127.0.1.1 skylake.home.arpa skylake
# See hosts(5) for proper format and other examples:
# 192.168.1.10 foo.mydomain.org foo
# 192.168.1.13 bar.mydomain.org bar
The template should be using example.{com|net|org} or home.arpa, and
not a random domain that is owned by someone:
$ whois mydomain.org | grep -E 'Name|ID'
Domain Name: mydomain.org
Registry Domain ID: 43938f3b31594bc394234043672173ed-LROR
Registrar IANA ID: 228
...
It seems to be a problem of education, at least for some folks.
Jeff
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2023-10-26 01:30 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HsVu1-RiZ-5@gated-at.bofh.it> |
| In reply to | #262690 |
On Wed 25 Oct 2023 at 08:33:25 (+0200), Erwan David wrote:
> Le 25/10/2023 à 03:47, David Wright a écrit :
> > 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}.
> >
> Or if you already have a domain, you can use a subdomain. eg. I have
> rail.eu.org, and at home it is depot.rail.eu.org
I'm not sure how that would work when my home network
is on a different continent from my domain's hosting.
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | jeremy ardley <jeremy.ardley@gmail.com> |
|---|---|
| Date | 2023-10-26 02:00 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HsVX3-Rsc-3@gated-at.bofh.it> |
| In reply to | #262730 |
On 26/10/23 07:24, David Wright wrote: >> Or if you already have a domain, you can use a subdomain. eg. I have >> rail.eu.org, and at home it is depot.rail.eu.org > I'm not sure how that would work when my home network > is on a different continent from my domain's hosting. This is no problem asides from DNS. You will have DNS records set up for your hosted service with public IP addresses. It's quite straight forward to add a subdomain and assign non routable IP addresses to it. Downside is it will look odd to an observer, and will leak some info about your internal network. As an alternative you can still use the same naming convention but not put it in the public domain. This will require you to set up your own internal DNS service or hosts files and have DNS queries resolved locally without going to the external DNS server.
[toc] | [prev] | [next] | [standalone]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Date | 2023-10-26 02:20 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HsWgp-RNE-3@gated-at.bofh.it> |
| In reply to | #262731 |
[Multipart message — attachments visible in raw view] — view raw
On Oct 26, 2023, jeremy ardley wrote: > > On 26/10/23 07:24, David Wright wrote: > > > Or if you already have a domain, you can use a subdomain. eg. I have > > > rail.eu.org, and at home it is depot.rail.eu.org > > I'm not sure how that would work when my home network > > is on a different continent from my domain's hosting. > > > This is no problem asides from DNS. > > You will have DNS records set up for your hosted service with public IP > addresses. It's quite straight forward to add a subdomain and assign non > routable IP addresses to it. > > Downside is it will look odd to an observer, and will leak some info about > your internal network. > > As an alternative you can still use the same naming convention but not put > it in the public domain. This will require you to set up your own internal > DNS service or hosts files and have DNS queries resolved locally without > going to the external DNS server. Indeed, split-horizon DNS is quite good for this "problem". -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2023-10-27 05:30 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HtlHP-18Uv-1@gated-at.bofh.it> |
| In reply to | #262731 |
On Thu 26 Oct 2023 at 07:58:45 (+0800), jeremy ardley wrote: > On 26/10/23 07:24, David Wright wrote: > > > Or if you already have a domain, you can use a subdomain. eg. I have > > > rail.eu.org, and at home it is depot.rail.eu.org > > I'm not sure how that would work when my home network > > is on a different continent from my domain's hosting. > > This is no problem asides from DNS. > > You will have DNS records set up for your hosted service with public > IP addresses. It's quite straight forward to add a subdomain and > assign non routable IP addresses to it. > > Downside is it will look odd to an observer, and will leak some info > about your internal network. > > As an alternative you can still use the same naming convention but not > put it in the public domain. This will require you to set up your own > internal DNS service or hosts files and have DNS queries resolved > locally without going to the external DNS server. I use hosts files, as my inexpensive router has no DNS facility to parallel its DHCP service. Setting up an internal DNS would just be extra work, another chance of inconsistency, and depend on an individual machine always being up. My machines send external DNS requests to the router, which is configured to forward them to Google. Currently I still use .corp as my domain name, and find it least confusing if anything with "lionunicorn…" in it is an external address. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | ghe2001 <ghe2001@protonmail.com> |
|---|---|
| Date | 2023-10-23 18:00 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <Hs5vr-jhM-3@gated-at.bofh.it> |
| In reply to | #262586 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 ------- Original Message ------- On Sunday, October 22nd, 2023 at 11:29 PM, Jeffrey Walton <noloader@gmail.com> wrote: > 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). Hadn't thought of that, but a shortcut name in the hosts file fixes it all. For example: One of my computers is called gobook3 (makes sense to me). In hosts, it's shortcut is 'gb'. 'ping gb' does what's expected. 'ping gv' says 'ping: gv: Name or service not known'. And I've had no reason to rattle ICANN's cage(s) -- it's all local. /etc/hosts has worked just fine for me since I became aware of IP and put up a little Internet domain (I disabled it a few years ago when my brain hit 75 years old and the ISP raised their rates). -- Glenn English -----BEGIN PGP SIGNATURE----- Version: ProtonMail wsBzBAEBCAAnBYJlNpbgCZCf14YxgqyMMhYhBCyicw9CUnAlY0ANl5/XhjGC rIwyAABxJgf/TiRVNvnU6+/TWEslmJQdit8GwdWRVDt2Qt4COngONjquR1jW 4Z+N55do+UwwPsHPkmZDaSE2yWkVwhfi1Yvr+ET2P8bUHgishQ6WevV2rOhB 2guatFVXb7B/DbYIfAU+/YAJPOwoNCLB95kH/Z0yh0gXjpZHl0eMeXWg+T9M VoGlJQlc1YoWHBVUPqx+eowTAnuW0FhWP3aO9t1lj+AkuJiQpvv2Othhwkok vzX2oSIUUGxSegaeHQ+l2OzB4Sv8FKtn1JWOQvYW8Vzm33N6XiBjS8IAWdfx UJUBjZH6UZiJoNosKxdlwfrSqoR0DwCgBb1Eilboy7XSzp8r/m47dA== =Ly3y -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-23 04:50 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HrTaV-bjU-3@gated-at.bofh.it> |
| In reply to | #262566 |
On 23/10/2023 04:43, gene heskett wrote: > > As I keep repeating Dan, there is not a local dns, its all a 15 entry > hosts file atm. So that cannot bite /me/. It can. Some day .den TLD may be registered and chosen by a 3d printer manufacturer. It might happen that you would not be able to access docs for your shiny new device and you would claim something like > Google seems to have high jacked port 80 https://lists.debian.org/msgid-search/0a8b96aa-8630-ee5c-5135-59221c55b5d7@shentel.net
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-23 18:20 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <Hs5ON-jDU-1@gated-at.bofh.it> |
| In reply to | #262579 |
On 10/22/23 22:55, Max Nikulin wrote: > On 23/10/2023 04:43, gene heskett wrote: >> >> As I keep repeating Dan, there is not a local dns, its all a 15 entry >> hosts file atm. So that cannot bite /me/. > > It can. Some day .den TLD may be registered and chosen by a 3d printer > manufacturer. It might happen that you would not be able to access docs > for your shiny new device and you would claim something like > >> Google seems to have high jacked port 80 > > https://lists.debian.org/msgid-search/0a8b96aa-8630-ee5c-5135-59221c55b5d7@shentel.net > They have, chromium, the google browser, absolutely cannot be sent to http://localhost:80 on any arm system here at the Heskett Ranchette. FF can, but not chromium, its doing a failed advertising lookup on google instead. Still works normally on wintel hdwe, but not on arm's. And I use bananapi-m5's to run klipper and friends on a couple tables full of 3d printers here. And except for an rpi4b doing a different job, they ALL run on debian bookworm/arm64 or ubuntu jammy/arm64 repos. 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]
Page 11 of 13 — ← Prev page 1 … 9 10 [11] 12 13 Next page →
Back to top | Article view | linux.debian.user
csiph-web