Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #188193 > unrolled thread
| Started by | Roberto C. Sánchez <roberto@debian.org> |
|---|---|
| First post | 2017-10-23 04:20 +0200 |
| Last post | 2017-10-25 16:20 +0200 |
| Articles | 20 on this page of 138 — 29 participants |
Back to article view | Back to linux.debian.user
Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-23 04:20 +0200
Re: Why does resolv.conf keep changing? Joe <joe@jretrading.com> - 2017-10-23 11:00 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-23 11:50 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-24 01:40 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-24 02:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-24 05:10 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-24 09:20 +0200
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-24 14:20 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-24 14:30 +0200
Re: Why does resolv.conf keep changing? Curt <curty@free.fr> - 2017-10-24 19:10 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-24 18:50 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 15:40 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-25 20:50 +0200
Re: Why does resolv.conf keep changing? Roger Lynn <Roger@rilynn.me.uk> - 2017-10-25 00:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 04:10 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-23 13:00 +0200
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-23 18:10 +0200
Re: Why does resolv.conf keep changing? Jude DaShiell <jdashiel@panix.com> - 2017-10-23 18:10 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-23 23:10 +0200
Re: Why does resolv.conf keep changing? Dan Ritter <dsr@randomstring.org> - 2017-10-24 00:00 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-24 02:40 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 03:20 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 05:00 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 05:10 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 06:20 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 13:40 +0200
Re: Why does resolv.conf keep changing? Alberto Luaces <aluaces@udc.es> - 2017-10-25 14:10 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 15:50 +0200
Re: Why does resolv.conf keep changing? Curt <curty@free.fr> - 2017-10-25 16:30 +0200
Re: Why does resolv.conf keep changing? Joe <joe@jretrading.com> - 2017-10-25 17:10 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 17:30 +0200
Re: Why does resolv.conf keep changing? rhkramer@gmail.com - 2017-10-25 19:00 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 19:10 +0200
Re: Why does resolv.conf keep changing? rhkramer@gmail.com - 2017-10-25 19:40 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 14:20 +0200
Re: Why does resolv.conf keep changing? Felix Miata <mrmazda@earthlink.net> - 2017-10-25 05:50 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 13:40 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 14:00 +0200
Re: Why does resolv.conf keep changing? tomas@tuxteam.de - 2017-10-25 14:20 +0200
Re: Why does resolv.conf keep changing? Nicolas George <george@nsup.org> - 2017-10-25 14:50 +0200
Re: Why does resolv.conf keep changing? Joe <joe@jretrading.com> - 2017-10-25 14:10 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 14:20 +0200
Re: Why does resolv.conf keep changing? Joe <joe@jretrading.com> - 2017-10-25 15:00 +0200
Re: Why does resolv.conf keep changing? Dan Ritter <dsr@randomstring.org> - 2017-10-25 17:10 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 18:50 +0200
Re: Why does resolv.conf keep changing? Don Armstrong <don@debian.org> - 2017-10-25 21:30 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 13:40 +0200
Re: Why does resolv.conf keep changing? Glenn English <ghe2001@gmail.com> - 2017-10-26 17:40 +0200
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-26 17:50 +0200
Re: Why does resolv.conf keep changing? The Wanderer <wanderer@fastmail.fm> - 2017-10-26 18:00 +0200
Re: Why does resolv.conf keep changing? Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-26 18:20 +0200
Re: Why does resolv.conf keep changing? Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-26 18:40 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-27 02:00 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-27 02:00 +0200
Re: Why does resolv.conf keep changing? Jörg-Volker Peetz <jvpeetz@web.de> - 2017-10-23 12:10 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 05:50 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 06:10 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 06:50 +0200
Re: Why does resolv.conf keep changing? Curt <curty@free.fr> - 2017-10-25 08:50 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 14:40 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 14:50 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 15:00 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 15:10 +0200
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-25 15:10 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 15:10 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 16:10 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 16:10 +0200
[SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 20:30 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 20:40 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-25 20:40 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-25 21:00 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 21:00 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 15:10 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-26 15:40 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 16:00 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Don Armstrong <don@debian.org> - 2017-10-26 21:40 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 21:40 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-26 16:30 +0200
The new normal of logging Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-10-26 21:10 +0200
Re: The new normal of logging Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-26 21:30 +0200
Re: The new normal of logging Gene Heskett <gheskett@shentel.net> - 2017-10-27 02:10 +0200
Re: The new normal of logging Ben Caradoc-Davies <ben@transient.nz> - 2017-10-27 03:30 +0200
Re: The new normal of logging Gene Heskett <gheskett@shentel.net> - 2017-10-27 07:00 +0200
Re: The new normal of logging Ben Caradoc-Davies <ben@transient.nz> - 2017-10-28 04:50 +0200
Re: The new normal of logging Gene Heskett <gheskett@shentel.net> - 2017-10-28 08:10 +0200
Re: The new normal of logging Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2017-10-27 04:10 +0200
Re: The new normal of logging Darac Marjal <mailinglist@darac.org.uk> - 2017-10-27 11:40 +0200
Plain text vs. binary (was Re: The new normal of logging) The Wanderer <wanderer@fastmail.fm> - 2017-10-27 14:40 +0200
Re: The new normal of logging Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 21:30 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-27 17:10 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-27 17:50 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Curt <curty@free.fr> - 2017-10-27 20:30 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Brian <ad44@cityscape.co.uk> - 2017-10-27 20:50 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Curt <curty@free.fr> - 2017-10-27 21:50 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-27 22:00 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-28 18:30 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-26 05:40 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 12:50 +0200
Re: Why does resolv.conf keep changing? Darac Marjal <mailinglist@darac.org.uk> - 2017-10-26 13:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 13:50 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-26 16:40 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 17:00 +0200
Re: Why does resolv.conf keep changing? Mart van de Wege <mvdwege@gmail.com> - 2017-10-27 10:10 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-27 13:50 +0200
Re: Why does resolv.conf keep changing? Darac Marjal <mailinglist@darac.org.uk> - 2017-10-27 14:20 +0200
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-27 14:40 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-27 20:50 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-27 20:50 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-27 16:20 +0200
Re: Why does resolv.conf keep changing? Mart van de Wege <mvdwege@gmail.com> - 2017-10-28 00:10 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-28 00:10 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-28 02:00 +0200
Re: Why does resolv.conf keep changing? Mart van de Wege <mvdwege@gmail.com> - 2017-10-28 15:30 +0200
Re: Why does resolv.conf keep changing? Glenn English <ghe2001@gmail.com> - 2017-10-28 18:50 +0200
Re: Why does resolv.conf keep changing? Mart van de Wege <mvdwege@gmail.com> - 2017-10-28 15:40 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-27 16:40 +0200
Re: Why does resolv.conf keep changing? Mart van de Wege <mvdwege@gmail.com> - 2017-10-28 00:10 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-27 16:30 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-28 02:40 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-26 14:40 +0200
Re: Why does resolv.conf keep changing? Roger Lynn <Roger@rilynn.me.uk> - 2017-11-04 00:30 +0100
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-11-04 08:50 +0100
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-11-04 13:10 +0100
Re: Why does resolv.conf keep changing? Brian <ad44@cityscape.co.uk> - 2017-11-04 22:00 +0100
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-11-04 22:10 +0100
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-11-04 22:10 +0100
Re: Why does resolv.conf keep changing? Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-11-04 15:40 +0100
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-26 15:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 15:00 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 15:10 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 16:20 +0200
Page 2 of 7 — ← Prev page 1 [2] 3 4 5 6 7 Next page →
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2017-10-24 00:00 +0200 |
| Message-ID | <uDSVk-2EN-7@gated-at.bofh.it> |
| In reply to | #188220 |
On Mon, Oct 23, 2017 at 05:03:30PM -0400, Gene Heskett wrote: > On Monday 23 October 2017 11:48:36 Jude DaShiell wrote: > > > If you've got dynamic ip addresses as many of us do, that file has to > > change to keep your internet connection up. > > > This true, but all the isp's I have dealt with over the last 23 years, > have all assigned that dynamic address BASED on the MAC of the device > doing the requesting. So while my router(s) do use dhcp to get its > internet address, I can even swap routers as long as I clone the > originals MAC address into the replacement. > You're conflating two different things, Gene. DHCP assigns a dynamic IP address. That's the main job. And it will provide a default router along with that. The original poster wants that. It also has lots of optional bits of data that it can provide, but doesn't have to. Among those: - DNS server addresses - default domain names - NTP servers - TFTP servers - NFS servers The original poster does not want their machine to pay attention to any of that, even if it is supplied. The full list, I think, is a little overwhelming: https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml -dsr-
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-10-24 02:40 +0200 |
| Message-ID | <uDVqa-4eF-1@gated-at.bofh.it> |
| In reply to | #188221 |
On Monday 23 October 2017 17:51:35 Dan Ritter wrote: > On Mon, Oct 23, 2017 at 05:03:30PM -0400, Gene Heskett wrote: > > On Monday 23 October 2017 11:48:36 Jude DaShiell wrote: > > > If you've got dynamic ip addresses as many of us do, that file has > > > to change to keep your internet connection up. > > > > This true, but all the isp's I have dealt with over the last 23 > > years, have all assigned that dynamic address BASED on the MAC of > > the device doing the requesting. So while my router(s) do use dhcp > > to get its internet address, I can even swap routers as long as I > > clone the originals MAC address into the replacement. > > You're conflating two different things, Gene. > > DHCP assigns a dynamic IP address. That's the main job. And it > will provide a default router along with that. The original > poster wants that. > > It also has lots of optional bits of data that it can provide, > but doesn't have to. Among those: > > - DNS server addresses > - default domain names > - NTP servers > - TFTP servers > - NFS servers > > The original poster does not want their machine to pay attention > to any of that, even if it is supplied. > > The full list, I think, is a little overwhelming: > > https://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-para >meters.xhtml > > -dsr- Having looked at the dhcpd code quite some time back, "its complex" is a gross understatement. But if the OP wants access, his router HAS to use the address the ISP assigns. Here, my local net is entirely hard coded and made immutable. Particularly is the fact that /etc/resolv.conf isn't a link to something else but contains: nameserver 192.168.XX.1 search host dns domain coyote.den And is made immutable. Where XX is the block in class D that is mine. 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) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2017-10-25 03:20 +0200 |
| Message-ID | <uEiwq-1RN-1@gated-at.bofh.it> |
| In reply to | #188228 |
On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote: >and made immutable. Particularly is the fact that /etc/resolv.conf isn't >a link to something else but contains: > >nameserver 192.168.XX.1 >search host dns >domain coyote.den Please stop posting that, it uses incorrect syntax (as has been explained to you before) and it would be a shame if other people copied it as a correct example. Mike Stone
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-10-25 05:00 +0200 |
| Message-ID | <uEk5b-2J8-3@gated-at.bofh.it> |
| In reply to | #188254 |
On Tuesday 24 October 2017 21:06:58 Michael Stone wrote: > On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote: > >and made immutable. Particularly is the fact that /etc/resolv.conf > > isn't a link to something else but contains: > > > >nameserver 192.168.XX.1 > >search host dns > >domain coyote.den > > Please stop posting that, it uses incorrect syntax (as has been > explained to you before) and it would be a shame if other people > copied it as a correct example. > > Mike Stone Mike, I think you said that before, but didn't correct it ATT, but I wrote it while referencing the man page for resolv.conf. And I rechecked it against the man page a few weeks ago after the last callout. It might not be correct, man pages have been wrong before, and will be again. But since its worked flawlessly for years, please explain what IS wrong with it. Just saying its wrong doesn't cut it in the face of the fact that I did it in self-defense against NM back when NM first came out, what, a decade ago and was not then removeable with anything but a root session of rm. The package managers insisted on gutting the system if you wanted it gone back then. Now, since my home net is host file based, about 8 machines and a printer these days, I make resolv.conf into a real file, and once /etc/network/interfaces is similarly setup to work, both are then made immutable, at which point resolvconfig and N-M can be like a steer, try, but cannot tear down a working circuit, that it can never bring back to life despite continueing efforts. Both N-M and resolvconfig are solutions looking for a problem I don't have anymore. Fortunately, both of these so-called solutions have the good sense to NOT spam the logs when they find they've been emasculated. Your turn Mike, but lets see the facts as to why its wrong, not just an argument for the sake of arguing. The list doesn't need that, it needs tutorials. 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) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2017-10-25 05:10 +0200 |
| Message-ID | <uEkeR-31u-1@gated-at.bofh.it> |
| In reply to | #188257 |
On Tue, Oct 24, 2017 at 10:52:03PM -0400, Gene Heskett wrote: >But since its worked flawlessly for years, please explain what IS wrong >with it. We've been over this before. Your "search host dns" line doesn't do anything at all as written, but will screw things up if copied in a different order by someone who doesn't know that it's simply broken. >Just saying its wrong doesn't cut it in the face of the fact >that I did it in self-defense against NM back when NM first came out, >what, a decade ago and was not then removeable with anything but a root >session of rm. The package managers insisted on gutting the system if >you wanted it gone back then. Really, rants about something that may or may not have happened 10 years ago are just a waste of time. If you're looking for instructions on how to use resolvconf, others have posted it in the recent past. Since you seem to just want to complain about it, I'm not sure what else to offer. Mike Stone
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-10-25 06:20 +0200 |
| Message-ID | <uElkB-3CS-1@gated-at.bofh.it> |
| In reply to | #188258 |
On Tuesday 24 October 2017 23:02:39 Michael Stone wrote: > On Tue, Oct 24, 2017 at 10:52:03PM -0400, Gene Heskett wrote: > >But since its worked flawlessly for years, please explain what IS > > wrong with it. > > We've been over this before. Your "search host dns" line doesn't do > anything at all as written, but will screw things up if copied in a > different order by someone who doesn't know that it's simply broken. > That still doesn't specify what IS wrong. Reading the now 5+ year old man page, the only change I might make is to change the dns string to nameserver. IP changed host to hosts too. My local network now pings at the same elapsed times as before. Shrug. > >Just saying its wrong doesn't cut it in the face of the fact > >that I did it in self-defense against NM back when NM first came out, > >what, a decade ago and was not then removeable with anything but a > > root session of rm. The package managers insisted on gutting the > > system if you wanted it gone back then. > > Really, rants about something that may or may not have happened 10 > years ago are just a waste of time. > Is it? When I see victims of this stuff posting weekly on every machine list I'm on and you folks can't solve their problems, what exactly am I supposed to think? If it waddles and quacks like a duck, it probably is a duck. > If you're looking for instructions on how to use resolvconf, others > have posted it in the recent past. Since you seem to just want to > complain about it, I'm not sure what else to offer. What you are missing is that there is more than one way to skin a cat, and I prefer the simplest, and fastest way. Eg, hard code it, make it immutable, and get on with the real work. I just scanned my network, and only one machine, an r-pi-3b actually has a resolvconf man page, its running jessie. A recent stretch install on a rock64 probably needs the man pages installed. However, the executable has not been found by locate. I'm outta here for some zz's. > Mike Stone 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) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2017-10-25 13:40 +0200 |
| Message-ID | <uEscq-7LE-11@gated-at.bofh.it> |
| In reply to | #188262 |
On Wed, Oct 25, 2017 at 12:16:49AM -0400, Gene Heskett wrote: >On Tuesday 24 October 2017 23:02:39 Michael Stone wrote: > >> On Tue, Oct 24, 2017 at 10:52:03PM -0400, Gene Heskett wrote: >> >But since its worked flawlessly for years, please explain what IS >> > wrong with it. >> >> We've been over this before. Your "search host dns" line doesn't do >> anything at all as written, but will screw things up if copied in a >> different order by someone who doesn't know that it's simply broken. >> >That still doesn't specify what IS wrong. Reading the now 5+ year old man >page, the only change I might make is to change the dns string to >nameserver. IP changed host to hosts too. What man page? Honestly, it seems like you're making things up at this point. Mike Stone
[toc] | [prev] | [next] | [standalone]
| From | Alberto Luaces <aluaces@udc.es> |
|---|---|
| Date | 2017-10-25 14:10 +0200 |
| Message-ID | <uEsFr-8aT-5@gated-at.bofh.it> |
| In reply to | #188269 |
Michael Stone writes: > On Wed, Oct 25, 2017 at 12:16:49AM -0400, Gene Heskett wrote: >>On Tuesday 24 October 2017 23:02:39 Michael Stone wrote: >> >>> On Tue, Oct 24, 2017 at 10:52:03PM -0400, Gene Heskett wrote: >>> >But since its worked flawlessly for years, please explain what IS >>> > wrong with it. >>> >>> We've been over this before. Your "search host dns" line doesn't do >>> anything at all as written, but will screw things up if copied in a >>> different order by someone who doesn't know that it's simply broken. >>> >>That still doesn't specify what IS wrong. Reading the now 5+ year old man >>page, the only change I might make is to change the dns string to >>nameserver. IP changed host to hosts too. > > What man page? Honestly, it seems like you're making things up at this point. Might be "man resolv.conf". -- Alberto
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2017-10-25 15:30 +0200 |
| Message-ID | <uEtUT-ot-23@gated-at.bofh.it> |
| In reply to | #188271 |
On Wed, Oct 25, 2017 at 01:59:42PM +0200, Alberto Luaces wrote:
>Michael Stone writes:
>
>> On Wed, Oct 25, 2017 at 12:16:49AM -0400, Gene Heskett wrote:
>>>On Tuesday 24 October 2017 23:02:39 Michael Stone wrote:
>>>
>>>> On Tue, Oct 24, 2017 at 10:52:03PM -0400, Gene Heskett wrote:
>>>> >But since its worked flawlessly for years, please explain what IS
>>>> > wrong with it.
>>>>
>>>> We've been over this before. Your "search host dns" line doesn't do
>>>> anything at all as written, but will screw things up if copied in a
>>>> different order by someone who doesn't know that it's simply broken.
>>>>
>>>That still doesn't specify what IS wrong. Reading the now 5+ year old man
>>>page, the only change I might make is to change the dns string to
>>>nameserver. IP changed host to hosts too.
>>
>> What man page? Honestly, it seems like you're making things up at this point.
>
>Might be "man resolv.conf".
Can't be, that man page clearly says:
search Search list for host-name lookup.
The search list is normally determined from the local domain name; by default,
it contains only the local domain name. This may be changed by listing the
desired domain search path following the search keyword with spaces or tabs
separating the names. Resolver queries having fewer than ndots dots (default
is 1) in them will be attempted using each component of the search path in
turn until a match is found. For environments with multiple subdomains please
read options ndots:n below to avoid man-in-the-middle attacks and unnecessary
traffic for the root-dns-servers. Note that this process may be slow and will
generate a lot of network traffic if the servers for the listed domains are
not local, and that queries will time out if no server is available for one of
the domains.
It certainly doesn't say anything about putting "host" or "dns" or
"nameserver" in that line.
Mike Stone
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2017-10-25 15:50 +0200 |
| Message-ID | <uEuee-uS-15@gated-at.bofh.it> |
| In reply to | #188291 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Oct 25, 2017 at 09:18:36AM -0400, Michael Stone wrote: [...] > >Might be "man resolv.conf". > > Can't be, that man page clearly says: > > search Search list for host-name lookup. [...] > It certainly doesn't say anything about putting "host" or "dns" or > "nameserver" in that line. Unless your domain name is "host" or "dns", that is. But then you're asking for it, I guess :-) (Don't chuckle. A company I was working at did set its internal "top level domain" to "local". Much hilarity with zeroconf [1] ensued). Cheers - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEUEARECAAYFAlnwlPMACgkQBcgs9XrR2kZH8ACePE8XSpmgcc0zRohuHo/JBrAF QDYAmK9KrKn0rsjYH8vM6HPznysMyek= =3ixt -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2017-10-25 16:30 +0200 |
| Message-ID | <uEuQV-Xl-3@gated-at.bofh.it> |
| In reply to | #188294 |
On 2017-10-25, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote: > > On Wed, Oct 25, 2017 at 09:18:36AM -0400, Michael Stone wrote: > > [...] > >> >Might be "man resolv.conf". >> >> Can't be, that man page clearly says: >> >> search Search list for host-name lookup. > > [...] > >> It certainly doesn't say anything about putting "host" or "dns" or >> "nameserver" in that line. > > Unless your domain name is "host" or "dns", that is. But then you're > asking for it, I guess :-) > > (Don't chuckle. A company I was working at did set its internal "top > level domain" to "local". Much hilarity with zeroconf [1] ensued). We did have the person here who host-named his machine localhost, which may blunt the hilarity somewhat as it does the surprise, the former often depending on a dose of the latter. > Cheers > - -- tomás > > -- "A simpering Bambi narcissist and a thieving, fanatical Albanian dwarf." Christopher Hitchens, commenting shortly after the nearly concurrent deaths of Lady Diana and Mother Theresa.
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2017-10-25 17:10 +0200 |
| Message-ID | <uEvtE-1pZ-5@gated-at.bofh.it> |
| In reply to | #188294 |
On Wed, 25 Oct 2017 15:43:15 +0200 <tomas@tuxteam.de> wrote: > > (Don't chuckle. A company I was working at did set its internal "top > level domain" to "local". Much hilarity with zeroconf [1] ensued). > That was the standard recommendation for users of MS Small Business Server, who were presumed not to be running their own public DNS servers, to avoid name problems with externally-hosted websites etc. It is an article of faith for MS people that no other operating system exists... -- Joe
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2017-10-25 17:30 +0200 |
| Message-ID | <uEvN0-1w7-15@gated-at.bofh.it> |
| In reply to | #188300 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Oct 25, 2017 at 04:01:50PM +0100, Joe wrote: > On Wed, 25 Oct 2017 15:43:15 +0200 > <tomas@tuxteam.de> wrote: > > > > > > (Don't chuckle. A company I was working at did set its internal "top > > level domain" to "local". Much hilarity with zeroconf [1] ensued). > > > > That was the standard recommendation for users of MS Small Business > Server, who were presumed not to be running their own public DNS > servers, to avoid name problems with externally-hosted websites etc. Yes, I think that's where it came from (the folks responsible for the internal DNS servers (!) have Microsoft background). Whatever "small" means -- this company has > 5K clients. > It is an article of faith for MS people that no other operating system > exists... Many things don't exist in that bubble. Cheers - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlnwrMMACgkQBcgs9XrR2kYZEwCeJ7T0Wxts1l9jBF6BTFEa2ff6 p5wAniW8wWnJidT6JlB40a/otDVE+crA =hV5e -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | rhkramer@gmail.com |
|---|---|
| Date | 2017-10-25 19:00 +0200 |
| Message-ID | <uExc5-2fQ-1@gated-at.bofh.it> |
| In reply to | #188294 |
On Wednesday, October 25, 2017 09:43:15 AM tomas@tuxteam.de wrote: > (Don't chuckle. A company I was working at did set its internal "top > level domain" to "local". Much hilarity with zeroconf [1] ensued). And I'll bet the person that did that was following the instructions he found / was given to the best of his ability. (I'll bet there were instructions somewhere that said something like "set it to ... local domain".
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2017-10-25 19:10 +0200 |
| Message-ID | <uExlL-2yp-1@gated-at.bofh.it> |
| In reply to | #188305 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Oct 25, 2017 at 12:55:01PM -0400, rhkramer@gmail.com wrote: > On Wednesday, October 25, 2017 09:43:15 AM tomas@tuxteam.de wrote: > > (Don't chuckle. A company I was working at did set its internal "top > > level domain" to "local". Much hilarity with zeroconf [1] ensued). > > And I'll bet the person that did that was following the instructions he found > / was given to the best of his ability. (I'll bet there were instructions > somewhere that said something like "set it to ... local domain". Yeah, hey. But those were MCSEs and network pros. Or something (you aren't in charge of ~5K client boxes, are you?) Cheers - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlnwxI0ACgkQBcgs9XrR2kYDxACfeB7tDtrqfarSQNkVNf7wtqyK xc4Anisq607TFPDnHqhJ2wheX+cCdHRK =FNWF -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | rhkramer@gmail.com |
|---|---|
| Date | 2017-10-25 19:40 +0200 |
| Message-ID | <uExON-2Iq-7@gated-at.bofh.it> |
| In reply to | #188306 |
On Wednesday, October 25, 2017 01:06:21 PM tomas@tuxteam.de wrote: > Yeah, hey. But those were MCSEs and network pros. Or something (you aren't > in charge of ~5K client boxes, are you?) Nope--just have read too many instructions that didn't clearly delineate what was a variable / parameter vs. fixed text or similar. ;-)
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-10-25 14:20 +0200 |
| Message-ID | <uEsP8-8e8-9@gated-at.bofh.it> |
| In reply to | #188269 |
On Wednesday 25 October 2017 07:36:54 Michael Stone wrote: > On Wed, Oct 25, 2017 at 12:16:49AM -0400, Gene Heskett wrote: > >On Tuesday 24 October 2017 23:02:39 Michael Stone wrote: > >> On Tue, Oct 24, 2017 at 10:52:03PM -0400, Gene Heskett wrote: > >> >But since its worked flawlessly for years, please explain what IS > >> > wrong with it. > >> > >> We've been over this before. Your "search host dns" line doesn't do > >> anything at all as written, but will screw things up if copied in a > >> different order by someone who doesn't know that it's simply > >> broken. > > > >That still doesn't specify what IS wrong. Reading the now 5+ year old > > man page, the only change I might make is to change the dns string > > to nameserver. IP changed host to hosts too. > > What man page? Honestly, it seems like you're making things up at this > point. > And if you haven't read the man page, you are too. And I object to being called a liar. I may be wrong, and if I am, you'll read it here. Man pages as opaque as this one make that wrong possibility lots greater than 0. Wanna fix it? First fix the man page so there is no ambiguity. I might note, and you should too, that all the blathering about here has NOT fixed the OP's problem. Something on his system is over-writing his resolv.conf, and maybe his /etc/network/interfaces in what, certainly something over a week, that something has yet to be found, and finding that s/b top priority. > Mike Stone man resolv.conf, it carrys a 2012-11-11 date on this uptodate wheezy system. I just put stretch on a rock64, and its man page is dated 2017-03-13. Without doing a diff on those two files, I think they are identical. They aren't exactly identical on a blink compare but may as well be. Far more text formatting diffs than content diffs. Its still a poorly written man page. IMO of course. 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) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2017-10-25 05:50 +0200 |
| Message-ID | <uEkRA-3e7-1@gated-at.bofh.it> |
| In reply to | #188257 |
Gene Heskett composed on 2017-10-24 22:52 (UTC-0400): >> On Mon, Oct 23, 2017 at 20:31:05 -0400, Gene Heskett wrote: >>>and made immutable. Particularly is the fact that /etc/resolv.conf >>> isn't a link to something else but contains: >>>nameserver 192.168.XX.1 >>>search host dns >>>domain coyote.den ... > Now, since my home net is host file based, about 8 machines and a printer > these days, I make resolv.conf into a real file, and > once /etc/network/interfaces is similarly setup to work, both are then > made immutable, at which point resolvconfig and N-M can be like a steer, > try, but cannot tear down a working circuit, that it can never bring > back to life despite continueing efforts. Both N-M and resolvconfig are > solutions looking for a problem I don't have anymore. ... > Your turn Mike, but lets see the facts as to why its wrong, not just an > argument for the sake of arguing. The list doesn't need that, it needs > tutorials. Apparently no one else is interested in tutoring, so I'll offer this: 1-My LAN is configured essentially the same as yours, including a 2k hosts file. 2-My lines 1 are always the search lines, each starting with the word "search", followed by domain(s) to be searched, e.g. "search mylan.net coyote.den someother.biz" 3-My lines 2[3,4,...] are always nameserver lines, containing only the string "nameserver" followed by one IPV4 address. 4-I have no lines starting with string "domain", but as a result of this thread, that may soon change. NAICT from the man page, Mike's objection to yours is your search line should contain neither the string "dns" nor the string "host", and probably ought to contain at least the string "coyote.den" following the string "search". -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-10-25 13:40 +0200 |
| Message-ID | <uEscq-7LE-5@gated-at.bofh.it> |
| In reply to | #188259 |
On Tuesday 24 October 2017 23:46:47 Felix Miata wrote: > Gene Heskett composed on 2017-10-24 22:52 (UTC-0400): > >> On Mon, Oct 23, 2017 at 20:31:05 -0400, Gene Heskett wrote: > >>>and made immutable. Particularly is the fact that /etc/resolv.conf > >>> isn't a link to something else but contains: > >>> > >>>nameserver 192.168.XX.1 > >>>search host dns > >>>domain coyote.den > > ... > > > Now, since my home net is host file based, about 8 machines and a > > printer these days, I make resolv.conf into a real file, and > > once /etc/network/interfaces is similarly setup to work, both are > > then made immutable, at which point resolvconfig and N-M can be like > > a steer, try, but cannot tear down a working circuit, that it can > > never bring back to life despite continueing efforts. Both N-M and > > resolvconfig are solutions looking for a problem I don't have > > anymore. > > ... > > > Your turn Mike, but lets see the facts as to why its wrong, not just > > an argument for the sake of arguing. The list doesn't need that, it > > needs tutorials. > > Apparently no one else is interested in tutoring, so I'll offer this: > > 1-My LAN is configured essentially the same as yours, including a 2k > hosts file. > > 2-My lines 1 are always the search lines, each starting with the word > "search", followed by domain(s) to be searched, e.g. "search mylan.net > coyote.den someother.biz" > > 3-My lines 2[3,4,...] are always nameserver lines, containing only the > string "nameserver" followed by one IPV4 address. > > 4-I have no lines starting with string "domain", but as a result of > this thread, that may soon change. > > NAICT from the man page, Mike's objection to yours is your search line > should contain neither the string "dns" nor the string "host", and > probably ought to contain at least the string "coyote.den" following > the string "search". Whereas my theory has always been WRT the search line, that it should first search the /etc/hosts file for a name match, and failing that, query my router, which is running dd-wrt which means its running dnsmasq. Now, if dnsmasq doesn't have it in its cache, then the router will query the dns server that it obtained from the isp via its dhcp session with the isp. Frankly, "man resolv.conf" is one of the poorer man pages we have. Without covering the fundamentals, it wastes 8 kilobytes on options most folks don't know or care about. Quite a ways down the page, I see this: "The domain and search keywords are mutually exclusive. If more than one instance of these keywords is present, the last instance wins." Other stanza's seem to say I should replace 'hosts' with the local domain name, 'coyote.den' as the first argument to the search keyword. And I cannot tell if its doing anything different, I changed it and restarted my networking without disturbing the ssh sessions opened to the other machines, they are still up and accessable w/o logging in a new session, and I can still ping yahoo in 112ms. A partial cat of /etc/network/interfaces: auto eth0 # regular network for coyote.den iface eth0 inet static address 192.168.XX.3 netmask 255.255.255.0 gateway 192.168.XX.1 dns-nameserver 192.168.XX.1 That also has the immutable bit set. The only thing I see of any concern is that since the last reboot, ifconfig says there has been 946 overrun errors, but total traffic has been nearly 200 GB in the last 27 days 9 hours of uptime. For some installations thats likely miniscule. Which is 100% correct? From the ambiguity and obtuseness of that man page, without any hint of a 'correct' example to be found it it, damnedifIknow. All I do know is that it Just Works(TM). And still does after changing it just now. And except for the router, not an active dhcpd on the property. Any machine can access any other local machine via ssh, or even sshfs, and any machine can fire up a browser and go net crawling. Isn't that how its supposed to work? Thanks Felix. 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) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2017-10-25 14:00 +0200 |
| Message-ID | <uEsvM-7Sc-7@gated-at.bofh.it> |
| In reply to | #188267 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Oct 25, 2017 at 07:35:35AM -0400, Gene Heskett wrote: > On Tuesday 24 October 2017 23:46:47 Felix Miata wrote: > > > Gene Heskett composed on 2017-10-24 22:52 (UTC-0400): > > >> On Mon, Oct 23, 2017 at 20:31:05 -0400, Gene Heskett wrote: > > >>>and made immutable. Particularly is the fact that /etc/resolv.conf > > >>> isn't a link to something else but contains: > > >>> > > >>>nameserver 192.168.XX.1 > > >>>search host dns > > >>>domain coyote.den This seems wrong (I know, I'm late to the party). The way I read resolv.conf's man page (and my hazy memory), "search" lists *domains* to be appended to the host name to be resolved if that is incomplete. For example: my resolv.conf has a line search lan (whoever put that in there, but it's irrelevant on my laptop anyway). If I try to resolve just "foo", the resolver will first try "foo.lan" (duh, that's most probably wrong), then just "foo". If I give an FQDN (e.g. duckduckgo.com), the dots in the host name tell the resolver to bypass the search list. "host" and "dns" seem like wrong things to put in "search". The search entry above looks to me like something which should be in /etc/nsswitch.conf, like hosts: files dns meaning: "when looking for a host name, look first in /etc/hosts (files), if that fails turn to the DNS (dns). As always, I might be wrong. Cheers - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlnwelkACgkQBcgs9XrR2kZAugCeP6rDs/BbSlluH5TXiI4O51qR f+0AmwZs5iEZlRs0yzj8DB/YcAjm3kSA =Wg4b -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
Page 2 of 7 — ← Prev page 1 [2] 3 4 5 6 7 Next page →
Back to top | Article view | linux.debian.user
csiph-web