Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #244291 > unrolled thread
| Started by | gene heskett <gheskett@shentel.net> |
|---|---|
| First post | 2022-01-22 00:50 +0100 |
| Last post | 2022-01-22 10:20 +0100 |
| Articles | 20 on this page of 78 — 16 participants |
Back to article view | Back to linux.debian.user
hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-22 00:50 +0100
Re: hostname is being reset, killing net on reboot "Andrew M.A. Cater" <amacater@einval.com> - 2022-01-22 00:50 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-22 01:30 +0100
Re: hostname is being reset, killing net on reboot Greg Wooledge <greg@wooledge.org> - 2022-01-22 01:50 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-22 03:40 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-22 04:10 +0100
Re: hostname is being reset, killing net on reboot Greg Wooledge <greg@wooledge.org> - 2022-01-22 04:50 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-22 06:00 +0100
Re: hostname is being reset, killing net on reboot <tomas@tuxteam.de> - 2022-01-22 08:10 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-22 10:40 +0100
Re: hostname is being reset, killing net on reboot <tomas@tuxteam.de> - 2022-01-22 11:20 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-22 13:20 +0100
Re: hostname is being reset, killing net on reboot Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-23 09:10 +0100
Re: hostname is being reset, killing net on reboot David Wright <deblis@lionunicorn.co.uk> - 2022-01-22 18:20 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-22 20:00 +0100
Re: hostname is being reset, killing net on reboot Greg Wooledge <greg@wooledge.org> - 2022-01-22 22:30 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-23 00:40 +0100
Re: hostname is being reset, killing net on reboot The Wanderer <wanderer@fastmail.fm> - 2022-01-23 01:10 +0100
Re: hostname is being reset, killing net on reboot David Wright <deblis@lionunicorn.co.uk> - 2022-01-23 03:10 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-23 03:30 +0100
Re: hostname is being reset, killing net on reboot The Wanderer <wanderer@fastmail.fm> - 2022-01-23 03:40 +0100
Re: hostname is being reset, killing net on reboot David Wright <deblis@lionunicorn.co.uk> - 2022-01-23 03:10 +0100
Re: hostname is being reset, killing net on reboot Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-23 09:00 +0100
Re: hostname is being reset, killing net on reboot Greg Wooledge <greg@wooledge.org> - 2022-01-23 14:50 +0100
Re: hostname is being reset, killing net on reboot Felix Miata <mrmazda@earthlink.net> - 2022-01-23 19:30 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-23 20:00 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-23 20:10 +0100
Re: hostname is being reset, killing net on reboot Charles Curley <charlescurley@charlescurley.com> - 2022-01-23 21:00 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-24 00:50 +0100
Re: hostname is being reset, killing net on reboot Charles Curley <charlescurley@charlescurley.com> - 2022-01-24 01:20 +0100
Re: hostname is being reset, killing net on reboot Greg Wooledge <greg@wooledge.org> - 2022-01-23 21:10 +0100
Re: hostname is being reset, killing net on reboot Felix Miata <mrmazda@earthlink.net> - 2022-01-23 21:20 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-24 01:00 +0100
Re: hostname is being reset, killing net on reboot David Wright <deblis@lionunicorn.co.uk> - 2022-01-24 17:40 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-25 01:00 +0100
Re: hostname is being reset, killing net on reboot Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-25 09:40 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-25 12:20 +0100
Re: hostname is being reset, killing net on reboot Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-25 13:10 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-25 17:30 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-25 18:00 +0100
Re: hostname is being reset, killing net on reboot David Wright <deblis@lionunicorn.co.uk> - 2022-01-26 01:40 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-26 03:30 +0100
Re: hostname is being reset, killing net on reboot Greg Wooledge <greg@wooledge.org> - 2022-01-26 05:20 +0100
Re: hostname is being reset, killing net on reboot David Wright <deblis@lionunicorn.co.uk> - 2022-01-26 05:40 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-26 11:20 +0100
Re: hostname is being reset, killing net on reboot David Wright <deblis@lionunicorn.co.uk> - 2022-01-26 17:50 +0100
Re: hostname is being reset, killing net on reboot Greg Wooledge <greg@wooledge.org> - 2022-01-26 18:00 +0100
Re: hostname is being reset, killing net on reboot Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-26 19:00 +0100
Re: hostname is being reset, killing net on reboot David Wright <deblis@lionunicorn.co.uk> - 2022-01-27 06:10 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-26 23:40 +0100
Re: hostname is being reset, killing net on reboot Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-26 19:20 +0100
Re: hostname is being reset, killing net on reboot Reco <recoverym4n@enotuniq.net> - 2022-01-26 20:00 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-26 16:40 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-26 16:50 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-26 16:50 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-26 23:40 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-26 17:10 +0100
Re: hostname is being reset, killing net on reboot David Wright <deblis@lionunicorn.co.uk> - 2022-01-26 17:50 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-26 20:30 +0100
Re: hostname is being reset, killing net on reboot Greg Wooledge <greg@wooledge.org> - 2022-01-26 20:50 +0100
Re: hostname is being reset, killing net on reboot Tixy <tixy@yxit.co.uk> - 2022-01-27 09:30 +0100
Re: hostname is being reset, killing net on reboot Dan Ritter <dsr@randomstring.org> - 2022-01-27 12:40 +0100
Re: hostname is being reset, killing net on reboot Brian <ad44@cityscape.co.uk> - 2022-01-27 15:10 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-23 22:50 +0100
Re: hostname is being reset, killing net on reboot David Wright <deblis@lionunicorn.co.uk> - 2022-01-23 17:00 +0100
Re: hostname is being reset, killing net on reboot Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-22 09:20 +0100
Re: hostname is being reset, killing net on reboot Lee <ler762@gmail.com> - 2022-01-23 03:00 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-23 03:20 +0100
Re: hostname is being reset, killing net on reboot <tomas@tuxteam.de> - 2022-01-22 08:00 +0100
Re: hostname is being reset, killing net on reboot David Wright <deblis@lionunicorn.co.uk> - 2022-01-22 18:20 +0100
Re: hostname is being reset, killing net on reboot <tomas@tuxteam.de> - 2022-01-22 07:50 +0100
Re: hostname is being reset, killing net on reboot Charles Curley <charlescurley@charlescurley.com> - 2022-01-22 15:40 +0100
Re: hostname is being reset, killing net on reboot <tomas@tuxteam.de> - 2022-01-22 17:10 +0100
Re: hostname is being reset, killing net on reboot gene heskett <gheskett@shentel.net> - 2022-01-22 23:30 +0100
Re: hostname is being reset, killing net on reboot "Andrew M.A. Cater" <amacater@einval.com> - 2022-01-23 00:00 +0100
Re: hostname is being reset, killing net on reboot deloptes <emanoil.kotsev@deloptes.org> - 2022-01-23 09:00 +0100
Re: hostname is being reset, killing net on reboot Curt <curty@free.fr> - 2022-01-22 10:10 +0100
Re: hostname is being reset, killing net on reboot <tomas@tuxteam.de> - 2022-01-22 10:20 +0100
Page 3 of 4 — ← Prev page 1 2 [3] 4 Next page →
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2022-01-26 01:40 +0100 |
| Message-ID | <DJEvT-1Ku-1@gated-at.bofh.it> |
| In reply to | #244571 |
On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote: > On Lu, 24 ian 22, 23:54:41, Brian wrote: > > > > Resolving hostnames on the local network is simple and reliable when > > avahi-daemon and linnss-mdns are available. > > > > brian@desktop:~$ getent hosts envy4500.local > > 192.168.7.235 envy4500.local > > > > Continually and nanually maintain /etc/hosts? Not in 2022! More like biannually :-) It's just pointless here, on such a static network. If I'm going to login to the router to add a MAC, then editing and distributing my master list is trivial. Last change: 2021-02-04, when I got hold of a redundant computer. > Ok, I'll bite :) > > Could you point to any (reasonably up-to-date) documentation or is it > sufficient to just install avahi-daemon and libnss-mdns? I looked at the Debian wiki: ouch. It seems to have been spammed a while back, and hasn't been touched in 4½ years. Although the Arch wiki is far better, I'm not able to judge how much one might be led astray by the differences between Arch and Debian. I can't speak to Gene's wanting a static network configured by his method, but I'm happy to defend my choice. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2022-01-26 03:30 +0100 |
| Message-ID | <DJGel-30A-1@gated-at.bofh.it> |
| In reply to | #244612 |
On Tuesday, January 25, 2022 7:35:54 PM EST David Wright wrote: > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote: > > On Lu, 24 ian 22, 23:54:41, Brian wrote: > > > Resolving hostnames on the local network is simple and reliable > > > when > > > avahi-daemon and linnss-mdns are available. > > > > > > brian@desktop:~$ getent hosts envy4500.local > > > 192.168.7.235 envy4500.local > > > > > > Continually and nanually maintain /etc/hosts? Not in 2022! > > More like biannually :-) > > It's just pointless here, on such a static network. If I'm going to > login to the router to add a MAC, then editing and distributing my > master list is trivial. Last change: 2021-02-04, when I got hold of > a redundant computer. > > > Ok, I'll bite :) > > > > Could you point to any (reasonably up-to-date) documentation or is it > > sufficient to just install avahi-daemon and libnss-mdns? > > I looked at the Debian wiki: ouch. It seems to have been spammed > a while back, and hasn't been touched in 4½ years. Although the > Arch wiki is far better, I'm not able to judge how much one might > be led astray by the differences between Arch and Debian. > > I can't speak to Gene's wanting a static network configured by his > method, but I'm happy to defend my choice. > > Cheers, > David. > It works fine with no complaints. Here is the bottom of /etc/dhcpcd.conf: # Example static IP configuration: #interface eth0 #static ip_address=192.168.0.10/24 #static ip6_address=fd51:42f8:caae:d92e::ff/64 #static routers=192.168.0.1 #static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1 # It is possible to fall back to a static IP if DHCP fails: # define static profile profile static_eth0 static ip_address=192.168.71.13/24 static routers=192.168.71.1 static domain_name_servers=192.168.71.1 # fallback to static profile on eth0 interface eth0 fallback static_eth0 So if dhcpd fails, it uses the above, and it Just Works. And I've not found any reference to it in the man page. So I've no clue why it seems to be such a huge, no one knows about it secret. Cheers David, and stay well, 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 Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2022-01-26 05:20 +0100 |
| Message-ID | <DJHWN-4kk-1@gated-at.bofh.it> |
| In reply to | #244614 |
On Tue, Jan 25, 2022 at 09:27:17PM -0500, gene heskett wrote: > Here is the bottom of /etc/dhcpcd.conf: WHY do you HAVE a dhcpcd.conf file if you don't use DHCP on your network? Or... well, you're not using Debian. You're using Raspbian, and Raspbian installs dhcpcd by default as I understand it. So that's why you HAVE the file. So I guess the real question is: WHY are you LOOKING AT this file, when you know that it's not used, because you don't have DHCP on your network? Or... if it turns out that it IS being used, even in the absence of a DHCP server, then go bother a Raspbian mailing list with your questions about this piece of software and the issues that it's causing you. Because those of us who run Debian, on the debian-user mailing list, do not typically install dhcpcd, nor do we know how it works. Debian uses isc-dhcp-client, which is a VERY different program.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2022-01-26 05:40 +0100 |
| Message-ID | <DJIg9-4sh-1@gated-at.bofh.it> |
| In reply to | #244614 |
On Tue 25 Jan 2022 at 21:27:17 (-0500), gene heskett wrote:
> On Tuesday, January 25, 2022 7:35:54 PM EST David Wright wrote:
> > I can't speak to Gene's wanting a static network configured by his
> > method, but I'm happy to defend my choice.
> >
> It works fine with no complaints.
OK. I've already forgotten what you complained in this thread's OP.
> Here is the bottom of /etc/dhcpcd.conf:
>
> # Example static IP configuration:
> #interface eth0
> #static ip_address=192.168.0.10/24
> #static ip6_address=fd51:42f8:caae:d92e::ff/64
> #static routers=192.168.0.1
> #static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1
>
> # It is possible to fall back to a static IP if DHCP fails:
> # define static profile
> profile static_eth0
> static ip_address=192.168.71.13/24
> static routers=192.168.71.1
> static domain_name_servers=192.168.71.1
>
> # fallback to static profile on eth0
> interface eth0
> fallback static_eth0
>
> So if dhcpd fails, it uses the above, and it Just Works.
> And I've not found any reference to it in the man page. So I've no clue
> why it seems to be such a huge, no one knows about it secret.
Drum roll … …
CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz
DHCPCD.CONF(5) BSD File Formats Manual DHCPCD.CONF(5)
NAME
dhcpcd.conf — dhcpcd configuration file
[ … ]
profile name
Subsequent options are only parsed for this profile name.
[ … ]
static value
Configures a static value. If you set ip_address then dhcpcd
will not attempt to obtain a lease and will just use the value
for the address with an infinite lease time. If you set
ip6_address, dhcpcd will continue auto-configuation as normal.
[ … ]
interface eth0
[ … ]
static ip_address=192.168.0.10/24
[ … ]
static routers=192.168.0.1
static domain_name_servers=192.168.0.1
[ … ]
fallback profile
Fall back to using this profile if DHCP fails. This allows you
to configure a static profile instead of using ZeroConf.
/That/ seems clear enough to me.
But excuse me if I was labouring under the impression that you wanted
to nuke DHCP lest "some coder dinking around in dhcp code thinks the
whole world is volatile".
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2022-01-26 11:20 +0100 |
| Message-ID | <DJNzb-8eB-1@gated-at.bofh.it> |
| In reply to | #244617 |
On Tuesday, January 25, 2022 11:36:05 PM EST David Wright wrote: > On Tue 25 Jan 2022 at 21:27:17 (-0500), gene heskett wrote: > > On Tuesday, January 25, 2022 7:35:54 PM EST David Wright wrote: > > > I can't speak to Gene's wanting a static network configured by his > > > method, but I'm happy to defend my choice. > > > > It works fine with no complaints. > > OK. I've already forgotten what you complained in this thread's OP. > > > Here is the bottom of /etc/dhcpcd.conf: > > > > # Example static IP configuration: > > #interface eth0 > > #static ip_address=192.168.0.10/24 > > #static ip6_address=fd51:42f8:caae:d92e::ff/64 > > #static routers=192.168.0.1 > > #static domain_name_servers=192.168.0.1 8.8.8.8 > > fd51:42f8:caae:d92e::1 > > > > # It is possible to fall back to a static IP if DHCP fails: > > # define static profile > > profile static_eth0 > > static ip_address=192.168.71.13/24 > > static routers=192.168.71.1 > > static domain_name_servers=192.168.71.1 > > > > # fallback to static profile on eth0 > > interface eth0 > > fallback static_eth0 > > > > So if dhcpd fails, it uses the above, and it Just Works. > > And I've not found any reference to it in the man page. So I've no > > clue why it seems to be such a huge, no one knows about it secret. > Drum roll … … > > CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz > > DHCPCD.CONF(5) BSD File Formats Manual > DHCPCD.CONF(5) > > NAME > dhcpcd.conf — dhcpcd configuration file > > [ … ] > > profile name > Subsequent options are only parsed for this profile name. > > [ … ] > > static value > Configures a static value. If you set ip_address then > dhcpcd will not attempt to obtain a lease and will just use the value > for the address with an infinite lease time. If you set ip6_address, > dhcpcd will continue auto-configuation as normal. > > [ … ] > > interface eth0 > [ … ] > static ip_address=192.168.0.10/24 > [ … ] > static routers=192.168.0.1 > static domain_name_servers=192.168.0.1 > > [ … ] > > fallback profile > Fall back to using this profile if DHCP fails. This > allows you to configure a static profile instead of using ZeroConf. > > /That/ seems clear enough to me. > `twould indeed be clear David, but man keeps telling me no such file. > But excuse me if I was labouring under the impression that you wanted > to nuke DHCP lest "some coder dinking around in dhcp code thinks the > whole world is volatile". The responses I get from this list or any list positively reeks of NIH syndrome if you want to do something different for a home net that doesn't depend on dhcp. hosts files existed and ran the internet before dhcp. I remember using them on both pc's and amiga's 30 years ago. Its the short term memory that is plaguing me now. Can you remember using trumpet on a pc? I can. The amiga's had miami for a net driver but I can't recall if I used it when I wrote our first web page server in ARexx we used when we went live on the net for news, pulling the text from the teleprompter. WDTV was in the first 5 tv stations in the country that had a web page that went live as the live tv news show closed. It also demo'd the atrocious spelling of our journalists which got rather hilarious at times. :o) At 87, I spend a lot of time contemplating the hereafter, I get up to go get a tool, and when I get to where the tool might be, I have to stop until I can remember what I'm hereafter. ;-) > Cheers, > David. > > . Take care and stay well David. 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 Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2022-01-26 17:50 +0100 |
| Message-ID | <DJTEC-3MD-11@gated-at.bofh.it> |
| In reply to | #244618 |
On Wed 26 Jan 2022 at 05:14:32 (-0500), gene heskett wrote: > On Tuesday, January 25, 2022 11:36:05 PM EST David Wright wrote: > > On Tue 25 Jan 2022 at 21:27:17 (-0500), gene heskett wrote: > > > On Tuesday, January 25, 2022 7:35:54 PM EST David Wright wrote: > > > > I can't speak to Gene's wanting a static network configured by his > > > > method, but I'm happy to defend my choice. > > > > > > It works fine with no complaints. > > > > OK. I've already forgotten what you complained [about] in this thread's OP. > > > > > Here is the bottom of /etc/dhcpcd.conf: > > > > > > # Example static IP configuration: > > > #interface eth0 > > > #static ip_address=192.168.0.10/24 > > > #static ip6_address=fd51:42f8:caae:d92e::ff/64 > > > #static routers=192.168.0.1 > > > #static domain_name_servers=192.168.0.1 8.8.8.8 > > > fd51:42f8:caae:d92e::1 > > > > > > # It is possible to fall back to a static IP if DHCP fails: > > > # define static profile > > > profile static_eth0 > > > static ip_address=192.168.71.13/24 > > > static routers=192.168.71.1 > > > static domain_name_servers=192.168.71.1 > > > > > > # fallback to static profile on eth0 > > > interface eth0 > > > fallback static_eth0 > > > > > > So if dhcpd fails, it uses the above, and it Just Works. > > > And I've not found any reference to it in the man page. So I've no > > > clue why it seems to be such a huge, no one knows about it secret. > > Drum roll … … > > > > CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz > > > > DHCPCD.CONF(5) BSD File Formats Manual > > DHCPCD.CONF(5) > > > > NAME > > dhcpcd.conf — dhcpcd configuration file > > > > [ … ] > > > > profile name > > Subsequent options are only parsed for this profile name. > > > > [ … ] > > > > static value > > Configures a static value. If you set ip_address then > > dhcpcd will not attempt to obtain a lease and will just use the value > > for the address with an infinite lease time. If you set ip6_address, > > dhcpcd will continue auto-configuation as normal. > > > > [ … ] > > > > interface eth0 > > [ … ] > > static ip_address=192.168.0.10/24 > > [ … ] > > static routers=192.168.0.1 > > static domain_name_servers=192.168.0.1 > > > > [ … ] > > > > fallback profile > > Fall back to using this profile if DHCP fails. This > > allows you to configure a static profile instead of using ZeroConf. > > > > /That/ seems clear enough to me. > > > `twould indeed be clear David, but man keeps telling me no such file. And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz" should tell you that I don't have that file either, but I downloaded dhcpcd5_7.1.0-2+b1_amd64.deb just as I did last time you raised this. And if I type "man" into google, I get a list of previously sought man pages as the response, rather than "camera tv". > > But excuse me if I was labouring under the impression that you wanted > > to nuke DHCP lest "some coder dinking around in dhcp code thinks the > > whole world is volatile". > > The responses I get from this list or any list positively reeks of NIH > syndrome if you want to do something different for a home net that > doesn't depend on dhcp. hosts files existed and ran the internet before > dhcp. And when you install Debian, it helpfully writes one for you. I don't know what is NIH about that. But your response here doesn't state unambiguously whether you want to run DHCP or not, nor whether you do or don't. Others have suggested that the OS you're actually dealing with is one that sets up certain things in a non-Debian manner. If so, then you need to investigate what those things are, and fit your changes round them, rather than just fighting it, trying to return to some "Golden Age" of networking from the 1990s. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2022-01-26 18:00 +0100 |
| Message-ID | <DJTOj-3QG-9@gated-at.bofh.it> |
| In reply to | #244630 |
On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote: > And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz" > should tell you that I don't have that file either, but I downloaded > dhcpcd5_7.1.0-2+b1_amd64.deb just as I did last time you raised this. > And if I type "man" into google, I get a list of previously sought > man pages as the response, rather than "camera tv". Why not just use <https://manpages.debian.org/bullseye/dhcpcd5/dhcpcd.conf.5.en.html>? Is it too new? You can replace "bullseye" with "buster" in the URL. Or "stretch", etc.
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2022-01-26 19:00 +0100 |
| Message-ID | <DJUKm-4to-3@gated-at.bofh.it> |
| In reply to | #244632 |
[Multipart message — attachments visible in raw view] — view raw
On Mi, 26 ian 22, 11:55:36, Greg Wooledge wrote: > On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote: > > And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz" > > should tell you that I don't have that file either, but I downloaded > > dhcpcd5_7.1.0-2+b1_amd64.deb just as I did last time you raised this. > > And if I type "man" into google, I get a list of previously sought > > man pages as the response, rather than "camera tv". > > Why not just use > <https://manpages.debian.org/bullseye/dhcpcd5/dhcpcd.conf.5.en.html>? +1 for manpages.debian.org, it's even possible to have it as an additional search engine in browsers that support it. > Is it too new? You can replace "bullseye" with "buster" in the URL. > Or "stretch", etc. I should close #931992 then ;) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2022-01-27 06:10 +0100 |
| Message-ID | <DK5cJ-3je-5@gated-at.bofh.it> |
| In reply to | #244634 |
On Wed 26 Jan 2022 at 18:56:17 (+0100), Andrei POPESCU wrote: > On Mi, 26 ian 22, 11:55:36, Greg Wooledge wrote: > > On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote: > > > And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz" > > > should tell you that I don't have that file either, but I downloaded > > > dhcpcd5_7.1.0-2+b1_amd64.deb just as I did last time you raised this. > > > And if I type "man" into google, I get a list of previously sought > > > man pages as the response, rather than "camera tv". > > > > Why not just use > > <https://manpages.debian.org/bullseye/dhcpcd5/dhcpcd.conf.5.en.html>? For pasting the manpage extracts? That's simple. In https://lists.debian.org/debian-user/2022/01/msg01055.html Gene quoted "the bottom of /etc/dhcpcd.conf" so I needed to see that file. $ apt-file find /etc/dhcpcd.conf dhcpcd5: /etc/dhcpcd.conf $ Have I got, or ever even seen, package dhcpcd5? Leaving off the 5 in case it's a version number: $ grep -r dhcpcd /home/debian/packages/ ~/pc/configure/out-of-date/dpkg-l-* $ No—never installed it, going back as far as hamm. So, off to https://packages.debian.org/index to get the link, and wget downloads the package into /home/debian/bullseye/dhcpcd5_7.1.0-2+b1_amd64.deb as there's no point in apt-get -d putting it into my cache. (Besides, I'm here sitting at a buster machine.) Then mc opens the .deb file as if it were a local directory. Everything's there: the configuration file itself, and all the docs, including the manpage(s). So why use <https://manpages.debian.org/bullseye/dhcpcd5/dhcpcd.conf.5.en.html>? Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2022-01-26 23:40 +0100 |
| Message-ID | <DJZ7j-7zo-3@gated-at.bofh.it> |
| In reply to | #244632 |
On Wednesday, January 26, 2022 11:55:36 AM EST Greg Wooledge wrote: > On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote: > > And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz" > > should tell you that I don't have that file either, but I downloaded > > dhcpcd5_7.1.0-2+b1_amd64.deb just as I did last time you raised this. > > And if I type "man" into google, I get a list of previously sought > > man pages as the response, rather than "camera tv". > > Why not just use > <https://manpages.debian.org/bullseye/dhcpcd5/dhcpcd.conf.5.en.html>? > Is it too new? You can replace "bullseye" with "buster" in the URL. > Or "stretch", etc. > I wasn't aware of that resource, 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 Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2022-01-26 19:20 +0100 |
| Message-ID | <DJV3H-4Rd-1@gated-at.bofh.it> |
| In reply to | #244614 |
[Multipart message — attachments visible in raw view] — view raw
On Ma, 25 ian 22, 21:27:17, gene heskett wrote: > > It works fine with no complaints. > > Here is the bottom of /etc/dhcpcd.conf: > > # Example static IP configuration: > #interface eth0 > #static ip_address=192.168.0.10/24 > #static ip6_address=fd51:42f8:caae:d92e::ff/64 > #static routers=192.168.0.1 > #static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1 > > # It is possible to fall back to a static IP if DHCP fails: > # define static profile > profile static_eth0 > static ip_address=192.168.71.13/24 > static routers=192.168.71.1 > static domain_name_servers=192.168.71.1 > > # fallback to static profile on eth0 > interface eth0 > fallback static_eth0 > > So if dhcpd fails, it uses the above, and it Just Works. > And I've not found any reference to it in the man page. So I've no clue > why it seems to be such a huge, no one knows about it secret. This must be the most complicated, round-about, inefficient method I've ever seen to configure a static IP :) Is it so difficult to find out what is the canonical method to configure a static IP on a Raspberry Pi OS? This is such a basic task it should be somewhere in their documentation, wiki, whatever. Even if they don't officially support static IPs (which I seriously doubt), you could still find out what is starting dhcpcd and disable it. Then it should be possible to configure a static IP with any of Debian's network management tools you like. You might need to install it first though, preferably while the network connection is still up ;). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2022-01-26 20:00 +0100 |
| Message-ID | <DJVGq-57v-1@gated-at.bofh.it> |
| In reply to | #244635 |
On Wed, Jan 26, 2022 at 07:11:36PM +0100, Andrei POPESCU wrote: > > # fallback to static profile on eth0 > > interface eth0 > > fallback static_eth0 > > > > So if dhcpd fails, it uses the above, and it Just Works. > > And I've not found any reference to it in the man page. So I've no clue > > why it seems to be such a huge, no one knows about it secret. > > This must be the most complicated, round-about, inefficient method I've > ever seen to configure a static IP :) I disagree. One can install NetworkManager, and then it will get even more complicated. > Is it so difficult to find out what is the canonical method to configure > a static IP on a Raspberry Pi OS? This is such a basic task it should be > somewhere in their documentation, wiki, whatever. Curiously enough, this time Gene used "official" way to configure static IP on RPi - [1]. Official documentation does not even mention e/n/i. > Then it should be possible to configure a static IP with any of Debian's > network management tools you like. And *that* would be fighting the distribution-approved method, and not working with it. It's totally possible (I did it), but then again, it's totally possible to install a real Debian on RPi. All this once again proves us, folks - RaspberryPi OS is not Debian. It's Debian-based. Certain list members do not see the difference, let's refrain from pointing fingers :) Reco [1] https://www.raspberrypi.com/documentation/computers/configuration.html#static-ip-addresses
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2022-01-26 16:40 +0100 |
| Message-ID | <DJSyS-36Q-15@gated-at.bofh.it> |
| In reply to | #244612 |
On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote: > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote: > > On Lu, 24 ian 22, 23:54:41, Brian wrote: > > > > > > Resolving hostnames on the local network is simple and reliable when > > > avahi-daemon and linnss-mdns are available. > > > > > > brian@desktop:~$ getent hosts envy4500.local > > > 192.168.7.235 envy4500.local > > > > > > Continually and nanually maintain /etc/hosts? Not in 2022! > > More like biannually :-) > > It's just pointless here, on such a static network. If I'm going to > login to the router to add a MAC, then editing and distributing my > master list is trivial. Last change: 2021-02-04, when I got hold of > a redundant computer. I am sure sue the use of the dawn of time /etc/hosts is a workabble solution. However many (most?) users will have libnns-mdns installed and immediately up to the job of resolving hostnames on a statically or dynamically configured network and is maintenance-free. Why not use it? > > Ok, I'll bite :) > > > > Could you point to any (reasonably up-to-date) documentation or is it > > sufficient to just install avahi-daemon and libnss-mdns? > > I looked at the Debian wiki: ouch. It seems to have been spammed > a while back, and hasn't been touched in 4½ years. Although the > Arch wiki is far better, I'm not able to judge how much one might > be led astray by the differences between Arch and Debian. Ouch indeed! The baisc structure and content of the wiki page was established in 2006. Its stated purpose is for "...tracking how Debian supports mdns and zeroconf stuff,...". The Discussion section is (IMO) inappropriate for a wiki page. The Arch wiki page is technically more informed and, with care, would guide a Debian user in the right direcion. Having said that, 'ssh desktop.local' does not require much guidance. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2022-01-26 16:50 +0100 |
| Message-ID | <DJSIx-3aE-3@gated-at.bofh.it> |
| In reply to | #244625 |
On Wednesday, January 26, 2022 10:31:46 AM EST Brian wrote: > On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote: > > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote: > > > On Lu, 24 ian 22, 23:54:41, Brian wrote: > > > > Resolving hostnames on the local network is simple and reliable > > > > when > > > > avahi-daemon and linnss-mdns are available. > > > > > > > > brian@desktop:~$ getent hosts envy4500.local > > > > 192.168.7.235 envy4500.local > > > > > > > > Continually and nanually maintain /etc/hosts? Not in 2022! > > > > More like biannually :-) > > > > It's just pointless here, on such a static network. If I'm going to > > login to the router to add a MAC, then editing and distributing my > > master list is trivial. Last change: 2021-02-04, when I got hold of > > a redundant computer. > > I am sure sue the use of the dawn of time /etc/hosts is a workabble > solution. However many (most?) users will have libnns-mdns installed > and immediately up to the job of resolving hostnames on a statically > or dynamically configured network and is maintenance-free. Why not use > it? > > > > Ok, I'll bite :) > > > > > > Could you point to any (reasonably up-to-date) documentation or is > > > it > > > sufficient to just install avahi-daemon and libnss-mdns? > > > > I looked at the Debian wiki: ouch. It seems to have been spammed > > a while back, and hasn't been touched in 4½ years. Although the > > Arch wiki is far better, I'm not able to judge how much one might > > be led astray by the differences between Arch and Debian. > > Ouch indeed! The baisc structure and content of the wiki page was > established in 2006. Its stated purpose is for "...tracking how Debian > supports mdns and zeroconf stuff,...". The Discussion section is (IMO) > inappropriate for a wiki page. > > The Arch wiki page is technically more informed and, with care, would > guide a Debian user in the right direcion. > > Having said that, 'ssh desktop.local' does not require much guidance. If a machine is "there" to reply, which one is it? 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 Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2022-01-26 16:50 +0100 |
| Message-ID | <DJSIx-3aE-9@gated-at.bofh.it> |
| In reply to | #244626 |
On Wed 26 Jan 2022 at 10:39:42 -0500, gene heskett wrote: > On Wednesday, January 26, 2022 10:31:46 AM EST Brian wrote: > > On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote: > > > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote: > > > > On Lu, 24 ian 22, 23:54:41, Brian wrote: > > > > > Resolving hostnames on the local network is simple and reliable > > > > > when > > > > > avahi-daemon and linnss-mdns are available. > > > > > > > > > > brian@desktop:~$ getent hosts envy4500.local > > > > > 192.168.7.235 envy4500.local > > > > > > > > > > Continually and nanually maintain /etc/hosts? Not in 2022! > > > > > > More like biannually :-) > > > > > > It's just pointless here, on such a static network. If I'm going to > > > login to the router to add a MAC, then editing and distributing my > > > master list is trivial. Last change: 2021-02-04, when I got hold of > > > a redundant computer. > > > > I am sure sue the use of the dawn of time /etc/hosts is a workabble > > solution. However many (most?) users will have libnns-mdns installed > > and immediately up to the job of resolving hostnames on a statically > > or dynamically configured network and is maintenance-free. Why not use > > it? > > > > > > Ok, I'll bite :) > > > > > > > > Could you point to any (reasonably up-to-date) documentation or is > > > > it > > > > sufficient to just install avahi-daemon and libnss-mdns? > > > > > > I looked at the Debian wiki: ouch. It seems to have been spammed > > > a while back, and hasn't been touched in 4½ years. Although the > > > Arch wiki is far better, I'm not able to judge how much one might > > > be led astray by the differences between Arch and Debian. > > > > Ouch indeed! The baisc structure and content of the wiki page was > > established in 2006. Its stated purpose is for "...tracking how Debian > > supports mdns and zeroconf stuff,...". The Discussion section is (IMO) > > inappropriate for a wiki page. > > > > The Arch wiki page is technically more informed and, with care, would > > guide a Debian user in the right direcion. > > > > Having said that, 'ssh desktop.local' does not require much guidance. > > If a machine is "there" to reply, which one is it? Sorry, I don't follow. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2022-01-26 23:40 +0100 |
| Message-ID | <DJZ7j-7zo-5@gated-at.bofh.it> |
| In reply to | #244627 |
On Wednesday, January 26, 2022 10:49:35 AM EST Brian wrote: > On Wed 26 Jan 2022 at 10:39:42 -0500, gene heskett wrote: > > On Wednesday, January 26, 2022 10:31:46 AM EST Brian wrote: > > > On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote: > > > > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote: > > > > > On Lu, 24 ian 22, 23:54:41, Brian wrote: > > > > > > Resolving hostnames on the local network is simple and > > > > > > reliable > > > > > > when > > > > > > avahi-daemon and linnss-mdns are available. > > > > > > > > > > > > brian@desktop:~$ getent hosts envy4500.local > > > > > > 192.168.7.235 envy4500.local > > > > > > > > > > > > Continually and nanually maintain /etc/hosts? Not in 2022! > > > > > > > > More like biannually :-) > > > > > > > > It's just pointless here, on such a static network. If I'm going > > > > to > > > > login to the router to add a MAC, then editing and distributing > > > > my > > > > master list is trivial. Last change: 2021-02-04, when I got hold > > > > of > > > > a redundant computer. > > > > > > I am sure sue the use of the dawn of time /etc/hosts is a workabble > > > solution. However many (most?) users will have libnns-mdns > > > installed > > > and immediately up to the job of resolving hostnames on a > > > statically > > > or dynamically configured network and is maintenance-free. Why not > > > use > > > it? > > > > > > > > Ok, I'll bite :) > > > > > > > > > > Could you point to any (reasonably up-to-date) documentation or > > > > > is > > > > > it > > > > > sufficient to just install avahi-daemon and libnss-mdns? > > > > > > > > I looked at the Debian wiki: ouch. It seems to have been spammed > > > > a while back, and hasn't been touched in 4½ years. Although the > > > > Arch wiki is far better, I'm not able to judge how much one might > > > > be led astray by the differences between Arch and Debian. > > > > > > Ouch indeed! The baisc structure and content of the wiki page was > > > established in 2006. Its stated purpose is for "...tracking how > > > Debian > > > supports mdns and zeroconf stuff,...". The Discussion section is > > > (IMO) > > > inappropriate for a wiki page. > > > > > > The Arch wiki page is technically more informed and, with care, > > > would > > > guide a Debian user in the right direcion. > > > > > > Having said that, 'ssh desktop.local' does not require much > > > guidance. > > > > If a machine is "there" to reply, which one is it? > > Sorry, I don't follow. IDK for sure, but the descriptions I've speed read, seem to indicate a rather wild card approach, and that spooks me a bit, so I was trying to be a little facetious. Obviously I failed. Thanks Brian 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 Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2022-01-26 17:10 +0100 |
| Message-ID | <DJT1U-3xo-9@gated-at.bofh.it> |
| In reply to | #244625 |
On Wed 26 Jan 2022 at 15:54:38 +0000, mick crane wrote: > On 2022-01-26 15:31, Brian wrote: > > > Having said that, 'ssh desktop.local' does not require much guidance. > > Is .local mDNS specific ? Yes. > I thought we are supposed to not use .local for a home network. That caveat is for allocating a domain name. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2022-01-26 17:50 +0100 |
| Message-ID | <DJTEC-3MD-9@gated-at.bofh.it> |
| In reply to | #244625 |
On Wed 26 Jan 2022 at 15:31:46 (+0000), Brian wrote: > On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote: > > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote: > > > On Lu, 24 ian 22, 23:54:41, Brian wrote: > > > > > > > > Resolving hostnames on the local network is simple and reliable when > > > > avahi-daemon and linnss-mdns are available. > > > > > > > > brian@desktop:~$ getent hosts envy4500.local > > > > 192.168.7.235 envy4500.local > > > > > > > > Continually and nanually maintain /etc/hosts? Not in 2022! > > > > More like biannually :-) > > > > It's just pointless here, on such a static network. If I'm going to > > login to the router to add a MAC, then editing and distributing my > > master list is trivial. Last change: 2021-02-04, when I got hold of > > a redundant computer. > > I am sure sue the use of the dawn of time /etc/hosts is a workabble > solution. However many (most?) users will have libnns-mdns installed > and immediately up to the job of resolving hostnames on a statically > or dynamically configured network and is maintenance-free. Why not use > it? Me personally? Because I want to avoid any complications with configuring two cooperating routers; because I want to be able to spot "foreign" interfaces by IP# (my brain doesn't work with either UUIDs or MACs); because I want to be able to poke a hole into my network, which raises security concerns; because I want to recognise that two IP#s point to the same machine (MACs again); because knowing how it all works is more valuable to me than the effort of lifting a finger to maintain it once in a while. Bear in mind that I'm likely installing Debian on something at the time I'm making said tweak, and perhaps having to relocate some functionailty to another machine if there's one heading for recycling at the same time. With running the d-i and configuring the router, what's to get worked up about with adding a line to /etc/hosts? I've worked this way for 15 years and, unlike Gene, I'm not having to fight any battles over it. I'm sure mDNS is perfect for people with different demands from mine. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2022-01-26 20:30 +0100 |
| Message-ID | <DJW9r-5zA-1@gated-at.bofh.it> |
| In reply to | #244629 |
On Wed 26 Jan 2022 at 10:42:38 -0600, David Wright wrote: [Snipping] > I've worked this way for 15 years and, unlike Gene, I'm not having > to fight any battles over it. I'm sure mDNS is perfect for people > with different demands from mine. My question was really directed at all users, particularly those who do not appreciate the existance or basic function of Avahi. I am not dead set aginst /etc/hosts and the explantion of your successful mode of working should give pause for thought. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2022-01-26 20:50 +0100 |
| Message-ID | <DJWsO-5Hh-11@gated-at.bofh.it> |
| In reply to | #244639 |
On Wed, Jan 26, 2022 at 07:26:49PM +0000, Brian wrote: > On Wed 26 Jan 2022 at 10:42:38 -0600, David Wright wrote: > > I've worked this way for 15 years and, unlike Gene, I'm not having > > to fight any battles over it. I'm sure mDNS is perfect for people > > with different demands from mine. > > My question was really directed at all users, particularly those who > do not appreciate the existance or basic function of Avahi. I am not > dead set aginst /etc/hosts and the explantion of your successful mode > of working should give pause for thought. I don't know how many people know *anything* about it at all. I certainly don't, other than what's been mentioned in this thread.
[toc] | [prev] | [next] | [standalone]
Page 3 of 4 — ← Prev page 1 2 [3] 4 Next page →
Back to top | Article view | linux.debian.user
csiph-web