Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #263943 > unrolled thread
| Started by | gene heskett <gheskett@shentel.net> |
|---|---|
| First post | 2023-11-29 19:00 +0100 |
| Last post | 2023-11-29 22:20 +0100 |
| Articles | 20 on this page of 100 — 17 participants |
Back to article view | Back to linux.debian.user
time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-29 19:00 +0100
Re: time question, as in ntp? Dan Ritter <dsr@randomstring.org> - 2023-11-29 19:20 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-29 19:40 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-29 19:20 +0100
Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-29 20:10 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-29 20:20 +0100
Re: time question, as in ntp? Jeffrey Walton <noloader@gmail.com> - 2023-11-30 01:30 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-29 22:00 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-30 00:00 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 01:40 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-30 11:40 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 11:50 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-11-30 03:50 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-30 11:50 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-11-29 19:30 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-29 20:00 +0100
Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-29 20:30 +0100
Re: time question, as in ntp? "Andrew M.A. Cater" <amacater@einval.com> - 2023-11-29 21:00 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 01:10 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 01:00 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-11-30 02:30 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 03:00 +0100
Re: time question, as in ntp? Charles Curley <charlescurley@charlescurley.com> - 2023-11-30 03:50 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 05:20 +0100
Re: time question, as in ntp? Charles Curley <charlescurley@charlescurley.com> - 2023-11-30 05:40 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 10:20 +0100
Re: time question, as in ntp? Karen Lewellen <klewellen@shellworld.net> - 2023-11-30 05:50 +0100
Re: time question, as in ntp? Karen Lewellen <klewellen@shellworld.net> - 2023-11-30 05:50 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-30 11:50 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-30 11:50 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-11-30 03:40 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 05:10 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-11-30 06:00 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 10:20 +0100
Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-30 13:20 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 11:20 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-11-30 13:40 +0100
Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-30 14:20 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 20:00 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 19:50 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-01 03:40 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 04:30 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-01 05:10 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 11:10 +0100
Re: time question, as in ntp? Curt <curty@free.fr> - 2023-12-01 18:00 +0100
Re: time question, as in ntp? <tomas@tuxteam.de> - 2023-12-01 19:50 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-01 20:30 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-01 05:20 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 11:50 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-12-01 12:40 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-01 16:30 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 20:30 +0100
Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-12-01 20:50 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 23:00 +0100
Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-12-01 23:40 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-02 12:20 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-02 08:50 +0100
Re: time question, as in ntp? Andy Smith <andy@strugglers.net> - 2023-12-01 08:40 +0100
Re: time question, as in ntp? "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-01 19:30 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 22:30 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-02 03:40 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-02 11:50 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-11-30 15:20 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 20:10 +0100
Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-30 20:20 +0100
Re: time question, as in ntp? Charles Curley <charlescurley@charlescurley.com> - 2023-11-30 21:00 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-11-30 21:30 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 03:10 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-01 04:10 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 04:40 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-01 05:20 +0100
Re: time question, as in ntp? David Wright <deblis@lionunicorn.co.uk> - 2023-12-01 06:10 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-12-01 11:50 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 12:00 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-12-01 12:30 +0100
Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-12-01 14:30 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-12-01 15:40 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 19:50 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 14:30 +0100
Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-12-01 14:50 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 19:50 +0100
Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-12-01 04:20 +0100
Re: time question, as in ntp? Charles Curley <charlescurley@charlescurley.com> - 2023-11-30 15:20 +0100
Re: time question, as in ntp? Andy Smith <andy@strugglers.net> - 2023-11-30 17:20 +0100
Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-30 19:10 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 02:40 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-01 17:30 +0100
Re: time question, as in ntp? Andy Smith <andy@strugglers.net> - 2023-12-01 21:50 +0100
Re: time question, as in ntp? Charles Curley <charlescurley@charlescurley.com> - 2023-12-02 00:10 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-02 17:40 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-04 04:10 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-04 05:40 +0100
Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-04 11:10 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-04 10:50 +0100
Re: time question, as in ntp? Stefan Monnier <monnier@iro.umontreal.ca> - 2023-12-04 15:40 +0100
Re: time question, as in ntp? <tomas@tuxteam.de> - 2023-12-04 15:40 +0100
Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-04 16:00 +0100
Re: time question, as in ntp? Tom Dial <tddial@comcast.net> - 2023-12-05 09:40 +0100
Re: time question, as in ntp? Lee <ler762@gmail.com> - 2023-11-29 20:20 +0100
Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-29 22:20 +0100
Page 2 of 5 — ← Prev page 1 [2] 3 4 5 Next page →
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-11-30 02:30 +0100 |
| Message-ID | <HFE2l-9Ok9-1@gated-at.bofh.it> |
| In reply to | #263961 |
Gene writes: > I've been told that /etc/network/interfaces is not the "today way" to > do it. It works fine. > Then [dhcp is] something else I'll have to maintain as my network > grows, A changing network is exactly what dhcp is for. With it you will not need to do anything when you add a machine. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-30 03:00 +0100 |
| Message-ID | <HFEvn-9OAu-1@gated-at.bofh.it> |
| In reply to | #263965 |
On 11/29/23 20:20, John Hasler wrote: > Gene writes: >> I've been told that /etc/network/interfaces is not the "today way" to >> do it. > > It works fine. > >> Then [dhcp is] something else I'll have to maintain as my network >> grows, > > A changing network is exactly what dhcp is for. With it you will not > need to do anything when you add a machine. Does it always lock the address to that MAC? ISTR a time long ago when it didn't. 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 | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2023-11-30 03:50 +0100 |
| Message-ID | <HFFhL-9PlI-1@gated-at.bofh.it> |
| In reply to | #263966 |
On Wed, 29 Nov 2023 20:53:19 -0500
gene heskett <gheskett@shentel.net> wrote:
> > A changing network is exactly what dhcp is for. With it you will
> > not need to do anything when you add a machine.
>
> Does it always lock the address to that MAC? ISTR a time long ago
> when it didn't.
Normally DHCP does not lock a given IP address to a given MAC address.
However, you can do so on a per machine basis with the fixed-address
option. E.g:
host hawk # new (2016) desktop
{
option host-name "hawk";
hardware ethernet 30:5a:3a:81:83:79;
fixed-address 192.168.100.6;
option domain-name-servers 192.168.100.30, 127.0.0.1; # chaffee, localhost
ddns-hostname hawk;
}
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-30 05:20 +0100 |
| Message-ID | <HFGGR-9R3c-1@gated-at.bofh.it> |
| In reply to | #263969 |
On 11/29/23 21:40, Charles Curley wrote:
> On Wed, 29 Nov 2023 20:53:19 -0500
> gene heskett <gheskett@shentel.net> wrote:
>
>>> A changing network is exactly what dhcp is for. With it you will
>>> not need to do anything when you add a machine.
>>
>> Does it always lock the address to that MAC? ISTR a time long ago
>> when it didn't.
>
> Normally DHCP does not lock a given IP address to a given MAC address.
> However, you can do so on a per machine basis with the fixed-address
> option. E.g:
>
> host hawk # new (2016) desktop
> {
> option host-name "hawk";
> hardware ethernet 30:5a:3a:81:83:79;
> fixed-address 192.168.100.6;
> option domain-name-servers 192.168.100.30, 127.0.0.1; # chaffee, localhost
> ddns-hostname hawk;
> }
In what file do I place similar info to this for eth0?
Thank you Charles. Stay warm and well
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2023-11-30 05:40 +0100 |
| Message-ID | <HFH0d-9Riq-1@gated-at.bofh.it> |
| In reply to | #263971 |
On Wed, 29 Nov 2023 23:15:16 -0500 gene heskett <gheskett@shentel.net> wrote: > In what file do I place similar info to this for eth0? That is part of the ISC DHCP server's configuration. /etc/dhcp/dhcpd.conf man dhcpd.conf -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-30 10:20 +0100 |
| Message-ID | <HFLnb-9W9g-1@gated-at.bofh.it> |
| In reply to | #263972 |
On 11/29/23 23:34, Charles Curley wrote: > On Wed, 29 Nov 2023 23:15:16 -0500 > gene heskett <gheskett@shentel.net> wrote: > >> In what file do I place similar info to this for eth0? > > That is part of the ISC DHCP server's configuration. > /etc/dhcp/dhcpd.conf man dhcpd.conf > I thought so but wanted a confirmation, thank you. > Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Karen Lewellen <klewellen@shellworld.net> |
|---|---|
| Date | 2023-11-30 05:50 +0100 |
| Message-ID | <HFH9T-9RqY-1@gated-at.bofh.it> |
| In reply to | #263971 |
Sorry!
Wrong list....comes from reading at 300 plus words per minute.
On Wed, 29 Nov 2023, Karen Lewellen wrote:
> Chime,
> in elinks do the following..there may be a faster way but it works.
> open the browser without providing a web location as in just type elinks
> Hit the escape key, bringing up the menu bar.
> arrow right to view
> arrow down until you hear toggle link numbering
> Hit space more than likely? Was so happy to find it, I did not change it
> laughs.
> Kare
>
>
>
> On Wed, 29 Nov 2023, gene heskett wrote:
>
>> On 11/29/23 21:40, Charles Curley wrote:
>> > On Wed, 29 Nov 2023 20:53:19 -0500
>> > gene heskett <gheskett@shentel.net> wrote:
>> >
>> > > > A changing network is exactly what dhcp is for. With it you will
>> > > > not need to do anything when you add a machine.
>> > >
>> > > Does it always lock the address to that MAC? ISTR a time long ago
>> > > when it didn't.
>> >
>> > Normally DHCP does not lock a given IP address to a given MAC address.
>> > However, you can do so on a per machine basis with the fixed-address
>> > option. E.g:
>> >
>> > host hawk # new (2016) desktop
>> > {
>> > option host-name "hawk";
>> > hardware ethernet 30:5a:3a:81:83:79;
>> > fixed-address 192.168.100.6;
>> > option domain-name-servers 192.168.100.30, 127.0.0.1; # chaffee,
>> > localhost
>> > ddns-hostname hawk;
>>> }
>> In what file do I place similar info to this for eth0?
>>
>> Thank you Charles. Stay warm and well
>>
>> Cheers, Gene Heskett.
>> --
>> "There are four boxes to be used in defense of liberty:
>> soap, ballot, jury, and ammo. Please use in that order."
>> -Ed Howdershelt (Author, 1940)
>> If we desire respect for the law, we must first make the law respectable.
>> - Louis D. Brandeis
>>
>>
>>
>
>
>
[toc] | [prev] | [next] | [standalone]
| From | Karen Lewellen <klewellen@shellworld.net> |
|---|---|
| Date | 2023-11-30 05:50 +0100 |
| Message-ID | <HFH9T-9RqY-3@gated-at.bofh.it> |
| In reply to | #263971 |
Chime,
in elinks do the following..there may be a faster way but it works.
open the browser without providing a web location as in just type elinks
Hit the escape key, bringing up the menu bar.
arrow right to view
arrow down until you hear toggle link numbering
Hit space more than likely? Was so happy to find it, I did not change it
laughs.
Kare
On Wed, 29 Nov 2023, gene heskett wrote:
> On 11/29/23 21:40, Charles Curley wrote:
>> On Wed, 29 Nov 2023 20:53:19 -0500
>> gene heskett <gheskett@shentel.net> wrote:
>>
>> > > A changing network is exactly what dhcp is for. With it you will
>> > > not need to do anything when you add a machine.
>> >
>> > Does it always lock the address to that MAC? ISTR a time long ago
>> > when it didn't.
>>
>> Normally DHCP does not lock a given IP address to a given MAC address.
>> However, you can do so on a per machine basis with the fixed-address
>> option. E.g:
>>
>> host hawk # new (2016) desktop
>> {
>> option host-name "hawk";
>> hardware ethernet 30:5a:3a:81:83:79;
>> fixed-address 192.168.100.6;
>> option domain-name-servers 192.168.100.30, 127.0.0.1; # chaffee,
>> localhost
>> ddns-hostname hawk;
>> }
> In what file do I place similar info to this for eth0?
>
> Thank you Charles. Stay warm and well
>
> Cheers, Gene Heskett.
> --
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author, 1940)
> If we desire respect for the law, we must first make the law respectable.
> - Louis D. Brandeis
>
>
>
[toc] | [prev] | [next] | [standalone]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Date | 2023-11-30 11:50 +0100 |
| Message-ID | <HFMMh-9Xyn-19@gated-at.bofh.it> |
| In reply to | #263971 |
[Multipart message — attachments visible in raw view] — view raw
On Nov 29, 2023, gene heskett wrote:
> On 11/29/23 21:40, Charles Curley wrote:
> > On Wed, 29 Nov 2023 20:53:19 -0500
> > gene heskett <gheskett@shentel.net> wrote:
> >
> > > > A changing network is exactly what dhcp is for. With it you will
> > > > not need to do anything when you add a machine.
> > >
> > > Does it always lock the address to that MAC? ISTR a time long ago
> > > when it didn't.
> >
> > Normally DHCP does not lock a given IP address to a given MAC address.
> > However, you can do so on a per machine basis with the fixed-address
> > option. E.g:
> >
> > host hawk # new (2016) desktop
> > {
> > option host-name "hawk";
> > hardware ethernet 30:5a:3a:81:83:79;
> > fixed-address 192.168.100.6;
> > option domain-name-servers 192.168.100.30, 127.0.0.1; # chaffee, localhost
> > ddns-hostname hawk;
> > }
> In what file do I place similar info to this for eth0?
You don't set it on a client, but the DHCP Server itself.
Specific network host (if Debian or a derivative) would be
/etc/network/interfaces.
--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
[toc] | [prev] | [next] | [standalone]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Date | 2023-11-30 11:50 +0100 |
| Message-ID | <HFMMh-9Xyn-11@gated-at.bofh.it> |
| In reply to | #263966 |
[Multipart message — attachments visible in raw view] — view raw
On Nov 29, 2023, gene heskett wrote: > On 11/29/23 20:20, John Hasler wrote: > > Gene writes: > > > I've been told that /etc/network/interfaces is not the "today way" to > > > do it. > > > > It works fine. > > > > > Then [dhcp is] something else I'll have to maintain as my network > > > grows, > > > > A changing network is exactly what dhcp is for. With it you will not > > need to do anything when you add a machine. > Does it always lock the address to that MAC? ISTR a time long ago when it > didn't. Not by default. It certainly /can/ though. I can't say it's been available "forever", but reservations for specific MAC addresses have been available for the last 20 years. Noting, of course, that just because a network has a DHCP pool, you don't _have_ to use it for all hosts. For example here, I have all "servers" and network hardware set up with static addresses outside the DHCP Pool, then a pool for mobile devices (phones / tablets / etc.) and obviously anything "new" that gets added. -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-11-30 03:40 +0100 |
| Message-ID | <HFF85-9PdD-19@gated-at.bofh.it> |
| In reply to | #263961 |
On 30/11/2023 06:51, gene heskett wrote:
>
> Which is what I want to do but I've been told that
> /etc/network/interfaces is not the "today way" to do it.
What was the context when you have been told that?
If you are using NetworkManager then just change connection properties
to "manual" in the IPv4 section. Alternatively just configure ifupdown
(/etc/network/interfaces) and reboot if you are unsure how to reload
NetworkManager configuration. By default NetworkManager ignores
interfaces configured using ifupdown. I assume that neither tool
configured systemd-networkd on your machine. Check output of the
following commands
networkctl
nmcli
P.S. Enabling DHCP may allow to use default network configuration on all
devices.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-30 05:10 +0100 |
| Message-ID | <HFGxb-9QUY-5@gated-at.bofh.it> |
| In reply to | #263967 |
On 11/29/23 21:31, Max Nikulin wrote: > On 30/11/2023 06:51, gene heskett wrote: >> >> Which is what I want to do but I've been told that >> /etc/network/interfaces is not the "today way" to do it. > > What was the context when you have been told that? > > If you are using NetworkManager then just change connection properties > to "manual" in the IPv4 section. Alternatively just configure ifupdown > (/etc/network/interfaces) and reboot if you are unsure how to reload > NetworkManager configuration. By default NetworkManager ignores > interfaces configured using ifupdown. I assume that neither tool > configured systemd-networkd on your machine. Check output of the > following commands > > networkctl root@mkspi:/etc# networkctl WARNING: systemd-networkd is not running, output will be incomplete. IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback n/a unmanaged 2 eth0 ether n/a unmanaged 3 wlan0 wlan n/a unmanaged 3 links listed. > nmcli > root@mkspi:/etc# nmcli -bash: nmcli: command not found > P.S. Enabling DHCP may allow to use default network configuration on all > devices. hummmm, I'm logged in wit ssh: root@mkspi:/etc# cat default/networking # Configuration for networking init script being run during # the boot sequence # Set to 'no' to skip interfaces configuration on boot #CONFIGURE_INTERFACES=yes # Don't configure these interfaces. Shell wildcards supported/ #EXCLUDE_INTERFACES= # Set to 'yes' to enable additional verbosity #VERBOSE=no # Method to wait for the network to become online, # for services that depend on a working network: # - ifup: wait for ifup to have configured an interface. # - route: wait for a route to a given address to appear. # - ping/ping6: wait for a host to respond to ping packets. # - none: don't wait. #WAIT_ONLINE_METHOD=ifup # Which interface to wait for. # If none given, wait for all auto interfaces, or if there are none, # wait for at least one hotplug interface. #WAIT_ONLINE_IFACE= # Which address to wait for for route, ping and ping6 methods. # If none is given for route, it waits for a default gateway. #WAIT_ONLINE_ADDRESS= # Timeout in seconds for waiting for the network to come online. #WAIT_ONLINE_TIMEOUT=300 -----EOF----- What does all this tell someone more experienced? > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-11-30 06:00 +0100 |
| Message-ID | <HFHjz-9RyY-1@gated-at.bofh.it> |
| In reply to | #263970 |
On 30/11/2023 11:07, gene heskett wrote:
> root@mkspi:/etc# networkctl
> WARNING: systemd-networkd is not running, output will be incomplete.
>
> IDX LINK TYPE OPERATIONAL SETUP
> 1 lo loopback n/a unmanaged
> 2 eth0 ether n/a unmanaged
> 3 wlan0 wlan n/a unmanaged
So systemd-networkd does not manage network. (You may still get a bit
more from it by "networkctl status").
> root@mkspi:/etc# nmcli
> -bash: nmcli: command not found
The network-manager package is not installed, so likely it is ifupdown.
> On 11/29/23 21:31, Max Nikulin wrote:
>> P.S. Enabling DHCP may allow to use default network configuration on
>> all devices.
>
> hummmm, I'm logged in wit ssh:
> root@mkspi:/etc# cat default/networking
Charles suggests to enable DHCP server on your router and I support him.
Concerning this particular machine and static network configuration see
/etc/network/interfaces, interfaces(5),
https://wiki.debian.org/NetworkConfiguration (this link was almost
certainly posted in earlier threads).
grep -r '' /etc/network/interfaces{,.d}
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-30 10:20 +0100 |
| Message-ID | <HFLnc-9W9g-3@gated-at.bofh.it> |
| In reply to | #263975 |
On 11/29/23 23:52, Max Nikulin wrote:
> On 30/11/2023 11:07, gene heskett wrote:
>> root@mkspi:/etc# networkctl
>> WARNING: systemd-networkd is not running, output will be incomplete.
>>
>> IDX LINK TYPE OPERATIONAL SETUP
>> 1 lo loopback n/a unmanaged
>> 2 eth0 ether n/a unmanaged
>> 3 wlan0 wlan n/a unmanaged
>
> So systemd-networkd does not manage network. (You may still get a bit
> more from it by "networkctl status").
>
>> root@mkspi:/etc# nmcli
>> -bash: nmcli: command not found
>
> The network-manager package is not installed, so likely it is ifupdown.
>
>> On 11/29/23 21:31, Max Nikulin wrote:
>>> P.S. Enabling DHCP may allow to use default network configuration on
>>> all devices.
>>
>> hummmm, I'm logged in wit ssh:
>> root@mkspi:/etc# cat default/networking
>
> Charles suggests to enable DHCP server on your router and I support him.
>
> Concerning this particular machine and static network configuration see
> /etc/network/interfaces, interfaces(5),
> https://wiki.debian.org/NetworkConfiguration (this link was almost
> certainly posted in earlier threads).
>
> grep -r '' /etc/network/interfaces{,.d}
Got it, thank you.
>
>
> .
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-11-30 13:20 +0100 |
| Message-ID | <HFObn-9Zgl-1@gated-at.bofh.it> |
| In reply to | #263977 |
On Thu, Nov 30, 2023 at 09:39:04AM +0000, Bonno Bloksma wrote: > I never used the network manager as that is more work for me, I have no idea how that works even. ;-) You and me both. > -=-=-=-=-=-=- > $ cat /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > source /etc/network/interfaces.d/* > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > allow-hotplug ens32 > iface ens32 inet static > address 172.16.208.19 > netmask 255.255.255.0 > gateway 172.16.208.1 > -=-=-=-=-=-=- Depending on what services your computer runs, you may wish to change "allow-hotplug ens32" to "auto ens32". The latter will cause certain services (e.g. NFS server) to wait until the network interface has been brought up before starting. As you have it now, most services will not wait. Of course, if everything is working as you have it, then "don't touch it" is a wise course. But you may want to make a mental note, in case a problem happens at some point in the future. The usual symptom is "Such-and-such doesn't start at boot time, but if I login and start it manually, it works fine. I checked and the service is enabled, but it fails."
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-30 11:20 +0100 |
| Message-ID | <HFMjf-9X9a-1@gated-at.bofh.it> |
| In reply to | #263975 |
On 11/29/23 23:52, Max Nikulin wrote:
> On 30/11/2023 11:07, gene heskett wrote:
>> root@mkspi:/etc# networkctl
>> WARNING: systemd-networkd is not running, output will be incomplete.
>>
>> IDX LINK TYPE OPERATIONAL SETUP
>> 1 lo loopback n/a unmanaged
>> 2 eth0 ether n/a unmanaged
>> 3 wlan0 wlan n/a unmanaged
>
> So systemd-networkd does not manage network. (You may still get a bit
> more from it by "networkctl status").
>
>> root@mkspi:/etc# nmcli
>> -bash: nmcli: command not found
>
> The network-manager package is not installed, so likely it is ifupdown.
>
>> On 11/29/23 21:31, Max Nikulin wrote:
>>> P.S. Enabling DHCP may allow to use default network configuration on
>>> all devices.
>>
>> hummmm, I'm logged in wit ssh:
>> root@mkspi:/etc# cat default/networking
>
> Charles suggests to enable DHCP server on your router and I support him.
>
> Concerning this particular machine and static network configuration see
> /etc/network/interfaces, interfaces(5),
> https://wiki.debian.org/NetworkConfiguration (this link was almost
> certainly posted in earlier threads).
>
> grep -r '' /etc/network/interfaces{,.d}
>
>
However it did not work, and the file was replaced by one containing
only lo by networkmangler on a powerdown reboot. Next???
I want to put it at 192.168.71.100/24. How do I do that in
/etc/dhcpcd.conf? This is already in /etc/hosts like this:
-------------------
root@mkspi:~# cat /etc/hosts
127.0.0.1 localhost
192.168.71.1 router.coyote.den router
192.168.71.3 coyote.coyote.den coyote
192.168.71.100 mkspi.coyote.den mkspi
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
------------------
For reference, this is what I put in /e/n/i":
------------
auto eth0
iface eth0 inet static
address 192.168.71.100/24
gateway 192.168.71.1
dns-nameservers 192.168.71.1
-----------
That format worked on an rpi4b running debian arm64 bookworm, but not on
the armbian buster in this printer.
Thank you.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-11-30 13:40 +0100 |
| Message-ID | <HFOuJ-9Zww-1@gated-at.bofh.it> |
| In reply to | #263978 |
On 30/11/2023 17:15, gene heskett wrote:
> On 11/29/23 23:52, Max Nikulin wrote:
>> On 30/11/2023 11:07, gene heskett wrote:
>>
>>> root@mkspi:/etc# nmcli
>>> -bash: nmcli: command not found
-----------^^^^^^^^^^^^^^^^^^^^^^^^
> However it did not work, and the file was replaced by one containing
> only lo by networkmangler on a powerdown reboot. Next???
What particular file has been replaced? You do not have NetworkManager
installed
dpkg -S /usr/bin/nmcli
network-manager: /usr/bin/nmcli
Moreover in default configuration it does not touch
/etc/network/interfaces. It just reads it do avoid managing of the same
interfaces. May it be that klipper-related "optimizers" add some script?
> I want to put it at 192.168.71.100/24. How do I do that in
> /etc/dhcpcd.conf? This is already in /etc/hosts like this:
Forget it for a while. You either configure static IP address or DHCP
server on your router or on another host with properly configured network.
> For reference, this is what I put in /e/n/i":
> ------------
> auto eth0
> iface eth0 inet static
> address 192.168.71.100/24
> gateway 192.168.71.1
> dns-nameservers 192.168.71.1
I expect "dns-nameservers" may cause changes in /etc/resolv.conf if you
mean it. Are address and gateway settings applied?
ip address list
ip route list
Do you get any error in "journalctl -b" or in syslog files?
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-11-30 14:20 +0100 |
| Message-ID | <HFP7r-a0iz-7@gated-at.bofh.it> |
| In reply to | #263987 |
> On 30/11/2023 17:15, gene heskett wrote: > > I want to put it at 192.168.71.100/24. How do I do that in > > /etc/dhcpcd.conf? This is already in /etc/hosts like this: You're confusing the DHCP server and the DHCP client. People have told you that you must either configure the static IP on the host itself, *or* set up a DHCP server. If you're going to set up a DHCP server, then after choosing a computer to act as the server, and after installing the DHCP server package on it, you would configure dhcpd.conf (in some directory) to define your dynamic address pool, and any reserved addresses for specific hosts. Note the file name: dhcpd.conf which is composed of these pieces: dhcpd -- DHCP server daemon .conf -- configuration file In the text cited above, you referred to dhcpcd.conf which is completely different file. That one is for one of the several different DHCP *client* packages. In your case, it's for the "dhcpcd" package, which is not used by default in Debian, but *is* used by default in some Debian derivatives. dhcpcd -- DHCP client daemon (from the "dhcpcd" package) .conf -- configuration file Now, the real goal here is that you want to configure a static IP address on this host. If this were Debian, the answer would simply be "edit /etc/network/interfaces, kill dhcpcd if it's running, ifdown eth0, ifup eth0" (not necessarily in that order, and with various safeguards in place). However, you seem to be running a "twice derivative" OS of some kind -- it's Armbian with some special Klipper management script installed which takes over glob-knows-what. The number of people who know how to configure networking on a "Debian no wait it's Armbian no wait it's Klipper" host is probably quite small, and I'm not one of them. If you don't have instructions, then you may need to find a community of fellow Klipper users and ask them. Though I suspect the overwhelming majority of them use a DHCP server instead of static addressing on the host, you may get lucky and find one who does it your preferred way.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-30 20:00 +0100 |
| Message-ID | <HFUqu-a62q-35@gated-at.bofh.it> |
| In reply to | #263989 |
On 11/30/23 08:11, Greg Wooledge wrote: >> On 30/11/2023 17:15, gene heskett wrote: >>> I want to put it at 192.168.71.100/24. How do I do that in >>> /etc/dhcpcd.conf? This is already in /etc/hosts like this: > > You're confusing the DHCP server and the DHCP client. > > People have told you that you must either configure the static IP on > the host itself, *or* set up a DHCP server. > > If you're going to set up a DHCP server, then after choosing a computer > to act as the server, and after installing the DHCP server package on > it, you would configure dhcpd.conf (in some directory) to define your > dynamic address pool, and any reserved addresses for specific hosts. > > Note the file name: dhcpd.conf which is composed of these pieces: > > dhcpd -- DHCP server daemon > .conf -- configuration file > > In the text cited above, you referred to dhcpcd.conf which is completely > different file. That one is for one of the several different DHCP *client* > packages. In your case, it's for the "dhcpcd" package, which is not used > by default in Debian, but *is* used by default in some Debian derivatives. > > dhcpcd -- DHCP client daemon (from the "dhcpcd" package) > .conf -- configuration file > > Now, the real goal here is that you want to configure a static IP > address on this host. If this were Debian, the answer would simply be > "edit /etc/network/interfaces, kill dhcpcd if it's running, ifdown eth0, > ifup eth0" (not necessarily in that order, and with various safeguards > in place). However, you seem to be running a "twice derivative" OS of > some kind -- it's Armbian with some special Klipper management script > installed which takes over glob-knows-what. > It is armbian, klipper is just a program that runs on anything linux, maybe even winderz too but I wouldn't know, I don't allow winderz on the premises. I might use the hd for target practice. > The number of people who know how to configure networking on a > "Debian no wait it's Armbian no wait it's Klipper" host is probably quite > small, and I'm not one of them. If you don't have instructions, then > you may need to find a community of fellow Klipper users and ask them. > Though I suspect the overwhelming majority of them use a DHCP server > instead of static addressing on the host, you may get lucky and find one > who does it your preferred way. I found another place to put it, but haven't tried it yet. Busy with another project, making a solar power supply for a mailbox ygm alarm. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-11-30 19:50 +0100 |
| Message-ID | <HFUgN-a5Ts-3@gated-at.bofh.it> |
| In reply to | #263987 |
On 11/30/23 07:31, Max Nikulin wrote: > On 30/11/2023 17:15, gene heskett wrote: >> On 11/29/23 23:52, Max Nikulin wrote: >>> On 30/11/2023 11:07, gene heskett wrote: >>> >>>> root@mkspi:/etc# nmcli >>>> -bash: nmcli: command not found > -----------^^^^^^^^^^^^^^^^^^^^^^^^ > >> However it did not work, and the file was replaced by one containing >> only lo by networkmangler on a powerdown reboot. Next??? > > What particular file has been replaced? You do not have NetworkManager > installed /e/n/i waa replaced, and nothing in an ip a or ip r was changed. It was restored to: root@mkspi:/# cat /etc/network/interfaces source /etc/network/interfaces.d/* # Network is managed by Network manager<-this line I had removed auto lo iface lo inet loopback > > dpkg -S /usr/bin/nmcli > network-manager: /usr/bin/nmcli > > Moreover in default configuration it does not touch > /etc/network/interfaces. It just reads it do avoid managing of the same > interfaces. May it be that klipper-related "optimizers" add some script? > klipper runs fine on several other bananapi-m5 here, w/o any special treatment as lomg as /dev/serial/by-id is wotking, debian nroke it in buster and it will not be fixed again till trixie. Discord/klipper has patches for it. >> I want to put it at 192.168.71.100/24. How do I do that in >> /etc/dhcpcd.conf? This is already in /etc/hosts like this: > > Forget it for a while. You either configure static IP address or DHCP > server on your router or on another host with properly configured network. > >> For reference, this is what I put in /e/n/i": >> ------------ >> auto eth0 >> iface eth0 inet static >> address 192.168.71.100/24 >> gateway 192.168.71.1 >> dns-nameservers 192.168.71.1 > > I expect "dns-nameservers" may cause changes in /etc/resolv.conf if you > mean it. Are address and gateway settings applied? > > ip address list > ip route list > > Do you get any error in "journalctl -b" or in syslog files? > > . root@mkspi:/# journalctl -b -- Logs begin at Mon 2023-01-02 02:56:20 PST, end at Mon 2023-01-02 04:01:23 PST. -- Jan 02 02:56:20 mkspi bash[1443]: CTRL-EVENT-BSS-REMOVED 1289 50:27:a9:d2:aa:e3 Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 416 Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: Jan 02 02:56:20 mkspi bash[1443]: CTRL-EVENT-SCAN-RESULTS Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 418 Jan 02 02:56:20 mkspi bash[1443]: 已获取到了扫描的结果 Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 416 Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: Jan 02 02:56:20 mkspi bash[1443]: WPS-AP-AVAILABLE Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 439 Jan 02 02:56:20 mkspi bash[1443]: Available WPS AP found in scan results. Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 416 Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: Jan 02 02:56:20 mkspi bash[1443]: CTRL-EVENT-NETWORK-NOT-FOUND Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 416 Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: Jan 02 02:56:20 mkspi bash[1443]: CTRL-EVENT-SCAN-STARTED Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 416 Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: Jan 02 02:56:20 mkspi bash[1443]: CTRL-EVENT-BSS-ADDED 1305 98:da:c4:98:b2:19 Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 416 Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: Jan 02 02:56:20 mkspi bash[1443]: CTRL-EVENT-SCAN-RESULTS Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 418 Jan 02 02:56:20 mkspi bash[1443]: 已获取到了扫描的结果 Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 416 Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: Jan 02 02:56:20 mkspi bash[1443]: WPS-AP-AVAILABLE Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 439 Jan 02 02:56:20 mkspi bash[1443]: Available WPS AP found in scan results. Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 416 Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: Jan 02 02:56:20 mkspi bash[1443]: CTRL-EVENT-NETWORK-NOT-FOUND Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 416 Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: lines 1-36 Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
Page 2 of 5 — ← Prev page 1 [2] 3 4 5 Next page →
Back to top | Article view | linux.debian.user
csiph-web