Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #208030 > unrolled thread

forcedeth?

Started byGene Heskett <gheskett@shentel.net>
First post2019-05-02 13:30 +0200
Last post2019-05-25 19:10 +0200
Articles 20 on this page of 72 — 18 participants

Back to article view | Back to linux.debian.user


Contents

  forcedeth? Gene Heskett <gheskett@shentel.net> - 2019-05-02 13:30 +0200
    Re: forcedeth? songbird <songbird@anthive.com> - 2019-05-02 14:20 +0200
    Re: forcedeth? Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-05-02 20:20 +0200
      Re: forcedeth? Gene Heskett <gheskett@shentel.net> - 2019-05-02 22:30 +0200
        Re: forcedeth? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-05-25 12:40 +0200
          Re: forcedeth? Gene Heskett <gheskett@shentel.net> - 2019-05-25 13:00 +0200
            Re: forcedeth? Andy Smith <andy@strugglers.net> - 2019-05-25 13:40 +0200
              Re: forcedeth? Gene Heskett <gheskett@shentel.net> - 2019-05-25 17:30 +0200
                That time IPv6 farted in Gene's church (Was Re: forcedeth?) Andy Smith <andy@strugglers.net> - 2019-05-27 04:20 +0200
                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-27 06:50 +0200
                    Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Andy Smith <andy@strugglers.net> - 2019-05-27 08:10 +0200
                      Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-27 18:20 +0200
                      Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jimmy Johnson <field.engineer@gmail.com> - 2019-05-27 19:20 +0200
                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Andy Smith <andy@strugglers.net> - 2019-05-28 17:50 +0200
                          Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jimmy Johnson <field.engineer@gmail.com> - 2019-05-28 19:20 +0200
                            Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Andy Smith <andy@strugglers.net> - 2019-05-28 20:40 +0200
                    Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) <tomas@tuxteam.de> - 2019-05-27 09:00 +0200
                      Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Curt <curty@free.fr> - 2019-05-27 09:50 +0200
                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) <tomas@tuxteam.de> - 2019-05-27 11:00 +0200
                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jonas Smedegaard <jonas@jones.dk> - 2019-05-27 11:00 +0200
                          Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jimmy Johnson <field.engineer@gmail.com> - 2019-05-27 19:30 +0200
                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jimmy Johnson <field.engineer@gmail.com> - 2019-05-27 19:30 +0200
                          Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Brian <ad44@cityscape.co.uk> - 2019-05-27 22:00 +0200
                            Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jimmy Johnson <field.engineer@gmail.com> - 2019-05-28 08:40 +0200
                              Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Erik Christiansen <dvalin@internode.on.net> - 2019-05-28 13:20 +0200
                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-27 19:50 +0200
                          Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Brian <ad44@cityscape.co.uk> - 2019-05-27 21:30 +0200
                            Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-27 23:30 +0200
                              Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Brian <ad44@cityscape.co.uk> - 2019-05-28 00:50 +0200
                                Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-28 04:50 +0200
                              Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) mick crane <mick.crane@gmail.com> - 2019-05-28 05:10 +0200
                          Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jonas Smedegaard <jonas@jones.dk> - 2019-05-27 21:50 +0200
                            Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-28 00:20 +0200
                              Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2019-05-28 05:40 +0200
                                Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Curt <curty@free.fr> - 2019-05-28 09:50 +0200
                                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Reco <recoverym4n@enotuniq.net> - 2019-05-28 10:00 +0200
                                    Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) <tomas@tuxteam.de> - 2019-05-28 10:50 +0200
                                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Jonas Smedegaard <jonas@jones.dk> - 2019-05-28 10:00 +0200
                                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2019-05-28 18:00 +0200
                                    Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Curt <curty@free.fr> - 2019-05-28 18:50 +0200
                                Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-28 14:10 +0200
                                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Erik Christiansen <dvalin@internode.on.net> - 2019-05-28 14:40 +0200
                                    Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-28 15:10 +0200
                                      Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Erik Christiansen <dvalin@internode.on.net> - 2019-05-28 15:50 +0200
                                        Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-28 17:00 +0200
                                  Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-05-28 14:50 +0200
                      Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?) Gene Heskett <gheskett@shentel.net> - 2019-05-27 19:20 +0200
                    IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) rhkramer@gmail.com - 2019-05-27 15:00 +0200
                      Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) <tomas@tuxteam.de> - 2019-05-27 15:20 +0200
                      Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-27 20:20 +0200
                        Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Reco <recoverym4n@enotuniq.net> - 2019-05-27 21:30 +0200
                          Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-27 23:10 +0200
                            Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) <tomas@tuxteam.de> - 2019-05-28 06:40 +0200
                            Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Reco <recoverym4n@enotuniq.net> - 2019-05-28 07:50 +0200
                              Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 14:40 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's  church (Was Re: forcedeth?)) Dan Purgert <dan@djph.net> - 2019-05-28 15:00 +0200
                                  Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 15:10 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Reco <recoverym4n@enotuniq.net> - 2019-05-28 15:10 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Greg Wooledge <wooledg@eeg.ccf.org> - 2019-05-28 15:40 +0200
                                  Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 16:30 +0200
                            Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Erik Christiansen <dvalin@internode.on.net> - 2019-05-28 13:10 +0200
                              Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) <tomas@tuxteam.de> - 2019-05-28 15:00 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) <tomas@tuxteam.de> - 2019-05-28 15:30 +0200
                                  Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 16:00 +0200
                                    Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) <tomas@tuxteam.de> - 2019-05-28 16:50 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 15:30 +0200
                                Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church  (Was Re: forcedeth?)) Erik Christiansen <dvalin@internode.on.net> - 2019-05-28 15:40 +0200
                                  Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 16:20 +0200
                              Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)) Gene Heskett <gheskett@shentel.net> - 2019-05-28 15:00 +0200
                      Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's  church (Was Re: forcedeth?)) Dan Purgert <dan@djph.net> - 2019-05-28 03:00 +0200
              Re: forcedeth? rhkramer@gmail.com - 2019-05-25 18:40 +0200
                Re: forcedeth? Gene Heskett <gheskett@shentel.net> - 2019-05-25 19:10 +0200

Page 3 of 4 — ← Prev page 1 2 [3] 4  Next page →


#209296 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromGene Heskett <gheskett@shentel.net>
Date2019-05-28 14:10 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2J5v-2qZ-7@gated-at.bofh.it>
In reply to#209274
On Monday 27 May 2019 11:18:49 pm Joe Pfeiffer wrote:

> Gene Heskett <gheskett@shentel.net> writes:
> > On Monday 27 May 2019 03:42:52 pm Jonas Smedegaard wrote:
> >> Quoting Gene Heskett (2019-05-27 19:42:46)
> >>
> >> > On Monday 27 May 2019 03:46:00 am Curt wrote:
> >> > > On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
> >> > > > If Network Manager is giving you grief, please go bark up
> >> > > > /that/ tree (I can't say much about N-M, because I banned it
> >> > > > from my boxes about ten years ago: I was at a customer's, in
> >> > > > his LAN via an Ethernet, when N-M suddenly saw a WLAN out
> >> > > > there, out the window and said "oh, let's go online over
> >> > > > there" and obliterated my network setting in favor of some
> >> > > > seedy captive portal. That was when I decided that N-M and
> >> > > > me, we aren't made for each other).
> >> > >
> >> > > This is a grave bug. I suppose we can assume from your
> >> > > description that the seedier the wifi portal, the more likely
> >> > > it is to spontaneously occur, despite any and all user
> >> > > configuration or intervention.
> >> >
> >> > This would appear to be more common, but as far as filing a bug
> >> > report, I logged in to do something in 2015, creating a new
> >> > account at the time, so now it refuses to let me in because the
> >> > username content rules have been changed and my username is now
> >> > invalid.  And because it knows my email address, it won't let me
> >> > create a new account. So its the classic chicken v egg. I am
> >> > locked out, so I rant on this list.
> >>
> >> Account? You need no account to report bugs in Debian:
> >> https://www.debian.org/Bugs/Reporting
> >
> > So that indicates I should have apt install reportbug, so I did.
> > Configured it on 1st run. then became me and ran it again.  It never
> > heard of NetworkManager or Network-Manager.  WTH?
>
> Debian package names are all lower case, and for better or worse the
> package management software is case-sensitive.

A detail I had forgotten due to all the capitalization used to refer to 
it publicly.

> snowball:532$ reportbug
> Please enter the name of the package in which you have found a
> problem, or type 'other' to report a more general problem. If you
> don't know what package the bug is in, please contact
> debian-user@lists.debian.org for assistance.
>
> > network-manager
>
> *** Welcome to reportbug.  Use ? for help at prompts. ***
> Note: bug reports are publicly archived (including the email address
> of the submitter). Detected character set: UTF-8
> Please change your locale if this is incorrect.
>
> Using 'Joe Pfeiffer <joseph@pfeifferfamily.net>' as your from address.
> Getting status for network-manager...
> Checking for newer versions at madison...
>
> Your version (1.14.6-2) of network-manager appears to be out of date.
> The following newer release(s) are available in the Debian archive:
>   experimental: 1.18.0-1
> Please try to verify if the bug you are about to report is already
> addressed by these releases.  Do you still want to file a report
> [y|N|q|?]?

And this exposes something in debian's policy I object to, as strenuously 
as I can. A newer version may well fix the bug, but its never given to 
the users until they upgrade to the next release, and that brings a 
never shrinking list of new bugs.

The withholding of showstopper bug fixes from a released version, by 
putting them in an experimental category where only a very small inner 
circle has access to them is not an impressive idea.

IMO a showstopper bugfix should be offered immediately to all releases 
currently supported. The wheezy version of firefox may have been 
marginally better than a horse with 3 broken legs, (another leg was 
broken by each update as it was during wheezy) but we were denied the 
improved versions as a matter of "policy". IMO, that sucks dead toads 
thru soda straws. But I don't set policy. It is what it is, but thats 
how this diehard fan of debian see's it.

TBT, I'd be happy paying say $100 year for a seat at the table where 
serious bugs were fixed while the release was still alive. Not however 
on a machine count basis as RH is doing. That would satisfy me as a good 
TANSTAAFL compromise, and would, I'd think buy a longer ladder up the 
side of the hog for the folks actually doing the work. I am sure they 
would appreciate that!
 
> (at which point I entered a ^C since I didn't actually want to report
> a bug)


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]


#209297 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromErik Christiansen <dvalin@internode.on.net>
Date2019-05-28 14:40 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2Jyx-2Bi-1@gated-at.bofh.it>
In reply to#209296
On 28.05.19 08:02, Gene Heskett wrote:
> On Monday 27 May 2019 11:18:49 pm Joe Pfeiffer wrote:
> 
> > Gene Heskett <gheskett@shentel.net> writes:
> > Your version (1.14.6-2) of network-manager appears to be out of date.
> > The following newer release(s) are available in the Debian archive:
> >   experimental: 1.18.0-1
> > Please try to verify if the bug you are about to report is already
> > addressed by these releases.  Do you still want to file a report
> > [y|N|q|?]?
> 
> And this exposes something in debian's policy I object to, as strenuously 
> as I can. A newer version may well fix the bug, but its never given to 
> the users until they upgrade to the next release, and that brings a 
> never shrinking list of new bugs.

Gene, you're just too shy and retiring. In such a case, if experimental
is not your cup of tea, why not conclude "It needs to be fixed in stable.",
and hit 'y' to still file a report. After all, until it's backported to
stable, it's still an outstanding bug.

That said, one could upgrade just that one package, and try it out. If
it is fixed, you're on a winner then and there. "Fixed" beats
"reported", as you can get on with the next issue. 

Erik

[toc] | [prev] | [next] | [standalone]


#209303 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromGene Heskett <gheskett@shentel.net>
Date2019-05-28 15:10 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2K1A-31r-7@gated-at.bofh.it>
In reply to#209297
On Tuesday 28 May 2019 08:34:37 am Erik Christiansen wrote:

> On 28.05.19 08:02, Gene Heskett wrote:
> > On Monday 27 May 2019 11:18:49 pm Joe Pfeiffer wrote:
> > > Gene Heskett <gheskett@shentel.net> writes:
> > > Your version (1.14.6-2) of network-manager appears to be out of
> > > date. The following newer release(s) are available in the Debian
> > > archive: experimental: 1.18.0-1
> > > Please try to verify if the bug you are about to report is already
> > > addressed by these releases.  Do you still want to file a report
> > > [y|N|q|?]?
> >
> > And this exposes something in debian's policy I object to, as
> > strenuously as I can. A newer version may well fix the bug, but its
> > never given to the users until they upgrade to the next release, and
> > that brings a never shrinking list of new bugs.
>
> Gene, you're just too shy and retiring. In such a case, if
> experimental is not your cup of tea, why not conclude "It needs to be
> fixed in stable.", and hit 'y' to still file a report. After all,
> until it's backported to stable, it's still an outstanding bug.

Which we are still suffering from.

> That said, one could upgrade just that one package, and try it out. If
> it is fixed, you're on a winner then and there. "Fixed" beats
> "reported", as you can get on with the next issue.
>
> Erik

A great idea Erik. What then is the deb line in sources.list to enable 
that?  Thats what I was alluding to when I said inner circle.


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]


#209310 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromErik Christiansen <dvalin@internode.on.net>
Date2019-05-28 15:50 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2KEi-3fl-3@gated-at.bofh.it>
In reply to#209303
On 28.05.19 08:59, Gene Heskett wrote:
> On Tuesday 28 May 2019 08:34:37 am Erik Christiansen wrote:
> > That said, one could upgrade just that one package, and try it out. If
> > it is fixed, you're on a winner then and there. "Fixed" beats
> > "reported", as you can get on with the next issue.
> >
> > Erik
> 
> A great idea Erik. What then is the deb line in sources.list to enable 
> that?  Thats what I was alluding to when I said inner circle.

At https://wiki.debian.org/DebianExperimental#To_configure_APT
we see a sources.list line and how to pin a specific package install to
that, either on the command line or in /etc/apt/preferences.

Here's hoping that your wife's COPD is bearable, she doesn't throw your
cooking at you, and you can maintain the stamina each day to be her
palliative carer despite your 84 years. 

Erik

[toc] | [prev] | [next] | [standalone]


#209318 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromGene Heskett <gheskett@shentel.net>
Date2019-05-28 17:00 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2LK1-3TZ-11@gated-at.bofh.it>
In reply to#209310
On Tuesday 28 May 2019 09:48:35 am Erik Christiansen wrote:

> On 28.05.19 08:59, Gene Heskett wrote:
> > On Tuesday 28 May 2019 08:34:37 am Erik Christiansen wrote:
> > > That said, one could upgrade just that one package, and try it
> > > out. If it is fixed, you're on a winner then and there. "Fixed"
> > > beats "reported", as you can get on with the next issue.
> > >
> > > Erik
> >
> > A great idea Erik. What then is the deb line in sources.list to
> > enable that?  Thats what I was alluding to when I said inner circle.
>
> At https://wiki.debian.org/DebianExperimental#To_configure_APT
> we see a sources.list line and how to pin a specific package install
> to that, either on the command line or in /etc/apt/preferences.
>
> Here's hoping that your wife's COPD is bearable, she doesn't throw
> your cooking at you, and you can maintain the stamina each day to be
> her palliative carer despite your 84 years.
>
> Erik

it does impinge on my playtime from time to time. But she was a good find 
when I found her in 1987. And we still haven't considered an Alaskan 
divorce after 30 years, which is longer than I've ever had before.  
She's my 3rd. First one had a stroke and died at about the 10th 
anniversary, she was 34 then, after very enthusiasticly giving me 3 
kids. They have all passed now, the 2 girls from cancer and the boy 
tried to play mumbledepeg  with a kia while he had a quart of scotch in 
him. Fatal of course. The second woof turned out to have her own agenda 
and left after 16 years.  She came with 3 and only one survives today, 
MD took the other 2 at about their 30th, and I made 3 boys with her, so 
I have 4 boys left today.  All doing well. But this dear lady is down to 
around 70-75 lbs, not much time left.  You never get used to losing the 
family you figured would be around ones own bed at the end.

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]


#209299 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

From"Stephen P. Molnar" <s.molnar@sbcglobal.net>
Date2019-05-28 14:50 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2JId-2EZ-1@gated-at.bofh.it>
In reply to#209296
On 05/28/2019 08:02 AM, Gene Heskett wrote:
> On Monday 27 May 2019 11:18:49 pm Joe Pfeiffer wrote:
>
>> Gene Heskett <gheskett@shentel.net> writes:
>>> On Monday 27 May 2019 03:42:52 pm Jonas Smedegaard wrote:
>>>> Quoting Gene Heskett (2019-05-27 19:42:46)
>>>>
>>>>> On Monday 27 May 2019 03:46:00 am Curt wrote:
>>>>>> On 2019-05-27, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote:
>>>>>>> If Network Manager is giving you grief, please go bark up
>>>>>>> /that/ tree (I can't say much about N-M, because I banned it
>>>>>>> from my boxes about ten years ago: I was at a customer's, in
>>>>>>> his LAN via an Ethernet, when N-M suddenly saw a WLAN out
>>>>>>> there, out the window and said "oh, let's go online over
>>>>>>> there" and obliterated my network setting in favor of some
>>>>>>> seedy captive portal. That was when I decided that N-M and
>>>>>>> me, we aren't made for each other).
>>>>>> This is a grave bug. I suppose we can assume from your
>>>>>> description that the seedier the wifi portal, the more likely
>>>>>> it is to spontaneously occur, despite any and all user
>>>>>> configuration or intervention.
>>>>> This would appear to be more common, but as far as filing a bug
>>>>> report, I logged in to do something in 2015, creating a new
>>>>> account at the time, so now it refuses to let me in because the
>>>>> username content rules have been changed and my username is now
>>>>> invalid.  And because it knows my email address, it won't let me
>>>>> create a new account. So its the classic chicken v egg. I am
>>>>> locked out, so I rant on this list.
>>>> Account? You need no account to report bugs in Debian:
>>>> https://www.debian.org/Bugs/Reporting
>>> So that indicates I should have apt install reportbug, so I did.
>>> Configured it on 1st run. then became me and ran it again.  It never
>>> heard of NetworkManager or Network-Manager.  WTH?
>> Debian package names are all lower case, and for better or worse the
>> package management software is case-sensitive.
> A detail I had forgotten due to all the capitalization used to refer to
> it publicly.
>
>> snowball:532$ reportbug
>> Please enter the name of the package in which you have found a
>> problem, or type 'other' to report a more general problem. If you
>> don't know what package the bug is in, please contact
>> debian-user@lists.debian.org for assistance.
>>
>>> network-manager
>> *** Welcome to reportbug.  Use ? for help at prompts. ***
>> Note: bug reports are publicly archived (including the email address
>> of the submitter). Detected character set: UTF-8
>> Please change your locale if this is incorrect.
>>
>> Using 'Joe Pfeiffer <joseph@pfeifferfamily.net>' as your from address.
>> Getting status for network-manager...
>> Checking for newer versions at madison...
>>
>> Your version (1.14.6-2) of network-manager appears to be out of date.
>> The following newer release(s) are available in the Debian archive:
>>    experimental: 1.18.0-1
>> Please try to verify if the bug you are about to report is already
>> addressed by these releases.  Do you still want to file a report
>> [y|N|q|?]?
> And this exposes something in debian's policy I object to, as strenuously
> as I can. A newer version may well fix the bug, but its never given to
> the users until they upgrade to the next release, and that brings a
> never shrinking list of new bugs.
>
> The withholding of showstopper bug fixes from a released version, by
> putting them in an experimental category where only a very small inner
> circle has access to them is not an impressive idea.
>
> IMO a showstopper bugfix should be offered immediately to all releases
> currently supported. The wheezy version of firefox may have been
> marginally better than a horse with 3 broken legs, (another leg was
> broken by each update as it was during wheezy) but we were denied the
> improved versions as a matter of "policy". IMO, that sucks dead toads
> thru soda straws. But I don't set policy. It is what it is, but thats
> how this diehard fan of debian see's it.
>
> TBT, I'd be happy paying say $100 year for a seat at the table where
> serious bugs were fixed while the release was still alive. Not however
> on a machine count basis as RH is doing. That would satisfy me as a good
> TANSTAAFL compromise, and would, I'd think buy a longer ladder up the
> side of the hog for the folks actually doing the work. I am sure they
> would appreciate that!
>   
>> (at which point I entered a ^C since I didn't actually want to report
>> a bug)
>
> Cheers, Gene Heskett
  How about moving this thread to a Developer's mailing list?

-- 
Stephen P. Molnar, Ph.D.          Life is a fuzzy set
www.molecular-modeling.net        Stochastic and multivariate
(614)312-7528(c)
Skype:  smolnar1

[toc] | [prev] | [next] | [standalone]


#209241 — Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

FromGene Heskett <gheskett@shentel.net>
Date2019-05-27 19:20 +0200
SubjectRe: That time IPv6 farted in Gene's church (Was Re: forcedeth?)
Message-ID<y2rrY-88e-11@gated-at.bofh.it>
In reply to#209207
On Monday 27 May 2019 02:56:07 am tomas@tuxteam.de wrote:

> On Mon, May 27, 2019 at 12:41:36AM -0400, Gene Heskett wrote:
>
> [...]
>
> > I don't think so. ipv6 I'm sure is nice where its available.  Where
> > it is not available, its a pain in the ass because even if you set
> > it up as a static ipv4, N-M will tear it down in 5 minutes or less.
> > And N-M is a dependency because most have a dhcpd running, probably
> > in the router by default.
> >
> > You are determined to exterminate any and all users of a hosts file,
> > staticly defined network. Its ideal for small home networks.
>
> [...]
>
> I've been following this monster thread with one eye (sorry, not
> enough bandwidth at the moment) and I think, Gene, you're barking up
> the wrong tree.
>
> IPv6 can coexist nicely with IPv4 (this is by design). My work laptop
> (which is my only work box) has both stacks up and running. Most
> places I'm at don't even know IPv6 exist. My ISP at home likewise. But
> my home router does, so I can magically "ping6" the more intelligent
> hosts at home, without having had to configure anything.
>
> If Network Manager is giving you grief, please go bark up /that/ tree
> (I can't say much about N-M, because I banned it from my boxes about
> ten years ago: I was at a customer's, in his LAN via an Ethernet, when
> N-M suddenly saw a WLAN out there, out the window and said "oh, let's
> go online over there" and obliterated my network setting in favor of
> some seedy captive portal. That was when I decided that N-M and me,
> we aren't made for each other).
>
> Cheers
> -- t
I agree totally Tomas. but its tied up in dependencies so bad it nukes 
the whole system if you try to remove it. Here I am tempted to fire up a 
root session of mc, and wear out the F8 key because I also have 
something going on that kills hid-common, so I have no input system. 
That has limited my uptime to under a week, sometimes under a day.

Whether brute-force killing of N-M will fix the input lockups remains to 
be tested by this method.  It was locked sometime in the night when I 
woke up to feed the missus about 7ish. And both the lack of a 
spamassasin start, bad expired certificate, ditto for clamscand I have 
yet to see the complete lines before the lockup, the log is being 
spammed at about 300 lines a minute, so I will next time set the konsole 
history to unlimited, and tail -fn100000 /var/log/syslog.  Maybe that 
will get me back to before the reboot.  Humm, less got me back far 
enough, but what I see is crazy:

May 27 02:53:00 coyote spamd[2309]: prefork: child states: II
May 27 02:54:14 coyote usbhid-ups[775]: libusb_get_report: could not 
claim interface 0: Device or resource busy
May 27 02:56:01 coyote CRON[6375]: (gene) CMD (/home/gene/bin/remindX)
May 27 09:04:37 coyote systemd[1]: Started udev Coldplug all Devices.
May 27 09:04:37 coyote systemd[1]: Starting udev Wait for Complete Device 
Initialization...
May 27 09:04:37 coyote systemd-modules-load[307]: Inserted module 'lp'
May 27 09:04:37 coyote systemd-modules-load[307]: Inserted module 'ppdev'
May 27 09:04:37 coyote systemd[1]: Started Create Static Device Nodes 
in /dev.
May 27 09:04:37 coyote systemd[1]: Starting udev Kernel Device Manager...
May 27 09:04:37 coyote systemd[1]: Started Set the console keyboard 
layout.
May 27 09:04:37 coyote systemd[1]: Reached target Local File Systems 
(Pre).
May 27 09:04:37 coyote systemd-modules-load[307]: Inserted 
module 'parport_pc'
May 27 09:04:37 coyote systemd[1]: Started Load Kernel Modules.
May 27 09:04:37 coyote kernel: [    0.000000] Linux version 
4.9.0-9-rt-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP PREEMPT RT Debian 
4.9.168-1+deb9u2 (2019-05-13)
May 27 09:04:37 coyote systemd[1]: Starting Apply Kernel Variables...
May 27 09:04:37 coyote kernel: [    0.000000] Command line: 
BOOT_IMAGE=/vmlinuz-4.9.0-9-rt-amd64 root=UUID=0e698024-1cf3

And there's at least another 500-1000 lines with the clock frozen at 
09:04:37.  Crazy...

The beginning of the crash is the 2nd line of this, usb-common has died.  
Thats all I know for sure right now. I had to use the front panel reset 
button to reboot it, something I've had to do quite a few times since a 
new stretch install 3 weeks ago now.

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]


#209220 — IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

Fromrhkramer@gmail.com
Date2019-05-27 15:00 +0200
SubjectIPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2nol-5sQ-1@gated-at.bofh.it>
In reply to#209203
On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:

<nothing quoted from Andy Smith, just left there as a reference to "you", 
below>

> You are determined to exterminate any and all users of a hosts file,
> staticly defined network. Its ideal for small home networks.

Hmm, that's interesting -- is there an analog to or replacement for the hosts 
file on ipv6?

Aside / background: AFAIK, I am not using IPV6 on either my Wheezy or Jessie 
system, but, I haven't really transitioned to the Jessie system as my everyday 
machine -- I don't really "surf the net" there, but instead tend to search for 
specific technically oriented pages related to the (development) work I'm 
trying to do on that Jessie system -- I don't notice much advertising -- it's 
probably because of the pages I view.

[toc] | [prev] | [next] | [standalone]


#209223 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

From<tomas@tuxteam.de>
Date2019-05-27 15:20 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2nHH-5OT-1@gated-at.bofh.it>
In reply to#209220

[Multipart message — attachments visible in raw view] — view raw

On Mon, May 27, 2019 at 08:58:14AM -0400, rhkramer@gmail.com wrote:
> On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> 
> <nothing quoted from Andy Smith, just left there as a reference to "you", 
> below>
> 
> > You are determined to exterminate any and all users of a hosts file,
> > staticly defined network. Its ideal for small home networks.
> 
> Hmm, that's interesting -- is there an analog to or replacement for the hosts 
> file on ipv6?

/etc/hosts. It works fine for both ipv4 and ipv6. Nothing changes
(except the address format, that is). Both can be mixed in /etc/hosts.

Cheers
-- t

[toc] | [prev] | [next] | [standalone]


#209251 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

FromGene Heskett <gheskett@shentel.net>
Date2019-05-27 20:20 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2so1-gc-1@gated-at.bofh.it>
In reply to#209220
On Monday 27 May 2019 08:58:14 am rhkramer@gmail.com wrote:

> On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
>
> <nothing quoted from Andy Smith, just left there as a reference to
> "you", below>
>
> > You are determined to exterminate any and all users of a hosts file,
> > staticly defined network. Its ideal for small home networks.
>
> Hmm, that's interesting -- is there an analog to or replacement for
> the hosts file on ipv6?
>
According to the default comments in that file, yes. But easy to read and 
understand docs on how to actually do it are somewhat hidden on the 
machine or on the net.

> Aside / background: AFAIK, I am not using IPV6 on either my Wheezy or
> Jessie system, but, I haven't really transitioned to the Jessie system
> as my everyday machine -- I don't really "surf the net" there, but
> instead tend to search for specific technically oriented pages related
> to the (development) work I'm trying to do on that Jessie system -- I
> don't notice much advertising -- it's probably because of the pages I
> view.

yup, been known to back out of such sites that "have an ax to sharpen" in 
5 secs or less myself.  Usually its an invitation to subscribe for 
around $80 a seat/year.

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]


#209255 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

FromReco <recoverym4n@enotuniq.net>
Date2019-05-27 21:30 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2ttM-Uq-1@gated-at.bofh.it>
In reply to#209251
On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> On Monday 27 May 2019 08:58:14 am rhkramer@gmail.com wrote:
> 
> > On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> >
> > <nothing quoted from Andy Smith, just left there as a reference to
> > "you", below>
> >
> > > You are determined to exterminate any and all users of a hosts file,
> > > staticly defined network. Its ideal for small home networks.
> >
> > Hmm, that's interesting -- is there an analog to or replacement for
> > the hosts file on ipv6?
> >
> According to the default comments in that file, yes. But easy to read and 
> understand docs on how to actually do it are somewhat hidden on the 
> machine or on the net.

hosts(5). You'll probably need a text editor too.

Reco

[toc] | [prev] | [next] | [standalone]


#209261 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

FromGene Heskett <gheskett@shentel.net>
Date2019-05-27 23:10 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2v2y-1Zc-9@gated-at.bofh.it>
In reply to#209255
On Monday 27 May 2019 03:19:44 pm Reco wrote:

> On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> > On Monday 27 May 2019 08:58:14 am rhkramer@gmail.com wrote:
> > > On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > > > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> > >
> > > <nothing quoted from Andy Smith, just left there as a reference to
> > > "you", below>
> > >
> > > > You are determined to exterminate any and all users of a hosts
> > > > file, staticly defined network. Its ideal for small home
> > > > networks.
> > >
> > > Hmm, that's interesting -- is there an analog to or replacement
> > > for the hosts file on ipv6?
> >
> > According to the default comments in that file, yes. But easy to
> > read and understand docs on how to actually do it are somewhat
> > hidden on the machine or on the net.
>
> hosts(5). You'll probably need a text editor too.
>
> Reco

Thats fine, shows the loop local stuff, but how does one determine the 
ipv6 address for picnc.coyote.den for instance. I think it somehow 
related to picnc's mac address, but thats just a WAG.
 

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]


#209276 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

From<tomas@tuxteam.de>
Date2019-05-28 06:40 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2C41-6lk-1@gated-at.bofh.it>
In reply to#209261

[Multipart message — attachments visible in raw view] — view raw

On Mon, May 27, 2019 at 05:06:24PM -0400, Gene Heskett wrote:

[...]

> Thats fine, shows the loop local stuff, but how does one determine the 
> ipv6 address for picnc.coyote.den for instance. I think it somehow 
> related to picnc's mac address, but thats just a WAG.

There's not THE ip address. A host can have (and actually typically
has, under IPv6) several addresses.

That said, what you're talking about is probably the link local address [1],
which under IPv6 is derived from the MAC address, to have some guarantee
of uniqueness.

Since under IPv6 a host can announce its address and the routers can
propagate this, the schema Just Works (TM) without central instances
to dole out addresses à la DHCP.

Cheers

[1] https://en.wikipedia.org/wiki/Link-local_address

-- tomás

[toc] | [prev] | [next] | [standalone]


#209278 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

FromReco <recoverym4n@enotuniq.net>
Date2019-05-28 07:50 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2D9M-71p-11@gated-at.bofh.it>
In reply to#209261
	Hi.

On Mon, May 27, 2019 at 05:06:24PM -0400, Gene Heskett wrote:
> On Monday 27 May 2019 03:19:44 pm Reco wrote:
> 
> > On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> > > On Monday 27 May 2019 08:58:14 am rhkramer@gmail.com wrote:
> > > > On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > > > > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> > > >
> > > > <nothing quoted from Andy Smith, just left there as a reference to
> > > > "you", below>
> > > >
> > > > > You are determined to exterminate any and all users of a hosts
> > > > > file, staticly defined network. Its ideal for small home
> > > > > networks.
> > > >
> > > > Hmm, that's interesting -- is there an analog to or replacement
> > > > for the hosts file on ipv6?
> > >
> > > According to the default comments in that file, yes. But easy to
> > > read and understand docs on how to actually do it are somewhat
> > > hidden on the machine or on the net.
> >
> > hosts(5). You'll probably need a text editor too.
> 
> Thats fine, shows the loop local stuff, but how does one determine the 
> ipv6 address for picnc.coyote.den for instance.

In another news, it also does not show how to 'determine' IPv4 address
of the host. Yet you manage to do it somehow.

Reco

[toc] | [prev] | [next] | [standalone]


#209298 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

FromGene Heskett <gheskett@shentel.net>
Date2019-05-28 14:40 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2Jyy-2Bi-3@gated-at.bofh.it>
In reply to#209278
On Tuesday 28 May 2019 01:49:29 am Reco wrote:

> 	Hi.
>
> On Mon, May 27, 2019 at 05:06:24PM -0400, Gene Heskett wrote:
> > On Monday 27 May 2019 03:19:44 pm Reco wrote:
> > > On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> > > > On Monday 27 May 2019 08:58:14 am rhkramer@gmail.com wrote:
> > > > > On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > > > > > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> > > > >
> > > > > <nothing quoted from Andy Smith, just left there as a
> > > > > reference to "you", below>
> > > > >
> > > > > > You are determined to exterminate any and all users of a
> > > > > > hosts file, staticly defined network. Its ideal for small
> > > > > > home networks.
> > > > >
> > > > > Hmm, that's interesting -- is there an analog to or
> > > > > replacement for the hosts file on ipv6?
> > > >
> > > > According to the default comments in that file, yes. But easy to
> > > > read and understand docs on how to actually do it are somewhat
> > > > hidden on the machine or on the net.
> > >
> > > hosts(5). You'll probably need a text editor too.
> >
> > Thats fine, shows the loop local stuff, but how does one determine
> > the ipv6 address for picnc.coyote.den for instance.
>
> In another news, it also does not show how to 'determine' IPv4 address
> of the host. Yet you manage to do it somehow.
>
> Reco

Thats a piece of cake Reco. On a new install, set both the hostname and 
the domainname, then add them, with the ipv4 net address into the hosts 
file. Then make resolv.conf back into a real file, with 2 lines, one to 
set the nameservers address, and one to set the search to look in hosts 
first, if that fails send the dns request to the gateway, my router, 
where if dnsmasq doesn't have it cached, the dns request gets sent on to 
my ISP's nameservers. And it all just works, typically in 30 
milliseconds. The only dhcp in the system is in the router, getting its 
outside address from my ISP.s server. The exception is in the router and 
only works when the radio is on because my boys all have smartphones and 
when they visit, I enable the radio but get their phones mac address and 
only talk to it. But if I leave the radio on, I've a neighbor whose 
phone will use it in a heartbeat regardless, and used 80GB of my net 
bandwidth according to my phone bill 2 years ago. I don't see that as 
its not bridged into this system. And although there are radios in 
almost everything these days, I keep those on my side of the router 
disabled. Just plain basic security.

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]


#209300 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

FromDan Purgert <dan@djph.net>
Date2019-05-28 15:00 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2JRU-2ID-1@gated-at.bofh.it>
In reply to#209298
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Gene Heskett wrote:
> only talk to it. But if I leave the radio on, I've a neighbor whose 
> phone will use it in a heartbeat regardless
> [...]

Sounds like someone forgot to set security on their wifi... 


-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlztLgYACgkQjhHd8xJ5
ooGNeQf/SBiWHnYGPPAbohsXqlpSL4EobWMyv4fm/KceUwN190cuRiBpn10Rt6+D
HTb8eYURl8PTrKRS9JDd+B5UZFvJiZvVdKSTaai3OSywggW056FE890QQUkB1q9L
bIricBJWjxrC7Te+mMZyFgrNKA03KHUsndNN2XZTFEi+1Q8o+dlcGpqjkXDBMedR
CwCmfNjg23IZCK72ZmJiDAkqFGM8KIka1QzxXfLtSouGWWbFEkW75RHWayDShNnj
g9tcT6m+DYUrZBlThk/IwQKaODbHNeJqYey19X87jl4b5m11SavJtLyS+FTuYS3t
7c+3Uqm+c/sGlxzUGLR7hV+mmzotWg==
=Mli/
-----END PGP SIGNATURE-----

-- 
|_|O|_| 
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

[toc] | [prev] | [next] | [standalone]


#209304 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

FromGene Heskett <gheskett@shentel.net>
Date2019-05-28 15:10 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2K1A-31r-11@gated-at.bofh.it>
In reply to#209300
On Tuesday 28 May 2019 08:48:06 am Dan Purgert wrote:

> Gene Heskett wrote:
> > only talk to it. But if I leave the radio on, I've a neighbor whose
> > phone will use it in a heartbeat regardless
> > [...]
>
> Sounds like someone forgot to set security on their wifi...

I thought that was what I was doing when I restricted the dhcp server in 
dd-wrt so it only responded to the mac address of my boy's phones. but 
that phone, when I kill the lease, is back online in well under 5 
seconds. So since I've nothing that needs the radios, cat5 is all over 
the place, I just turn the radios off.

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]


#209305 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

FromReco <recoverym4n@enotuniq.net>
Date2019-05-28 15:10 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2K1A-31r-9@gated-at.bofh.it>
In reply to#209298
	Hi.

On Tue, May 28, 2019 at 08:32:38AM -0400, Gene Heskett wrote:
> On Tuesday 28 May 2019 01:49:29 am Reco wrote:
> 
> > 	Hi.
> >
> > On Mon, May 27, 2019 at 05:06:24PM -0400, Gene Heskett wrote:
> > > On Monday 27 May 2019 03:19:44 pm Reco wrote:
> > > > On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> > > > > On Monday 27 May 2019 08:58:14 am rhkramer@gmail.com wrote:
> > > > > > On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > > > > > > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> > > > > >
> > > > > > <nothing quoted from Andy Smith, just left there as a
> > > > > > reference to "you", below>
> > > > > >
> > > > > > > You are determined to exterminate any and all users of a
> > > > > > > hosts file, staticly defined network. Its ideal for small
> > > > > > > home networks.
> > > > > >
> > > > > > Hmm, that's interesting -- is there an analog to or
> > > > > > replacement for the hosts file on ipv6?
> > > > >
> > > > > According to the default comments in that file, yes. But easy to
> > > > > read and understand docs on how to actually do it are somewhat
> > > > > hidden on the machine or on the net.
> > > >
> > > > hosts(5). You'll probably need a text editor too.
> > >
> > > Thats fine, shows the loop local stuff, but how does one determine
> > > the ipv6 address for picnc.coyote.den for instance.
> >
> > In another news, it also does not show how to 'determine' IPv4 address
> > of the host. Yet you manage to do it somehow.
> 
> Thats a piece of cake Reco. On a new install, set both the hostname and 
> the domainname, then add them, with the ipv4 net address into the hosts 
> file.

I see nothing that can stop you from doing the same for IPv6.
Whatever resolver configuration (and assorted kludges) you describe
later are hardly relevant here.


> The only dhcp in the system is in the router, getting its 
> outside address from my ISP.s server.

So all your LAN IPv4s are statically assigned. Again, nobody forbids you
to do the same static assignment for IPv6.


> But if I leave the radio on, I've a neighbor whose 
> phone will use it in a heartbeat regardless, and used 80GB of my net 
> bandwidth according to my phone bill 2 years ago.

An admirable generosity on your part, running WiFi AP without any
encryption.

Reco

[toc] | [prev] | [next] | [standalone]


#209309 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2019-05-28 15:40 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2KuB-3bJ-9@gated-at.bofh.it>
In reply to#209298
On Tue, May 28, 2019 at 08:32:38AM -0400, Gene Heskett wrote:
> Thats a piece of cake Reco. On a new install, set both the hostname and 
> the domainname, then add them, with the ipv4 net address into the hosts 
> file. Then make resolv.conf back into a real file, with 2 lines, one to 
> set the nameservers address, [...]

All good so far.

> and one to set the search to look in hosts 
> first, if that fails send the dns request to the gateway, [...]

We've been over this multiple times before, but apparently it bears
repeating.

There is nothing in resolv.conf that tells NSS whether to look in hosts
first or in DNS first.  That functionality is in the /etc/nsswitch.conf
file.

The syntax you have described in past threads belonged in
the /etc/host.conf file back in the 1990s.  See for example
<https://www.tldp.org/LDP/nag/node82.html>:

=========================================================
A sample file for vlager is shown below:
           # /etc/host.conf
           # We have named running, but no NIS (yet)
           order   bind hosts
           # Allow multiple addrs
           multi   on
           # Guard against spoof attempts
           nospoof on
           # Trim local domain (not really necessary).
           trim    vbrew.com.
=========================================================

Somehow, you got things mixed up, and you included part of this syntax
in your /etc/resolv.conf file, and convinced yourself that it was
actually doing something.

On modern Debian releases (yes, even wheezy) this functionality
is in /etc/nsswitch.conf and the defaults work for almost
everyone, so you probably never had to touch it.  See
<http://manpages.debian.org/5/nsswitch.conf> for details.

=========================================================
wooledg:~$ grep hosts /etc/nsswitch.conf 
hosts:          files mdns4_minimal [NOTFOUND=return] dns
=========================================================

The "hosts" line in this file is what tells the system to look in
"files" (/etc/hosts) first, and in "dns" last.

/etc/resolv.conf simply configures how the "dns" lookup works.

[toc] | [prev] | [next] | [standalone]


#209313 — Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

FromGene Heskett <gheskett@shentel.net>
Date2019-05-28 16:30 +0200
SubjectRe: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))
Message-ID<y2Lh0-3J7-5@gated-at.bofh.it>
In reply to#209309
On Tuesday 28 May 2019 09:35:17 am Greg Wooledge wrote:

> On Tue, May 28, 2019 at 08:32:38AM -0400, Gene Heskett wrote:
> > Thats a piece of cake Reco. On a new install, set both the hostname
> > and the domainname, then add them, with the ipv4 net address into
> > the hosts file. Then make resolv.conf back into a real file, with 2
> > lines, one to set the nameservers address, [...]
>
> All good so far.
>
> > and one to set the search to look in hosts
> > first, if that fails send the dns request to the gateway, [...]
>
> We've been over this multiple times before, but apparently it bears
> repeating.
>
> There is nothing in resolv.conf that tells NSS whether to look in
> hosts first or in DNS first.  That functionality is in the
> /etc/nsswitch.conf file.
>
> The syntax you have described in past threads belonged in
> the /etc/host.conf file back in the 1990s.  See for example
> <https://www.tldp.org/LDP/nag/node82.html>:

All I know for sure is that networking doesn't get off the motherboard 
without it. Wheezy or stretch doesn't make any diff. Stretch is a new 
install on a new drive.

> =========================================================
> A sample file for vlager is shown below:
>            # /etc/host.conf
>            # We have named running, but no NIS (yet)
>            order   bind hosts
>            # Allow multiple addrs
>            multi   on
>            # Guard against spoof attempts
>            nospoof on
>            # Trim local domain (not really necessary).
>            trim    vbrew.com.
> =========================================================
>
> Somehow, you got things mixed up, and you included part of this syntax
> in your /etc/resolv.conf file, and convinced yourself that it was
> actually doing something.
>
> On modern Debian releases (yes, even wheezy) this functionality
> is in /etc/nsswitch.conf and the defaults work for almost
> everyone, so you probably never had to touch it.  See
> <http://manpages.debian.org/5/nsswitch.conf> for details.
>
> =========================================================
> wooledg:~$ grep hosts /etc/nsswitch.conf
> hosts:          files mdns4_minimal [NOTFOUND=return] dns
> =========================================================
>
> The "hosts" line in this file is what tells the system to look in
> "files" (/etc/hosts) first, and in "dns" last.
>
> /etc/resolv.conf simply configures how the "dns" lookup works.


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]


Page 3 of 4 — ← Prev page 1 2 [3] 4  Next page →

Back to top | Article view | linux.debian.user


csiph-web