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 8 of 13 — ← Prev page 1 … 6 7 [8] 9 10 … 13 Next page →
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-10-27 18:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htyc1-1gf5-1@gated-at.bofh.it> |
| In reply to | #262801 |
Erwan writes: > Here are the first lines of 'man domainname" : That doesn't help very much with no hint as to what NIS is and that it isn't relevant to DNS. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-27 19:10 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htyvn-1gAI-5@gated-at.bofh.it> |
| In reply to | #262802 |
On 27 Oct 2023 11:45 -0500, from john@sugarbit.com (John Hasler): >> Here are the first lines of 'man domainname" : > > That doesn't help very much with no hint as to what NIS is and that it > isn't relevant to DNS. The part of the beginning of that man page which Erwan didn't quote does seem a bit more helpful, though. Quoting the entire NAME section: > HOSTNAME(1) Linux Programmer's Manual HOSTNAME(1) > > NAME > hostname - show or set the system's host name > domainname - show or set the system's NIS/YP domain name > ypdomainname - show or set the system's NIS/YP domain name > nisdomainname - show or set the system's NIS/YP domain name > dnsdomainname - show the system's DNS domain name Even for someone who doesn't know what "NIS/YP" is, that should be a strong suggestion already that it is _not_ the same thing as "DNS". (And let's not get into the issue of the term "domain" in terms like _classless inter-domain routing_.) -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-27 19:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtyF3-1gDQ-1@gated-at.bofh.it> |
| In reply to | #262806 |
On 27 Oct 2023 17:02 +0000, from 2695bd53d63c@ewoof.net (Michael Kjörling): >> HOSTNAME(1) Linux Programmer's Manual HOSTNAME(1) >> >> NAME >> hostname - show or set the system's host name >> domainname - show or set the system's NIS/YP domain name >> ypdomainname - show or set the system's NIS/YP domain name >> nisdomainname - show or set the system's NIS/YP domain name >> dnsdomainname - show the system's DNS domain name > > Even for someone who doesn't know what "NIS/YP" is, that should be a > strong suggestion already that it is _not_ the same thing as "DNS". Addendum: And that even if you don't know what DNS _or_ NIS/YP is, it should be a clue that there are different things called "domain name" which don't necessarily have much if anything in common. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-27 14:00 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HttFn-1dw5-3@gated-at.bofh.it> |
| In reply to | #262774 |
On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote: > On 10/27/23 07:12, gene heskett wrote: > > 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? *What* is "all gone"? Show us commands and their output, and then explain why the output is not what you expected. > /etc/hosts If you're using short-form hostnames like this: unicorn:~$ hostname unicorn then yeah, that's all you need. If you're using long-form hostnames (with dots in them), then you also need to configure /etc/hostname. I use the short-form hostnames, so mine is simply: unicorn:~$ cat /etc/hostname unicorn Couldn't be simpler, really.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-27 17:20 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtwMV-1fwG-1@gated-at.bofh.it> |
| In reply to | #262776 |
On 10/27/23 07:50, Greg Wooledge wrote: > On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote: >> On 10/27/23 07:12, gene heskett wrote: >>> 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? > > *What* is "all gone"? Show us commands and their output, and then explain > why the output is not what you expected. > >> /etc/hosts > > If you're using short-form hostnames like this: > > unicorn:~$ hostname > unicorn > > then yeah, that's all you need. If you're using long-form hostnames > (with dots in them), then you also need to configure /etc/hostname. > > I use the short-form hostnames, so mine is simply: > > unicorn:~$ cat /etc/hostname > unicorn > > Couldn't be simpler, really. > > . You saw my hosts entry in the last post, but again 192.168.71.3 coyote.home.arpa coyote but after a reboot, domainname returns none, and the /etc/domainname file has been deleted. As in not visible to an ls of /etc. hostname works as it should. My hosts file is all long form, dotted names with a trailing alias. So I just sudo edited /etc/domainname, and entered "home.arpa\return" and wrote the flle. results: gene@coyote:/etc$ sudo nano domainnane [sudo] password for gene: gene@coyote:/etc$ domainname (none) gene@coyote:/etc$ cat domainname cat: domainname: No such file or directory now I see the typu. sudo mv to fx the files name. but even with a corrected filename visible to an ls: gene@coyote:/etc$ domainname (none) gene@coyote:/etc$ cat domainname home.arpa I'd reboot again, but that, by the time I get everything remounted and my system fully operational, takes me entering my pw about 20 times. when done I am logged into 6 other machines via an ssh -X login to each, and I've a sshfs file transfer link setup to each so mc can copy work output around. Then I can go to work. Why was the domainname I set and could see with a cat, deleted by a reboot? Seems to be the question for the day... I sure didn't delete it. But it was gone after a reboot. Seems to me there ought to be a PERMANENT way to do this. Now, even if the file exists, its ignored. 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-27 17:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtxfX-1fG6-5@gated-at.bofh.it> |
| In reply to | #262789 |
On Fri, Oct 27, 2023 at 11:13:59AM -0400, gene heskett wrote: > You saw my hosts entry in the last post, but again > 192.168.71.3 coyote.home.arpa coyote That looks fine to me. > but after a reboot, domainname returns none, and the /etc/domainname file !!!!! > So I just sudo edited /etc/domainname, and entered "home.arpa\return" and > wrote the flle. !!!!! > gene@coyote:/etc$ sudo nano domainnane > [sudo] password for gene: > gene@coyote:/etc$ domainname > (none) Gene. Please read what I'm saying. The "domainname" command is NOT FOR DNS. It's for NIS. You should not be using it. Remove the /etc/domainname file because it's just going to confuse you. You don't need one. You don't WANT one. It's for NIS. Not for DNS. Not for hosts-file-based name resolution. If your system's hostname is "coyote" -- i.e. if the "hostname" command gives you "coyote" as output -- then you're already finished. Debian reads /etc/hostname at boot time to set the hostname. This file (on this computer) should contain the word "coyote". Your /etc/hosts file contains the line posted above, which maps the hostname "coyote" to the fully qualified domain name "coyote.home.arpa". This means your DNS domain name is "home.arpa". If you run the "dnsdomainname" command, you should see "home.arpa" as output. Here's what my system's output looks like: unicorn:~$ hostname unicorn unicorn:~$ domainname (none) unicorn:~$ dnsdomainname wooledge.org And here's what yours should say: gene@coyote:/etc$ hostname coyote gene@coyote:/etc$ domainname (none) gene@coyote:/etc$ dnsdomainname home.arpa
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-27 18:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtxSF-1g8r-11@gated-at.bofh.it> |
| In reply to | #262794 |
On 10/27/23 11:43, Greg Wooledge wrote: > On Fri, Oct 27, 2023 at 11:13:59AM -0400, gene heskett wrote: >> You saw my hosts entry in the last post, but again >> 192.168.71.3 coyote.home.arpa coyote > > That looks fine to me. > >> but after a reboot, domainname returns none, and the /etc/domainname file > > !!!!! > >> So I just sudo edited /etc/domainname, and entered "home.arpa\return" and >> wrote the flle. > > !!!!! > >> gene@coyote:/etc$ sudo nano domainnane >> [sudo] password for gene: >> gene@coyote:/etc$ domainname >> (none) > > Gene. Please read what I'm saying. > > The "domainname" command is NOT FOR DNS. It's for NIS. > > You should not be using it. > > Remove the /etc/domainname file because it's just going to confuse you. > You don't need one. You don't WANT one. It's for NIS. Not for DNS. > Not for hosts-file-based name resolution. > > If your system's hostname is "coyote" -- i.e. if the "hostname" command > gives you "coyote" as output -- then you're already finished. > > Debian reads /etc/hostname at boot time to set the hostname. This file > (on this computer) should contain the word "coyote". > > Your /etc/hosts file contains the line posted above, which maps the > hostname "coyote" to the fully qualified domain name "coyote.home.arpa". > This means your DNS domain name is "home.arpa". > > If you run the "dnsdomainname" command, you should see "home.arpa" as > output. > > Here's what my system's output looks like: > > unicorn:~$ hostname > unicorn > unicorn:~$ domainname > (none) > unicorn:~$ dnsdomainname > wooledge.org > > And here's what yours should say: > > gene@coyote:/etc$ hostname > coyote > gene@coyote:/etc$ domainname > (none) > gene@coyote:/etc$ dnsdomainname > home.arpa > > . The man pages, IMO, should explain the diffs here. Historically, they do not. Leads to a lot of my confusion. 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 18:50 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Htyc1-1gf5-9@gated-at.bofh.it> |
| In reply to | #262800 |
On 10/27/23 12:26, gene heskett wrote: > On 10/27/23 11:43, Greg Wooledge wrote: >> On Fri, Oct 27, 2023 at 11:13:59AM -0400, gene heskett wrote: >>> You saw my hosts entry in the last post, but again >>> 192.168.71.3 coyote.home.arpa coyote >> >> That looks fine to me. >> >>> but after a reboot, domainname returns none, and the /etc/domainname >>> file >> >> !!!!! >> >>> So I just sudo edited /etc/domainname, and entered "home.arpa\return" >>> and >>> wrote the flle. >> >> !!!!! >> >>> gene@coyote:/etc$ sudo nano domainnane >>> [sudo] password for gene: >>> gene@coyote:/etc$ domainname >>> (none) >> >> Gene. Please read what I'm saying. >> >> The "domainname" command is NOT FOR DNS. It's for NIS. >> >> You should not be using it. >> >> Remove the /etc/domainname file because it's just going to confuse you. >> You don't need one. You don't WANT one. It's for NIS. Not for DNS. >> Not for hosts-file-based name resolution. Done. >> If your system's hostname is "coyote" -- i.e. if the "hostname" command >> gives you "coyote" as output -- then you're already finished. >> >> Debian reads /etc/hostname at boot time to set the hostname. This file >> (on this computer) should contain the word "coyote". >> >> Your /etc/hosts file contains the line posted above, which maps the >> hostname "coyote" to the fully qualified domain name "coyote.home.arpa". >> This means your DNS domain name is "home.arpa". >> >> If you run the "dnsdomainname" command, you should see "home.arpa" as >> output. >> >> Here's what my system's output looks like: >> >> unicorn:~$ hostname >> unicorn >> unicorn:~$ domainname >> (none) >> unicorn:~$ dnsdomainname >> wooledge.org >> >> And here's what yours should say: >> >> gene@coyote:/etc$ hostname >> coyote >> gene@coyote:/etc$ domainname >> (none) >> gene@coyote:/etc$ dnsdomainname >> home.arpa So this is what I get now: gene@coyote:/etc$ dnsdomainname home.arpa gene@coyote:/etc$ hostname coyote.home.arpa gene@coyote:/etc$ cat hostname coyote Is that correct and will it withstand a reboot? >> . > The man pages, IMO, should explain the diffs here. Historically, they do > not. Leads to a lot of my confusion. > Thanks Greg. 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-27 19:30 +0200 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HtyOJ-1gGT-9@gated-at.bofh.it> |
| In reply to | #262803 |
On Fri, Oct 27, 2023 at 12:46:16PM -0400, gene heskett wrote: > So this is what I get now: > gene@coyote:/etc$ dnsdomainname > home.arpa > gene@coyote:/etc$ hostname > coyote.home.arpa > gene@coyote:/etc$ cat hostname > coyote > Is that correct and will it withstand a reboot? Your hostname will go back to "coyote" at reboot, which is good, because that's what it was originally, and clearly what it's supposed to be. If you want it to go back to the original hostname without needing to reboot, you can run "sudo hostname coyote" to change it immediately.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2023-10-29 15:30 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HueXD-1GCX-9@gated-at.bofh.it> |
| In reply to | #262789 |
On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote: > You saw my hosts entry in the last post, but again > 192.168.71.3 coyote.home.arpa coyote > but after a reboot, domainname returns none, and the /etc/domainname > file has been deleted. As in not visible to an ls of /etc. hostname > works as it should. My hosts file is all long form, dotted names with > a trailing alias. > So I just sudo edited /etc/domainname, and entered "home.arpa\return" > and wrote the flle. > results: > > gene@coyote:/etc$ sudo nano domainnane > [sudo] password for gene: > gene@coyote:/etc$ domainname > (none) > gene@coyote:/etc$ cat domainname > cat: domainname: No such file or directory > now I see the typu. sudo mv to fx the files name. but even with a > corrected filename visible to an ls: > gene@coyote:/etc$ domainname > (none) > gene@coyote:/etc$ cat domainname > home.arpa > > I'd reboot again, but that, by the time I get everything remounted and > my system fully operational, takes me entering my pw about 20 times. > when done I am logged into 6 other machines via an ssh -X login to > each, and I've a sshfs file transfer link setup to each so mc can copy > work output around. Then I can go to work. > > Why was the domainname I set and could see with a cat, deleted by a > reboot? Seems to be the question for the day... I sure didn't delete > it. But it was gone after a reboot. Seems to me there ought to be a > PERMANENT way to do this. Now, even if the file exists, its ignored. I'm just wondering where this file /etc/domainname came from in the first place. I can't find it with apt-file (killing two birds): $ apt-file find etc/domain $ Neither can I find it/them in the install/remove scripts for the packages on my systems: $ grep etc/domain /var/lib/dpkg/info/* $ I don't recall ever seeing either /etc/domainname or /etc/domain in the past either, as I would have my copy backed up. /etc/domainname might be anodyne on your system, but it raises suspicions when this is meant to be a recent bookworm netinst where "I'm not doing anything the installer didn't ask me to do" (posted last week). Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-29 16:30 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HufTH-1HeV-3@gated-at.bofh.it> |
| In reply to | #262864 |
On Sun, Oct 29, 2023 at 09:22:38AM -0500, David Wright wrote: > I'm just wondering where this file /etc/domainname came from in the > first place. I can't find it with apt-file (killing two birds): > > $ apt-file find etc/domain > $ I'm assuming either Gene created it himself, because he thought he needed to, or his non-Debian installer created it, for reasons only the maintainer of said installer would know. Having that file on a non-NIS system doesn't actually hurt anything. I advised Gene to remove his in order to avoid confusion. We can all do with less of that.
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-10-29 17:00 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HugmK-1Hqc-7@gated-at.bofh.it> |
| In reply to | #262864 |
David Wright writes: > I'm just wondering where this file /etc/domainname came from in the > first place. I can't find it with apt-file (killing two birds): Gene created it, having been confused by the hostname man page. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-29 17:30 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HugPL-1HOX-7@gated-at.bofh.it> |
| In reply to | #262864 |
On 10/29/23 10:23, David Wright wrote: > On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote: > >> You saw my hosts entry in the last post, but again >> 192.168.71.3 coyote.home.arpa coyote >> but after a reboot, domainname returns none, and the /etc/domainname >> file has been deleted. As in not visible to an ls of /etc. hostname >> works as it should. My hosts file is all long form, dotted names with >> a trailing alias. >> So I just sudo edited /etc/domainname, and entered "home.arpa\return" >> and wrote the flle. >> results: >> >> gene@coyote:/etc$ sudo nano domainnane >> [sudo] password for gene: >> gene@coyote:/etc$ domainname >> (none) >> gene@coyote:/etc$ cat domainname >> cat: domainname: No such file or directory >> now I see the typu. sudo mv to fx the files name. but even with a >> corrected filename visible to an ls: >> gene@coyote:/etc$ domainname >> (none) >> gene@coyote:/etc$ cat domainname >> home.arpa >> >> I'd reboot again, but that, by the time I get everything remounted and >> my system fully operational, takes me entering my pw about 20 times. >> when done I am logged into 6 other machines via an ssh -X login to >> each, and I've a sshfs file transfer link setup to each so mc can copy >> work output around. Then I can go to work. >> >> Why was the domainname I set and could see with a cat, deleted by a >> reboot? Seems to be the question for the day... I sure didn't delete >> it. But it was gone after a reboot. Seems to me there ought to be a >> PERMANENT way to do this. Now, even if the file exists, its ignored. > > I'm just wondering where this file /etc/domainname came from in the > first place. I can't find it with apt-file (killing two birds): > > $ apt-file find etc/domain > $ > > Neither can I find it/them in the install/remove scripts for the packages > on my systems: > > $ grep etc/domain /var/lib/dpkg/info/* > $ > > I don't recall ever seeing either /etc/domainname or /etc/domain > in the past either, as I would have my copy backed up. > > /etc/domainname might be anodyne on your system, but it raises > suspicions when this is meant to be a recent bookworm netinst > where "I'm not doing anything the installer didn't ask me to do" > (posted last week). > > Cheers, > David. > You are quite right David, /etc/domainname was composed by me in nano after that was posted, I have also made a very painfull attempt to change my domainname from coyote.den to home.arpa, and finally reverted that, amoung an attack by network mangler, 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 gets the "search coyote.den" it keeps putting in resolv.conf every 45 seconds as it times out and sets it offline for 5 seconds. Maybe its not right, but it fixes it. All of the -alphabet options to hostname now work once I edited out the domainname part of /etc/hostname. IMO, giving network mangler the ability to change resolv.conf has been the single glaringly biggest headache for hosts file users in the last decade. After 3 days of screwing around with an armbian jammy on a bananapi-m5, one of many on this home network, its finally working. I had to revert to an earlier xfce desktop image to get the video to work. Then with everything looking correct, I had a net connection for 45 seconds, followed by a 5 second reset. So chattr +i to the rescue after making sure the nameserver address was in resolv.conf. And the chrome browser is still broken, it cannot look at localhost:80, hostname:80 or alias:80. It blanks that out of the address line and refills it with 250+ chars of a failure message from google %$#^@!& dns server. I had to fix my net before I could install the snap of firefox, which DOES follow the lookup rules chrome refuses to use. google. spit. I have 4 more bananapi-m5's coming, so I may be back but last post on this thread unless someone can tell me how to housebreak network mangler. I'm plumb tuckered out from mopping up its messes. Take care & stay well, 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 | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-29 18:10 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Huhst-1Ih9-17@gated-at.bofh.it> |
| In reply to | #262870 |
On 10/29/23 12:24, gene heskett wrote: > On 10/29/23 10:23, David Wright wrote: >> On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote: >> >>> You saw my hosts entry in the last post, but again >>> 192.168.71.3 coyote.home.arpa coyote >>> but after a reboot, domainname returns none, and the /etc/domainname >>> file has been deleted. As in not visible to an ls of /etc. hostname >>> works as it should. My hosts file is all long form, dotted names with >>> a trailing alias. >>> So I just sudo edited /etc/domainname, and entered "home.arpa\return" >>> and wrote the flle. >>> results: >>> > You are quite right David, /etc/domainname was composed by me in nano > after that was posted, I have also made a very painfull attempt to > change my domainname from coyote.den to home.arpa, and finally > reverted that, amoung an attack by network mangler, 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 gets the > "search coyote.den" it keeps putting in resolv.conf every 45 seconds > as it times out and sets it offline for 5 seconds. Maybe its not > right, but it fixes it. All of the -alphabet options to hostname now > work once I edited out the domainname part of /etc/hostname. IMO, > giving network mangler the ability to change resolv.conf has been the > single glaringly biggest headache for hosts file users in the last > decade. After 3 days of screwing around with an armbian jammy on a > bananapi-m5, one of many on this home network, its finally working. I > had to revert to an earlier xfce desktop image to get the video to > work. Then with everything looking correct, I had a net connection for > 45 seconds, followed by a 5 second reset. So chattr +i to the rescue > after making sure the nameserver address was in resolv.conf. NetworkManager keeps updating the /etc/resolv.conf file in my opinion because it is querying the DHCP server. After much trouble this is my current setup for what will become my new DNS, NFS and web server which BTW is running on a raspberry pi 4, with debian bookworm. Be mindful of the following NetworkManager uses this if the configuration file is not in /etc/NetworkManager/system-connections/<some name> ls /run/NetworkManager/system-connections/ 'Wired connection 1.nmconnection' lo.nmconnection My setup: cat /etc/hostname gremlin cat /etc/hosts 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters 127.0.1.1 gremlin.home.arpa gremlin cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile [ifupdown] managed=false [device] wifi.scan-rand-mac-address=no [global-dns] options=edns0 trust-ad This is for my Wireless connection, Wired has the same settings: cat /etc/NetworkManager/system-connections/GREMLIN.nmconnection [connection] id=GREMLIN uuid=49743fda-4a97-4ff4-b46a-a12a7b1383fb type=wifi interface-name=wlan0 [wifi] mode=infrastructure ssid=GREMLIN [ipv4] method=auto dns-search=home.arpa; [ipv6] addr-gen-mode=stable-privacy method=auto dns-search=home.arpa; dns=<ipv6 address of router here> ignore-auto-dns=true cat /etc/resolv.conf # Generated by NetworkManager search home.arpa nameserver 192.168.1.1 nameserver <ipv6 address of router here> options edns0 trust-ad That is all it took to get it setup on my Network. NetworkManager will populate /etc/resolv.conf using both wired and wifi connections/setup, maybe that is some of your troubles as well? I make them with the same settings Also maybe your router needs some TLC I have 4 more bananapi-m5's coming, so I may be back but last post on this thread unless someone can tell me how to housebreak network mangler. I'm plumb tuckered out from mopping up its messes. > > Take care & stay well, all. > > Cheers, Gene Heskett. -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-29 19:20 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Huiye-1ITz-15@gated-at.bofh.it> |
| In reply to | #262873 |
On 10/29/23 13:09, Pocket wrote: > > On 10/29/23 12:24, gene heskett wrote: >> On 10/29/23 10:23, David Wright wrote: >>> On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote: >>> >>>> You saw my hosts entry in the last post, but again >>>> 192.168.71.3 coyote.home.arpa coyote >>>> but after a reboot, domainname returns none, and the /etc/domainname >>>> file has been deleted. As in not visible to an ls of /etc. hostname >>>> works as it should. My hosts file is all long form, dotted names with >>>> a trailing alias. >>>> So I just sudo edited /etc/domainname, and entered "home.arpa\return" >>>> and wrote the flle. >>>> results: >>>> >> You are quite right David, /etc/domainname was composed by me in nano >> after that was posted, I have also made a very painfull attempt to >> change my domainname from coyote.den to home.arpa, and finally >> reverted that, amoung an attack by network mangler, 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 gets the >> "search coyote.den" it keeps putting in resolv.conf every 45 seconds >> as it times out and sets it offline for 5 seconds. Maybe its not >> right, but it fixes it. All of the -alphabet options to hostname now >> work once I edited out the domainname part of /etc/hostname. IMO, >> giving network mangler the ability to change resolv.conf has been the >> single glaringly biggest headache for hosts file users in the last >> decade. After 3 days of screwing around with an armbian jammy on a >> bananapi-m5, one of many on this home network, its finally working. I >> had to revert to an earlier xfce desktop image to get the video to >> work. Then with everything looking correct, I had a net connection for >> 45 seconds, followed by a 5 second reset. So chattr +i to the rescue >> after making sure the nameserver address was in resolv.conf. > > > NetworkManager keeps updating the /etc/resolv.conf file in my opinion > because it is querying the DHCP server. > > After much trouble this is my current setup for what will become my new > DNS, NFS and web server > > which BTW is running on a raspberry pi 4, with debian bookworm. > > Be mindful of the following NetworkManager uses this if the > configuration file is not in > /etc/NetworkManager/system-connections/<some name> > > ls /run/NetworkManager/system-connections/ > 'Wired connection 1.nmconnection' lo.nmconnection > > My setup: > > cat /etc/hostname > > gremlin > > cat /etc/hosts > 127.0.0.1 localhost > ::1 localhost ip6-localhost ip6-loopback > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > 127.0.1.1 gremlin.home.arpa gremlin > > cat /etc/NetworkManager/NetworkManager.conf > [main] > plugins=ifupdown,keyfile > > [ifupdown] > managed=false > > [device] > wifi.scan-rand-mac-address=no > > [global-dns] > options=edns0 trust-ad > > This is for my Wireless connection, Wired has the same settings: > > cat /etc/NetworkManager/system-connections/GREMLIN.nmconnection > [connection] > id=GREMLIN > uuid=49743fda-4a97-4ff4-b46a-a12a7b1383fb > type=wifi > interface-name=wlan0 > > [wifi] > mode=infrastructure > ssid=GREMLIN > > [ipv4] > method=auto > dns-search=home.arpa; > > [ipv6] > addr-gen-mode=stable-privacy > method=auto > dns-search=home.arpa; > dns=<ipv6 address of router here> > ignore-auto-dns=true > > cat /etc/resolv.conf > # Generated by NetworkManager > search home.arpa > nameserver 192.168.1.1 > nameserver <ipv6 address of router here> > options edns0 trust-ad > > That is all it took to get it setup on my Network. > > NetworkManager will populate /etc/resolv.conf using both wired and wifi > connections/setup, maybe that is some of your troubles as well? > > I make them with the same settings Finally some info worth checking out and putting on dead tree. > > Also maybe your router needs some TLC possibly, its a Buffalo Netfinity with a now elderly dd-wrt reflash, and whose pw I've long since forgot, and its 30 chars of random gibberish IIRC. So I'll have to start with the long reset to factory, which was easy because the old asus mobo had two net plugs, but this one only has one. I have a spare router whose mac has been cloned that can be used in a pinch, but will need to get a usb to net dongle first. With a ups and auto stand by here, its not even been rebooted in years. What can I say? As a guard dog its sharp teeth have been 100% effective so I haven't had an excuse to log into it since I turned off the radio about 5 years ago to keep a neighbors phone from using 80GB a month to watch porn. I could probably turn the radio back on, he spent some time in jail for mail nondelivery, and his woman thru him out when he got out, so he and his hacked phone are no longer neighbors. Found a dongle. Bought it. Be here Tuesday. And this time around, I'll set a pw and write it down. ;o)> > > > I have 4 more bananapi-m5's coming, so I may be back but last post on > this thread unless someone can tell me how to housebreak network > mangler. I'm plumb tuckered out from mopping up its messes. >> >> Take care & stay well, all. >> >> 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 | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-10-29 19:40 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuiRz-1J0R-5@gated-at.bofh.it> |
| In reply to | #262874 |
Gene writes: > possibly, its a Buffalo Netfinity with a now elderly dd-wrt reflash, > and whose pw I've long since forgot, and its 30 chars of random > gibberish IIRC. Write the password on the router. Write all your passwords down. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-30 03:20 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <Huq2J-1Nug-1@gated-at.bofh.it> |
| In reply to | #262873 |
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 has no DHCP server, so it should be method=manual. Frankly speaking, I see almost no advantages of NetworkManager over ifupdown in a purely static network. E.g. cable plug/unplug events should not matter since there is no need to update configuration in response.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-30 09:00 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuvlL-1QHG-1@gated-at.bofh.it> |
| In reply to | #262879 |
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; ignore-auto-routes=true may-fail=false method=manual route1=192.168.71.1/24,192.168.71.1 [ipv6] addr-gen-mode=stable-privacy method=disabled [proxy] ======== All of which now looks totally legit once /etc/resolv.conf was made immutable. As an aside, I have yet to see a complaint from modern NM when it finds that file cannot be changed. When it was new, many generations ago, it had a cow quite regularly. Then the only way to clean up the logs was to rm the executable. It, when new, was not removable by apt as it took the rest of the system with it. So I've always looked at NM as something looking for a problem I didn't have. A Karen to be removed by whatever means worked. A root rm usually solved it all. So for me, its still, in the year of our lord 2023, a PITA. A hosts file for local lookups, with anything not found there forwarded to my ISP's dns server is all I've ever needed. And it has not changed in 25 years. To me, dhcp is a total waste of cpu cycles. > > Gene has no DHCP server, so it should be method=manual. Frankly > speaking, I see almost no advantages of NetworkManager over ifupdown in > a purely static network. E.g. cable plug/unplug events should not matter > since there is no need to update configuration in response. > > . 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 | Timothy M Butterworth <timothy.m.butterworth@gmail.com> |
|---|---|
| Date | 2023-10-30 10:20 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuwBb-1RCA-1@gated-at.bofh.it> |
| In reply to | #262882 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, Oct 30, 2023 at 3:55 AM gene heskett <gheskett@shentel.net> 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; > ignore-auto-routes=true > may-fail=false > method=manual > route1=192.168.71.1/24,192.168.71.1 > Try adding ignore-auto-dns=true with this setting you should not need to make resolv.conf immutable. You may also want to add a default gateway route. > [ipv6] > addr-gen-mode=stable-privacy > method=disabled > > [proxy] > ======== > All of which now looks totally legit once /etc/resolv.conf was made > immutable. As an aside, I have yet to see a complaint from modern NM > when it finds that file cannot be changed. When it was new, many > generations ago, it had a cow quite regularly. Then the only way to > clean up the logs was to rm the executable. It, when new, was not > removable by apt as it took the rest of the system with it. So I've > always looked at NM as something looking for a problem I didn't have. A > Karen to be removed by whatever means worked. A root rm usually solved > it all. So for me, its still, in the year of our lord 2023, a PITA. A > hosts file for local lookups, with anything not found there forwarded to > my ISP's dns server is all I've ever needed. And it has not changed in > 25 years. To me, dhcp is a total waste of cpu cycles. > > > > Gene has no DHCP server, so it should be method=manual. Frankly > > speaking, I see almost no advantages of NetworkManager over ifupdown in > > a purely static network. E.g. cable plug/unplug events should not matter > > since there is no need to update configuration in response. > > > > . > > 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 > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-30 17:10 +0100 |
| Subject | Re: Domain name to use on home networks |
| Message-ID | <HuCZX-1Vu3-1@gated-at.bofh.it> |
| In reply to | #262884 |
On 10/30/23 05:15, Timothy M Butterworth wrote: > > > On Mon, Oct 30, 2023 at 3:55 AM gene heskett <gheskett@shentel.net > <mailto:gheskett@shentel.net>> 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 > <http://192.168.71.55/24,192.168.71.1> > dns=192.168.71.1; > dns-search=hosts;nameserver; > ignore-auto-routes=true > may-fail=false > method=manual > route1=192.168.71.1/24,192.168.71.1 > <http://192.168.71.1/24,192.168.71.1> > > > Try adding ignore-auto-dns=true with this setting you should not need to > make resolv.conf immutable. You may also want to add a default gateway > route. Thank you Timothy, I appreciate the advice and the msg is tagged FFR, but I've no clue as to the "proper" way to edit that. Making resolv.conf immutable seems to be the way to permanently insulate me from NM's broken idea of whats right. Gateway is set in the edit pulldown that opens from the status icon at the top right corner of the screen. Which works but upsets me because it has no "about" info anyplace to identify the src of that whole shebang. And as I explained in another post, I can't file bugzilla stuff. And I am not seeing anything indicating there is a way to fix that. IOW, nobody cares. > > [ipv6] > addr-gen-mode=stable-privacy > method=disabled > > [proxy] > ======== > All of which now looks totally legit once /etc/resolv.conf was made > immutable. As an aside, I have yet to see a complaint from modern NM > when it finds that file cannot be changed. When it was new, many > generations ago, it had a cow quite regularly. Then the only way to > clean up the logs was to rm the executable. It, when new, was not > removable by apt as it took the rest of the system with it. So I've > always looked at NM as something looking for a problem I didn't > have. A > Karen to be removed by whatever means worked. A root rm usually solved > it all. So for me, its still, in the year of our lord 2023, a PITA. A > hosts file for local lookups, with anything not found there > forwarded to > my ISP's dns server is all I've ever needed. And it has not changed in > 25 years. To me, dhcp is a total waste of cpu cycles. > > > > Gene has no DHCP server, so it should be method=manual. Frankly > > speaking, I see almost no advantages of NetworkManager over > ifupdown in > > a purely static network. E.g. cable plug/unplug events should not > matter > > since there is no need to update configuration in response. > > > > . > > 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 > > > > -- > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ <https://www.debian.org/> > ⠈⠳⣄⠀⠀ Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
Page 8 of 13 — ← Prev page 1 … 6 7 [8] 9 10 … 13 Next page →
Back to top | Article view | linux.debian.user
csiph-web