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 10 of 13 — ← Prev page 1 … 8 9 [10] 11 12 13 Next page →
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-30 19:50 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuFuN-1WQx-3@gated-at.bofh.it> |
| In reply to | #262910 |
On 10/30/23 14:30, gene heskett wrote:
> On 10/30/23 13:40, John Hasler wrote:
>> I wrote:
>>> Why do you have NetworkManager installed at all?
>>
>> Gene writes:
>>> Std image dd'd to u-sd card install on the arm64 stuff, can't get away
>>> from it.
>>
>> Why won't "sudo apt remove --purge network-manager" work for you?
> It did, but took the network down too after a reboot. To make sure I do
> it right, whats next?
>
> Thanks John.
I made /e/n/interfaces look like this:
gene@bananapim55:~$ cat /etc/network/interfaces
source /etc/network/interfaces.d/*
# Network is managed by Gene Heskett
auto lo eth0
iface lo inet loopback
iface eth0 inet static
address 192.168.71.55/24
gateway 192.168.71.1
gene@bananapim55:~$
and restarted /etc/init.d/networking.
And it all works.
> Cheers, Gene Heskett.
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 | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-31 04:00 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuN8Z-21sK-1@gated-at.bofh.it> |
| In reply to | #262892 |
On 30/10/2023 23:09, gene heskett wrote: > Making resolv.conf immutable seems to be the way to permanently insulate > me from NM's broken idea of whats right. Gene, from what you have written in this thread I see nothing wrong in behavior of NetworkManager. Certainly it is easier to continue barking at NetworkManager instead of getting rid of gibberish you put into its config. Reread this thread from its start. NetworkManager is flexible enough and recipes for tuning of DNS settings have been posted here.
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-30 13:20 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Huzpn-1Th7-1@gated-at.bofh.it> |
| In reply to | #262882 |
On 10/30/23 03:54, gene heskett wrote: > On 10/29/23 22:17, Max Nikulin wrote: >> On 30/10/2023 00:08, Pocket wrote: >>> On 10/29/23 12:24, gene heskett wrote: >>>> I have also made a very painfull attempt to change my domainname >>>> from coyote.den to home.arpa, and finally reverted that, >> >> Gene, have you posted what exactly you did to switch from coyote.den >> to home.arpa? You have been told that setting NIS domainname was a >> wrong direction since you do not manage your hosts through NIS. >> >>> NetworkManager keeps updating the /etc/resolv.conf file in my >>> opinion because it is querying the DHCP server. >> [ ... ]> cat /etc/NetworkManager/system-connections/GREMLIN.nmconnection >>> [ipv4] >>> method=auto > gene@coyote:/etc$ cat > /etc/NetworkManager/system-connections/GREMLIN.nmconnection > cat: /etc/NetworkManager/system-connections/GREMLIN.nmconnection: No > such file or directory > > Thats this machine, but applied to the problematic machine it becomes > sudo cat /etc/NetworkManager/system-connections/'Wired connection > 1.nmconnection' > which returns: > ========== > gene@bananapim55:/etc/systemd$ sudo cat > /etc/NetworkManager/system-connections/'Wired connection 1.nmconnection' > [connection] > id=Wired connection 1 > uuid=14621305-9887-3c6c-9e50-50894877ab68 > type=ethernet > autoconnect-priority=999 > interface-name=eth0 > timestamp=1698571927 > > [ethernet] > cloned-mac-address=BE:63:9C:35:DD:4F > duplex=full > speed=1000 > > [ipv4] > address1=192.168.71.55/24,192.168.71.1 > dns=192.168.71.1; > dns-search=hosts;nameserver; ^^^^^^^^^^^^^^^^^^^^^ this is incorrect nmcli connection modify Network_InterfaceName ipv4.dns-search (searchDomainname- for multiple entry you can use comma) That needs to be the domain you want to search ie home.arpa in your case Not the order of domain resolution, that is what /etc/nsswitch.conf is for. dns-search=home.arpa; Please have a look at the working example I posted, -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-30 13:30 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Huzz3-1Tkx-1@gated-at.bofh.it> |
| In reply to | #262885 |
[Multipart message — attachments visible in raw view] — view raw
On 10/30/23 08:19, Pocket wrote:
>
> On 10/30/23 03:54, gene heskett wrote:
>> On 10/29/23 22:17, Max Nikulin wrote:
>>> On 30/10/2023 00:08, Pocket wrote:
>>>> On 10/29/23 12:24, gene heskett wrote:
>>>>> I have also made a very painfull attempt to change my domainname
>>>>> from coyote.den to home.arpa, and finally reverted that,
>>>
>>> Gene, have you posted what exactly you did to switch from coyote.den
>>> to home.arpa? You have been told that setting NIS domainname was a
>>> wrong direction since you do not manage your hosts through NIS.
>>>
>>>> NetworkManager keeps updating the /etc/resolv.conf file in my
>>>> opinion because it is querying the DHCP server.
>>> [ ... ]> cat
>>> /etc/NetworkManager/system-connections/GREMLIN.nmconnection
>>>> [ipv4]
>>>> method=auto
>> gene@coyote:/etc$ cat
>> /etc/NetworkManager/system-connections/GREMLIN.nmconnection
>> cat: /etc/NetworkManager/system-connections/GREMLIN.nmconnection: No
>> such file or directory
>>
>> Thats this machine, but applied to the problematic machine it becomes
>> sudo cat /etc/NetworkManager/system-connections/'Wired connection
>> 1.nmconnection'
>> which returns:
>> ==========
>> gene@bananapim55:/etc/systemd$ sudo cat
>> /etc/NetworkManager/system-connections/'Wired connection 1.nmconnection'
>> [connection]
>> id=Wired connection 1
>> uuid=14621305-9887-3c6c-9e50-50894877ab68
>> type=ethernet
>> autoconnect-priority=999
>> interface-name=eth0
>> timestamp=1698571927
>>
>> [ethernet]
>> cloned-mac-address=BE:63:9C:35:DD:4F
>> duplex=full
>> speed=1000
>>
>> [ipv4]
>> address1=192.168.71.55/24,192.168.71.1
>> dns=192.168.71.1;
>> dns-search=hosts;nameserver;
>
>
> ^^^^^^^^^^^^^^^^^^^^^
>
> this is incorrect
>
> nmcli connection modify Network_InterfaceName ipv4.dns-search
> (searchDomainname- for multiple entry you can use comma)
>
> That needs to be the domain you want to search ie
>
> home.arpa in your case
>
> Not the order of domain resolution, that is what /etc/nsswitch.conf is
> for.
>
> dns-search=home.arpa;
|ipv4.dns-search|
List of DNS search domains. Domains starting with a tilde ('~') are
considered 'routing' domains and are used only to decide the interface
over which a query must be forwarded; they are not used to complete
unqualified host names.
When using a DNS plugin that supports Conditional Forwarding or Split
DNS, then the search domains specify which name servers to query. This
makes the behavior different from running with plain /etc/resolv.conf.
For more information see also the dns-priority setting.
When set on a profile that also enabled DHCP, the DNS search list
received automatically (option 119 for DHCPv4 and option 24 for DHCPv6)
gets merged with the manual list. This can be prevented by setting
"ignore-auto-dns". Note that if no DNS searches are configured, the
fallback will be derived from the domain from DHCP (option 15).
Format: array of string
https://networkmanager.dev/docs/api/latest/nm-settings-nmcli.html
--
It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-30 13:30 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Huzz3-1Tkx-5@gated-at.bofh.it> |
| In reply to | #262885 |
On Mon, Oct 30, 2023 at 08:19:24AM -0400, Pocket wrote: > On 10/30/23 03:54, gene heskett wrote: > > [ipv4] > > address1=192.168.71.55/24,192.168.71.1 > > dns=192.168.71.1; > > dns-search=hosts;nameserver; > > > ^^^^^^^^^^^^^^^^^^^^^ > > this is incorrect > > nmcli connection modify Network_InterfaceName ipv4.dns-search > (searchDomainname- for multiple entry you can use comma) > > That needs to be the domain you want to search ie > > home.arpa in your case > > Not the order of domain resolution, that is what /etc/nsswitch.conf is for. > > dns-search=home.arpa; Oh. Wow. We finally found out where that completely broken line in Gene's /etc/resolv.conf came from!
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-30 13:40 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuzIK-1Tnx-5@gated-at.bofh.it> |
| In reply to | #262887 |
[Multipart message — attachments visible in raw view] — view raw
On 10/30/23 08:24, Greg Wooledge wrote: > On Mon, Oct 30, 2023 at 08:19:24AM -0400, Pocket wrote: >> On 10/30/23 03:54, gene heskett wrote: >>> [ipv4] >>> address1=192.168.71.55/24,192.168.71.1 >>> dns=192.168.71.1; >>> dns-search=hosts;nameserver; >> >> ^^^^^^^^^^^^^^^^^^^^^ >> >> this is incorrect >> >> nmcli connection modify Network_InterfaceName ipv4.dns-search >> (searchDomainname- for multiple entry you can use comma) >> >> That needs to be the domain you want to search ie >> >> home.arpa in your case >> >> Not the order of domain resolution, that is what /etc/nsswitch.conf is for. >> >> dns-search=home.arpa; > Oh. Wow. We finally found out where that completely broken line in > Gene's /etc/resolv.conf came from! Sometimes I even amaze myself -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-30 17:40 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuDsZ-1VD6-3@gated-at.bofh.it> |
| In reply to | #262887 |
On 10/30/23 08:25, Greg Wooledge wrote: > On Mon, Oct 30, 2023 at 08:19:24AM -0400, Pocket wrote: >> On 10/30/23 03:54, gene heskett wrote: >>> [ipv4] >>> address1=192.168.71.55/24,192.168.71.1 >>> dns=192.168.71.1; >>> dns-search=hosts;nameserver; >> >> >> ^^^^^^^^^^^^^^^^^^^^^ >> >> this is incorrect >> >> nmcli connection modify Network_InterfaceName ipv4.dns-search >> (searchDomainname- for multiple entry you can use comma) >> >> That needs to be the domain you want to search ie >> >> home.arpa in your case >> >> Not the order of domain resolution, that is what /etc/nsswitch.conf is for. >> >> dns-search=home.arpa; > > Oh. Wow. We finally found out where that completely broken line in > Gene's /etc/resolv.conf came from! > Worse Greg, I don't ever recall editing any of that stuff, so its been like that since the 23rd or 24th bookworm install, when someone suggested I unplug all the usb stuff to do the install. That installer was busted as it did not ask me what to do, it just did it, because it found a usb-serial converter which I have two of here and just assumed I was blind! Which I was forced to do repeatedly because it would not reboot once I'd put a hot potatoe in orca's mouth and did away with brltty. So everytime I had to reboot, I had to reinstall. That and my home raid10 which worked in real time on buster, now takes 30 seconds to 5 minutes just to draw a file requestor accessing this raid10. Once that is done, it works in real time. I've repeatedly fussed about that and been ignored. Am I the only one on the planet with that problem? Access list problem or what, no one has made a single try this suggestion. But its sure a PITA to me. And you all wonder why I seem to be short tempered... Thanks Greg, take care & stay well. > . 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-30 17:20 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuD9D-1Vx6-7@gated-at.bofh.it> |
| In reply to | #262885 |
On 10/30/23 08:20, Pocket wrote: > > On 10/30/23 03:54, gene heskett wrote: >> On 10/29/23 22:17, Max Nikulin wrote: >>> On 30/10/2023 00:08, Pocket wrote: >>>> On 10/29/23 12:24, gene heskett wrote: >>>>> I have also made a very painfull attempt to change my domainname >>>>> from coyote.den to home.arpa, and finally reverted that, >>> >>> Gene, have you posted what exactly you did to switch from coyote.den >>> to home.arpa? You have been told that setting NIS domainname was a >>> wrong direction since you do not manage your hosts through NIS. >>> >>>> NetworkManager keeps updating the /etc/resolv.conf file in my >>>> opinion because it is querying the DHCP server. >>> [ ... ]> cat /etc/NetworkManager/system-connections/GREMLIN.nmconnection >>>> [ipv4] >>>> method=auto >> gene@coyote:/etc$ cat >> /etc/NetworkManager/system-connections/GREMLIN.nmconnection >> cat: /etc/NetworkManager/system-connections/GREMLIN.nmconnection: No >> such file or directory >> >> Thats this machine, but applied to the problematic machine it becomes >> sudo cat /etc/NetworkManager/system-connections/'Wired connection >> 1.nmconnection' >> which returns: >> ========== >> gene@bananapim55:/etc/systemd$ sudo cat >> /etc/NetworkManager/system-connections/'Wired connection 1.nmconnection' >> [connection] >> id=Wired connection 1 >> uuid=14621305-9887-3c6c-9e50-50894877ab68 >> type=ethernet >> autoconnect-priority=999 >> interface-name=eth0 >> timestamp=1698571927 >> >> [ethernet] >> cloned-mac-address=BE:63:9C:35:DD:4F >> duplex=full >> speed=1000 >> >> [ipv4] >> address1=192.168.71.55/24,192.168.71.1 >> dns=192.168.71.1; >> dns-search=hosts;nameserver; > > > ^^^^^^^^^^^^^^^^^^^^^ > > this is incorrect > > nmcli connection modify Network_InterfaceName ipv4.dns-search > (searchDomainname- for multiple entry you can use comma) > > That needs to be the domain you want to search ie > > home.arpa in your case > > Not the order of domain resolution, that is what /etc/nsswitch.conf is for. > > dns-search=home.arpa; > > > Please have a look at the working example I posted, That msg now tagged FFR, thank you > 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 | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-30 16:00 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuBUd-1UAO-1@gated-at.bofh.it> |
| In reply to | #262870 |
On 29/10/2023 23:24, gene heskett wrote: > finally solved by editing resolv.conf to put the nameserver address into > it, followed by a chattr +i resolv.conf. I have no d clue where mangler I have realized that it is a nice stance taking into account that the topic of the original thread was configuring DNS plugins of NetworkManager...
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-30 17:40 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuDsZ-1VD6-1@gated-at.bofh.it> |
| In reply to | #262890 |
On 10/30/23 10:57, Max Nikulin wrote: > On 29/10/2023 23:24, gene heskett wrote: >> finally solved by editing resolv.conf to put the nameserver address >> into it, followed by a chattr +i resolv.conf. I have no d clue where >> mangler > > I have realized that it is a nice stance taking into account that the > topic of the original thread was configuring DNS plugins of > NetworkManager... > > . Thank you Max. Take care and stay well. 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-27 16:40 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htwad-1f4f-1@gated-at.bofh.it> |
| In reply to | #262774 |
On 10/27/23 07:29, Pocket wrote: > > On 10/27/23 07:12, 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`. >>> >>> >>> Stefan >>> >> 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? >> >> Thanks. >> >> >> Cheers, Gene Heskett. > > > /etc/hosts > > Its in there, for this machine, but on a reboot, the domainname reverts to "none" Apparently I didn't use the approved systemd way to change it. from a cat of /etc/hosts: 192.168.71.3 coyote.home.arpa coyote Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | "Marco M." <mm@dorfdsl.de> |
|---|---|
| Date | 2023-10-27 16:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtwjT-1f7F-1@gated-at.bofh.it> |
| In reply to | #262784 |
Am 27.10.2023 um 10:37:12 Uhr schrieb gene heskett: > Its in there, for this machine, but on a reboot, the domainname > reverts to "none" Apparently I didn't use the approved systemd way to > change it. from a cat of /etc/hosts: > 192.168.71.3 coyote.home.arpa coyote That is only relevant for the name resolution, not for the name your system has.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-27 18:10 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htxzk-1g2b-9@gated-at.bofh.it> |
| In reply to | #262786 |
On 10/27/23 10:40, Marco M. wrote: > Am 27.10.2023 um 10:37:12 Uhr schrieb gene heskett: > >> Its in there, for this machine, but on a reboot, the domainname >> reverts to "none" Apparently I didn't use the approved systemd way to >> change it. from a cat of /etc/hosts: >> 192.168.71.3 coyote.home.arpa coyote > > That is only relevant for the name resolution, not for the name your > system has. > Picky, define the differemce please. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | "Marco M." <mm@dorfdsl.de> |
|---|---|
| Date | 2023-10-27 21:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtAGU-1hR6-59@gated-at.bofh.it> |
| In reply to | #262796 |
Am 27.10.2023 um 12:09:23 Uhr schrieb gene heskett: > On 10/27/23 10:40, Marco M. wrote: > > Am 27.10.2023 um 10:37:12 Uhr schrieb gene heskett: > > > >> Its in there, for this machine, but on a reboot, the domainname > >> reverts to "none" Apparently I didn't use the approved systemd way > >> to change it. from a cat of /etc/hosts: > >> 192.168.71.3 coyote.home.arpa coyote > > > > That is only relevant for the name resolution, not for the name your > > system has. > > > > Picky, define the differemce please. /etc/hostname sets the name that is being used for the prompt in your terminal, for outgoing mail (MTA uses that by default, but can be changed) and such stuff. If you don't have that in /etc/hosts, it can't be resolved to an IP address by that method. Some applications require it to work and unicast DNS is not always available and won't resolve to ::1/127.0.0.1. If you only put it in /etc/hosts, name resolution will work, but you system doesn't use that as hostname.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-27 16:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtwjT-1f7F-13@gated-at.bofh.it> |
| In reply to | #262784 |
On Fri, Oct 27, 2023 at 10:37:12AM -0400, gene heskett wrote: > Its in there, for this machine, but on a reboot, the domainname reverts to > "none" Apparently I didn't use the approved systemd way to change it. > from a cat of /etc/hosts: > 192.168.71.3 coyote.home.arpa coyote What command are you using that shows you the word "none" in its output? Please show us the shell prompt, the command, and its complete output. You wrote "domainname" with no spaces above. That happens to be the name of an NIS command, domainname(1). Are you running that? If so, then the answer is "stop running domainname". It's for NIS systems, and I don't believe you're using NIS. It's *completely normal* to get this result on a system that doesn't use NIS: unicorn:~$ domainname (none) If you were getting something *other* than this previously, then I'd say you had a misconfiguration. Unless you had experimented with NIS at some point, and had never fully expunged it.... Note that there is also a dnsdomainname(1) command, which is completely different from domainname(1). Please read the man page for it, if you think you would like to use it.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-27 18:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtxJ0-1g5b-5@gated-at.bofh.it> |
| In reply to | #262787 |
On 10/27/23 10:49, Greg Wooledge wrote: > On Fri, Oct 27, 2023 at 10:37:12AM -0400, gene heskett wrote: >> Its in there, for this machine, but on a reboot, the domainname reverts to >> "none" Apparently I didn't use the approved systemd way to change it. >> from a cat of /etc/hosts: >> 192.168.71.3 coyote.home.arpa coyote > > What command are you using that shows you the word "none" in its output? > Please show us the shell prompt, the command, and its complete output. > > You wrote "domainname" with no spaces above. That happens to be the name > of an NIS command, domainname(1). Are you running that? If so, then > the answer is "stop running domainname". It's for NIS systems, and I > don't believe you're using NIS. > > It's *completely normal* to get this result on a system that doesn't use > NIS: > Define NIS please. I've seen it before. But everybody assumes the whole planet knows every last 3 letter acronym on the planet. > unicorn:~$ domainname > (none) > > If you were getting something *other* than this previously, then I'd > say you had a misconfiguration. Unless you had experimented with NIS > at some point, and had never fully expunged it.... > > Note that there is also a dnsdomainname(1) command, which is completely > different from domainname(1). Please read the man page for it, if you > think you would like to use it. > > . 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-27 18:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtxSF-1g8r-9@gated-at.bofh.it> |
| In reply to | #262798 |
Gene writes: > Define NIS please. Network Information Service. You've never heard of it because it's obsolete. You should ignore it. <https://en.wikipedia.org/wiki/Network_Information_Service> -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-27 19:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtyF3-1gDQ-5@gated-at.bofh.it> |
| In reply to | #262799 |
On Fri, Oct 27, 2023 at 11:23:19AM -0500, John Hasler wrote: > Gene writes: > > Define NIS please. > > Network Information Service. You've never heard of it because it's > obsolete. You should ignore it. > > <https://en.wikipedia.org/wiki/Network_Information_Service> Originally known as "Yellow Pages" (YP), the name had to be changed because of trademarks. However, most of the NIS command names begin with "yp" (ypinit, ypwhich, ypset, and so on) and those never changed. For reasons unknown to me, "domainname" is one of the exceptions. Why they didn't call it "ypdomainname" or "ypdomain", I do not know. If you don't know what NIS is, that's totally fine. You obviously don't use it or need it. Even among actual NIS users, the use of NIS's hostname resolution features is *severely* deprecated. Common advice is to use NIS only for users, groups, service names, and things associated with those. For hostname resolution, you should use DNS instead. In any case, both NIS and DNS have a "domain name", but they are different and it's important not to mix them up. On systems that use both, it's common for the two domain names to be different from each other, to avoid accidents. (On some of my systems at work, the NIS domain name is "neurology" whereas the DNS domain name is "eeg.ccf.org".)
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-10-27 20:00 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtzhL-1gQi-1@gated-at.bofh.it> |
| In reply to | #262808 |
The NIS stuff should be evicted from the hostname man page. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-27 20:10 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htzrr-1h8R-13@gated-at.bofh.it> |
| In reply to | #262812 |
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.
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.
[toc] | [prev] | [next] | [standalone]
Page 10 of 13 — ← Prev page 1 … 8 9 [10] 11 12 13 Next page →
Back to top | Article view | linux.debian.user
csiph-web