On 14/10/2020 12.31, Carlos E. R. wrote:

On 14/10/2020 11.13, Carlos E. R. wrote:

I do again the edit to dnsmasq, but the name keeps. I check the log to see when did the name change:

...

At zero hours of Tuesday - that was when syslog became aware of the name change.

Another log shows the instant the problem happened: +++................ <7.7> 2020-10-12T20:28:01.430137+02:00 Telcontar fetchnews 32349 - - config: debugmode is 1 <7.7> 2020-10-12T20:28:01.430334+02:00 Telcontar fetchnews 32349 - - config: maxfetch is 5000 <7.7> 2020-10-12T20:28:01.430457+02:00 Telcontar fetchnews 32349 - - config: maxage is 0 <7.7> 2020-10-12T20:28:01.430572+02:00 Telcontar fetchnews 32349 - - config: postings have max. 500000 bytes <7.7> 2020-10-12T20:28:01.430683+02:00 Telcontar fetchnews 32349 - - config: timeout_long is 100 days <7.7> 2020-10-12T20:28:01.430801+02:00 Telcontar fetchnews 32349 - - config: timeout_fetchnews is 90 seconds <7.7> 2020-10-12T20:28:01.430914+02:00 Telcontar fetchnews 32349 - - config: newsadmin is postmaster@telcontar.valinor <7.7> 2020-10-12T20:28:01.431026+02:00 Telcontar fetchnews 32349 - - config: allow_8bit_headers is 1 <7.7> 2020-10-12T20:28:04.430540+02:00 Telcontar fetchnews 32349 - - leafnode 1.11.11: verbosity level is 2, debugmode is 1 <7.7> 2020-10-12T20:28:04.430792+02:00 Telcontar fetchnews 32349 - - try_lock(timeout=5), fqdn="Telcontar.valinor" <====== ... <7.7> 2020-10-12T20:32:02.145306+02:00 Telcontar fetchnews 32562 - - config: allow_8bit_headers is 1 <7.2> 2020-10-12T20:32:02.145361+02:00 Telcontar fetchnews 32562 - - #012Leafnode must have a fully-qualified and globally unique domain name,#012not just "localhost".#012Edit your /etc/hosts file to add a unique, fully qualified domain name.#012"localhost.localdomain" or thereabouts will not work;#012it's qualified, but not unique.#012Please see the README-FQDN file for details. ................++- So between 20:28:04 and 20:32:02 hours of Monday 12. If it were resolv.conf: cer@Telcontar:~> l /etc/resolv.conf -rw-r--r-- 1 root root 1204 Oct 12 19:39 /etc/resolv.conf cer@Telcontar:~> so that was not the culprit. Could be dnsmasq, but that one I don't have the significant timestamp of my edit (I changed it later more than once). Still, I think that was it, but I can't reproduce the problem.

So no idea what caused the problem... :-(

-- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

On 14/10/2020 12.37, Ralph wrote:

On Wed, 14 Oct 2020 11:13:37 +0200 (CEST) "Carlos E. R." wrote:

...

+++.............. cer@Telcontar:~> su - Password: localhost:~ # ..............++-

My computer suddenly believes it is called "localhost". Huh?

If I open a new terminal, I see:

cer@localhost:~>

15.2 and xfce? You can try the gui in Yast Control Center / Network Settings / Hostname / Static Hostname. IIRC, you then need to restart.

15.1, but yes, that is what I did and it worked, as I posted a moment ago. No, reboot was not necessary. But I have no idea what it changed that worked, nor what caused the problem. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

On 14/10/2020 13.16, Ralph wrote:

On Wed, 14 Oct 2020 12:54:13 +0200 "Carlos E. R." <> wrote:

...

On 14/10/2020 12.37, Ralph wrote:

...

On Wed, 14 Oct 2020 11:13:37 +0200 (CEST) "Carlos E. R." <> wrote:

...

...

...

My computer suddenly believes it is called "localhost". Huh?

If I open a new terminal, I see:

cer@localhost:~>

15.2 and xfce? You can try the gui in Yast Control Center / Network Settings / Hostname / Static Hostname. IIRC, you then need to restart.

15.1, but yes, that is what I did and it worked, as I posted a moment ago. No, reboot was not necessary. But I have no idea what it changed that worked, nor what caused the problem.

The reason I asked if it was 15.2 is that I got surprised by that @localhost machine name in a fresh install of 15.2, where we instead used to get a random string of characters as the initial hostname in 15.1 and previous versions. In my case (fresh 15.2) I did IIRC need to restart.

Ah, yes, you are right, I saw it on a new install of 15.2. But this machine is old. It had the correct name and suddenly it changed. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

On 15/10/2020 07.56, David Haller wrote:

Hello,

On Wed, 14 Oct 2020, Carlos E. R. wrote:

...

The "/etc/hosts" file is normal: +++.............. 127.0.0.1 localhost ::1 localhost ipv6-localhost ipv6-loopback 192.168.1.14 Telcontar.valinor Telcontar ..............++-

RTF comments: ==== /etc/hosts ==== # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname ====

Thus:

==== 127.0.0.1 Telcontar.valinor Telcontar localhost

No, this entry breaks postfix. Well... I haven't tried that exact entry, but the one that YaST created in the past: 127.0.0.2 Telcontar.valinor Telcontar The error caused was "fatal: parameter inet_interfaces: no local interface found for 127.0.0.2" Although I have a note from 20180825 that maybe the error was solved. Previous to that date, I had an email exchange with postfix developer where he said it was not postfix fault. Adding a fourth field is not in my documentation :-?

::1 Telcontar.valinor Telcontar localhost ipv6-localhost ipv6-loopback 192.168.1.14 Telcontar.valinor Telcontar ====

-- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

Hello, On Thu, 15 Oct 2020, Carlos E.R. wrote:

On 15/10/2020 09.28, Carlos E. R. wrote:

...

On 15/10/2020 07.56, David Haller wrote:

...

On Wed, 14 Oct 2020, Carlos E. R. wrote:

...

...

...

127.0.0.1 Telcontar.valinor Telcontar localhost

No, this entry breaks postfix. Well... I haven't tried that exact entry, but the one that YaST created in the past:

127.0.0.2 Telcontar.valinor Telcontar

Then do try that exact entry (no .2). But, admittedly, I do set 'myhostname' explicitly in main.cf. Should work without though. When it's correct you should get: $ hostname Telcontar $ hostname -f Telcontar.valinor $ hostname -a Telcontar localhost $ host localhost localhost has address 127.0.0.1 Dunno about the IPv6 stuff. HTH, -dnh -- BUGS It is not yet possible to change operating system by writ­ ing to /proc/sys/kernel/ostype. -- Linux sysctl(2) manpage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hello, On Thu, 15 Oct 2020, Carlos E. R. wrote:

On 15/10/2020 10.03, David Haller wrote:

...

On Thu, 15 Oct 2020, Carlos E.R. wrote:

...

On 15/10/2020 09.28, Carlos E. R. wrote:

...

On 15/10/2020 07.56, David Haller wrote: ...

...

127.0.0.1 Telcontar.valinor Telcontar localhost

No, this entry breaks postfix. Well... I haven't tried that exact entry, but the one that YaST created in the past:

127.0.0.2 Telcontar.valinor Telcontar

Then do try that exact entry (no .2). But, admittedly, I do set 'myhostname' explicitly in main.cf. Should work without though. [..] After:

cer@Telcontar:~> hostname Telcontar cer@Telcontar:~> hostname -f Telcontar.valinor cer@Telcontar:~> hostname -a Telcontar localhost Telcontar cer@Telcontar:~> host localhost localhost has address 127.0.0.1 localhost has IPv6 address ::1 cer@Telcontar:~>

Telcontar:~ # systemctl restart postfix Telcontar:~ # systemctl status postfix ? postfix.service - Postfix Mail Transport Agent Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2020-10-15 17:59:19 CEST; 23s ago Process: 31997 ExecStopPost=/etc/postfix/system/cond_slp deregister (code=exited, status=0/SUCCESS) ...

Telcontar:~ # mail cer Subject: test after localhost change hi . EOT Telcontar:~ #

There you go ;) As soon as you do it right, it works ... *hrhr* *scnr*

...

Dunno about the IPv6 stuff.

It is there on mine

Yeah, should be the same as for 127.0.0.1 AFAIR. BTW: you can add more IPs/Hostnames after the first as above. E.g.: 127.0.0.1 news.example.com news 127.0.0.1 irc.example.com irc [..] 127.0.1.8 track.adform.net adform.net but that's old, I now use dnsmasq where one entry suffices for a whole domain and supports delivering NXDOMAIN instead of 127/8, e.g.: address=/adform.net/ in a seperate file in /etc/dnsmasq.d/, which is included from /etc/dnsmasq.conf: $ host track.adform.net Host track.adform.net not found: 3(NXDOMAIN) $ host track.adform.net 1.1.1.1 Name: 1.1.1.1 Address: 1.1.1.1#53 Aliases: track.adform.net is an alias for track-eu.adformnet.akadns.net. track-eu.adformnet.akadns.net has address 37.157.4.41 [..] HTH, -dnh -- Why oh why did I remember that? Bad brain. Naughty brain. -- JoeB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hello, On Thu, 15 Oct 2020, Carlos E.R. wrote:

On 15/10/2020 18.47, David Haller wrote:

...

There you go ;) As soon as you do it right, it works ... *hrhr* *scnr*

:-)

Well, at somepoint postfix must have changed ideas about this, or it would not work.

Not that I know of. [..]

...

but that's old, I now use dnsmasq where one entry suffices for a whole domain and supports delivering NXDOMAIN instead of 127/8, e.g.:

address=/adform.net/

Yes, I use dnsmasq in this machine. Previously I used bind9. I was not aware of that syntax, though.

It's somewhat easy to overlook in the manpage: ==== -A, --address=/<domain>[/<domain>...]/[<ipaddr>] # ^ note that the second '/' # is not optional here, but # the IP is As for --server, one or more domains with no address returns a no-such- domain answer, so --address=/example.com/ is equivalent to --server=/example.com/ and returns NXDOMAIN for example.com and all its subdomains. ^^^ [..] ^^^^^^^^^^^^^^^^^^ Note that NULL addresses normally work in the same way as localhost, so beware that clients looking up these names are likely to end up talking to themselves. ==== The last means: don't use '0.0.0.0' or '::' as addresses (in dnsmasq NOR in /etc/hosts).

...

In a seperate file in /etc/dnsmasq.d/, which is included from /etc/dnsmasq.conf: $ host track.adform.net Host track.adform.net not found: 3(NXDOMAIN) $ host track.adform.net 1.1.1.1 Name: 1.1.1.1 Address: 1.1.1.1#53 Aliases:

track.adform.net is an alias for track-eu.adformnet.akadns.net. track-eu.adformnet.akadns.net has address 37.157.4.41 [..]

Interesting :-)

Does somebody publish lists of such "bad" domains, separated by purposes, like tracking, in ready syntax?

None that I'me aware of. I use not so many sites and UMatrix/UBlock/NoScript (for XSS etc.), so I just add those annoying me a couple of times... Should port my /etc/hosts based blocks to dnsmasq though ;) It's rather easy to add hosts though, you could even use a script/shell-alias/shell-function: ==== /etc/dnsmasq.conf ==== conf-dir=/etc/dnsmasq.d,*.conf ==== That means to only include *.conf files under /etc/dnsmasq.d/, not other files there. ==== /etc/dnsmasq.d/blocklist.conf ==== address=/adform.net/ [..] address=/fb.com/ address=/fb.me/ [..] ==== just use as a script: ==== block_domains.sh ==== #!/bin/bash for domain; do printf 'address=/%s/\n' "$domain" >> /etc/dnsmasq.d/blocklist.conf done systemctl restart dnsmasq ==== or something to that effect ;) I just wish dnsmasq would support brace-expansion, so one could use e.g. 'address=/facebook.{com,de,fr,co.uk,net}/'. But with above script, it'd be: # block_domains.sh facebook.{com,de,fr,co.uk,net} so that'd be ok ;) HTH, -dnh -- To resist the influence of others, knowledge of one's self is most important. -- Teal'C, Stargate SG-1, 9x14 - Stronghold -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hello, On Thu, 15 Oct 2020, Carlos E. R. wrote:

On 15/10/2020 19.50, David Haller wrote:

...

On Thu, 15 Oct 2020, Carlos E.R. wrote:

...

On 15/10/2020 18.47, David Haller wrote:

...

There you go ;) As soon as you do it right, it works ... *hrhr* *scnr*

:-)

Well, at somepoint postfix must have changed ideas about this, or it would not work.

Not that I know of.

You can read the link to the discussion at the postfix mail list, and the corresponding bugzilla here (Bug 824141).

Read that (and linked) a bit, Wietse's (Postfix's) view seems quite sane. And Yast-genreated /etc/hosts files have been broken as such since at least, IIRC, S.u.S.E 5.3 (or always). No idea why that's never been fixed (or even filed as a bug (by anyone, including esp. me *sigh*)).

...

[..]

...

...

but that's old, I now use dnsmasq where one entry suffices for a whole domain and supports delivering NXDOMAIN instead of 127/8, e.g.:

address=/adform.net/

Yes, I use dnsmasq in this machine. Previously I used bind9. I was not aware of that syntax, though.

It's somewhat easy to overlook in the manpage:

==== -A, --address=/<domain>[/<domain>...]/[<ipaddr>] # ^ note that the second '/' # is not optional here, but # the IP is

Ah.

That's tricky. From reading the manpage, it looks as if you can use: address=/example.com/example.org/[<ipaddr>] Hm. Let's just try: $ host example.com example.com has address 93.184.216.34 example.com has IPv6 address 2606:2800:220:1:248:1893:25c8:1946 example.com mail is handled by 0 . $ host example.org [same] $ host example.net [same] [adding address=/example.com/example.org/example.net/127.128.129.130 to dnsmasq config & restarting dnsmasq] $ host example.net example.net has address 127.128.129.130 $ host example.org example.org has address 127.128.129.130 $ host example.com example.com has address 127.128.129.130 [editing to address=/example.com/example.org/example.net/ (note again the trailing '/'!) & restart] $ host example.com Host example.com not found: 3(NXDOMAIN) $ host example.org Host example.org not found: 3(NXDOMAIN) $ host example.net Host example.net not found: 3(NXDOMAIN) Way cool! :) Now that weird syntax makes sense, but the lonely '/' before the optional <ipaddr> is quite easy to overlook inbetween those brackets '[..]/[..]'... But, it's correct :) It might be easier to see, but differently irritating on the syntax if written as: -A, --address=[/<domain>...]/<domain>/[<ipaddr>] but the ending '/' might not quite as easily be overlooked. Writing correct and understandable documentation for syntax like this is _HARD_. Examples can help (but not always!). Using: address=/example.com/example.org/example.net/<ipaddr> to point the example domains to a local webswerver might actually make sense, esp. in a larger organization :)

...

As for domain answer, so --address=/example.com/ is equivalent to all its subdomains. ^^^ [..] ^^^^^^^^^^^^^^^^^^ Note that NULL addresses normally work in the same way as localhost, so beware that clients looking up these names are likely to end up talking to themselves. ====

The last means: don't use '0.0.0.0' or '::' as addresses (in dnsmasq NOR in /etc/hosts).

Ok, nice to have a translation :-)

You're welcome :) That's another thing you _often_ see: using the NULL address in /etc/hosts or whatnot, which usually is just wrong. But again, my main point was that dnsmasq takes _all subdomains_ of a domain... Continuing above example: $ host www.example.net 1.1.1.1 [..] www.example.net has address 93.184.216.34 $ host foo.bar.example.net 1.1.1.1 Using domain server: Name: 1.1.1.1 Address: 1.1.1.1#53 Aliases: Host foo.bar.example.net not found: 3(NXDOMAIN) $ host www.example.net Host www.example.net not found: 3(NXDOMAIN) $ host foo.bar.example.net Host foo.bar.example.net not found: 3(NXDOMAIN)

...

...

...

In a seperate file in /etc/dnsmasq.d/, which is included from /etc/dnsmasq.conf: $ host track.adform.net Host track.adform.net not found: 3(NXDOMAIN) $ host track.adform.net 1.1.1.1 Name: 1.1.1.1 Address: 1.1.1.1#53 Aliases:

track.adform.net is an alias for track-eu.adformnet.akadns.net. track-eu.adformnet.akadns.net has address 37.157.4.41 [..]

Interesting :-)

Does somebody publish lists of such "bad" domains, separated by purposes, like tracking, in ready syntax?

None that I'me aware of.

I know of published hosts files. Windows people use them.

Not only those ;) But see my answer to Patrick.

An interesting caveat is that now M$ own antivirus (defender?) flags as a virus if you modify the file or if they see their own addresses in there :-} (they list M$ addresses to stop some features from working that can not be uninstalled. Like doing updates, or privacy breaking).

M$. Need I say more? :-P [..]

...

just use as a script: [..] Right.

...

I just wish dnsmasq would support brace-expansion, so one could use e.g. 'address=/facebook.{com,de,fr,co.uk,net}/'. But with above script, it'd be:

# block_domains.sh facebook.{com,de,fr,co.uk,net}

so that'd be ok ;)

Yep.

*bg* Glad you see it the same way :) It's a matter of priorities and how much control you want on that level... I use prefabbed blocklists (e.g. EasyList) in UBlock/UMatrix/NoScript in my browsers anyway, but I like to block e.g. farcebarf et.al. on the DNS-level system-wide[1]. Try trackin' me with those ubiquitous like buttons if your domain just does not exist *hrhr*... BTW: you do know that 'valinor' is not a valid TLD? Have you thought about "legalizing" that to e.g. valinor.localdomain? (*$@#! those that took over .local!) I've been using my registered .de domain locally for ~20 years now, ~10 with sendmail, ~10 with postfix. If you know what you're doing, if you've got a grasp on DNS as such, it's not that difficult. The hardest part is seperating out mails to other peeps under the same domain sending them to the smarthost or whereever. I took the easy way and use my second domain for most stuff that goes out :) See 'man 5 transport' and 'man 5 virtual' ;) And yes, all in- and outgoing mail goes through my local postfix, no shortcut from fetchmail to procmail via the former's 'mda' option (which would be totally feasible)... HTH, -dnh [1] and if "needed", I can just comment those 2 lines in the blocklist, restart dnsmasq, run 'youtube-dl ...', uncomment, restart and FB's just seen the dl of the vid "out of the blue" ;) It is very rare (IIRC so far only some severe weather vids I was quite keen on having a look at), so that's absolutely fine. -- No question is too silly to ask, but, of course, some are too silly to answer. -- The Perl book -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E.R. [10-15-20 13:03]:

On 15/10/2020 18.47, David Haller wrote:

[...] ## 347.65916/π lines of quoting removed

...

Aliases:

track.adform.net is an alias for track-eu.adformnet.akadns.net. track-eu.adformnet.akadns.net has address 37.157.4.41 [..]

Interesting :-)

Does somebody publish lists of such "bad" domains, separated by purposes, like tracking, in ready syntax?

https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=1&mimetype=plaintext -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E. R. [10-15-20 14:14]:

On 15/10/2020 20.03, Patrick Shanahan wrote:

...

* Carlos E.R. <> [10-15-20 13:03]:

...

On 15/10/2020 18.47, David Haller wrote:

[...] ## 347.65916/π lines of quoting removed

...

...

Aliases:

track.adform.net is an alias for track-eu.adformnet.akadns.net. track-eu.adformnet.akadns.net has address 37.157.4.41 [..]

Interesting :-)

Does somebody publish lists of such "bad" domains, separated by purposes, like tracking, in ready syntax?

https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=1&mimetype=plaintext

In /etc/hosts syntax.

Thanks. But that one misses the "separated by purposes", or commenting what does each address there.

you didn't ask, but ... and you will not spend enough time to peruse what you request. there are limits. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E. R. [10-15-20 16:21]:

On 15/10/2020 20.33, Patrick Shanahan wrote:

...

* Carlos E. R. <> [10-15-20 14:14]:

...

On 15/10/2020 20.03, Patrick Shanahan wrote:

...

* Carlos E.R. <> [10-15-20 13:03]:

...

On 15/10/2020 18.47, David Haller wrote:

[...] ## 347.65916/π lines of quoting removed

...

...

Aliases:

track.adform.net is an alias for track-eu.adformnet.akadns.net. track-eu.adformnet.akadns.net has address 37.157.4.41 [..]

Interesting :-)

Does somebody publish lists of such "bad" domains, separated by purposes, like tracking, in ready syntax?

https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=1&mimetype=plaintext

In /etc/hosts syntax.

Thanks. But that one misses the "separated by purposes", or commenting what does each address there.

you didn't ask, but ... and you will not spend enough time to peruse what you request. there are limits.

I can not block that many hosts without knowing what they are for. I did ask for purpose separation.

to to the site, pgl.yoyo.org and see what he offers. I only provided the line to the text list for addition to /etc/hosts. use your time instead of mine. I have many other non-essential tasks to waste time on. presently consuming Dos Equis XX while listening to Diana Washington on Amazon Prime music, ie: very busy. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E.R. [10-15-20 17:04]:

On 15/10/2020 22.58, Patrick Shanahan wrote:

...

* Carlos E. R. <> [10-15-20 16:21]:

...

On 15/10/2020 20.33, Patrick Shanahan wrote:

...

* Carlos E. R. <> [10-15-20 14:14]:

...

On 15/10/2020 20.03, Patrick Shanahan wrote:

...

* Carlos E.R. <> [10-15-20 13:03]: > On 15/10/2020 18.47, David Haller wrote:

[...] ## 347.65916/π lines of quoting removed

> > Aliases: > > > > track.adform.net is an alias for track-eu.adformnet.akadns.net. > > track-eu.adformnet.akadns.net has address 37.157.4.41 > > [..] > > Interesting :-) > > Does somebody publish lists of such "bad" domains, separated by purposes, > like tracking, in ready syntax?

https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=1&mimetype=plaintext

In /etc/hosts syntax.

Thanks. But that one misses the "separated by purposes", or commenting what does each address there.

you didn't ask, but ... and you will not spend enough time to peruse what you request. there are limits.

I can not block that many hosts without knowing what they are for. I did ask for purpose separation.

to to the site, pgl.yoyo.org and see what he offers. I only provided the line to the text list for addition to /etc/hosts. use your time instead of mine. I have many other non-essential tasks to waste time on.

You could simply have pointed from the start to the information page, but I'm just commenting on why I do not like lists like that one, not asking you to do the job of creating one.

...

presently consuming Dos Equis XX while listening to Diana Washington on Amazon Prime music, ie: very busy.

:-)

all you want is at https://pgl.yoyo.org/ -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

David C. Rankin wrote:

The use of

127.0.0.2 has basically been done away with. It was used up through 11.4? but I think when IPv6 was integrated that (I don't even know what you actually call it) implementation was retired. I don't have any hard details there.

IPv6 was integrated/implemented quite a while before that - starting 2006, I was using an ipv6 tunnel - I don't know what that corresponds to in terms of SUSE/openSUSE releases, maybe 10.0 ? I think(!) the /etc/hosts used to be "127.0.0.2 linux.site linux" (I see it mentioned in several places on the net) I also see it mentioned way earlier, on the suse-linux-e lists in 2001, but unfortunately the archive is gone. I don't quite get why 127.0.0.2 should be a topic now, almost twenty years later :-)

The use of 127.0.0.2 (with RFC references) is described here: https://superuser.com/questions/393700/what-is-127-0-0-2-ip-address-for

TBH, I don't see much description other than people talking about what it _might_ be used for. I use a few 127.x.x.x addresses myself, 127.0.0.1, 127.0.0.36, 127.0.0.99 and 127.0.0.111, for instance. On a large mailserver setup, instead of having miscellaneous services use localhost:xxxxx, we have them use 'some.local.name:pp', which makes the mail log easier to read. ("some.local.name" resolves to some 127.0.0.x address). -- Per Jessen, Zürich (8.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 17/10/2020 10.16, Per Jessen wrote:

David C. Rankin wrote:

...

The use of

127.0.0.2 has basically been done away with. It was used up through 11.4? but I think when IPv6 was integrated that (I don't even know what you actually call it) implementation was retired. I don't have any hard details there.

IPv6 was integrated/implemented quite a while before that - starting 2006, I was using an ipv6 tunnel - I don't know what that corresponds to in terms of SUSE/openSUSE releases, maybe 10.0 ?

I think(!) the /etc/hosts used to be "127.0.0.2 linux.site linux" (I see it mentioned in several places on the net)

I also see it mentioned way earlier, on the suse-linux-e lists in 2001, but unfortunately the archive is gone.

Huh? I see the archive there. Mine starts on 2003.

I don't quite get why 127.0.0.2 should be a topic now, almost twenty years later :-)

Oh, because I showed the commented out line in my /etc/hosts file, and mentioned why I have it commented out, and David Haller convinced me to put a variant back.

...

The use of 127.0.0.2 (with RFC references) is described here: https://superuser.com/questions/393700/what-is-127-0-0-2-ip-address-for

TBH, I don't see much description other than people talking about what it _might_ be used for. I use a few 127.x.x.x addresses myself, 127.0.0.1, 127.0.0.36, 127.0.0.99 and 127.0.0.111, for instance. On a large mailserver setup, instead of having miscellaneous services use localhost:xxxxx, we have them use 'some.local.name:pp', which makes the mail log easier to read. ("some.local.name" resolves to some 127.0.0.x address).

-- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

On 18/10/2020 12.40, Per Jessen wrote:

Carlos E. R. wrote:

...

On 17/10/2020 10.16, Per Jessen wrote:

...

David C. Rankin wrote:

...

The use of

127.0.0.2 has basically been done away with. It was used up through 11.4? but I think when IPv6 was integrated that (I don't even know what you actually call it) implementation was retired. I don't have any hard details there.

IPv6 was integrated/implemented quite a while before that - starting 2006, I was using an ipv6 tunnel - I don't know what that corresponds to in terms of SUSE/openSUSE releases, maybe 10.0 ?

I think(!) the /etc/hosts used to be "127.0.0.2 linux.site linux" (I see it mentioned in several places on the net)

I also see it mentioned way earlier, on the suse-linux-e lists in 2001, but unfortunately the archive is gone.

Huh? I see the archive there. Mine starts on 2003.

I found this link, somewhere:

https://lists.suse.com/archive/suse-linux-e/2001-Oct/2197.html

(gives error 404) Is it not the same as https://lists.opensuse.org/opensuse/2001-10/all.html ? 127.0.0.2 is mentioned. it's about SuSEconfig adding the line when it was not wanted, and how to disable creation of the hosts file. I seem to recall that there was an specific setting that disabled the 127.0.0.2 one. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

On 10/17/20 3:16 AM, Per Jessen wrote:

TBH, I don't see much description other than people talking about what it _might_ be used for. I use a few 127.x.x.x addresses myself, 127.0.0.1, 127.0.0.36, 127.0.0.99 and 127.0.0.111, for instance. On a large mailserver setup, instead of having miscellaneous services use localhost:xxxxx, we have them use 'some.local.name:pp', which makes the mail log easier to read. ("some.local.name" resolves to some 127.0.0.x address).

The crux I got from the link was that 127.0.0.2 was implementation defined (by the various distros) to behave as they needed it to. So there wasn't any one thing that that address did on its own. (it could have been any 127.0.0 address, but I guess the next after .1 was what most used when they used it) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org