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 1 of 13 [1] 2 3 … 13 Next page →
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-21 18:40 +0200 |
| Subject | Bookworm: NetworkManager |
| Message-ID | <Hrnb4-hs5G-13@gated-at.bofh.it> |
I want NetworkManager to not over write /etc/resolv.conf According to the docs if dns=none is set it will not touch /etc/resolv.conf This is what I need /etc/resolv.conf to be (I have bind on the machine) domain example.org nameserver 127.0.0.1 options edns0 trust-ad First Go at this This is conf.d/dns.conf [main] dns=none rc-manager=unmanaged [global-dns] searches= example.org options=edns0 trust-ad Did not work, it still overwrote /etc/resolv.conf on booting So I then edited NetworkManager.conf as follows after restoring /etc/resolv.conf to what I need [main] plugins=ifupdown,keyfile dns=none [ifupdown] managed=false [device] wifi.scan-rand-mac-address=no And it still over writes /etc/resolv.conf on booting/rebooting cat /etc/resolv.conf # Generated by NetworkManager search example.org search.charter.com columbus.rr.com nameserver 192.168.1.6 nameserver 192.168.1.1 Is there something I am over looking? -- It's not easy to be me
[toc] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-21 18:50 +0200 |
| Message-ID | <HrnkJ-hs93-1@gated-at.bofh.it> |
| In reply to | #262472 |
On Sat, Oct 21, 2023 at 12:23:45PM -0400, Pocket wrote: > I want NetworkManager to not over write /etc/resolv.conf https://wiki.debian.org/resolv.conf
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-21 19:10 +0200 |
| Message-ID | <HrnE6-hsvx-7@gated-at.bofh.it> |
| In reply to | #262473 |
On 10/21/23 12:49, Greg Wooledge wrote: > On Sat, Oct 21, 2023 at 12:23:45PM -0400, Pocket wrote: >> I want NetworkManager to not over write /etc/resolv.conf > https://wiki.debian.org/resolv.conf > openresolv or resolvconf is not installed no dhcp client is running only networkmanager is installed/running making /etc/resolv.conf immutable is not the answer -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-21 19:30 +0200 |
| Message-ID | <HrnXr-hsC3-1@gated-at.bofh.it> |
| In reply to | #262474 |
On Sat, Oct 21, 2023 at 01:08:58PM -0400, Pocket wrote: > > On 10/21/23 12:49, Greg Wooledge wrote: > > On Sat, Oct 21, 2023 at 12:23:45PM -0400, Pocket wrote: > > > I want NetworkManager to not over write /etc/resolv.conf > > https://wiki.debian.org/resolv.conf > > > openresolv or resolvconf is not installed > > no dhcp client is running only networkmanager is installed/running > > making /etc/resolv.conf immutable is not the answer If you're asking us to tell you how to *make NetWorkManager behave* then you might be frustrated. Most of the people on this mailing list don't use it. There are some who actively despise it, and go out of their way to ensure it's never installed. (Those people are a small minority, but they're definitely here.) So, in all likelihood, nobody here might know that answer. If you believe NM is not behaving according to its documentation, then file a bug report. If you want to *solve your problem* then I've offered you the only answers I know. So I guess you get to decide whether you'd prefer to solve your problem, or battle the injustices of the world as you perceive them.
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-21 19:40 +0200 |
| Message-ID | <Hro77-hsFk-1@gated-at.bofh.it> |
| In reply to | #262476 |
On 10/21/23 13:24, Greg Wooledge wrote: > On Sat, Oct 21, 2023 at 01:08:58PM -0400, Pocket wrote: >> On 10/21/23 12:49, Greg Wooledge wrote: >>> On Sat, Oct 21, 2023 at 12:23:45PM -0400, Pocket wrote: >>>> I want NetworkManager to not over write /etc/resolv.conf >>> https://wiki.debian.org/resolv.conf >>> >> openresolv or resolvconf is not installed >> >> no dhcp client is running only networkmanager is installed/running >> >> making /etc/resolv.conf immutable is not the answer > If you're asking us to tell you how to *make NetWorkManager behave* > then you might be frustrated. Most of the people on this mailing list > don't use it. There are some who actively despise it, and go out of > their way to ensure it's never installed. (Those people are a small > minority, but they're definitely here.) So, in all likelihood, nobody > here might know that answer. Well the default install for bookworm does install it and use it. That is why I am here. > > If you believe NM is not behaving according to its documentation, then > file a bug report. That may be what I do but I want to be sure that it is the fault of networkmanager or there is a better fix before I file a bug report > > If you want to *solve your problem* then I've offered you the only > answers I know. It is my opinion is that information is old and not valid for bookworm > > So I guess you get to decide whether you'd prefer to solve your problem, > or battle the injustices of the world as you perceive them. I am not battling or in conflict with any one. -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-21 20:00 +0200 |
| Message-ID | <Hroqt-hsMq-1@gated-at.bofh.it> |
| In reply to | #262477 |
On Sat, Oct 21, 2023 at 01:38:37PM -0400, Pocket wrote: > Well the default install for bookworm does install it and use it. > > That is why I am here. There's no single "default install". Sure, if you just hit the Enter key straight through an install you end up with GNOME, and also with NM. But if you *don't* install GNOME (or any desktop environment) then you also don't get NM. NM is not the default in a "Standard" install (Standard being the name of a specific package set in the tasksel dialog). Only in desktop installs. The regulars on this mailing list skew toward people who do not use desktop environments. Therefore, we don't possess a lot of knowledge about NM. > > If you want to *solve your problem* then I've offered you the only > > answers I know. > > It is my opinion is that information is old and not valid for bookworm Feel free to correct whatever you believe needs correcting. That's what a wiki is, after all. Do you have a specific example of an incorrect statement on that page? > I am not battling or in conflict with any one. Then why do you reject *all* the answers? sudo -s apt-get install openresolv echo resolvconf=NO >> /etc/resolvconf.conf exit
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-21 20:10 +0200 |
| Message-ID | <HroA9-ht66-25@gated-at.bofh.it> |
| In reply to | #262478 |
On 10/21/23 13:55, Greg Wooledge wrote: > On Sat, Oct 21, 2023 at 01:38:37PM -0400, Pocket wrote: >> Well the default install for bookworm does install it and use it. >> >> That is why I am here. > There's no single "default install". Sure, if you just hit the Enter > key straight through an install you end up with GNOME, and also with NM. > But if you *don't* install GNOME (or any desktop environment) then you > also don't get NM. I did not install a GUI and I am working on a minimal install and nm was installed along with isc-dhcp and wpa_supplicant > > NM is not the default in a "Standard" install (Standard being the name > of a specific package set in the tasksel dialog). Only in desktop > installs. The regulars on this mailing list skew toward people who do > not use desktop environments. Therefore, we don't possess a lot of > knowledge about NM. > >>> If you want to *solve your problem* then I've offered you the only >>> answers I know. >> It is my opinion is that information is old and not valid for bookworm > Feel free to correct whatever you believe needs correcting. That's what > a wiki is, after all. Do you have a specific example of an incorrect > statement on that page? Well it doesn't work or of little value if you don't have openresolv or resolvconf installed > >> I am not battling or in conflict with any one. > Then why do you reject *all* the answers? > > sudo -s > apt-get install openresolv > echo resolvconf=NO >> /etc/resolvconf.conf > exit I didn't, I am only trying to work with nm on a non desktop install. -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-22 10:10 +0200 |
| Message-ID | <HrBH3-xO-1@gated-at.bofh.it> |
| In reply to | #262476 |
On 22/10/2023 00:24, Greg Wooledge wrote:
> If you're asking us to tell you how to *make NetWorkManager behave* then
> you might be frustrated. Most of the people on this mailing list don't
> use it. There are some who actively despise it, and go out of their way
> to ensure it's never installed.
I just have tried with
/etc/NetworkManager/conf.d/90-disable-resovl.conf
[main]
dns=none
in a VM and it just works. I edited /etc/resolv.conf and NetworkManager
does not override it. I have no idea what is wrong in Pocket's case,
perhaps a typo or another config file with higher priority. I would check
NetworkManager --print-config
This particular instance was installed as bullseye in minimal
configuration. NetworkManager was added later and enp0s2 originally was
managed by ifupdown. I edited /etc/network/interfaces to allow
NetworkManager to take control of it. Later it was upgraded to bookworm.
Overriding DNS servers for each connection is another viable approach.
I admit that NetworkManager has issues and limitations, its GUI applets
have even more bugs and expose quite limited set of preferences, but
this tool still works in simple cases and convenient in the case of laptops.
P.S. I do not see any reason to insist on NetworkManager in the case of
a box which role is a DNS server for a local network. ifupdown should be
sufficient. There is no need to detect cable plug/unplug events, to
switch between connection configurations depending on current location
or other circumstances.
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-22 14:30 +0200 |
| Message-ID | <HrFKF-2YK-3@gated-at.bofh.it> |
| In reply to | #262510 |
On 10/22/23 04:02, Max Nikulin wrote: > On 22/10/2023 00:24, Greg Wooledge wrote: >> If you're asking us to tell you how to *make NetWorkManager behave* >> then you might be frustrated. Most of the people on this mailing list >> don't use it. There are some who actively despise it, and go out of >> their way to ensure it's never installed. > > I just have tried with > > /etc/NetworkManager/conf.d/90-disable-resovl.conf > > [main] > dns=none > > in a VM and it just works. I edited /etc/resolv.conf and > NetworkManager does not override it. I have no idea what is wrong in > Pocket's case, perhaps a typo or another config file with higher > priority. I would check What version of NetworkManager is installed with bullseye? Maybe a newer version is broken? > > NetworkManager --print-config Didn't show me anything unexpected. > > This particular instance was installed as bullseye in minimal > configuration. NetworkManager was added later and enp0s2 originally > was managed by ifupdown. I edited /etc/network/interfaces to allow > NetworkManager to take control of it. Later it was upgraded to bookworm. > > Overriding DNS servers for each connection is another viable approach. > > I admit that NetworkManager has issues and limitations, its GUI > applets have even more bugs and expose quite limited set of > preferences, but this tool still works in simple cases and convenient > in the case of laptops. > > P.S. I do not see any reason to insist on NetworkManager in the case > of a box which role is a DNS server for a local network. ifupdown > should be sufficient. There is no need to detect cable plug/unplug > events, to switch between connection configurations depending on > current location or other circumstances. I would normally not use NetworkManager on a server system either, but in this case NetworkManager is installed on all the bookworm installation so in this case I choose to work with it instead of removing it. -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-22 14:50 +0200 |
| Message-ID | <HrG41-35U-7@gated-at.bofh.it> |
| In reply to | #262520 |
On 10/22/23 08:36, mick.crane wrote: > On 2023-10-22 13:22, Pocket wrote: > <snipped> >> I would normally not use NetworkManager on a server system either, but >> in this case NetworkManager is installed on all the bookworm >> installation so in this case I choose to work with it instead of >> removing it. > > It maybe comes with the desktop thing. > With Bookworm I selected xfce only and network-manager was installed. > Out of interest I put static address in /etc/network/interfaces > and purged network-manager and network-manager-gnome. > and seemed happy. > > mick > In my case no desktop is installed on this particular system that I want to use as a server. I have no idea what pulled NetworkManager in and really don't want to find out. All I know is that the script I use to install debian causes it to be pulled in, so in this case I chose to use what was installed rather than to rip it out and put something else in it's place. I used the same script for bullseye and it has ifupdown and dhcpcd. Go figure? -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2023-10-22 15:20 +0200 |
| Message-ID | <HrGx3-3vK-7@gated-at.bofh.it> |
| In reply to | #262520 |
On 22 Oct 2023 08:22 -0400, from pocket@columbus.rr.com (Pocket): > What version of NetworkManager is installed with bullseye? https://packages.debian.org/bullseye/network-manager https://tracker.debian.org/network-manager -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-22 18:50 +0200 |
| Message-ID | <HrJOh-5pK-3@gated-at.bofh.it> |
| In reply to | #262520 |
On 22/10/2023 19:22, Pocket wrote:
> What version of NetworkManager is installed with bullseye?
>
> Maybe a newer version is broken?
I upgraded this VM to bookworm months ago.
apt policy network-manager
network-manager:
Installed: 1.42.4-1
Candidate: 1.42.4-1
Version table:
*** 1.42.4-1 500
500 http://deb.debian.org/debian bookworm/main amd64 Packages
100 /var/lib/dpkg/status
My point was that it required some efforts to get an ethernet card be
controlled by NetworkManager. Due to deprecation of isc-dhcp-client
things may change in bookworm, but I do not see anything suspicious in
output of "apt-cache showpkg network-manager".
I am curious which package pulled network-manager in your case
aptitude why network-manager
or
apt list '?narrow(~i,
~DRecommends:~n^network-manager$|~D~n^network-manager$)'
In my case it is recommended by plasma-desktop.
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-22 19:50 +0200 |
| Message-ID | <HrKKl-60o-1@gated-at.bofh.it> |
| In reply to | #262541 |
Because the script does what the Debian installer does and runs without intervention Sent from my iPad > On Oct 22, 2023, at 12:41 PM, Max Nikulin <manikulin@gmail.com> wrote: > > On 22/10/2023 19:22, Pocket wrote: >> What version of NetworkManager is installed with bullseye? >> Maybe a newer version is broken? > > I upgraded this VM to bookworm months ago. > > apt policy network-manager > > network-manager: > Installed: 1.42.4-1 > Candidate: 1.42.4-1 > Version table: > *** 1.42.4-1 500 > 500 http://deb.debian.org/debian bookworm/main amd64 Packages > 100 /var/lib/dpkg/status > > My point was that it required some efforts to get an ethernet card be controlled by NetworkManager. Due to deprecation of isc-dhcp-client things may change in bookworm, but I do not see anything suspicious in output of "apt-cache showpkg network-manager". > > I am curious which package pulled network-manager in your case > > aptitude why network-manager > > or > > apt list '?narrow(~i, ~DRecommends:~n^network-manager$|~D~n^network-manager$)' > > In my case it is recommended by plasma-desktop. >
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2023-10-22 19:40 +0200 |
| Message-ID | <HrKAF-5WX-23@gated-at.bofh.it> |
| In reply to | #262520 |
Hello, On Sun, Oct 22, 2023 at 08:22:24AM -0400, Pocket wrote: > On 10/22/23 04:02, Max Nikulin wrote: > > P.S. I do not see any reason to insist on NetworkManager in the case of > > a box which role is a DNS server for a local network. ifupdown should be > > sufficient. There is no need to detect cable plug/unplug events, to > > switch between connection configurations depending on current location > > or other circumstances. > > I would normally not use NetworkManager on a server system either, but in > this case NetworkManager is installed on all the bookworm installation so in > this case I choose to work with it instead of removing it. That's a reasonable choice but it is a choice you've made. NetworkManager isn't any sort of default on Debian; it's a dependency pulled in by something in your install script, so it's just another choice you've made even if not explicitly. There is no compelling reason why you should stick with NetworkManager unless you want to or it's a hard dependency of something else. If not then it would be fine to remove it and achieve the same configuration in a simpler way with ifupdown, netplan or systemd-networkd directly. A lot of people would consider that a simpler and therefore more desirable setup if NetworkManager was not otherwise required. I realise that all this has been pointed out already in this thread, but again here you've stated that NetworkManager is some sort of default for Debian and that the implication as such is that it should be worked with rather than removed. One is by no means straying from the "main sequence" of Debian by removing NetworkManager where no dependency exists. I'm glad you have worked with it though, in order to find a solution for the problem you were having, and communicated that with us. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-22 20:00 +0200 |
| Message-ID | <HrKU1-63W-3@gated-at.bofh.it> |
| In reply to | #262550 |
Sent from my iPad > On Oct 22, 2023, at 1:35 PM, Andy Smith <andy@strugglers.net> wrote: > > Hello, > >> On Sun, Oct 22, 2023 at 08:22:24AM -0400, Pocket wrote: >>> On 10/22/23 04:02, Max Nikulin wrote: >>> P.S. I do not see any reason to insist on NetworkManager in the case of >>> a box which role is a DNS server for a local network. ifupdown should be >>> sufficient. There is no need to detect cable plug/unplug events, to >>> switch between connection configurations depending on current location >>> or other circumstances. >> >> I would normally not use NetworkManager on a server system either, but in >> this case NetworkManager is installed on all the bookworm installation so in >> this case I choose to work with it instead of removing it. > > That's a reasonable choice but it is a choice you've made. > NetworkManager isn't any sort of default on Debian; it's a > dependency pulled in by something in your install script, so it's > just another choice you've made even if not explicitly. > > There is no compelling reason why you should stick with > NetworkManager unless you want to or it's a hard dependency of > something else. If not then it would be fine to remove it and > achieve the same configuration in a simpler way with ifupdown, > netplan or systemd-networkd directly. A lot of people would consider > that a simpler and therefore more desirable setup if NetworkManager > was not otherwise required. > The reason is that with my default installation I can create a server or desktop from the same base. I have scripts that after a basic install make me a new server or desktop. NetworkManager is installed somehow in that base install and then it becomes common so rather than having two different ways of bringing up the network I just have one and it just happened to be NetworkManager. I would have ok if Systemd networking would have been the common way as well. I have used the ifupdown with dhcpcd and Systemd networking in the past. The is my first go with NetworkManger > I realise that all this has been pointed out already in this thread, > but again here you've stated that NetworkManager is some sort of > default for Debian and that the implication as such is that it > should be worked with rather than removed. One is by no means > straying from the "main sequence" of Debian by removing > NetworkManager where no dependency exists. > > I'm glad you have worked with it though, in order to find a solution > for the problem you were having, and communicated that with us. > > Thanks, > Andy > > -- > https://bitfolk.com/ -- No-nonsense VPS hosting >
[toc] | [prev] | [next] | [standalone]
| From | Henning Follmann <hfollmann@itcfollmann.com> |
|---|---|
| Date | 2023-10-22 17:10 +0200 |
| Message-ID | <HrIfv-4C7-7@gated-at.bofh.it> |
| In reply to | #262476 |
On Sat, Oct 21, 2023 at 01:24:21PM -0400, Greg Wooledge wrote: > On Sat, Oct 21, 2023 at 01:08:58PM -0400, Pocket wrote: > > > > On 10/21/23 12:49, Greg Wooledge wrote: > > > On Sat, Oct 21, 2023 at 12:23:45PM -0400, Pocket wrote: > > > > I want NetworkManager to not over write /etc/resolv.conf > > > https://wiki.debian.org/resolv.conf > > > > > openresolv or resolvconf is not installed > > > > no dhcp client is running only networkmanager is installed/running > > Well, NM is a dhcp client, technically. > > making /etc/resolv.conf immutable is not the answer > > If you're asking us to tell you how to *make NetWorkManager behave* > then you might be frustrated. Most of the people on this mailing list > don't use it. There are some who actively despise it, and go out of > their way to ensure it's never installed. (Those people are a small > minority, but they're definitely here.) So, in all likelihood, nobody > here might know that answer. Well, that is not true. I think for a desktop NM is the right tool for most users. Some of these statements are based of past issues which mostly are resolved these days. > > If you believe NM is not behaving according to its documentation, then > file a bug report. Yes true, But I would assume that the initial question points to the real problem here. I assume you have some special requirments for your DNS resolver and you just put specific dns resolver in your /etc/resolcv.conf There might be better ways with NM to manually specify your dns server. Each network connection stanza can be individually configured based on your location requirements. I would look into the documentation to solve the issue the "NM way" and not come up with some hack and then fight the NM. -H -- Henning Follmann | hfollmann@itcfollmann.com
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-22 18:30 +0200 |
| Message-ID | <HrJuV-5iG-7@gated-at.bofh.it> |
| In reply to | #262532 |
On 10/22/23 11:02, Henning Follmann wrote: > On Sat, Oct 21, 2023 at 01:24:21PM -0400, Greg Wooledge wrote: >> On Sat, Oct 21, 2023 at 01:08:58PM -0400, Pocket wrote: >>> >>> On 10/21/23 12:49, Greg Wooledge wrote: >>>> On Sat, Oct 21, 2023 at 12:23:45PM -0400, Pocket wrote: >>>>> I want NetworkManager to not over write /etc/resolv.conf >>>> https://wiki.debian.org/resolv.conf >>>> >>> openresolv or resolvconf is not installed >>> >>> no dhcp client is running only networkmanager is installed/running >>> > > Well, NM is a dhcp client, technically. > >>> making /etc/resolv.conf immutable is not the answer >> >> If you're asking us to tell you how to *make NetWorkManager behave* >> then you might be frustrated. Most of the people on this mailing list >> don't use it. There are some who actively despise it, and go out of >> their way to ensure it's never installed. (Those people are a small >> minority, but they're definitely here.) So, in all likelihood, nobody >> here might know that answer. > > Well, that is not true. I think for a desktop NM is the right tool for most > users. > Some of these statements are based of past issues which mostly are > resolved these days. > >> >> If you believe NM is not behaving according to its documentation, then >> file a bug report. I did that decades ago, and was ignored. I don't even have the bugzilla number cuz of seagates crappy 2T drives failing in a month taking first my backups, then then a couple days later the main drive in this machine, forcing a bookworm install that took 22 damned installs to get rid of orca and brltty cuz the installer found a serial-usb adaptor and assumed I was blind. They are used for a lot of ups's and for X10 stuff that have nothing to do with hearing loss. > > Yes true, > > But I would assume that the initial question points to the real problem > here. > > I assume you have some special requirments for your DNS resolver and you > just put specific dns resolver in your /etc/resolcv.conf > You all have given me a hard time over this, but I have a nearly 35 year history with hosts files which work for such as my home network at an address block 192.168.nnn.nnn that is not relayed thru a router. So that means my whole network is not net accessible without NAT in the router which has been running dd-wrt forever. My whole home net has no dhcp server, host files do it all. NM, and avahi, seems to want to assign a default route in the 169 block if it cannot find a dns server, but until recently that default route has been the biggest PITA ever foisted of on us linux users. You cannot get out of your T-shirt pocket for any reason, and getting rid of it seems to be a big secret, no one has yet answered. So we put a nameserver address pointing to the routers local address in resolv.conf and quickly make it immutable before NM has a chance to screw it up. Then a suitable entry in /e/n/interfaces usually results in a ping -c1 yahoo.com that just works. NM's purpose seems to be is to jump thru dhcp hoops a host file user does not need, so I put the router as a default nameserver in /etc/resolv.conf and make it immutable, which router I think is running dnsmasq, so if the name isn't cached there, dnsmasq forwards the request to my isp's server which is supposedly up to date. I can ping any named & registered site on this ball of rock and water, usually in less than 30 milliseconds unless its to Ulan Bator. IF I can prevent NM and avahi from assigning a totally bogus 169. route, it just works. Until that stops, neither is welcome for the initial install on my premises. Once I have networking working, then cups might need avahi. but _NOT_ before the rest of my network is up and running. And every machine on my local net can browse the world with FF. So please tell me again what NM is supposed to do for /me/? Thank you. > There might be better ways with NM to manually specify your dns server. > > > Each network connection stanza can be individually configured based on your > location requirements. I would look into the documentation to solve the > issue the "NM way" and not come up with some hack and then fight the NM. > > -H > Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2023-10-22 20:40 +0200 |
| Message-ID | <HrLwJ-6xU-9@gated-at.bofh.it> |
| In reply to | #262539 |
gene heskett wrote: > > So please tell me again what NM is supposed to do for /me/? Nothing, You do not have a good use case for NM. NM is for laptops that connect to many different networks, primarily, and secondarily for corporate networks where many people will need IT handholding. In my personal opinion, of course. -dsr-
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-24 18:50 +0200 |
| Message-ID | <HssLn-yCN-1@gated-at.bofh.it> |
| In reply to | #262539 |
On 22/10/2023 23:29, gene heskett wrote: > My whole home net has no > dhcp server, host files do it all. > > NM, and avahi, seems to want to assign a default route in the 169 block > if it cannot find a dns server, [...] > IF I can prevent NM and avahi > from assigning a totally bogus 169. route, it just works. NetworkManager supports static network configuration and it has been working for years. Of course, by default it tries to get configuration from a DHCP server. A connection with a static address may be created even from GUI. There was a thread several months ago with discussion of link local 169.254.x.y addresses. They may coexist with dynamic or static IP addresses. avahi-autoipd (avahi is another daemon) just tries to make at least some network resources available for you. It is not a fault of avahi-autoipd or NetworkManager that your configuration expects DHCP response on a network where static addresses are used.
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-24 19:30 +0200 |
| Message-ID | <Hsto5-z5R-5@gated-at.bofh.it> |
| In reply to | #262677 |
On 10/24/23 12:48, Max Nikulin wrote: > On 22/10/2023 23:29, gene heskett wrote: >> My whole home net has no dhcp server, host files do it all. >> >> NM, and avahi, seems to want to assign a default route in the 169 >> block if it cannot find a dns server, > [...] >> IF I can prevent NM and avahi from assigning a totally bogus 169. >> route, it just works. > > NetworkManager supports static network configuration and it has been > working for years. > > Of course, by default it tries to get configuration from a DHCP > server. A connection with a static address may be created even from GUI. > > There was a thread several months ago with discussion of link local > 169.254.x.y addresses. They may coexist with dynamic or static IP > addresses. avahi-autoipd (avahi is another daemon) just tries to make > at least some network resources available for you. It is not a fault > of avahi-autoipd or NetworkManager that your configuration expects > DHCP response on a network where static addresses are used. > Where may I find that thread? I would like to read it Thanks -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
Page 1 of 13 [1] 2 3 … 13 Next page →
Back to top | Article view | linux.debian.user
csiph-web