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 4 of 13 — ← Prev page 1 2 3 [4] 5 6 … 13 Next page →
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-21 23:00 +0200 |
| Message-ID | <HrreF-hux1-9@gated-at.bofh.it> |
| In reply to | #262496 |
On Sat, Oct 21, 2023 at 02:46:25PM -0600, Charles Curley wrote: > Also, you should not be using example.org. That is a reserved domain > name. https://en.wikipedia.org/wiki/Example.com I just assumed this was a lie. An obfuscation of the actual domain name.
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-21 23:20 +0200 |
| Message-ID | <Hrry1-huTJ-3@gated-at.bofh.it> |
| In reply to | #262497 |
On 10/21/23 16:52, Greg Wooledge wrote: > On Sat, Oct 21, 2023 at 02:46:25PM -0600, Charles Curley wrote: >> Also, you should not be using example.org. That is a reserved domain >> name. https://en.wikipedia.org/wiki/Example.com > I just assumed this was a lie. An obfuscation of the actual domain name. > Nope I use it on an internal network and have done so for 40 years. -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-21 23:20 +0200 |
| Message-ID | <Hrry1-huTJ-1@gated-at.bofh.it> |
| In reply to | #262496 |
[Multipart message — attachments visible in raw view] — view raw
On 10/21/23 16:46, Charles Curley wrote:
> On Sat, 21 Oct 2023 14:40:49 -0400
> Pocket<pocket@columbus.rr.com> wrote:
>
>> but the machine in question has
>> bind running so nameserver needs to be set to 127.0.0.1 and the
>> domain to example.org in the resolv.conf file.
>>
>> This is my problem in a nutshell
> Oh, why didn't you say that! Actually, it doesn't have to use the
> loopback address; you can use the address of the Ethernet interface.
>
> Also, you should not be using example.org. That is a reserved domain
> name.https://en.wikipedia.org/wiki/Example.com
rfc2606.html 3 <https://www.rfc-editor.org/rfc/rfc2606.html#section-3>.
Reserved Example Second Level Domain Names
The Internet Assigned Numbers Authority (IANA) also currently has the
following second level domain names reserved which can be used as
examples.
example.com
example.net
example.org
rfc6761.html
7. DNS Registries/Registrars:
How should DNS Registries/Registrars treat requests to register
this reserved domain name? Should such requests be denied?
Should such requests be allowed, but only to a specially-
designated entity? (For example, the name "www.example.org" is
reserved for documentation examples and is not available for
registration; however, the name is in fact registered; and there
is even a web site at that name, which states circularly that the
name is reserved for use in documentation and cannot be
registered!)
Which I take it that you can use them for any purpose as long as it is not on the internet.
Why would I register a domain name for an internal network?
Any name will do. You could make the same argument if you just makeup a domain to use as it could already be registered or someone my register it in the future.
That is why I picked example.org as It will/can not be used, no collision with domain names that way.
Somebody is usinghttp://example.org/ on the internet, try it in your browser
and it ishttps://www.iana.org/help/example-domains
IANA-managed Reserved Domains
Certain domains are set aside, and nominally registered to “IANA”, for
specific policy or technical purposes.
Example domains
As described in RFC 2606 <https://www.iana.org/go/rfc2606> and RFC 6761
<https://www.iana.org/go/rfc6761>, a number of domains such as
example.com and example.org are maintained for documentation purposes.
These domains may be used as illustrative examples in documents without
prior coordination with us. They are not available for registration or
transfer.
So I can not use or I am forbidden to use 192.168.1.0/24 network as it is reserved?
>
> I am going to guess (since you haven't
> said so) that this is also not a laptop, and therefor it has a permanent
> IP address.
This is for a name server
>
> If you insist on retaining NetworkManager, this page might be useful.
> https://serverfault.com/questions/810636/how-to-manage-dns-in-networkmanager-via-console-nmcli
> You can also add DNS servers in the GTK version of the NM GUI. I don't
> know about the KDE version.
I am just using what was installed by my scripted debian installation
>
> You can use isc-dhcp to tell the whole network where its DNS server is.
> You can also make over-rides for individual hosts. In dhcpd.conf:
Yes but if the currently installed and enabled NetwokManager will work
then there is little need to change it. why change it?
> You said in another email that you are using a dhcp server on a
> "router". That doesn't tell me much. A router is simply a computer that
> sits between two networks, and routes packets between them. My router
> is a 16 year old computer designed for embedded applications that runs
> Debian. I run ISC DHCPD on that an another machine with fail-over
> between them.
It is a "home office router" by linksys
I could have built my own "router" with my own custom scratch built OS
as I did starting 35 years ago, but why should I if I can get something
off the shelf?
>
> From what I have seen most "routers" these days are cheap boxes
> provided by ISPs that have buggy, insecure, and limited software which
> may not be able to do this.
>
> You can also set the ISC dhcp client to add name servers.
>
> prepend domain-name-servers 127.0.0.1;
Then all clients get the localhost address for DNS resolution, which
will not come close to working.
Anyway I have solved this issue by modifying the keyfile for device end0
see my previous post
I will find a way........
--
It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-22 13:20 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm: NetworkManager |
| Message-ID | <HrEEW-2lD-21@gated-at.bofh.it> |
| In reply to | #262498 |
On 21 Oct 2023 17:13 -0400, from pocket@columbus.rr.com (Pocket): > Why would I register a domain name for an internal network? > Any name will do. You could make the same argument if you just > makeup a domain to use as it could already be registered or someone > my register it in the future. > That is why I picked example.org as It will/can not be used, no > collision with domain names that way. It's fairly recent (RFC 8375, May 2018) but this type of usage is pretty much exactly what home.arpa is meant for. https://www.rfc-editor.org/info/rfc8375 -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-22 14:30 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm: NetworkManager |
| Message-ID | <HrFKF-2YK-1@gated-at.bofh.it> |
| In reply to | #262514 |
On 10/22/23 07:13, Michael Kjörling wrote: > On 21 Oct 2023 17:13 -0400, from pocket@columbus.rr.com (Pocket): >> Why would I register a domain name for an internal network? >> Any name will do. You could make the same argument if you just >> makeup a domain to use as it could already be registered or someone >> my register it in the future. >> That is why I picked example.org as It will/can not be used, no >> collision with domain names that way. > It's fairly recent (RFC 8375, May 2018) but this type of usage is > pretty much exactly what home.arpa is meant for. > > https://www.rfc-editor.org/info/rfc8375 > I am researching this as I am aware that things have changed from 20 years ago and with ipv6 adoption -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-10-22 17:20 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm: NetworkManager |
| Message-ID | <HrIpb-4Fv-1@gated-at.bofh.it> |
| In reply to | #262514 |
On Sun, Oct 22, 2023 at 7:13 AM Michael Kjörling <2695bd53d63c@ewoof.net> wrote: > > On 21 Oct 2023 17:13 -0400, from pocket@columbus.rr.com (Pocket): > > Why would I register a domain name for an internal network? > > Any name will do. You could make the same argument if you just > > makeup a domain to use as it could already be registered or someone > > my register it in the future. > > That is why I picked example.org as It will/can not be used, no > > collision with domain names that way. > > It's fairly recent (RFC 8375, May 2018) but this type of usage is > pretty much exactly what home.arpa is meant for. > > https://www.rfc-editor.org/info/rfc8375 Thanks for that. I was not aware the domain was reserved. Jeff
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-22 19:00 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm: NetworkManager |
| Message-ID | <HrJXX-5t8-5@gated-at.bofh.it> |
| In reply to | #262533 |
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: >> It's fairly recent (RFC 8375, May 2018) but this type of usage is >> pretty much exactly what home.arpa is meant for. >> >> 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. just for S&G, and because a half G.S., half Coyote mix was the smartest "dog" I ever met, my home network domainname has been the "coyote.den" for 25 years now. "Lady" understood English and could do simple math, barking the number of times the answer was. > Thanks for that. I was not aware the domain was reserved. > > Jeff > 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 | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-10-22 20:20 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm: NetworkManager |
| Message-ID | <HrLdn-6rc-1@gated-at.bofh.it> |
| In reply to | #262542 |
Gene writes: > 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. It's for people who haven't a clue as to what a domainname or address block is. https://datatracker.ietf.org/doc/html/rfc7788 -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-22 20:40 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HrLwJ-6xU-1@gated-at.bofh.it> |
| In reply to | #262558 |
On 22 Oct 2023 13:13 -0500, from john@sugarbit.com (John Hasler): > It's for people who haven't a clue as to what a domainname or address > block is. > > https://datatracker.ietf.org/doc/html/rfc7788 RFC 8375 section 1: "Although this document makes specific reference to [RFC7788], it is not intended that the use of 'home.arpa.' be restricted solely to networks where HNCP is deployed. Rather, 'home.arpa.' is intended to be the correct domain for uses like the one described for '.home' in [RFC7788]: local name service in residential homenets." -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-23 00:10 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm: NetworkManager |
| Message-ID | <HrONX-8Ho-1@gated-at.bofh.it> |
| In reply to | #262558 |
On 10/22/23 14:19, John Hasler wrote: > Gene writes: >> 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. > > It's for people who haven't a clue as to what a domainname or address > block is. If that is an insult, so be it. > > https://datatracker.ietf.org/doc/html/rfc7788 Many Thanks for the link John, but having spent 20 minutes scanning thru that, my probably invalid comment would be that all the links are there but not even a Philadelphia lawyer could grasp it in 5 years time. Assuming each link is 20,000 words or more, at 400 wpm I don't have enough time left to read it all. 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 | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-10-23 00:50 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm: NetworkManager |
| Message-ID | <HrPqF-8V1-3@gated-at.bofh.it> |
| In reply to | #262567 |
I wrote: > It's for people who haven't a clue as to what a domainname or address > block is. Gene writes: > If that is an insult, so be it. I just meant to explain that though it is not a solution to your problem, it is a solution to a problem some other people have. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-23 02:40 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm: NetworkManager |
| Message-ID | <HrR97-a0z-1@gated-at.bofh.it> |
| In reply to | #262570 |
On 10/22/23 18:45, John Hasler wrote: > I wrote: >> It's for people who haven't a clue as to what a domainname or address >> block is. > > Gene writes: >> If that is an insult, so be it. > > I just meant to explain that though it is not a solution to your problem, > it is a solution to a problem some other people have. Six of one, half a dozen of the other John. What really bugs me is when the maintainers forget there are hosts file users, and do something that totally screws us up, getting help to restore a broken system can't be done, cuz you can't ask anything with it broken, and when by brute force, you finally get it sorta working, 95% of the help you need to really make it right is replaced by instructions on how to setup just one facet of dhcp, so it often has to be a snippet there, and another from someplace else, repeat till it all works, gleaned from the 5% who do understand but are often drowned out by the why the hell don't you run dhcp crowd representing the other 95%. Not your fault of course, that is just how it is as viewed from this chair, by the same guy whose been online since before Delphi, with a trs-80 Color computer since we were blessed with a server at Princeton in the 80's. A remodel got it walled in and forgotten about till another remodel tore out the wall exposing it a decade later, still running. 30+ years later I can't even remember its name. Perhaps you do. Take care & stay well John. 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 | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-23 02:50 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm: NetworkManager |
| Message-ID | <HrRiN-a47-1@gated-at.bofh.it> |
| In reply to | #262573 |
On Sun, Oct 22, 2023 at 08:36:53PM -0400, gene heskett wrote: > What really bugs me is when the maintainers forget there are hosts file > users, and do something that totally screws us up, Gene, you're being irrational again. "Hosts file only" systems have been supported since before Debian existed, without surcease. There has never been a time when they weren't supported. There never will be. 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.
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-10-23 04:40 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HrT1f-bgd-1@gated-at.bofh.it> |
| In reply to | #262574 |
Gene writes: > 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 and last years fix doesn't work this year. And you can't > ask for help when its not working. So YOU have to fix it based of what > YOU know works. Makes one wonder about the motives. I use host files and I don't have that problem. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2023-10-23 05:10 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HrTuh-bGd-7@gated-at.bofh.it> |
| In reply to | #262577 |
>> 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 and last years fix doesn't work this year. And you can't
>> ask for help when its not working. So YOU have to fix it based of what
>> YOU know works. Makes one wonder about the motives.
> I use host files and I don't have that problem.
Same here: the last time I had problems with `/etc/hosts` files was
back when `/etc/nsswitch.conf` was introduced :-)
That was before I started using Debian.
I can relate to Gene's feelings since there's been indeed some churn
over the years, but `/etc/hosts` seems like an odd example because this
one is among the most stable part of Unix/Linux.
Stefan
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-23 09:20 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HrXod-e8g-3@gated-at.bofh.it> |
| In reply to | #262582 |
On 23/10/2023 09:59, Stefan Monnier wrote: > I can relate to Gene's feelings since there's been indeed some churn > over the years, but `/etc/hosts` seems like an odd example because this > one is among the most stable part of Unix/Linux. Gene's issue was with resolv.conf and he was refusing Greg's suggestions to fix it for a long time. By the way, is there a way to validate correctness of the resolv.conf file, e.g. to force libc to spit warnings in response to unrecognized entries?
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-23 17:20 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <Hs4SJ-iXr-3@gated-at.bofh.it> |
| In reply to | #262582 |
On 10/22/23 23:08, Stefan Monnier wrote: >>> 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 and last years fix doesn't work this year. And you can't >>> ask for help when its not working. So YOU have to fix it based of what >>> YOU know works. Makes one wonder about the motives. >> I use host files and I don't have that problem. > > Same here: the last time I had problems with `/etc/hosts` files was > back when `/etc/nsswitch.conf` was introduced :-) > That was before I started using Debian. > > I can relate to Gene's feelings since there's been indeed some churn > over the years, but `/etc/hosts` seems like an odd example because this > one is among the most stable part of Unix/Linux. > > > Stefan > The squawk includes /etc/hosts because that method is the root cause of all the troubles. For a while you could hide what used to be in /etc/network/interfaces in the last stanza of /etc/dhcpdc(sp?).conf, but that like /e/n/interfaces was too easy, anybody could do it so that went away. There it was the last ditch src if a dhcp could not be found. That actually made sense but wasn't ever published that I know of. The churn seems more like change just for the hell of it as no real reason for the changes ever seemed to make it into the docs that get installed in a bare metal install. Not even a hint in any of the usual suspects conf files. It was pure serendipity that I found that with a global grep of the whole /etc tree for any mention of dhcp. That fell out, so I read it, finding this cute little fill in the blanks thing clear at the bottom of a 5k file. So I "filled in the blanks" and it worked, For two major releases. But again that was way too easy so it went away, I guess in favor of nsswitch. But not one grep able word about it made it into the bare metal installed docs. And that is where this old (89 now) Iowa farm kid who tested in the 7th grade at an IQ of 147, blows his cool. Which unfortunately gets me way more than my std 15 minutes of fame here. Anyway Stefan, take care and stay well. And unvaxed. A small selenium and a couple d3's a day is much better insurance. 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 | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-23 18:00 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <Hs5vr-jhM-7@gated-at.bofh.it> |
| In reply to | #262577 |
On 10/22/23 22:37, John Hasler wrote: > Gene writes: >> 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 and last years fix doesn't work this year. And you can't >> ask for help when its not working. So YOU have to fix it based of what >> YOU know works. Makes one wonder about the motives. > > I use host files and I don't have that problem. And where, if you don't have a network, did you find the info to fix it?, when two junk 2T seagates around 6 weeks old die in the same week, making one start from square one with a new bookworm install? And install that pulled in and enabled orca and brltty and which could not be rebooted once they were disabled. You could only reinstall to reboot, which I did 22 times before someone suggested unplugging any usb<->serial adapters, the installer was assuming I was blind and NEVER ASKED ME if I wanted them. Have you, I assume with decent hearing, ever tried to use a computer that is locked up and spending about a second for every key press by announcing in a barely understandable but loud voice, every key's identity as they are being pressed? Distraction is a wholly inadequate description. I rest my case on that one. Take care & stay well John. 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 | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-23 04:40 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <HrT1f-bgd-3@gated-at.bofh.it> |
| In reply to | #262574 |
On 10/22/23 20:48, Greg Wooledge wrote: > On Sun, Oct 22, 2023 at 08:36:53PM -0400, gene heskett wrote: >> What really bugs me is when the maintainers forget there are hosts file >> users, and do something that totally screws us up, > > Gene, you're being irrational again. "Hosts file only" systems have been > supported since before Debian existed, without surcease. There has never > been a time when they weren't supported. There never will be. > > 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 and last years fix doesn't work this year. And you can't ask for help when its not working. So YOU have to fix it based of what YOU know works. Makes one wonder about the motives. 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 | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2023-10-23 22:40 +0200 |
| Subject | Re: Domain name to use on home networks; was: Bookworm:NetworkManager |
| Message-ID | <Hs9Sq-mq3-17@gated-at.bofh.it> |
| In reply to | #262578 |
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. Those reading this later need to believe Greg's statements and not Gene's. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
Page 4 of 13 — ← Prev page 1 2 3 [4] 5 6 … 13 Next page →
Back to top | Article view | linux.debian.user
csiph-web