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 3 of 13 — ← Prev page 1 2 [3] 4 5 … 13 Next page →
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2023-11-02 19:00 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvK93-2Dxy-9@gated-at.bofh.it> |
| In reply to | #263048 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Nov 02, 2023 at 10:41:06PM +0700, Max Nikulin wrote: > On 02/11/2023 00:44, tomas@tuxteam.de wrote: > > On Wed, Nov 01, 2023 at 10:00:45PM +0700, Max Nikulin wrote: > > > > > > Doesn't allow-hotplug means adding a network adapter (e.g. a USB one), not > > > plugging network cable into an existing adapter (built-in or connected > > > earlier)? > > > > Following the man page (interfaces (5)) you are right, of course. In > > theory, however, since things are kicked off by an udev rule (i.e. > > udev calling some command) it shouldn't be too hard (TM) to wire up > > things, provided you've a monitor which tells you when an eth has > > carrier. > > I am unsure if it is exposed as a udev event or it is necessary to receive > messages from netlink socket. Now I know. No udev -- so one would have to "wire it up". > I am a bit surprised by a use case when temporary unplugging of cable should > be ignored. I have not tested it, but I hope, a setting, I have noticed in > docs, allows NetworkManager to handle it as well. TCP/IP can take that. Retransmit and things. Only after a (usually generous) timeout the application layer notices. Which has upsides and downsides, of course :-) Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-11-03 16:50 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <Hw4AN-2RGx-1@gated-at.bofh.it> |
| In reply to | #263054 |
On 03/11/2023 00:58, tomas@tuxteam.de wrote: > On Thu, Nov 02, 2023 at 10:41:06PM +0700, Max Nikulin wrote: > >> I am a bit surprised by a use case when temporary unplugging of cable should >> be ignored. I have not tested it, but I hope, a setting, I have noticed in >> docs, allows NetworkManager to handle it as well. > > TCP/IP can take that. Retransmit and things. Only after a (usually generous) > timeout the application layer notices. Which has upsides and downsides, of > course :-) TCP/IP is another level. E.g. ssh connection may survive after sleep during several minutes and wake up. It was an unintended experiment with 2 laptops connected directly using an ethernet cable. On the other end I had to activate connection again (NetworkManager). Just now I have tried "nmcli con down" for wifi connection on both sides and "nmcli con up". A ssh connection has not died. My conclusion is that TCP connection may survive even without ignoring of carrier lost on network interfaces. Certainly connection would be not restored if new DHCP leases had other addresses. A particular application may detect that the link is down. To deal with such cases it may be necessary to adjust NetworkManager configuration.
[toc] | [prev] | [next] | [standalone]
| From | debian-user@howorth.org.uk |
|---|---|
| Date | 2023-11-01 21:00 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvpxD-2qga-1@gated-at.bofh.it> |
| In reply to | #262993 |
<tomas@tuxteam.de> wrote: > On Wed, Nov 01, 2023 at 10:17:16AM -0400, Felix Miata wrote: > > tomas@tuxteam.de composed on 2023-11-01 12:12 (UTC+0100): > > > > > More "down to the bolts" folks use ifupdown (I do). If I stick an > > > Ethernet cable into my laptop I want to be able to say "sudo ifup > > > eth0". > > > > That's more than I need to do. systemd-networkd.socket notices and > > appropriately responds to the ethernet cable connection without any > > help from me. > > But this is exactly what I /don't/ want "just happening". That's why > I am more than happy with plain, simple ifupdown. Exactly. If the cable goes down, for example, I want TCP connections to stay intact and continue when it is plugged back in! What is 'appropriate' when a physical connection goes down is entirely dependent on circumstances. > I was just pointing at the fact that even ifupdown can automatically > bring up an interface on connect (cf. allow-hotplug), courtesy of > udev. > > So many ways to cut the cake :-) > > Cheers
[toc] | [prev] | [next] | [standalone]
| From | "Marco M." <mm@dorfdsl.de> |
|---|---|
| Date | 2023-11-01 12:30 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvhA5-2lup-3@gated-at.bofh.it> |
| In reply to | #262979 |
Am 01.11.2023 um 11:43:32 Uhr schrieb Alessandro Baggi: > I've read on an old email that many don't use NM for network > configuration. I'm using it because I replaced some CentOS > installation with Debian 12. > > What is the default method to configure the network? Desktop environments use the NM because it is feature-rich, offers desktop and CLI tools, supports VPN and WiFi and more. > There is an alternative to NM on Debian 12? Of course there are, ifupdown, systemd-networkd and manual (ip addr add) exist. The questions you have to answer: What do you need? Is NetworkManager fine? Then don't change it.
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2023-11-01 13:20 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <Hvimt-2m0f-3@gated-at.bofh.it> |
| In reply to | #262984 |
On Wed, 1 Nov 2023 12:19:47 +0100 "Marco M." <mm@dorfdsl.de> wrote: > Am 01.11.2023 um 11:43:32 Uhr schrieb Alessandro Baggi: > > > I've read on an old email that many don't use NM for network > > configuration. I'm using it because I replaced some CentOS > > installation with Debian 12. > > > > What is the default method to configure the network? > > Desktop environments use the NM because it is feature-rich, offers > desktop and CLI tools, supports VPN and WiFi and more. > > My desktop has it because it's a dependency of Xfce4. Yes. I could remove it, but the days when it was known as Notwork Manager are many years gone, it's pretty reliable now so it's not doing me any harm. The principle 'if it ain't broke, don't fix it' long predates the computer era, but it applies at least a hundredfold to anything IT. I don't actually do anything with the NM user features on the desktop, which doesn't use VPN or get moved to any other network, but on the other hand I do find it useful on my laptop and netbook. Those are the devices used for messing about in other networks, or doing odd things like tethering wi-fi, and NM now correctly manages the dirty little details like DNS, routing and DHCP serving. I don't manage ssh with it, because stuff done over ssh is command-line so I may as well initiate the link that way as well. NM adds nothing to ssh. Of course, NM has never been anywhere near my server, which doesn't have a GUI. Horses for courses... -- Joe
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2023-10-22 07:20 +0200 |
| Subject | Making resolv.conf immutable [was: Bookworm: NetworkManager] |
| Message-ID | <Hrz2x-hzJ2-5@gated-at.bofh.it> |
| In reply to | #262474 |
[Multipart message — attachments visible in raw view] — view raw
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 Sigh. Since I have been one of those proposing this for some time, i feel somewhat responsible for that meme having escaped the lab. So let me state this: I never proposed making resolv.conf immutable as a "solution". I always knew and said that this is going to bite the sysadmin in the rear two years down the street. What I have proposed it for is as a debugging tool: make it immutable and watch the logs to see who complains. If found, configure the culprit to your taste. If not, look for another debugging approach. Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2023-10-21 20:00 +0200 |
| Message-ID | <Hroqu-hsMq-5@gated-at.bofh.it> |
| In reply to | #262472 |
Pocket composed on 2023-10-21 12:23 (UTC-0400):
> I want NetworkManager to not over write /etc/resolv.conf
...
> Is there something I am over looking?
If you're not personally committed to NetworkMangler and only need static
networking, then remove it and ifupdown. Systemd provides simple static IP
network setup:
# inxi -S
System:
Host: gx780 Kernel: 6.1.0-11-amd64 arch: x86_64 bits: 64 Console: pty pts/0
Distro: Debian GNU/Linux 12 (bookworm)
# dpkg-query --showformat='${Package}\t${Version}\n' --show | egrep 'netw|solv|temd|ifupdown'
libpam-systemd 252.12-1~deb12u1
libqt5network5 5.15.8+dfsg-11
libsystemd-shared 252.12-1~deb12u1
libsystemd0 252.12-1~deb12u1
systemd 252.12-1~deb12u1
systemd-sysv 252.12-1~deb12u1
# ls -gG /etc/systemd/network
total 1
-rw-r--r-- 1 175 Apr 3 2023 eth0.network
# systemctl list-unit-files | egrep -i 'net|solv|anager'
ntpsec-systemd-netif.path enabled enabled
display-manager.service alias -
ntpsec-systemd-netif.service static -
systemd-network-generator.service disabled enabled
systemd-networkd-wait-online.service disabled disabled
systemd-networkd-wait-online@.service disabled enabled
systemd-networkd.service disabled enabled
systemd-networkd.socket enabled enabled
network-online.target static -
network-pre.target static -
network.target static -
# ping -c1 www.google.com
PING www.google.com (64.233.177.99) 56(84) bytes of data.
64 bytes from yx-in-f99.1e100.net (64.233.177.99): icmp_seq=1 ttl=58 time=155 ms
--- www.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 154.625/154.625/154.625/0.000 ms
#
Nothing writes to my /etc/resolv.conf except me. :)
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-21 20:20 +0200 |
| Message-ID | <HroJP-ht9x-1@gated-at.bofh.it> |
| In reply to | #262479 |
On 10/21/23 13:58, Felix Miata wrote:
> Pocket composed on 2023-10-21 12:23 (UTC-0400):
>
>> I want NetworkManager to not over write /etc/resolv.conf
> ...
>> Is there something I am over looking?
>
> If you're not personally committed to NetworkMangler and only need static
> networking, then remove it and ifupdown. Systemd provides simple static IP
> network setup:
I may well be at that point to use systemd networking.
That would require me to rip out all the no defunct packages which I
could do, but I would rather just get nm working correctly if I can.
ifupdown and dhcpcd has worked for me in bullseye and that may indeed be
where this resolved to.
My setup is that I was a dhcp server to give out IPs and DNS info.
That way I can control those things without having to do so on ever system.
I just make the change on the router and I am done.
>
> # inxi -S
> System:
> Host: gx780 Kernel: 6.1.0-11-amd64 arch: x86_64 bits: 64 Console: pty pts/0
> Distro: Debian GNU/Linux 12 (bookworm)
> # dpkg-query --showformat='${Package}\t${Version}\n' --show | egrep 'netw|solv|temd|ifupdown'
> libpam-systemd 252.12-1~deb12u1
> libqt5network5 5.15.8+dfsg-11
> libsystemd-shared 252.12-1~deb12u1
> libsystemd0 252.12-1~deb12u1
> systemd 252.12-1~deb12u1
> systemd-sysv 252.12-1~deb12u1
> # ls -gG /etc/systemd/network
> total 1
> -rw-r--r-- 1 175 Apr 3 2023 eth0.network
> # systemctl list-unit-files | egrep -i 'net|solv|anager'
> ntpsec-systemd-netif.path enabled enabled
> display-manager.service alias -
> ntpsec-systemd-netif.service static -
> systemd-network-generator.service disabled enabled
> systemd-networkd-wait-online.service disabled disabled
> systemd-networkd-wait-online@.service disabled enabled
> systemd-networkd.service disabled enabled
> systemd-networkd.socket enabled enabled
> network-online.target static -
> network-pre.target static -
> network.target static -
> # ping -c1 www.google.com
> PING www.google.com (64.233.177.99) 56(84) bytes of data.
> 64 bytes from yx-in-f99.1e100.net (64.233.177.99): icmp_seq=1 ttl=58 time=155 ms
>
> --- www.google.com ping statistics ---
> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> rtt min/avg/max/mdev = 154.625/154.625/154.625/0.000 ms
> #
> Nothing writes to my /etc/resolv.conf except me. :)
--
It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2023-10-21 20:40 +0200 |
| Message-ID | <Hrp3c-htg3-3@gated-at.bofh.it> |
| In reply to | #262481 |
>>> I want NetworkManager to not over write /etc/resolv.conf
[...]
> My setup is that I was a dhcp server to give out IPs and DNS info.
> That way I can control those things without having to do so on every system.
Populating `/etc/resolv.conf` from the DHCP-provided info is a useful
part of "control those things without having to do so on every system",
so I don't see why you "want NetworkManager to not over write
/etc/resolv.conf".
Stefan
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-21 20:50 +0200 |
| Message-ID | <HrpcS-htjG-11@gated-at.bofh.it> |
| In reply to | #262482 |
On 10/21/23 14:32, Stefan Monnier wrote: >>>> I want NetworkManager to not over write /etc/resolv.conf > [...] >> My setup is that I was a dhcp server to give out IPs and DNS info. >> That way I can control those things without having to do so on every system. > Populating `/etc/resolv.conf` from the DHCP-provided info is a useful > part of "control those things without having to do so on every system", > so I don't see why you "want NetworkManager to not over write > /etc/resolv.conf". > > > Stefan > I agree about that on most machines, but the machine in question has bind running so nameserver needs to be set to 127.0.0.1 and the domain to example.org in the resolv.conf file. This is my problem in a nutshell -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Christoph Brinkhaus <c.brinkhaus@t-online.de> |
|---|---|
| Date | 2023-10-21 21:00 +0200 |
| Message-ID | <Hrpmy-htn6-3@gated-at.bofh.it> |
| In reply to | #262484 |
[Multipart message — attachments visible in raw view] — view raw
Am Sat, Oct 21, 2023 at 02:40:49PM -0400 schrieb Pocket:
>
> On 10/21/23 14:32, Stefan Monnier wrote:
> > > > > I want NetworkManager to not over write /etc/resolv.conf
> > [...]
> > > My setup is that I was a dhcp server to give out IPs and DNS info.
> > > That way I can control those things without having to do so on every system.
> > Populating `/etc/resolv.conf` from the DHCP-provided info is a useful
> > part of "control those things without having to do so on every system",
> > so I don't see why you "want NetworkManager to not over write
> > /etc/resolv.conf".
> >
> >
> > Stefan
> >
> I agree about that on most machines, but the machine in question has bind
> running so nameserver needs to be set to 127.0.0.1 and the domain to
> example.org in the resolv.conf file.
>
> This is my problem in a nutshell
I am not 100% sure if I fully understood your setup. My system gets its
network settings via DHCP. I also run a nameserver on 127.0.0.1. My
external interface is bond0. I have the following configuration:
#v+
ris@lenovo ~> cat /etc/dhcp/dhclient.conf|grep -v "^#"
option rfc3442-classless-static-routes code 121 = array of unsigned
integer 8;
send host-name = gethostname();
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn,
dhcp6.sntp-servers,
netbios-name-servers, netbios-scope,
interface-mtu,
rfc3442-classless-static-routes,
ntp-servers;
interface "bond0" {
supersede domain-name-servers 127.0.0.1;
}
#v-
The last block prevents my local resolv.conf to be overwritten.
I am not sure if that measure could help in your setup.
Kind regards,
Christoph
--
Ist die Katze gesund
schmeckt sie dem Hund.
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-21 21:20 +0200 |
| Message-ID | <HrpFT-htJe-1@gated-at.bofh.it> |
| In reply to | #262486 |
On 10/21/23 14:53, Christoph Brinkhaus wrote:
> Am Sat, Oct 21, 2023 at 02:40:49PM -0400 schrieb Pocket:
>> On 10/21/23 14:32, Stefan Monnier wrote:
>>>>>> I want NetworkManager to not over write /etc/resolv.conf
>>> [...]
>>>> My setup is that I was a dhcp server to give out IPs and DNS info.
>>>> That way I can control those things without having to do so on every system.
>>> Populating `/etc/resolv.conf` from the DHCP-provided info is a useful
>>> part of "control those things without having to do so on every system",
>>> so I don't see why you "want NetworkManager to not over write
>>> /etc/resolv.conf".
>>>
>>>
>>> Stefan
>>>
>> I agree about that on most machines, but the machine in question has bind
>> running so nameserver needs to be set to 127.0.0.1 and the domain to
>> example.org in the resolv.conf file.
>>
>> This is my problem in a nutshell
> I am not 100% sure if I fully understood your setup. My system gets its
> network settings via DHCP. I also run a nameserver on 127.0.0.1. My
> external interface is bond0. I have the following configuration:
>
> #v+
> ris@lenovo ~> cat /etc/dhcp/dhclient.conf|grep -v "^#"
>
> option rfc3442-classless-static-routes code 121 = array of unsigned
> integer 8;
>
> send host-name = gethostname();
> request subnet-mask, broadcast-address, time-offset, routers,
> domain-name, domain-name-servers, domain-search, host-name,
> dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn,
> dhcp6.sntp-servers,
> netbios-name-servers, netbios-scope,
> interface-mtu,
> rfc3442-classless-static-routes,
> ntp-servers;
>
> interface "bond0" {
> supersede domain-name-servers 127.0.0.1;
> }
> #v-
>
> The last block prevents my local resolv.conf to be overwritten.
> I am not sure if that measure could help in your setup.
>
> Kind regards,
> Christoph
Well the default minimal install that I do (or use, done,did,etc) has
networkmanager, isc-dhcp-client and wpa_supplicant, so that is the
parameters that I have to work under. I would like not to change that
by removing or adding packages if I can.
As I understand this networkmanager has an internal dhcp client.
It can setup all the other parameters.
Which is ok and will for me if I can get it to leave /etc/resolv.conf alone.
This is what I am trying to accomplish.
Barring that I am gonna try to get it to put the following into
resolv.conf if it just has to write that file
and call it a day,week or month whatever it takes
domain example.org
nameserver 127.0.0.1
options edns0 trust-ad
--
It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2023-10-21 21:10 +0200 |
| Message-ID | <Hrpwd-htFQ-1@gated-at.bofh.it> |
| In reply to | #262484 |
> I agree about that on most machines, but the machine in question has bind
> running so nameserver needs to be set to 127.0.0.1 and the domain to
> example.org in the resolv.conf file.
Beware: at this rate, you may end up giving us enough info about what
you're doing for us to actually help you.
I think you're still safe (e.g., you're still keeping us in the dark
about why you run bind on "this machine" yet you also want it to receive
"IPs and DNS info" from some other dhcp server, or otherwise keeping us
confused about which machine is which), but you're playing
a dangerous game.
Stefan
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-21 21:40 +0200 |
| Message-ID | <HrpZf-htPU-3@gated-at.bofh.it> |
| In reply to | #262487 |
On 10/21/23 15:02, Stefan Monnier wrote: >> I agree about that on most machines, but the machine in question has bind >> running so nameserver needs to be set to 127.0.0.1 and the domain to >> example.org in the resolv.conf file. > Beware: at this rate, you may end up giving us enough info about what > you're doing for us to actually help you. > > I think you're still safe (e.g., you're still keeping us in the dark > about why you run bind on "this machine" yet you also want it to receive > "IPs and DNS info" from some other dhcp server, or otherwise keeping us > confused about which machine is which), but you're playing > a dangerous game. > > > Stefan > I need to run a dns server on this network and I want to get the ip and routing info from a dhcp server. For this machine I don't need the dns info from the dhcp server. Doing this lets me control the IP addresses on the entire network and I can replace one server with another by simply changing the IP address handed out by the dhcp server. The dhcp server hands out the lease IP by MAC address for some (server, printers, "security machines/devices" etc) machines that need a "static" IP address and dynamic for all the others like tablets notebooks etc. This has worked for more that 35 years for me. On all other client machines I use all the dhcp information, just not for this machine as it is an email server, dns and web server. I use to build my own custom "distro" (rpm package with all packages built from scratch) for servers but I am getting too old to do that so I am trying to use debian to replace that. I don't get you context here as the problem is simply trying to get networkmanager to quit writing /etc/resolv.conf. Being that debian has config files in many places I could have missed that. If I can do this then my issue is solved. -- It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-10-21 21:50 +0200 |
| Message-ID | <Hrq8V-htTr-1@gated-at.bofh.it> |
| In reply to | #262489 |
On Sat, Oct 21, 2023 at 03:29:40PM -0400, Pocket wrote:
> I don't get you context here as the problem is simply trying to get
> networkmanager to quit writing /etc/resolv.conf.
The context -- what has certain people confused -- is that most people who
do what you're doing run the DNS and DHCP servers on the *same machine*.
They're wondering why you are running those on *different* machines.
Now, personally I don't care. I'm just watching the drama play out.
> If I can do this then my issue is solved.
Except you've also got some self-imposed restrictions:
1) You're using a non-vanilla Debian installation method that installs
Network Manager despite not choosing a desktop environment.
2) You refuse to remove Network Manager despite it being the apparent
source of your problems.
3) You refuse to install any package that you don't already have.
Points 1, 2 and 3 taken together seem to point toward some sort of
virtualization story ("I need to be able to replicate this setup
later") that's also being hidden from us, but who knows.
4) You refuse the chattr +i solution which would solve the problem in
one simple step. (This one doesn't surprise me. A lot of people
object to it on some sort of religious ground. I don't understand
the objection, but it's so common that it's no longer a surprise.)
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-21 22:00 +0200 |
| Message-ID | <HrqiB-htXc-11@gated-at.bofh.it> |
| In reply to | #262491 |
On 10/21/23 15:41, Greg Wooledge wrote:
> On Sat, Oct 21, 2023 at 03:29:40PM -0400, Pocket wrote:
>> I don't get you context here as the problem is simply trying to get
>> networkmanager to quit writing /etc/resolv.conf.
> The context -- what has certain people confused -- is that most people who
> do what you're doing run the DNS and DHCP servers on the *same machine*.
>
> They're wondering why you are running those on *different* machines.
>
> Now, personally I don't care. I'm just watching the drama play out.
the DHCP server is on a router
Running DNS service on a machine is done by many
>
>> If I can do this then my issue is solved.
> Except you've also got some self-imposed restrictions:
>
> 1) You're using a non-vanilla Debian installation method that installs
> Network Manager despite not choosing a desktop environment.
>
> 2) You refuse to remove Network Manager despite it being the apparent
> source of your problems.
I would like to get this working as is
>
> 3) You refuse to install any package that you don't already have.
>
> Points 1, 2 and 3 taken together seem to point toward some sort of
> virtualization story ("I need to be able to replicate this setup
> later") that's also being hidden from us, but who knows.
I would like not to install or remove any packages
>
> 4) You refuse the chattr +i solution which would solve the problem in
> one simple step. (This one doesn't surprise me. A lot of people
> object to it on some sort of religious ground. I don't understand
> the objection, but it's so common that it's no longer a surprise.)
That is a crutch, ie If you can configure something then use chatter +i
I prefer to do this correctly
--
It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2023-10-21 23:40 +0200 |
| Message-ID | <HrrRo-hv0g-7@gated-at.bofh.it> |
| In reply to | #262492 |
> the DHCP server is on a router
> Running DNS service on a machine is done by many
FWIW, I run `dnsmasq` as local DNS server on many of my machines, and
this is already automatically setup to "DTRT" somehow (the DNS
info obtained via DHCP are provided to `dnsmasq` and `/etc/resolv.conf`
only points to 127.0.0.1).
You might want to look at how they do it.
Stefan
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2023-10-22 07:30 +0200 |
| Message-ID | <Hrzcd-hzNR-3@gated-at.bofh.it> |
| In reply to | #262489 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, Oct 21, 2023 at 03:29:40PM -0400, Pocket wrote:
>
> On 10/21/23 15:02, Stefan Monnier wrote:
> > > I agree about that on most machines, but the machine in question has bind
> > > running so nameserver needs to be set to 127.0.0.1 and the domain to
> > > example.org in the resolv.conf file.
> > Beware: at this rate, you may end up giving us enough info about what
> > you're doing for us to actually help you.
> >
> > I think you're still safe (e.g., you're still keeping us in the dark
> > about why you run bind on "this machine" yet you also want it to receive
> > "IPs and DNS info" from some other dhcp server, or otherwise keeping us
> > confused about which machine is which), but you're playing
> > a dangerous game.
> >
> >
> > Stefan
> >
> I need to run a dns server on this network and I want to get the ip and
> routing info from a dhcp server.
>
> For this machine I don't need the dns info from the dhcp server.
OK. And the server is sending the DNS info unrequested? Or is your
DHCP client (whoever that is) asking for it?
Furthermore: if your DHCP client is dhclient, there are hooks for
you to configure things in /etc/dhcp/dhclient-{enter,exit}-hooks.d
Cheers
--
t
[toc] | [prev] | [next] | [standalone]
| From | Pocket <pocket@columbus.rr.com> |
|---|---|
| Date | 2023-10-22 14:40 +0200 |
| Message-ID | <HrFUl-328-9@gated-at.bofh.it> |
| In reply to | #262507 |
On 10/22/23 01:24, tomas@tuxteam.de wrote:
> On Sat, Oct 21, 2023 at 03:29:40PM -0400, Pocket wrote:
>> On 10/21/23 15:02, Stefan Monnier wrote:
>>>> I agree about that on most machines, but the machine in question has bind
>>>> running so nameserver needs to be set to 127.0.0.1 and the domain to
>>>> example.org in the resolv.conf file.
>>> Beware: at this rate, you may end up giving us enough info about what
>>> you're doing for us to actually help you.
>>>
>>> I think you're still safe (e.g., you're still keeping us in the dark
>>> about why you run bind on "this machine" yet you also want it to receive
>>> "IPs and DNS info" from some other dhcp server, or otherwise keeping us
>>> confused about which machine is which), but you're playing
>>> a dangerous game.
>>>
>>>
>>> Stefan
>>>
>> I need to run a dns server on this network and I want to get the ip and
>> routing info from a dhcp server.
>>
>> For this machine I don't need the dns info from the dhcp server.
> OK. And the server is sending the DNS info unrequested? Or is your
> DHCP client (whoever that is) asking for it?
>
> Furthermore: if your DHCP client is dhclient, there are hooks for
> you to configure things in /etc/dhcp/dhclient-{enter,exit}-hooks.d
>
> Cheers
The dhcp client is NetworkManager.
It is request a new lease as it should
Oct 22 03:59:35 gremlin NetworkManager[664]: <info> [1697961575.2993]
dhcp4 (end0): state changed new lease, address=192.168.1.3
--
It's not easy to be me
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2023-10-21 22:50 +0200 |
| Message-ID | <Hrr4Z-hutc-1@gated-at.bofh.it> |
| In reply to | #262484 |
On Sat, 21 Oct 2023 14:40:49 -0400
Pocket <pocket@columbus.rr.com> wrote:
> but the machine in question has
> bind running so nameserver needs to be set to 127.0.0.1 and the
> domain to example.org in the resolv.conf file.
>
> This is my problem in a nutshell
Oh, why didn't you say that! Actually, it doesn't have to use the
loopback address; you can use the address of the Ethernet interface.
Also, you should not be using example.org. That is a reserved domain
name. https://en.wikipedia.org/wiki/Example.com
I am going to guess (since you haven't
said so) that this is also not a laptop, and therefor it has a permanent
IP address.
If you insist on retaining NetworkManager, this page might be useful.
https://serverfault.com/questions/810636/how-to-manage-dns-in-networkmanager-via-console-nmcli
You can also add DNS servers in the GTK version of the NM GUI. I don't
know about the KDE version.
You can use isc-dhcp to tell the whole network where its DNS server is.
You can also make over-rides for individual hosts. In dhcpd.conf:
subnet blah {
option domain-name-servers blah, blah;
option domain-search etc.;
host dns-server
{
option domain-name-servers 192.168.100.30, 127.0.0.1;
}
}
You said in another email that you are using a dhcp server on a
"router". That doesn't tell me much. A router is simply a computer that
sits between two networks, and routes packets between them. My router
is a 16 year old computer designed for embedded applications that runs
Debian. I run ISC DHCPD on that an another machine with fail-over
between them.
From what I have seen most "routers" these days are cheap boxes
provided by ISPs that have buggy, insecure, and limited software which
may not be able to do this.
You can also set the ISC dhcp client to add name servers.
prepend domain-name-servers 127.0.0.1;
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
Page 3 of 13 — ← Prev page 1 2 [3] 4 5 … 13 Next page →
Back to top | Article view | linux.debian.user
csiph-web