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 2 of 13 — ← Prev page 1 [2] 3 4 … 13 Next page →
| From | "Andrew M.A. Cater" <amacater@einval.com> |
|---|---|
| Date | 2023-10-24 19:40 +0200 |
| Message-ID | <HstxL-z9b-1@gated-at.bofh.it> |
| In reply to | #262679 |
On Tue, Oct 24, 2023 at 01:21:04PM -0400, Pocket wrote: > <snips> > > > > 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? > There are threads from Gene and others in (at least) February and March 2023 archives for this list on addresses, nameservers and so on.. In general, go to the url of the form https://lists.debian.org/debian-user/2023/04/ and change the last digits for the appropriate month. Reading the archives of this list is often instructive > I would like to read it > > Thanks > > > -- > It's not easy to be me >
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-10-25 03:10 +0200 |
| Message-ID | <HsAzf-DES-1@gated-at.bofh.it> |
| In reply to | #262679 |
On 10/24/23 13:21, Pocket wrote: > > 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 So would I. > > Thanks > > 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 | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2023-10-25 03:50 +0200 |
| Message-ID | <HsBbX-DSl-1@gated-at.bofh.it> |
| In reply to | #262679 |
On Tue 24 Oct 2023 at 13:21:04 (-0400), Pocket wrote: > 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 You go to https://lists.debian.org/debian-user/ and search for gheskett 169.254 (his sign-off and the address in question). That'll drop you into the middle of a 2022-01 thread that might be relevant. All words, BTW. There may be others; in fact I'm almost certain there are. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-10-25 18:50 +0200 |
| Subject | link-local 169.254.x.y addresses |
| Message-ID | <HsPeV-Nkw-5@gated-at.bofh.it> |
| In reply to | #262679 |
On 25/10/2023 00:21, Pocket wrote: > On 10/24/23 12:48, Max Nikulin wrote: >> >> There was a thread several months ago with discussion of link local >> 169.254.x.y addresses. >> > Where may I find that thread? See latest threads with the "mdns" keyword. Despite mDNS-SD (e.g. printer discovery) does not necessary mean link-local addresses, 169.254.x.y is a fallback (so falls under the zeroconf umbrella). Do not neglect the IPv6 thread started by Gene as well. https://lists.debian.org/cgi-bin/search?P=mdns&DEFAULTOP=or&B=Gdebian-user&SORT=0&HITSPERPAGE=50 Besides avahi-autoipd, link-local addresses may be assigned by systemd-networkd, dhcpcd, NetworkManager.
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2023-10-25 01:40 +0200 |
| Message-ID | <Hsza9-CG0-1@gated-at.bofh.it> |
| In reply to | #262677 |
Hi Max, On Tue, Oct 24, 2023 at 11:48:35PM +0700, Max Nikulin wrote: > There was a thread several months ago with discussion of link local > 169.254.x.y addresses. $ notmuch count 'from:gheskett@shentel.net (body:"169.254" or body:"avahi")' 110 i.e. in the last 4 years I have 110 emails from Gene that feature the string "169.254" or "avahi". They are all from this mailing list. Avahi is one of Gene's bogeymen. It has been explained to Gene many times why he ends up with these link-local addresses, and what (if anything) to do about it. It is chiefly to do with Gene's use of Armbian (which isn't Debian, so is off-topic here) and it being configured to use DHCP by default. There is unlikely to be anything you can say to Gene about IPv4 link-local addresses that has not already been said to him multiple times. This conversation will likely happen again next time Gene feels we are due a rant about Avahi, and as here, it will probably start to hijack someone else's thread. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | Alessandro Baggi <alessandro.baggi@gmail.com> |
|---|---|
| Date | 2023-11-01 11:50 +0100 |
| Subject | Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvgXn-2kZz-7@gated-at.bofh.it> |
| In reply to | #262476 |
Hi list, 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? There is an alternative to NM on Debian 12? Thank you in advance. Alessandro.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-11-01 12:20 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <Hvhqp-2lrq-1@gated-at.bofh.it> |
| In reply to | #262979 |
On Wed, Nov 01, 2023 at 11:43:32AM +0100, Alessandro Baggi wrote: > 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? Depends on how you install. > There is an alternative to NM on Debian 12? ALL installations of ALL versions of Debian support "ifupdown", also known as /etc/network/interfaces, for configuring the network. If your system is NOT a laptop, and doesn't move around from place to place, this is probably what you want. Servers? Ethernet-based workstations? This is probably what you want. If you install a Desktop Environment when you install Debian, then you probably also get Network Manager. This is designed for laptops and other systems whose networking may change at any time, or for systems that rely on wireless networking rather than ethernet. If that describes your system, then this is probably what you'll be using. Debian also supports systemd-networkd for configuring the network. This is available, but is not configured by default. If you want to use this, you may do so. I know very little about it, so I can't tell you what use cases it's best for. Ultimately, Debian offers flexibility and choice. Use whatever works best for you and your systems.
[toc] | [prev] | [next] | [standalone]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2023-11-01 12:40 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvhJL-2lxM-3@gated-at.bofh.it> |
| In reply to | #262980 |
[Multipart message — attachments visible in raw view] — view raw
Greg Wooledge (12023-11-01): > ALL installations of ALL versions of Debian support "ifupdown", also > known as /etc/network/interfaces, for configuring the network. If > your system is NOT a laptop, and doesn't move around from place to > place, this is probably what you want. > > Servers? Ethernet-based workstations? This is probably what you want. I second this. I recently configured a series of workstations. They were Ubuntu, so I went for what seems to be the official supported mechanism: systemd-networkd plus netplan. It was terrible, the network would get de-configured if somebody pulled the ethernet cable (and that happens a lot here!) and rebooted the machine while they were at it, and the NIS and NFS do not appreciate it much. I switched to ifupdown and everything worked nicely. Regards, -- Nicolas George
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-11-01 17:10 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvlX3-2ofv-3@gated-at.bofh.it> |
| In reply to | #262985 |
On 01/11/2023 18:31, Nicolas George wrote: > systemd-networkd plus netplan. It was terrible, the network would get > de-configured if somebody pulled the ethernet cable (and that happens a > lot here!) and rebooted the machine while they were at it, and the NIS > and NFS do not appreciate it much. I am curious if ConfigureWithoutCarrier= and IgnoreCarrierLoss= from systemd.network(5) may help. NetworkManager has a similar option, unfortunately it may be changed per-device, not per-connection.
[toc] | [prev] | [next] | [standalone]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2023-11-01 17:20 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <Hvm6K-2oiA-3@gated-at.bofh.it> |
| In reply to | #262999 |
[Multipart message — attachments visible in raw view] — view raw
Max Nikulin (12023-11-01): > I am curious if ConfigureWithoutCarrier= and IgnoreCarrierLoss= from > systemd.network(5) may help. > > NetworkManager has a similar option, unfortunately it may be changed > per-device, not per-connection. I do not have the time to test it anew. IIRC, when I tried, I looked into the source and there was no way of preventing the de-configuration that was happening. But I have not kept note of the details. Regards, -- Nicola George
[toc] | [prev] | [next] | [standalone]
| From | yxcv@vienna.at |
|---|---|
| Date | 2023-11-01 12:20 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <Hvhqp-2lrq-11@gated-at.bofh.it> |
| In reply to | #262979 |
On Wed, 1 Nov 2023 11:43:32 +0100 Alessandro Baggi <alessandro.baggi@gmail.com> wrote: > Hi list, > 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? > There is an alternative to NM on Debian 12? > > Thank you in advance. > > Alessandro. > With SystemD instead of SysV and ip of Kusnetsow and iproute2 with Baturin you should do it by yourselve.
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2023-11-01 12:20 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <Hvhqp-2lrq-23@gated-at.bofh.it> |
| In reply to | #262981 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, Nov 01, 2023 at 01:10:22PM +0200, yxcv@vienna.at wrote: > On Wed, 1 Nov 2023 11:43:32 +0100 > Alessandro Baggi <alessandro.baggi@gmail.com> wrote: > > Hi list, [...] > With SystemD instead of SysV and ip of Kusnetsow and iproute2 with Baturin > you should do it by yourselve. See? Yet another choice (I can't vouch for that one, for lack of experience :) Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2023-11-01 12:20 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <Hvhqp-2lrq-19@gated-at.bofh.it> |
| In reply to | #262979 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, Nov 01, 2023 at 11:43:32AM +0100, Alessandro Baggi wrote: > Hi list, > 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. [...] I don't know how the actual numbers are. I'd guess that "desktop environment" folks do have NM (my primary Debian "customer" is like that: they expect to plug in their computer into an Ethernet and some widgit to appear up there). 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". Likewise, I do issue "sudo ifup wlan0" to connect to my configured wlan, which I do in /etc/network/interfaces. The latter can also be automated to a certain extent, of course. Pick your style :-) Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2023-11-01 15:20 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvkeB-2nah-3@gated-at.bofh.it> |
| In reply to | #262982 |
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. -- 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 | <tomas@tuxteam.de> |
|---|---|
| Date | 2023-11-01 15:40 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvkxX-2ngP-7@gated-at.bofh.it> |
| In reply to | #262991 |
[Multipart message — attachments visible in raw view] — view raw
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. 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 -- t
[toc] | [prev] | [next] | [standalone]
| From | Alessandro Baggi <alessandro.baggi@gmail.com> |
|---|---|
| Date | 2023-11-01 15:50 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvkHD-2nkx-1@gated-at.bofh.it> |
| In reply to | #262993 |
Il 01/11/23 15:33, tomas@tuxteam.de ha scritto: > 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. > > 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 thank you to all for suggestions and answer. Alessandro.
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-11-01 16:10 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <Hvl10-2nGs-19@gated-at.bofh.it> |
| In reply to | #262993 |
On 01/11/2023 21:33, tomas@tuxteam.de wrote: > I was just pointing at the fact that even ifupdown can automatically > bring up an interface on connect (cf. allow-hotplug), courtesy of udev. 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)? I believed that e.g. ifplugd is necessary if there are reasons to avoid NetowrkManager and systemd-networkd.
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2023-11-01 18:50 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvnvQ-2p1f-13@gated-at.bofh.it> |
| In reply to | #262997 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, Nov 01, 2023 at 10:00:45PM +0700, Max Nikulin wrote: > On 01/11/2023 21:33, tomas@tuxteam.de wrote: > > I was just pointing at the fact that even ifupdown can automatically > > bring up an interface on connect (cf. allow-hotplug), courtesy of udev. > > 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)? I believed that e.g. ifplugd is necessary if there are reasons to > avoid NetowrkManager and systemd-networkd. 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. Currently I haven't an Ehternet to fool around, so I'll leave it at that. Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-11-02 16:50 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvI7f-2Cnt-1@gated-at.bofh.it> |
| In reply to | #263004 |
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. Anyway it is already implemented in NetworkManager and it allows to get a DHCP lease immediately when cable is plugged. On the other hand it is possible to uncheck connection.autoconnect to make NetworkManager waiting for an explicit user action, either a couple of mouse clicks or a command in terminal, to activate a particular connection. 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.
[toc] | [prev] | [next] | [standalone]
| From | Jeffrey Walton <noloader@gmail.com> |
|---|---|
| Date | 2023-11-02 18:00 +0100 |
| Subject | Re: Alternative to NetworkManager on Debian 12 |
| Message-ID | <HvJcZ-2CYO-5@gated-at.bofh.it> |
| In reply to | #263048 |
On Thu, Nov 2, 2023 at 11:41 AM Max Nikulin <manikulin@gmail.com> 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. I think it is a bit broader than that. On wireless devices, like cell phones, some connection managers pretend the device is [still] connected to the network, even when service drops. So the device seems like it is always connected, and a loss of the link is not exposed up the stack. I don't know if NetworkManager behaves the same way. But I know the connection managers on WIndows and iOS used to behave that way. Jeff
[toc] | [prev] | [next] | [standalone]
Page 2 of 13 — ← Prev page 1 [2] 3 4 … 13 Next page →
Back to top | Article view | linux.debian.user
csiph-web