Re: xsane can't see Brother ADS-2700W scanner

[Celejar]

On Tue, 30 Mar 2021 19:24:36 -0700
Charlie Gibbs  wrote:

> I just got a Brother ADS-2700W sheet-fed scanner and am trying
> to access it from xsane.  I've done a lot of flatbed scanning,
> first with an HP 3970, and lately with an Epson WF-2650 all-in-one,
> but I have a lot of old manuals I want to scan and upload to
> Bitsavers, and a sheet feeder will speed the process along.
> 
> The Brother got a lot of good reviews so I decided to give it a try.
> It offers many options, such as e-mail, [S]FTP, etc. over Ethernet,
> wi-fi, and USB.  But so far, I haven't been able to get xsane to
> recognize it.  My wife tried to get at it from her Macbook (which
> accesses the Epson with no trouble), but had no luck either.
> It's not a connectivity issue - the scanner happily connects
> to my wi-fi and gets an IP address, and I can access it from
> a web browser and get at all of its configuration screens.
> But neither xsane nor my wife's Macbook can see it.
> 
> The one way I did manage to get the scanner to work was to a
> USB flash drive.  It quickly sucked in a handful of sheets,
> scanned both sides, and wrote them to a file on the stick.
> If all else fails, I can work with it that way.  But I'd
> really like to let xsane manage the process.
> 
> I'm beginning to wonder, though, whether fashions are changing.
> Scanners nowadays seem to want to push data to a server, rather
> than being commanded to scan by a computer.  Is this really
> happening?  If so, whither (or should that be "wither") xsane?
> 
> If anyone has gotten one of these newfangled machines to work
> as a slave, rather than a master, please share your secrets.

I recently had some trouble getting xsane to find my networked Brother 
HL-2280DW. I eventually got it to work by adding "brother4" to 
/etc/sane.d/dll.conf, following the directions from the ArchWiki:

https://wiki.archlinux.org/index.php/SANE/Scanner-specific_problems#Network_Scanning

Celejar

Re: Temporary failure in name resolution

[David Christensen]

On 3/31/21 3:28 PM, Dan Norton wrote:

David Christensen wrote on Wed, 31 Mar 2021 13:49:56 -0700:

I would do 'apt-get update' and 'apt-get upgrade' ('autoremove',
'clean', etc.). Once apt-get(8) is done, I would revert the changes
to /etc/resolv.conf and see if name resolution breaks or remains
working. (I would test by renaming /etc/resolve.conf and rebooting.)

Here is what I did:
# apt update
# apt upgrade
# apt autoremove
# apt-get clean
# cp /etc/resolv.conf /etc/resolv.confX
# chattr -i /etc/resolv.conf
## to make resolv.conf *not* immutable
# cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.1.254

Shutdown then power-on boot

## rebooted with /etc/resolv.conf *not* immutable
root@deb4:~# ping google.com
ping: google.com: Temporary failure in name resolution
root@deb4:~# cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 192.168.1.254
## showing that /etc/resolv.conf has been clobbered

After restoring resolv.conf so that it looks like this:
# cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.1.254
# chattr +i /etc/resolv.conf
## making it immutable

Rebooted and posted this.



Thank you for following through with that information.


It looks like Greg Wooledge is correct -- Debian 10.9 has problems with 
the DNS forwarding service on certain residential gateways.  A bug 
report would seem to be appropriate, but I do not know which package to 
file it against.



David

Re: Subject: Mr. Dan Ritter, why is it that you appear to be posting your POV on my posts? Are you a covert agent of the anti-FSF cabal, trying to subvert something "positive for FSF, but detrimenta

[Joe Pfeiffer]

Dan Ritter  writes:

> Laura Smith wrote: 
>> On Wednesday, March 31st, 2021 at 18:28, Dan Ritter  
>> wrote:
>> 
>> > That was the subject line of a message I just received from a
>> > -   I am not a covert agent of an anti-FSF cabal [...]
>> 
>> Unless you were a very bad covert agent, you would say that, wouldn't you ;).
>
> Correct.
>
> However, one might decide to look at my blog, my history of (I
> hope) helpful posts in debian-user, or indeed my career -- and
> find quite a bit of counter-evidence.

So deeply undercover you don't recognize it yourself.

Re : Re: probleme unsquash

[k6dedijon]

Merci Didier de ta réponse.
Les sommes de contrôle MD5 et SHA256 sont correctes.
L'avantage que je trouve à passer par le live USB est que je peux accéder à mes 
données en attendant de réussir une nouvelle installation.
Je mets toujours mes données dans /home/moi/datas sachant que "datas" est sur 
une partition séparée.

J'ai constaté, en effet, que Debian avait fait de gros progrès pour que 
l'installation soit accessible à plus d'utilisateurs et depuis Jessie je 
l'utilise sans passer par les bidouilleurs qui souvent tentent des opérations 
plus orientées vers gnome.
Je suis très satisfait et attaché à KDE qui convient mieux à ma logique et à 
mon organisation.
J'apprécie le menu K configurable à volonté, la barre nommée "panneau" elle 
aussi très facilement configurable et aussi le fait que KDE permet de 
configurer les fenêtres (épaisseur, largeur des contours et des barres de 
défilement, contraste des couleurs personnalisation des polices, ...

En attendant, j'espère que mon problème d'installation pourra être résolu.
Cassis





- Mail d'origine -
De: didier gaumet 
À: debian-user-french@lists.debian.org
Envoyé: Wed, 31 Mar 2021 09:00:56 +0200 (CEST)
Objet: Re: probleme unsquash


D'une manière générale je trouve que, au moins par le passé, les médias 
Live présentent plus de problèmes et moins de flexibilité d'installation 
que les médias purement dédiés à l'installation, et encore plus dans le 
cas de Debian.

Ton problème pourrait être causé par un téléchargement corrompu du média 
(as-tu vérifié une somme de contrôle?) et un nouveau téléchargement 
pourrait le solutionner. ça pourrait aussi être dû à l'utilisation d'un 
outil du genre d'Unetbootin pour créer la clé USB. Ou à un défaut dans 
les nouvelles images 10.9. Mais de toutes façons j'aurais tendance à te 
conseiller d'utiliser un vrai média d'installation plutôt qu'un media 
live pour installer


Bonjour,
Suite à un problème, je suis amené à réinstaller ma Debian 10.
J'ai pris l'image : debian-live-10.9.0-amd64-kde.iso
L'installation avorte sur un message disant que unsquash n'est pas installé.
Que faire ?
Merci pour vos réponses
Cassis

Re: Wayland and GNOME 3

[Paul M Foster]

On Wed, Mar 31, 2021 at 10:24:25PM +, Andrew M.A. Cater wrote:

> On Wed, Mar 31, 2021 at 05:31:59PM -0400, Paul M Foster wrote:
> > A while back I installed GNOME 3 (Buster), and it dragged Wayland in, and
> > now runs on top of Wayland. I like Wayland, but some things (like Synaptic)
> > don't work with it. Is there a way to run GNOME 3 on Xorg?
> > 
> > Paul
> > 
> > -- 
> > Paul M. Foster
> > http://noferblatz.com
> > http://quillandmouse.com
> > 
> Log out of Gnome3. You get the login splash with username to click on. That
> opens the password box. Just under the password box is a cog wheel icon.
> Before you put your password in, click on the cog. You get various options -
> Gnome will default to Wayland but you can also choose Gnome on X11. [I can't 
> remember what Default X11 does]

Absolutely correct. Seems a little more sluggish under Xorg, but otherwise
seems okay. Thanks.

Paul

-- 
Paul M. Foster
http://noferblatz.com
http://quillandmouse.com

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Nicholas Geovanis]

On Wed, Mar 31, 2021, 4:26 PM Moritz Kempe 
wrote:

> Up until now i used my AVM Fritz!Box (my router) with the (supported)
> firmware version FRITZ!OS-Version 07.21.
>
> Just now, i upgraded the firmware to FRITZ!OS-Version 07.25 and the DNS
> is now working on my Raspberry Pi 400.
>
>
> I cannot yet say, if my problem is solved but it seems like it. I will
> reply to this mail if the problem will reoccur
>

Wow, you're fast :-)
I feared you would find exactly those long DHCP discover sequences that you
noticed. I was just going back to see if the server that granted you was at
the address you were expecting.
Gruß Gott

Here is an changelog
> https://en.avm.de/fritz-lab/fresh-from-development/updates-improvements/
>
> > *Improved *- Update process more robust for potential DNS problems
> Or here in the German changelog
>
> https://avm.de/service/downloads/update-news/download/show/eyJkaXNwbGF5IjoiRlJJVFohQm94IDc1OTAiLCJ1cmwiOiJodHRwOlwvXC9kb3dubG9hZC5hdm0uZGVcL2ZyaXR6Ym94XC9mcml0emJveC03NTkwXC9kZXV0c2NobGFuZFwvZnJpdHoub3NcL2luZm9fZGUudHh0IiwiaGFzaCI6IjNiYmQ1ZTI5YTg4N2NjM2U3ZjRhZTRhOTY4YjE3OTNmYTA2MWU1NzA1Y2NkYjZlYjA2ODM2NWYwNjEzYWMzZjcifQ%3D%3D/
>
>
> *Behoben* IPv6: Im IPv6 Router Advertisement (RA) mit Option 25
> (Recursive DNS Server) wurden zum Teil Bits des Feldes "Reserved" gesetzt
>
> [EN] Fixed: IPv6 Router Advertisement (RA) with Option 25 (Recursive DNS
> Server) got manipulated bits at the field "Reserved"
>
>
> *Behoben* DNS-Anfragen des Typs "PTR" wurden teilweise nicht korrekt
> aufgelöst
>
> [EN] Fixed: DNS Querries with Type "PTR" wouldn't get resolved right.
>
>
> Could on of this changes be the cause of my problems, or the problems
> other people are also getting?
>
>

Re: Wayland and GNOME 3

[Gene Heskett]

On Wednesday 31 March 2021 17:31:59 Paul M Foster wrote:

> A while back I installed GNOME 3 (Buster), and it dragged Wayland in,
> and now runs on top of Wayland. I like Wayland, but some things (like
> Synaptic) don't work with it. Is there a way to run GNOME 3 on Xorg?
>
> Paul

Give this commandline a try after opening your fav konsole:

sudo -E synaptic

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Subject: Mr. Dan Ritter, why is it that you appear to be posting your POV on my posts? Are you a covert agent of the anti-FSF cabal, trying to subvert something "positive for FSF, but detrimental

[Dan Ritter]

Laura Smith wrote: 
> On Wednesday, March 31st, 2021 at 18:28, Dan Ritter  
> wrote:
> 
> > That was the subject line of a message I just received from a
> > -   I am not a covert agent of an anti-FSF cabal [...]
> 
> Unless you were a very bad covert agent, you would say that, wouldn't you ;).

Correct.

However, one might decide to look at my blog, my history of (I
hope) helpful posts in debian-user, or indeed my career -- and
find quite a bit of counter-evidence.

-dsr-

Re: Temporary failure in name resolution

[Dan Norton]

David Christensen wrote on Wed, 31 Mar 2021 13:49:56 -0700:

I would do 'apt-get update' and 'apt-get upgrade' ('autoremove',
'clean', etc.). Once apt-get(8) is done, I would revert the changes
to /etc/resolv.conf and see if name resolution breaks or remains
working. (I would test by renaming /etc/resolve.conf and rebooting.)

Here is what I did:
# apt update
# apt upgrade
# apt autoremove
# apt-get clean
# cp /etc/resolv.conf /etc/resolv.confX
# chattr -i /etc/resolv.conf
## to make resolv.conf *not* immutable
# cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.1.254

Shutdown then power-on boot

## rebooted with /etc/resolv.conf *not* immutable
root@deb4:~# ping google.com
ping: google.com: Temporary failure in name resolution
root@deb4:~# cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 192.168.1.254
## showing that /etc/resolv.conf has been clobbered

After restoring resolv.conf so that it looks like this:
# cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.1.254
# chattr +i /etc/resolv.conf
## making it immutable

Rebooted and posted this.

 - Dan

Re: Wayland and GNOME 3

[Andrew M.A. Cater]

On Wed, Mar 31, 2021 at 05:31:59PM -0400, Paul M Foster wrote:
> A while back I installed GNOME 3 (Buster), and it dragged Wayland in, and
> now runs on top of Wayland. I like Wayland, but some things (like Synaptic)
> don't work with it. Is there a way to run GNOME 3 on Xorg?
> 
> Paul
> 
> -- 
> Paul M. Foster
> http://noferblatz.com
> http://quillandmouse.com
> 
Log out of Gnome3. You get the login splash with username to click on. That
opens the password box. Just under the password box is a cog wheel icon.
Before you put your password in, click on the cog. You get various options -
Gnome will default to Wayland but you can also choose Gnome on X11. [I can't 
remember what Default X11 does]

Hope this helps,

All the very best as ever,

Andy C

Wayland and GNOME 3

[Paul M Foster]

A while back I installed GNOME 3 (Buster), and it dragged Wayland in, and
now runs on top of Wayland. I like Wayland, but some things (like Synaptic)
don't work with it. Is there a way to run GNOME 3 on Xorg?

Paul

-- 
Paul M. Foster
http://noferblatz.com
http://quillandmouse.com

Re: Temporary failure in name resolution

[David Christensen]

On 3/31/21 1:58 PM, Greg Wooledge wrote:

On Wed, Mar 31, 2021 at 01:43:23PM -0700, David Christensen wrote:

Is there technical documentation that explains how name resolution works in
Linux 4.19.0-16-amd64 and/or Debian 10?  (e.g. design and implementation,
userland tools, etc..)


It's not the kernel.  At all.

The standard name resolution in Debian is done by a modular system
called NSS (Name Service Switch).  The configuration file for this
is /etc/nsswitch.conf.

NSS is responsible for several different kinds of name resolution.  For
hostnames, the line in question is "hosts:".  This tells NSS whether to
use DNS, NIS, plain files, or other modules, in which order, and whether
a failure should abort or continue.

nsswitch.conf(5)
gethostbyname(3)
resolver(3)
hosts(5)
resolv.conf(5)

If you want to test the *standard* name resolution as documented by the
pages above, the correct shell tool is getent(1).

unicorn:~$ getent hosts www.debian.org
2603:400a::bb8::801f:3e www.debian.org
2001:4f8:1:c::15 www.debian.org

This uses the configuration from nsswitch.conf, so it will consult
/etc/hosts and/or DNS, or whatever you've configured your system to use.

There are other tools that specifically probe DNS, such as host(1)
and dig(1).  These bypass nsswitch.conf and go straight to DNS, because
they're designed to help an administrator test their DNS configuration.
(These are just two of the most common tools for this purpose -- there
are many more.)

unicorn:~$ host unicorn
Host unicorn not found: 3(NXDOMAIN)
unicorn:~$ getent hosts unicorn
127.0.1.1   unicorn.wooledge.org unicorn



Thank you for the clarification.


David

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Moritz Kempe]

Up until now i used my AVM Fritz!Box (my router) with the (supported) 
firmware version FRITZ!OS-Version 07.21.


Just now, i upgraded the firmware to FRITZ!OS-Version 07.25 and the DNS 
is now working on my Raspberry Pi 400.



I cannot yet say, if my problem is solved but it seems like it. I will 
reply to this mail if the problem will reoccur.



Here is an changelog 
https://en.avm.de/fritz-lab/fresh-from-development/updates-improvements/



*Improved *- Update process more robust for potential DNS problems
Or here in the German changelog 
https://avm.de/service/downloads/update-news/download/show/eyJkaXNwbGF5IjoiRlJJVFohQm94IDc1OTAiLCJ1cmwiOiJodHRwOlwvXC9kb3dubG9hZC5hdm0uZGVcL2ZyaXR6Ym94XC9mcml0emJveC03NTkwXC9kZXV0c2NobGFuZFwvZnJpdHoub3NcL2luZm9fZGUudHh0IiwiaGFzaCI6IjNiYmQ1ZTI5YTg4N2NjM2U3ZjRhZTRhOTY4YjE3OTNmYTA2MWU1NzA1Y2NkYjZlYjA2ODM2NWYwNjEzYWMzZjcifQ%3D%3D/



*Behoben* IPv6: Im IPv6 Router Advertisement (RA) mit Option 25 
(Recursive DNS Server) wurden zum Teil Bits des Feldes "Reserved" gesetzt


[EN] Fixed: IPv6 Router Advertisement (RA) with Option 25 (Recursive DNS 
Server) got manipulated bits at the field "Reserved"



*Behoben* DNS-Anfragen des Typs "PTR" wurden teilweise nicht korrekt 
aufgelöst


[EN] Fixed: DNS Querries with Type "PTR" wouldn't get resolved right.


Could on of this changes be the cause of my problems, or the problems 
other people are also getting?

Re: Subject: Mr. Dan Ritter, why is it that you appear to be posting your POV on my posts? Are you a covert agent of the anti-FSF cabal, trying to subvert something "positive for FSF, but detrimental

[Laura Smith]

On Wednesday, March 31st, 2021 at 18:28, Dan Ritter  
wrote:

> That was the subject line of a message I just received from a
> -   I am not a covert agent of an anti-FSF cabal [...]

Unless you were a very bad covert agent, you would say that, wouldn't you ;).

Re: How I scan, was Re: xsane can't see Brother ADS-2700W scanner

[Stefan Monnier]

> Scanning the output to a server just seems plain obvious to me.
> What's the downside?

It has its advantages, indeed.  On the downsides:

- the scanner usually has a very limited UI, making it
  difficult/inconvenient (if at all possible) to control and select the
  scanning options, compared to the comfort of a large screen.

- scanning to a server implies allowing the scanner device write access
  to a server, which either implies the users authenticating themselves
  on the scanner itself (which is rather problematic and is compounded
  with the previous downside), or making the scan result land on an
  "anonymous" area where anyone can see what anyone else scans.

- It usually means you're stuck with the functionality that the
  manufacturer decided to include in the scanner's software stack,
  because it's always proprietary or "walled" (it may contain Free
  Software for all I know, but I can't access nor modify the code).

The option I favor is that the scan is controlled by your own computer,
but you can trigger new scans by hitting buttons on the scanner
(i.e. the button-presses get sent to your computer who then decides
what action to take in response to them), so that you can comfortably
setup the scan parameters on your computer and then you can comfortably
scan the various documents without having to go back to your computer
between them.

Sadly, I haven't figured out how to do that yet :-(


Stefan

Re: Temporary failure in name resolution

[Greg Wooledge]

On Wed, Mar 31, 2021 at 01:43:23PM -0700, David Christensen wrote:
> Is there technical documentation that explains how name resolution works in
> Linux 4.19.0-16-amd64 and/or Debian 10?  (e.g. design and implementation,
> userland tools, etc..)

It's not the kernel.  At all.

The standard name resolution in Debian is done by a modular system
called NSS (Name Service Switch).  The configuration file for this
is /etc/nsswitch.conf.

NSS is responsible for several different kinds of name resolution.  For
hostnames, the line in question is "hosts:".  This tells NSS whether to
use DNS, NIS, plain files, or other modules, in which order, and whether
a failure should abort or continue.

nsswitch.conf(5)
gethostbyname(3)
resolver(3)
hosts(5)
resolv.conf(5)

If you want to test the *standard* name resolution as documented by the
pages above, the correct shell tool is getent(1).

unicorn:~$ getent hosts www.debian.org
2603:400a::bb8::801f:3e www.debian.org
2001:4f8:1:c::15 www.debian.org

This uses the configuration from nsswitch.conf, so it will consult
/etc/hosts and/or DNS, or whatever you've configured your system to use.

There are other tools that specifically probe DNS, such as host(1)
and dig(1).  These bypass nsswitch.conf and go straight to DNS, because
they're designed to help an administrator test their DNS configuration.
(These are just two of the most common tools for this purpose -- there
are many more.)

unicorn:~$ host unicorn
Host unicorn not found: 3(NXDOMAIN)
unicorn:~$ getent hosts unicorn
127.0.1.1   unicorn.wooledge.org unicorn

Re: Cannot see update to recent linux kernel 5.10.19-1~bpo10+1 (from 5.10.13-1~bpo10+1)

[l0f4r0]

Hi,

30 mars 2021, 08:16 de andreimpope...@gmail.com:

> $ rmadison linux-signed-amd64
> linux-signed-amd64 | 4.19.118+2+deb10u1~bpo9+1 | stretch-backports | source
> linux-signed-amd64 | 4.19.171+2| stable| source
> linux-signed-amd64 | 4.19.181+1| stable| source
> linux-signed-amd64 | 5.9.15+1~bpo10+1  | buster-backports  | source
> linux-signed-amd64 | 5.10.13+1~bpo10+1 | buster-backports  | source
> linux-signed-amd64 | 5.10.19+1~bpo10+1 | backports-policy  | source
> linux-signed-amd64 | 5.10.24+1 | testing   | source
> linux-signed-amd64 | 5.10.24+1 | unstable  | source
>
Is linux-signed-amd64 the source of linux-image-amd64? I suppose there are some 
constraints here but it would be (apparently) easier if the names were matching 
^^

If I follow you, we have more information by inquiring about the source package 
than the binary one?


> The packages appears to be stuck in the backports-policy. If I recall 
> correctly (see recent -backports archives) this is related to the 
> freeze.
>
Very interesting. You have certainly something here...

But if true, why 
https://lists.debian.org/debian-backports-changes/2021/03/msg00053.html 
mentions "Accepted linux 5.10.19-1~bpo10+1 (source) into 
buster-backports->backports-policy, buster-backports" if it's just in 
backports-policy?

Indeed, as soon as I see "buster-backports" mentioned, I expect the package to 
be available through...(drum roll)... buster-backports.

30 mars 2021, 16:14 de deb...@lionunicorn.co.uk:

> On Sun 28 Mar 2021 at 19:46:07 (+0200), > l0f...@tuta.io>  wrote:
>
>>
>> By the way, what is image-5.10.0-0.bpo.4* serie for?Is it only related to 
>> "Change ABI number to 0.bpo.4"? Do I need that?
>>
> I guess you have to read the changes file to find that out.
> https://lists.debian.org/debian-backports-changes/2021/03/msg00053.html
> might be of use here.
>
Actually, what I need is just linux-image-5.10.0-0.bpo.4-amd64 but it hasn't 
been made available yet. This one will be related to kernel 5.10.19-1~bpo10+1.


> Perhaps it's worth subscribing to debian-backports-changes and
> debian-backports. You can post to the latter.
>
That's a good suggestion, thanks :)

Best regards,
l0f4r0

Re: Creating my first LAN

[Joe]

On Wed, 31 Mar 2021 15:25:55 -0500
David Wright  wrote:


> 
> But going back to the OP's original scenario, a broken¹ router would
> be an ideal solution for linking two wifi laptops, with no possibility
> of accidentally joining the Internet (horrors!).
> 
> ¹ Is this a common mode of failure? My guess would be that, plus
>   the radio part. (Note: nowhere am I talking about modems.)
> 
>
I don't think so. But a modem-router will eventually be superseded, and
will then work as a switch if you ignore the WAN part, I think that's
a more common situation than cable router WAN failure. I have a couple
of old ADSL routers, while I'm actually using a VDSL one provided by the
ISP. I do have the occasional temporary need for a portable 4-port
hub/switch.

I've just bought a wireless (cable) router to improve the range over my
very old one. I've left it in router mode, it provides DNS and DHCP to
wireless clients using my bind9 server as DNS source, the latter
working from first principles (root hints). Another spare router...

-- 
Joe

Re: Temporary failure in name resolution

[David Christensen]

On 3/31/21 11:58 AM, Dan Norton wrote:

Thank you, Felix. This post is coming from Debian with names resolved:
#1 SMP Debian 4.19.181-1 (2021-03-19)

Also resolv.conf is un-messed with:
$ cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.1.254

All is well again. Thanks again and thanks to everyone who responded.



Okay.


I would do 'apt-get update' and 'apt-get upgrade' ('autoremove', 
'clean', etc.).  Once apt-get(8) is done, I would revert the changes to 
/etc/resolv.conf and see if name resolution breaks or remains working. 
(I would test by renaming /etc/resolve.conf and rebooting.)



David

Re: Temporary failure in name resolution

[David Christensen]

On 3/31/21 10:37 AM, Greg Wooledge wrote:


As of right now, we have at least two people posting to debian-user
about DNS failures involving what appears to be their home router's
forwarding DNS service, and Debian 10.9.

Switching the nameserver lines in resolv.conf to something *other than*
the home router's DNS seems like a reasonable workaround.  Many of us
do that full-time anyway.

If anyone knows of a change to libc6 or libnss* in Debian 10.9 that might
be the underlying cause of these issues, please file a bug report or
something so it can be fixed.


Then I would

sudo chattr +i /etc/resolv.conf


That's *one* of the methods listed on the wiki.  Just be aware that it
can leave a whole bunch of /etc/resolv.conf.dhclient-new.* files sitting
around, and be prepared to remove them.

(I use a weekly crontab job.)



Is there technical documentation that explains how name resolution works 
in Linux 4.19.0-16-amd64 and/or Debian 10?  (e.g. design and 
implementation, userland tools, etc..)



David

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Moritz Kempe]

On 3/31/21 3:22 PM, Nicholas Geovanis wrote:
On Wed, Mar 31, 2021, 8:08 AM Moritz Kempe > wrote:


On 3/31/21 1:55 PM, Lee wrote:
> On 3/31/21, Moritz Kempe mailto:deblist%2bdeb...@moke12g.de>> wrote:
>> On 3/31/21 1:25 PM, Greg Wooledge wrote:
>>> On Wed, Mar 31, 2021 at 12:14:59AM +0200, Moritz Kempe wrote:
 -- Firefox Hmm. We’re having trouble finding that site. We can’t
 connect to the server at github.com .
 -- Chromium This site can’t be reachedCheck if there is a typo in
 github.com . DNS_PROBE_FINISHED_NXDOMAIN
 moke@rpi4-20201112:~$ host github.com 
Host github.com  not found:
 2(SERVFAIL)
>>> grep ^hosts: /etc/nsswitch.conf
>> --
>> hosts:          files mdns4_minimal [NOTFOUND=return] dns
mymachines
> I don't trust multicast dns, so in addition to turning it off
I've also got
> $ grep host /etc/nsswitch.conf
> # hosts:          files mdns4_minimal [NOTFOUND=return] dns
> hosts:          files dns
>
> Maybe worth a shot?

Changed my /etc/nsswitch.conf to

--

..

#hosts:  files mdns4_minimal [NOTFOUND=return] dns mymachines
hosts:  files dns
..

--

and rebooted the system. The behavior hasn't changed.

github.com  is still blocked. And dig is still
able to find the ip address.

Or do i have done something wrong?


I have found out, that i can restore some domains when running
"/sbin/dhclient" as root but not all. Github is still not accessible.


That's why I suggested checking for DHCP messages in the logs. But 
also logs upstream from your pi's. Each time you get a DHCP grant, 
potentially you've switched DNS servers.


Do you mean the logs at /var/log/syslog?

And for what i look out for?

Here are some entries, maybe you see something important for this issue.

--

Mar 31 14:39:04 rpi4-20201112 dhclient[5538]: DHCPDISCOVER on docker0 to 
255.255.255.255 port 67 interval 7
Mar 31 14:39:11 rpi4-20201112 dhclient[5538]: DHCPDISCOVER on docker0 to 
255.255.255.255 port 67 interval 20
Mar 31 14:39:31 rpi4-20201112 dhclient[5538]: DHCPDISCOVER on docker0 to 
255.255.255.255 port 67 interval 12
Mar 31 14:39:43 rpi4-20201112 dhclient[5538]: DHCPDISCOVER on docker0 to 
255.255.255.255 port 67 interval 19
Mar 31 14:40:02 rpi4-20201112 dhclient[5538]: DHCPDISCOVER on docker0 to 
255.255.255.255 port 67 interval 3

Mar 31 14:40:05 rpi4-20201112 dhclient[5538]: No DHCPOFFERS received.
Mar 31 14:40:05 rpi4-20201112 dhclient[5538]: No working leases in 
persistent database - sleeping.


-- This was logged for many times.

--

Mar 31 15:05:49 rpi4-20201112 dhclient[478]: Internet Systems Consortium 
DHCP Client 4.4.1
Mar 31 15:05:49 rpi4-20201112 dhclient[478]: Copyright 2004-2018 
Internet Systems Consortium.
Mar 31 15:05:49 rpi4-20201112 ifup[478]: For info, please visit 
https://www.isc.org/software/dhcp/

Mar 31 15:05:49 rpi4-20201112 dhclient[478]: All rights reserved.
Mar 31 15:05:49 rpi4-20201112 dhclient[478]: For info, please visit 
https://www.isc.org/software/dhcp/

Mar 31 15:05:49 rpi4-20201112 dhclient[478]:
Mar 31 15:05:49 rpi4-20201112 dhclient[478]: Listening on 
LPF/eth0/##:##:##:##:##:##    # censored by me
Mar 31 15:05:49 rpi4-20201112 dhclient[478]: Sending on 
LPF/eth0/##:##:##:##:##:## # censored by me

Mar 31 15:05:49 rpi4-20201112 dhclient[478]: Sending on Socket/fallback
Mar 31 15:05:49 rpi4-20201112 dhclient[478]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 8
Mar 31 15:05:50 rpi4-20201112 NetworkManager[417]:  
[1617195950.2281] dhcp-init: Using DHCP client 'internal'
Mar 31 15:05:57 rpi4-20201112 dhclient[478]: DHCPDISCOVER on eth0 to 
255.255.255.255 port 67 interval 14
Mar 31 15:05:58 rpi4-20201112 dhclient[478]: DHCPOFFER of 10.0.0.70 from 
10.0.0.1
Mar 31 15:05:58 rpi4-20201112 dhclient[478]: DHCPREQUEST for 10.0.0.70 
on eth0 to 255.255.255.255 port 67
Mar 31 15:05:58 rpi4-20201112 dhclient[478]: DHCPACK of 10.0.0.70 from 
10.0.0.1
Mar 31 15:06:38 rpi4-20201112 dhclient[478]: bound to 10.0.0.70 -- 
renewal in 3831703 seconds.


--

I used the command "cat /var/log/syslog | grep dhc"


And you said


But also logs upstream from your pi's.
do you mean the DHCP log from my router? Because i searched for one, but 
i haven't found one yet.


Or do you mean that i should use Wireshark to analyze my DHCP requests?


I haven't looked into networking on that level.

I would be nice, if you would give me an explanation or link a website 
which could do that.




Note: I haven't changed any networking configuration on this
device. I
haven't even enabled wifi.

Re: Temporary failure in name resolution

[David Christensen]

I have reorganized the content below to improve comprehension.


On 3/31/21 9:46 AM, Dan Norton wrote:
Thanks to all who responded. 

> Thanks for your detailed help. Let me know if I can dig out more.

YW.  We are making progress.  See below.



Have not changed any of the gateway settings that I'm aware of.



Okay.



This problem makes me post from a Windows laptop and transfer terminal output 
via thumb drive to the laptop. Not pretty.



Sneakernet works. :-)


> This laptop is the only other computer but it runs Windows. Is that 
testing name resolution with another computer?



Shutdown the Debian computer.  Shutdown the Windows laptop.  Look at the 
LED's on the AT gateway so that you know their state when it is 
operating.  Power off the gateway.  Unpatch the Ethernet cable connected 
to the laptop (e.g. disconnect both ends).  Wait at least 2 minutes. 
Boot the laptop and disable or delete all network connections.  Reboot 
Windows and verify that all network connections are down or gone.  Power 
up the gateway.  Wait for the LED's to return to the operating state. 
Patch the laptop to the gateway with an Ethernet cable.  Configure or 
create an Ethernet network connection to the gateway in Windows.  Fix 
any problems and verify everything works (contact AT technical support 
if necessary).  Stop the Ethernet connection in Windows.  Configure or 
create a Wi-Fi network connection to the gateway in Windows.  Fix any 
problems and verify everything works (contact AT technical support if 
necessary).  Turn off the Wi-Fi connection in Windows.  Choose either 
the Ethernet network connection or the Wi-Fi network connection, and 
enable one.



Ensure that the Debian computer is connected to the gateway with an 
Ethernet cable via the primary Ethernet port.  Unpatch all cables 
connected to all other Ethernet ports.  Boot the Debian computer.



> Yes, I have done a cold reboot [of the Debian computer] since upgrading.


Okay.


> # cat /etc/debian_version ; uname -a
> 10.9
> Linux deb4 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) 
x86_64 GNU/Linux



Okay.  Those are current.


> # ifconfig eno1
> eno1: flags=4163  mtu 1500
>  inet 192.168.1.66  netmask 255.255.255.0  broadcast 
192.168.1.255
>  inet6 ::***:::::  prefixlen 64 
scopeid 0x0
>  inet6 :::::  prefixlen 64  scopeid 
0x20

>  ether **:**:**:**:**:**  txqueuelen 1000  (Ethernet)
>  RX packets 10009  bytes 1101640 (1.0 MiB)
>  RX errors 0  dropped 0  overruns 0  frame 0
>  TX packets 1734  bytes 180973 (176.7 KiB)
>  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


Okay.


> # cd /etc
> # cat resolv.conf
> domain attlocal.net
> search attlocal.net
> nameserver 192.168.1.254
> [something removes additional nameserver lines that I add]


Okay.  For now, do not try to edit that file.



# apt update
0% [Connecting to deb.debian.org] [Connecting to qgis.org] [Connecting to 
brave-browser-apt-release.s3.brave.com]^C
[cancelled early]

# apt update
Err:1 http://deb.debian.org/debian buster InRelease
   Temporary failure resolving 'deb.debian.org'
Err:2 https://qgis.org/debian buster InRelease
   Temporary failure resolving 'qgis.org'
Err:3 https://brave-browser-apt-release.s3.brave.com stable InRelease
   Temporary failure resolving 'brave-browser-apt-release.s3.brave.com'
0% [Working]^C
[cancelled later]

# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
   libqgis-3d3.18.0 libqgis-analysis3.18.0 libqgis-app3.18.0 libqgis-core3.18.0 
libqgis-gui3.18.0
   libqgis-native3.18.0 libqgis-server3.18.0 libqgisgrass7-3.18.0 
libqgispython3.18.0
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
   libqgis-3d3.18.1 libqgis-analysis3.18.1 libqgis-app3.18.1 libqgis-core3.18.1 
libqgis-gui3.18.1
   libqgis-native3.18.1 libqgis-server3.18.1 libqgisgrass7-3.18.1 
libqgispython3.18.1
The following packages will be upgraded:
   libqgis-customwidgets python3-qgis python3-qgis-common qgis qgis-common 
qgis-plugin-grass
   qgis-plugin-grass-common qgis-provider-grass qgis-providers 
qgis-providers-common
10 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 105 MB of archives.
After this operation, 91.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Err:1 https://qgis.org/debian buster/main amd64 qgis-plugin-grass amd64 
1:3.18.1+15buster
   Temporary failure resolving 'qgis.org'
[this continues to Err:19 then more]



So, the updates/ upgrades are incomplete because you need packages and 
the DNS problems are preventing apt-get(8) from fetching the packages 
needed to complete the updates/ upgrades.  A Catch-22 situation...



Have you modified /etc/apt/sources.list or added any configuration 

How I scan, was Re: xsane can't see Brother ADS-2700W scanner

[David Wright]

On Wed 31 Mar 2021 at 07:18:14 (-0400), Dan Ritter wrote:
> Charlie Gibbs wrote:
> > The one way I did manage to get the scanner to work was to a
> > USB flash drive.  It quickly sucked in a handful of sheets,
> > scanned both sides, and wrote them to a file on the stick.
> > If all else fails, I can work with it that way.  But I'd
> > really like to let xsane manage the process.

That's the way I've always scanned anything. Earlier this century,
the alternatives were (a) walking to a room with "the" public scanner,
connected to a dedicated computer, and coordinating between holding
a book on the platen and pressing buttons on the screen with a mouse,
or (b) pushing a USB stick into a giant photocopier and pretending
to copy it. Also (b) had the super document feeder (1/2 sided)
and could scan up to A3, whereas (a) had a limp rubbery cover over
the A4 platen glass.

> > I'm beginning to wonder, though, whether fashions are changing.
> > Scanners nowadays seem to want to push data to a server, rather
> > than being commanded to scan by a computer.  Is this really
> > happening?  If so, whither (or should that be "wither") xsane?
> 
> In office environments, with shared resources, this is often
> preferable. Having the scanner drop everything into a
> samba-shared filesystem, for example...

Well, yes. What's the point of controlling the scanner from your
disk when you've got to *at least* visit the scanner to place the
document in the feed hopper—why not just press a button to start
it, while you're there?

And obviously there are cases where the feeding has to be done
manually. In fact, most of my scanning is like this. (Why are
multiple-page documents being printed in the first place, so that
people have to scan them back in?)

Scanning the output to a server just seems plain obvious to me.
What's the downside?

Cheers,
David.

Re: Creating my first LAN

[David Wright]

On Wed 31 Mar 2021 at 10:45:59 (-0400), Marc Auslander wrote:
> Anssi Saari  writes:
> >Brian  writes:
> >
> >> Now - could I use this non-internet-capable router as a switch?

> >
> >Probably. Usually LAN ports on a router are setup as a switch. The
> >router may have a DHCP server running though which you may want to
> >disable.

That's precisely the scenario I have here, posted in
https://lists.debian.org/debian-user/2021/02/msg00603.html
where it's the second diagram. Reason, the same or similar:
a failed WAN port. But it's ideal for radiating to the
living half of the house, and all its ports are active
as well.

> In my experiance, you should put the router into access point mode,
> connect your lan to the wan port, and then use the lan ports as
> additional ports.  Some routers get confused when they think they are
> routing even though they can't reach the wan.  And remember to turn off
> WiFi unless it is far from your primary router and you want to extend
> your WiFi network.

Yes, you only *have to* switch to AP if you have a working WAN port,
which you're connecting to the primary router. It does no harm either
way in Brian's case (or mine), with no functional WAN port.

I don't know that the secondary router gets "confused" if you leave it
in non-AP mode (when you are using the WAN port), but I assume that a
host on the primary router should be seen as an outsider if it tries
to connect to one on the secondary router, which would be a problem.

> Also, make sure you set the IP address of the router to one on your lan
> that's not in use and not in the DHCP range of your primary router.  I
> normally use .2 for this purpose.

The primary router has the secondary one at a reserved address—
actually that's the case for all the hosts in the house. (Neither
router is capable of acting as a DNS server.)

The wifi settings are identical for both, and hosts just connect
to whichever gives the stronger signal.

But going back to the OP's original scenario, a broken¹ router would
be an ideal solution for linking two wifi laptops, with no possibility
of accidentally joining the Internet (horrors!).

¹ Is this a common mode of failure? My guess would be that, plus
  the radio part. (Note: nowhere am I talking about modems.)

Cheers,
David.

Re: Temporary failure in name resolution

[Dan Norton]

Thank you, Felix. This post is coming from Debian with names resolved:
#1 SMP Debian 4.19.181-1 (2021-03-19)

Also resolv.conf is un-messed with:
$ cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 192.168.1.254

All is well again. Thanks again and thanks to everyone who responded.

 - Dan

Re: Temporary failure in name resolution

[Greg Wooledge]

On Wed, Mar 31, 2021 at 01:26:32PM -0400, Felix Miata wrote:
> Dan Norton composed on 2021-03-31 12:46 (UTC-0400):
> 
> > # cd /etc
> > # cat resolv.conf
> > domain attlocal.net
> > search attlocal.net
> > nameserver 192.168.1.254
> > [something removes additional nameserver lines that I add]  
> > 
> I can't tell why this happens, or suggest a proper fix,

https://wiki.debian.org/resolv.conf

> but if it was happening to
> me, I would replace
> 
>   nameserver 192.168.1.254
> 
> with
>   nameserver 1.1.1.1
>   nameserver 1.0.0.1
> 
> and possibly add
> 
>   nameserver 192.168.1.1
> 
> or whatever the IP of your router is.

I'm assuming 192.168.1.254 is his router.

As of right now, we have at least two people posting to debian-user
about DNS failures involving what appears to be their home router's
forwarding DNS service, and Debian 10.9.

Switching the nameserver lines in resolv.conf to something *other than*
the home router's DNS seems like a reasonable workaround.  Many of us
do that full-time anyway.

If anyone knows of a change to libc6 or libnss* in Debian 10.9 that might
be the underlying cause of these issues, please file a bug report or
something so it can be fixed.

> Then I would
> 
>   sudo chattr +i /etc/resolv.conf

That's *one* of the methods listed on the wiki.  Just be aware that it
can leave a whole bunch of /etc/resolv.conf.dhclient-new.* files sitting
around, and be prepared to remove them.

(I use a weekly crontab job.)

Subject: Mr. Dan Ritter, why is it that you appear to be posting your POV on my posts? Are you a covert agent of the anti-FSF cabal, trying to subvert something "positive for FSF, but detrimental for

[Dan Ritter]

That was the subject line of a message I just received from a
Debian-user member.

In case anyone is confused:

- I write my point of view because that's the one I have

- I am not a covert agent of an anti-FSF cabal, to the best of
  my knowledge.

- I have no idea what 'trying to subvert something "positive
  for FSF, but detrimental for Proprietary"' means.

- I have no confusion in my mind between the FSF and Debian. I
  suspect that the author does have some confusion there.

I have been asked by this person not to write to them, so I have
killfiled them. I may end up in one of the threads that they
contribute to anyway, but I won't be responding to them.

-dsr-

(Psst... got any more interesting cabals to join?)

Re: Temporary failure in name resolution

[Felix Miata]

Dan Norton composed on 2021-03-31 12:46 (UTC-0400):

> # cd /etc
> # cat resolv.conf
> domain attlocal.net
> search attlocal.net
> nameserver 192.168.1.254
> [something removes additional nameserver lines that I add]
> 
I can't tell why this happens, or suggest a proper fix, but if it was happening 
to
me, I would replace

nameserver 192.168.1.254

with
nameserver 1.1.1.1
nameserver 1.0.0.1

and possibly add

nameserver 192.168.1.1

or whatever the IP of your router is. Then I would

sudo chattr +i /etc/resolv.conf

and expect no further need for thumb drive or Windows.


Is resolvconf installed?

What is output from

systemctl status systemd-resolved.service

In Bullseye right now I have neither resolvconf installed, nor systemd-resolvd
enabled, and am running static IP.
-- 
Evolution as taught in public schools, like religion,
is based on faith, not on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Debían 10 problemas con driver Nvidia

[Camaleón]

El 2021-03-31 a las 10:51 -0600, Rolando Granados escribió:

> Estoy teniendo problemas con el driver de nvidia-340xx ya realice la
> instalación desde ap-get install se reinicia la máquina y no marca ningún
> error, la pantalla de bloqueo también funciona pero cuando me logueo con mi
> usuario se queda en pantalla negra y de ahí no pasa, que podría ser??

Salta a una consola (Ctrl+Alt+F1) y revisa el log de Xorg que tienes en 
«/var/log/Xorg.0.log».

Las instrucciones y pasos de instalación, según la versión de Debian 
que tengas, las tienes por aquí:

NVIDIA Proprietary Driver
https://wiki.debian.org/NvidiaGraphicsDrivers

Asegúrate de que tu gráfica está admitida por la versión del 
controlador que has instalado.

Saludos,

-- 
Camaleón 

Re: Temporary failure in name resolution

[Dan Norton]

Thanks to all who responded. This problem makes me post from a Windows laptop 
and transfer terminal output via thumb drive to the laptop. Not pretty.

To David: Yes, I have done a cold reboot since upgrading.
# apt update
0% [Connecting to deb.debian.org] [Connecting to qgis.org] [Connecting to 
brave-browser-apt-release.s3.brave.com]^C
[cancelled early]

# apt update
Err:1 http://deb.debian.org/debian buster InRelease 
 
  Temporary failure resolving 'deb.debian.org'
Err:2 https://qgis.org/debian buster InRelease  
 
  Temporary failure resolving 'qgis.org'
Err:3 https://brave-browser-apt-release.s3.brave.com stable InRelease   
  
  Temporary failure resolving 'brave-browser-apt-release.s3.brave.com'
0% [Working]^C 
[cancelled later]

# apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libqgis-3d3.18.0 libqgis-analysis3.18.0 libqgis-app3.18.0 libqgis-core3.18.0 
libqgis-gui3.18.0
  libqgis-native3.18.0 libqgis-server3.18.0 libqgisgrass7-3.18.0 
libqgispython3.18.0
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  libqgis-3d3.18.1 libqgis-analysis3.18.1 libqgis-app3.18.1 libqgis-core3.18.1 
libqgis-gui3.18.1
  libqgis-native3.18.1 libqgis-server3.18.1 libqgisgrass7-3.18.1 
libqgispython3.18.1
The following packages will be upgraded:
  libqgis-customwidgets python3-qgis python3-qgis-common qgis qgis-common 
qgis-plugin-grass
  qgis-plugin-grass-common qgis-provider-grass qgis-providers 
qgis-providers-common
10 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 105 MB of archives.
After this operation, 91.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Err:1 https://qgis.org/debian buster/main amd64 qgis-plugin-grass amd64 
1:3.18.1+15buster
  Temporary failure resolving 'qgis.org'
[this continues to Err:19 then more]

Have not changed any of the gateway settings that I'm aware of.

This laptop is the only other computer but it runs Windows. Is that testing 
name resolution with another computer?

# ifconfig eno1
eno1: flags=4163  mtu 1500
inet 192.168.1.66  netmask 255.255.255.0  broadcast 192.168.1.255
inet6 ::***:::::  prefixlen 64  scopeid 
0x0
inet6 :::::  prefixlen 64  scopeid 0x20
ether **:**:**:**:**:**  txqueuelen 1000  (Ethernet)
RX packets 10009  bytes 1101640 (1.0 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 1734  bytes 180973 (176.7 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

# cd /etc
# cat resolv.conf
domain attlocal.net
search attlocal.net
nameserver 192.168.1.254
[something removes additional nameserver lines that I add]

# cat /etc/debian_version ; uname -a
10.9
Linux deb4 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 
GNU/Linux

$ nmcli g status
$ nmcli c show
$ nmcli d show
[I don't seem to have nmcli]

# host -v -t A www.debian.org 8.8.8.8
Trying "www.debian.org"
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases: 

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58963
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.debian.org.IN  A

;; ANSWER SECTION:
www.debian.org. 299 IN  A   128.31.0.62
www.debian.org. 299 IN  A   149.20.4.15

Received 64 bytes from 8.8.8.8#53 in 102 ms

# host -v -t A www.debian.org
Trying "www.debian.org"
;; connection timed out; no servers could be reached

Thanks for your detailed help. Let me know if I can dig out more.

 - Dan

Debían 10 problemas con driver Nvidia

[Rolando Granados]

Estoy teniendo problemas con el driver de nvidia-340xx ya realice la
instalación desde ap-get install se reinicia la máquina y no marca ningún
error, la pantalla de bloqueo también funciona pero cuando me logueo con mi
usuario se queda en pantalla negra y de ahí no pasa, que podría ser??

Re: IANA port ups/401

[Dan Ritter]

Roger Price wrote: 
> On Wed, 31 Mar 2021, to...@tuxteam.de wrote:
> 
> > On Wed, Mar 31, 2021 at 04:51:55PM +0200, Roger Price wrote:
> > > Has any reader of this list ever used IANA port ups/401
> > > "Uninterruptible Power Supply" (other than the One Windows Trojan)?
> > > I'm looking for protocol documentation or reports of usage. The port
> > > was assigned in 2008 to Mr. Charles Bennett as both assignee and
> > > contact. Mr. Bennett himself died in 2015.

Sysadmin-type since 1996ish, so: in the last 25 years, I believe
the only time I have encountered "ups/401" is in /etc/services.

SunOS
Solaris
DEC OSF/1
Harris Nighthawk something-or-another B3 (awful even for the
time) 
VMS on a microVAX the size of a largish microwave oven
NetBSD and OpenBSD but somehow never FreeBSD
Linux in many distros


-dsr-

Re: IANA port ups/401

[Roger Price]

On Wed, 31 Mar 2021, to...@tuxteam.de wrote:


On Wed, Mar 31, 2021 at 04:51:55PM +0200, Roger Price wrote:

Has any reader of this list ever used IANA port ups/401
"Uninterruptible Power Supply" (other than the One Windows Trojan)?
I'm looking for protocol documentation or reports of usage. The port
was assigned in 2008 to Mr. Charles Bennett as both assignee and
contact. Mr. Bennett himself died in 2015.


Funny. Search engine finds someone with your name:

 https://html.duckduckgo.com/html/?q=%22401%22+%22UPS%22+site:tools.ietf.org

giving:

 https://tools.ietf.org/html/draft-rprice-ups-management-protocol-00

I have the strong hunch you /know/ this person :-)


I do not confirm and I do not deny that I know that guy :-) In the discussions 
associated with the I-D, I expect IANA to ask to be shown that there are no 
current users for ups/401.  It seemed useful to tap the accumulated wisdom and 
deep memories of the debian list.


Cheers, Roger

Re: xsane can't see Brother ADS-2700W scanner

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256






‐‐‐ Original Message ‐‐‐
On Wednesday, March 31, 2021 8:24 AM, Hans  wrote:

> Am Mittwoch, 31. März 2021, 14:23:31 CEST schrieb Eduardo M KALINOWSKI:
>
> Hi,
>
> please check in /lib/udev/rules.d/*-libsane1.rules if there is an entry for 
> your scanner. In my case with a brother scanner I had to manually add it, as 
> the brother packages installation is missing this.

Yeah.  I had a similar problem getting xsane to recognize my Fujitsu ScanSnap 
1300.  I searched the web on model number and found a detailed howTo to make it 
work.  (The manual add involved downloading a driver and editing a couple 
files.)

--
Glenn English


-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBzBAEBCAAGBQJgZJdJACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDIo2gf5AT/5vT7kfoDAt6zzPaEaikqqj6xmJmYZyXdYCcF3Potz+I1O
Kek9/PDrOIuW7xWlcUGy0HCtE7apxJC3GR93gg7UOUF9R37mnzxorsDi8pfc
XusVf5IhQ2BinpcUlRWJjsL1XQupe69gbgLPx5MjLgwbklEDhhwc7vyZQM1d
P8OED8TAg9hQF8CGvb0q/NGhKbvHiiPursCPSrq8eeaT2lTf6EsUDUtM9sdW
4+Qe493AFD1o6T0Ip3CgD9z9guz1IzDb+c507r84+u3ALoR2YL+iZuVvdhN0
pmCIunwif83oUFaTefuPz957Uj4ABAj6gQMPLG4dN9/6iNJn0VRaTA==
=MMG5
-END PGP SIGNATURE-

Re: IANA port ups/401

[tomas]

On Wed, Mar 31, 2021 at 04:51:55PM +0200, Roger Price wrote:
> Has any reader of this list ever used IANA port ups/401
> "Uninterruptible Power Supply" (other than the One Windows Trojan)?
> I'm looking for protocol documentation or reports of usage. The port
> was assigned in 2008 to Mr. Charles Bennett as both assignee and
> contact. Mr. Bennett himself died in 2015.

Funny. Search engine finds someone with your name:

  https://html.duckduckgo.com/html/?q=%22401%22+%22UPS%22+site:tools.ietf.org

giving:

  https://tools.ietf.org/html/draft-rprice-ups-management-protocol-00

I have the strong hunch you /know/ this person :-)

Cheers
 - t


signature.asc
Description: Digital signature

Re: Creating my first LAN

[Marc Auslander]

Anssi Saari  writes:

>Brian  writes:
>
...
>>
>> Now - could I use this non-internet-capable router as a switch?
>
>Probably. Usually LAN ports on a router are setup as a switch. The
>router may have a DHCP server running though which you may want to
>disable.
In my experiance, you should put the router into access point mode,
connect your lan to the wan port, and then use the lan ports as
additional ports.  Some routers get confused when they think they are
routing even though they can't reach the wan.  And remember to turn off
WiFi unless it is far from your primary router and you want to extend
your WiFi network.

Also, make sure you set the IP address of the router to one on your lan
that's not in use and not in the DHCP range of your primary router.  I
normally use .2 for this purpose.

IANA port ups/401

[Roger Price]

Has any reader of this list ever used IANA port ups/401 "Uninterruptible Power 
Supply" (other than the One Windows Trojan)?  I'm looking for protocol 
documentation or reports of usage. The port was assigned in 2008 to Mr. Charles 
Bennett as both assignee and contact. Mr. Bennett himself died in 2015.


Roger

PS: The NUT package uses port nut/3493 for UPS management.

Re: xsane can't see Brother ADS-2700W scanner

[Hans]

Am Mittwoch, 31. März 2021, 14:23:31 CEST schrieb Eduardo M 
KALINOWSKI:

Hi,

please check in /lib/udev/rules.d/*-libsane1.rules if there is an entry for 
your scanner. In my case with a brother scanner I had to manually add 
it, as the brother packages installation is missing this.

Good luck! 

Best

Hans 

Re: xsane can't see Brother ADS-2700W scanner

[Brian]

On Wed 31 Mar 2021 at 09:23:31 -0300, Eduardo M KALINOWSKI wrote:

> On 30/03/2021 23:24, Charlie Gibbs wrote:
> > The one way I did manage to get the scanner to work was to a
> > USB flash drive.  It quickly sucked in a handful of sheets,
> > scanned both sides, and wrote them to a file on the stick.
> > If all else fails, I can work with it that way.  But I'd
> > really like to let xsane manage the process.
> > 
> Which sane backend are you using?

'scanimage -L' will be informative.
 
> Most new scanners support airscan, so try installing sane-airscan. Note that
> for your scanner to be discovered you need avahi-daemon running. (Or maybe
> you just need avahi-utils).

sane-airscan is a possible solution, and a neat one too, It would be
useful to know the output of

  avahi-browse -rt _uscan._tcp

and which Debian version is in use.

avahi-brows is in the avahi-utils package.

-- 
Brian.

Re: backb losing its mount point

[songbird]

Sharon Kimble wrote:
> Thanks for replying Darac.
...
>> It might be helpful to see the relevant lines from your /etc/fstab.
>>
> - --8<--- current fstab ---start->8---
> /dev/sda2   /mnt/backb  ext4defaults,nofail,x-gvfs-show 0 
> 2
> /dev/sdb2 /mnt/backa  ext4defaults,nofail,x-gvfs-show 0 2
> - --8<---cut here---end--->8---
>
> because the system originally showed this
>
> - --8<--- original fstab ---start->8---
> /dev/sda2   /mnt/backa  ext4defaults,nofail,x-gvfs-show 0 
> 2
> /dev/sdb2 /mnt/backb  ext4defaults,nofail,x-gvfs-show 0 2
> - --8<---cut here---end--->8---
>   
> but for some reason it mounted backb on /dev/sda2 so to regain access I
> changed it to what is currently showing in fstab.

  um, that is a prime example of why UUIDs or LABELS should be used
instead of what you have there because /dev/sdXY names can change 
after a reboot or a device gets disconnected and reconnected.


...

  you can use blkid to give you the UUID and if you've given the
partition/filesystem a LABEL it will also report that.

  update your fstab to use either of those.


  songbird

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Nicholas Geovanis]

On Wed, Mar 31, 2021, 8:08 AM Moritz Kempe 
wrote:

> On 3/31/21 1:55 PM, Lee wrote:
> > On 3/31/21, Moritz Kempe  wrote:
> >> On 3/31/21 1:25 PM, Greg Wooledge wrote:
> >>> On Wed, Mar 31, 2021 at 12:14:59AM +0200, Moritz Kempe wrote:
>  -- Firefox Hmm. We’re having trouble finding that site. We can’t
>  connect to the server at github.com.
>  -- Chromium This site can’t be reachedCheck if there is a typo in
>  github.com. DNS_PROBE_FINISHED_NXDOMAIN
>  moke@rpi4-20201112:~$ host github.com Host github.com not found:
>  2(SERVFAIL)
> >>> grep ^hosts: /etc/nsswitch.conf
> >> --
> >> hosts:  files mdns4_minimal [NOTFOUND=return] dns mymachines
> > I don't trust multicast dns, so in addition to turning it off I've also
> got
> > $ grep host /etc/nsswitch.conf
> > # hosts:  files mdns4_minimal [NOTFOUND=return] dns
> > hosts:  files dns
> >
> > Maybe worth a shot?
>
> Changed my /etc/nsswitch.conf to
>
> --
>
> ..
>
> #hosts:  files mdns4_minimal [NOTFOUND=return] dns mymachines
> hosts:  files dns
> ..
>
> --
>
> and rebooted the system. The behavior hasn't changed.
>
> github.com is still blocked. And dig is still able to find the ip address.
>
> Or do i have done something wrong?
>
>
> I have found out, that i can restore some domains when running
> "/sbin/dhclient" as root but not all. Github is still not accessible.
>

That's why I suggested checking for DHCP messages in the logs. But also
logs upstream from your pi's. Each time you get a DHCP grant, potentially
you've switched DNS servers.

Note: I haven't changed any networking configuration on this device. I
> haven't even enabled wifi.
>
>

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Moritz Kempe]

On 3/31/21 2:44 PM, Greg Wooledge wrote:

On Wed, Mar 31, 2021 at 01:42:36PM +0200, Moritz Kempe wrote:

grep ^hosts: /etc/nsswitch.conf

--
hosts:  files mdns4_minimal [NOTFOUND=return] dns mymachines

I don't know what "mymachines" is.  I don't see it in the man page.

What happens if you get rid of the "mymachines" field?


I have restarted my device with "mymachines" commented out.

It seems like, it behaviors the same.


-rw-r--r-- 1 root root 54 Mar 31 13:28 /etc/resolv.conf
domain fritz.box
search fritz.box
nameserver 10.0.0.1

You're using a local caching resolver, or at least something that
forwards requests.  That's fine, if it works.  You might try probing
the DNS resolver at 10.0.0.1 to see whether it actually does work.


Do you mean like so?

--

moke@rpi4-20201112:~$ dig @10.0.0.1 debian.org

; <<>> DiG 9.16.13-Debian <<>> @10.0.0.1 debian.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13415
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;debian.org.            IN    A

;; ANSWER SECTION:
debian.org.        300    IN    A    149.20.4.15
debian.org.        300    IN    A    130.89.148.77
debian.org.        300    IN    A    128.31.0.62

;; Query time: 351 msec
;; SERVER: 10.0.0.1#53(10.0.0.1)
;; WHEN: Wed Mar 31 15:11:15 CEST 2021
;; MSG SIZE  rcvd: 87
--


(There's a really good chance that 10.0.0.1 is your router, and that
your router implements a forwarding nameserver, which just passes
your requests to your ISP.  These router-based forwarding resolvers
can be a bit flaky sometimes.)

Yes, 10.0.0.1 is my router.

; <<>> DiG 9.16.13-Debian <<>> @8.8.8.8 www.debian.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20269
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.debian.org.            IN    A

;; ANSWER SECTION:
www.debian.org.        229    IN    A 130.89.148.77
www.debian.org.        229    IN    A 149.20.4.15
www.debian.org.        229    IN    A 128.31.0.62

;; Query time: 35 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Mar 31 13:38:10 CEST 2021
;; MSG SIZE  rcvd: 91

That's good.  At least you're not blocking UDP packets or something like
that.  If the weird entry in nsswitch.conf doesn't turn out to be the
problem, and 10.0.0.1 turns out to be non-functional in some way, you
could use Google's resolvers as a fallback.


Yes, i could add a fallback resolver to every device but the advantage 
of the router is, that you can set a dns server for a whole network 
which is a feature i do not want to miss. Also is there still the 
question, why Debian on the Raspberry Pi 400 can't use a dns server, 
which can be used by all other devices.

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Moritz Kempe]

On 3/31/21 1:55 PM, Lee wrote:

On 3/31/21, Moritz Kempe  wrote:

On 3/31/21 1:25 PM, Greg Wooledge wrote:

On Wed, Mar 31, 2021 at 12:14:59AM +0200, Moritz Kempe wrote:

-- Firefox Hmm. We’re having trouble finding that site. We can’t
connect to the server at github.com.
-- Chromium This site can’t be reachedCheck if there is a typo in
github.com. DNS_PROBE_FINISHED_NXDOMAIN
moke@rpi4-20201112:~$ host github.com Host github.com not found:
2(SERVFAIL)

grep ^hosts: /etc/nsswitch.conf

--
hosts:  files mdns4_minimal [NOTFOUND=return] dns mymachines

I don't trust multicast dns, so in addition to turning it off I've also got
$ grep host /etc/nsswitch.conf
# hosts:  files mdns4_minimal [NOTFOUND=return] dns
hosts:  files dns

Maybe worth a shot?


Changed my /etc/nsswitch.conf to

--

..

#hosts:  files mdns4_minimal [NOTFOUND=return] dns mymachines
hosts:  files dns
..

--

and rebooted the system. The behavior hasn't changed.

github.com is still blocked. And dig is still able to find the ip address.

Or do i have done something wrong?


I have found out, that i can restore some domains when running 
"/sbin/dhclient" as root but not all. Github is still not accessible.



Note: I haven't changed any networking configuration on this device. I 
haven't even enabled wifi.

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Greg Wooledge]

On Wed, Mar 31, 2021 at 01:42:36PM +0200, Moritz Kempe wrote:
> > grep ^hosts: /etc/nsswitch.conf
> --
> hosts:  files mdns4_minimal [NOTFOUND=return] dns mymachines

I don't know what "mymachines" is.  I don't see it in the man page.

What happens if you get rid of the "mymachines" field?

> -rw-r--r-- 1 root root 54 Mar 31 13:28 /etc/resolv.conf

> domain fritz.box
> search fritz.box
> nameserver 10.0.0.1

You're using a local caching resolver, or at least something that
forwards requests.  That's fine, if it works.  You might try probing
the DNS resolver at 10.0.0.1 to see whether it actually does work.

(There's a really good chance that 10.0.0.1 is your router, and that
your router implements a forwarding nameserver, which just passes
your requests to your ISP.  These router-based forwarding resolvers
can be a bit flaky sometimes.)

> ; <<>> DiG 9.16.13-Debian <<>> @8.8.8.8 www.debian.org
> ; (1 server found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20269
> ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 512
> ;; QUESTION SECTION:
> ;www.debian.org.            IN    A
> 
> ;; ANSWER SECTION:
> www.debian.org.        229    IN    A 130.89.148.77
> www.debian.org.        229    IN    A 149.20.4.15
> www.debian.org.        229    IN    A 128.31.0.62
> 
> ;; Query time: 35 msec
> ;; SERVER: 8.8.8.8#53(8.8.8.8)
> ;; WHEN: Wed Mar 31 13:38:10 CEST 2021
> ;; MSG SIZE  rcvd: 91

That's good.  At least you're not blocking UDP packets or something like
that.  If the weird entry in nsswitch.conf doesn't turn out to be the
problem, and 10.0.0.1 turns out to be non-functional in some way, you
could use Google's resolvers as a fallback.

Re: xsane can't see Brother ADS-2700W scanner

[Eduardo M KALINOWSKI]

On 30/03/2021 23:24, Charlie Gibbs wrote:

The one way I did manage to get the scanner to work was to a
USB flash drive.  It quickly sucked in a handful of sheets,
scanned both sides, and wrote them to a file on the stick.
If all else fails, I can work with it that way.  But I'd
really like to let xsane manage the process.


Which sane backend are you using?

Most new scanners support airscan, so try installing sane-airscan. Note 
that for your scanner to be discovered you need avahi-daemon running. 
(Or maybe you just need avahi-utils).


Brother generally offers proprietary drivers, including a Sane backend. 
Did you install that?



--
The most disagreeable thing that your worst enemy says to your face does
not approach what your best friends say behind your back.
-- Alfred De Musset

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Lee]

On 3/31/21, Moritz Kempe  wrote:
> On 3/31/21 1:25 PM, Greg Wooledge wrote:
>> On Wed, Mar 31, 2021 at 12:14:59AM +0200, Moritz Kempe wrote:
>>> -- Firefox Hmm. We’re having trouble finding that site. We can’t
>>> connect to the server at github.com.
>>> -- Chromium This site can’t be reachedCheck if there is a typo in
>>> github.com. DNS_PROBE_FINISHED_NXDOMAIN
>>> moke@rpi4-20201112:~$ host github.com Host github.com not found:
>>> 2(SERVFAIL)
>> grep ^hosts: /etc/nsswitch.conf
> --
> hosts:  files mdns4_minimal [NOTFOUND=return] dns mymachines

I don't trust multicast dns, so in addition to turning it off I've also got
$ grep host /etc/nsswitch.conf
# hosts:  files mdns4_minimal [NOTFOUND=return] dns
hosts:  files dns

Maybe worth a shot?

Regards,
Lee

>
> --
>
>
>> ls -ld /etc/resolv.conf
> --
> -rw-r--r-- 1 root root 54 Mar 31 13:28 /etc/resolv.conf
> --
>
>> cat /etc/resolv.conf
> --
> domain fritz.box
> search fritz.box
> nameserver 10.0.0.1
> --
>
>> dig @8.8.8.8 www.debian.org
> --
> ; <<>> DiG 9.16.13-Debian <<>> @8.8.8.8 www.debian.org
> ; (1 server found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20269
> ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 512
> ;; QUESTION SECTION:
> ;www.debian.org.INA
>
> ;; ANSWER SECTION:
> www.debian.org.229INA 130.89.148.77
> www.debian.org.229INA 149.20.4.15
> www.debian.org.229INA 128.31.0.62
>
> ;; Query time: 35 msec
> ;; SERVER: 8.8.8.8#53(8.8.8.8)
> ;; WHEN: Wed Mar 31 13:38:10 CEST 2021
> ;; MSG SIZE  rcvd: 91
>
> --
>
>
> I hope i interpreted your mail in the right way.
>
>

Re: Request: A Debian public Wiki repository/bank for complex code lines with examples, scripts, self-explanatory with terminal, otherwise Minimal explanatory texts

[Dan Ritter]

Susmita/Rajib wrote: 
> 
> 
> The best possible method of learning appears to be minimal
> explanation, but exhaustive implementation of code lines in a
> console/terminal.

While you may think that this is the best way for you to learn
about command lines, most people don't do well this way.

Most people like to read a story: I had this problem, I tried
these things, and this is what worked. That helps them
understand not just the solution, but the process of finding the
solution so that they can someday find their own solutions.

In a freshly-installed Debian system, there are about 1200
commands. Each of these takes between 1 and 50-ish arguments, not
counting the arguments that can be repeated indefinitely. 

If every command can be reasonably combined with 50% of the
other commands, a 2-layer wiki of your design would need 

1200 * 600 = 72 entries

That's quite a project.

When learning a language, we don't compile a list of all
possible sentences and try to look them up; we write primers and
guides to grammar.

-dsr-

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Moritz Kempe]

On 3/31/21 1:25 PM, Greg Wooledge wrote:

On Wed, Mar 31, 2021 at 12:14:59AM +0200, Moritz Kempe wrote:
-- Firefox Hmm. We’re having trouble finding that site. We can’t 
connect to the server at github.com. 
-- Chromium This site can’t be reachedCheck if there is a typo in 
github.com. DNS_PROBE_FINISHED_NXDOMAIN 
moke@rpi4-20201112:~$ host github.com Host github.com not found: 
2(SERVFAIL) 

grep ^hosts: /etc/nsswitch.conf

--
hosts:  files mdns4_minimal [NOTFOUND=return] dns mymachines

--



ls -ld /etc/resolv.conf

--
-rw-r--r-- 1 root root 54 Mar 31 13:28 /etc/resolv.conf
--


cat /etc/resolv.conf

--
domain fritz.box
search fritz.box
nameserver 10.0.0.1
--


dig @8.8.8.8 www.debian.org

--
; <<>> DiG 9.16.13-Debian <<>> @8.8.8.8 www.debian.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20269
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.debian.org.            IN    A

;; ANSWER SECTION:
www.debian.org.        229    IN    A 130.89.148.77
www.debian.org.        229    IN    A 149.20.4.15
www.debian.org.        229    IN    A 128.31.0.62

;; Query time: 35 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Mar 31 13:38:10 CEST 2021
;; MSG SIZE  rcvd: 91

--


I hope i interpreted your mail in the right way.

Re: backb losing its mount point

[Sharon Kimble]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Darac Marjal  writes:

> On 31/03/2021 09:32, Sharon Kimble wrote:
>>
>> I'm hoping that you folks can help me with a problem that is now
>> happening reasonably regularly, actually twice.
>>
>> I have 2 data drives on my system /mnt/backa and /mnt/backb. Both are
>> 4tb drives, with backa being 2.74tb and backb 2.81tb.
>
> It might be helpful to see the relevant lines from your /etc/fstab.
>
>
>>
>> Backb is now regularly losing its mount point when I reboot, meaning
>> that only backa is mounted, and backb holds my restic backup.
>>
>> To regain access to backb I'm having to 'sudo e2fsck -y -b 32768
>> /dev/sdc2' which rebuilds the mount point such that I can mount it on
>> reboot, as backb.
>
> Firstly, it's usually better to run the "fsck" frontend, which will
> determine which filesystem you've got and run the appropriate backend,
> but I can see that you're passing advanced parameters here, so jumping
> straight to e2fsck isn't that unusual.
>
> Secondly, you're specifying "-b 32768" which is telling fsck to use a
> secondary superblock. Why is this? Generally, the primary superblock
> should be "good enough" to repair a filesystem. The man page does state
> that the primary superblock *should* be updated after the fixes are
> complete, so this shouldn't be necessary. So, why are you having to use
> a secondary superblock? Do you know what's wrong with the primary one?
>
>
>>
>> So how do I stop it happening again please? And what is the cause of it
>> all? Should I physically unmount the drives before rebooting?
>
> The answers you seek should already be logged somewhere.  Try the following:
>
> $ journalctl -b -u mnt-backb.mount        # 
> This will show output from
> attempts to mount /mnt/backb since the current bootup
>
> $ journalctl -b -g sdc2                              # This will grep
> the journal for all messages containing "sdc2" since the current bootup
>

Following on from my previous posting -

- --8<---cut here---start->8---
 sudo journalctl -b -g sdc2
[sudo] password for boudiccas: 
- -- Journal begins at Thu 2021-02-18 12:51:54 GMT, ends at Wed 2021-03-31 
12:31:04 BST. --
Mar 31 08:21:47 london kernel:  sdc: sdc1 sdc2 sdc3 sdc4 sdc5 sdc6 sdc7
Mar 31 12:29:51 london sudo[323326]: boudiccas : TTY=pts/28 ; 
PWD=/home/boudiccas ; USER=root ; COMMAND=/usr/bin/journalctl -b -g sdc2
Mar 31 12:31:04 london sudo[437870]: boudiccas : TTY=pts/30 ; 
PWD=/home/boudiccas/.emacs.d/org ; USER=root ; COMMAND=/usr/bin/journalctl -b 
-g sdc2
- --8<---cut here---end--->8---

and also

- --8<---cut here---start->8---
sudo journalctl -b -u /mnt/backb.mount
- -- Journal begins at Thu 2021-02-18 12:51:54 GMT, ends at Wed 2021-03-31 
12:31:50 BST. --
- -- No entries --
- --8<---cut here---end--->8---

and

- --8<---cut here---start->8---
sudo journalctl -b -u mnt-backb.mount
- -- Journal begins at Thu 2021-02-18 12:51:54 GMT, ends at Wed 2021-03-31 
12:36:23 BST. --
Mar 31 08:21:54 london systemd[1]: Mounting /mnt/backb...
Mar 31 08:21:54 london systemd[1]: Mounted /mnt/backb.
- --8<---cut here---end--->8---

Thanks
  Sharon.
- -- 
Debian 10.9, fluxbox 1.3.7, emacs 28.0.50, org 9.4.5
-BEGIN PGP SIGNATURE-

iQJPBAEBCgA5FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmBkXvQbHGJvdWRpY2Nh
c0Bza2ltYmxlLnBsdXMuY29tAAoJEDaBgBkK+INbofUP/iFtIe+2LZhZC3oc5i3W
YV2RrbSBvTBdKfe64hU80cjEVUxErEqLmUGTKiQOFDlQ8ZHX2hJpNSK9XE3P0e3W
vBComrmnkauK6KTxRrUeC+rDE///g5NjRC9zz/l3b9+EmUQ8YM/3Ty68dZAumZzl
MlqYjgx/30GDu45YHj2wW8zbUGUxqJOv5eXwU8Hf8/aEs9awyJbfg7iYFXVMh4OQ
WO9NJC6uafpPLNilbY6HjxPqjeFQiVKVfHMN9uYCJSA6ticCc9e0Zn1m0e+MFOu7
n82quc94NLk3BswUvNjqBlIBPvX5MNmoGJ0SF9NhDCp1YJpdW5Xc96B7QuE4NFZl
a6Kfa5Khx/y3ESShG0MAO/kNOadRw4Ljc05h3YJI2U50vB9Yw9yew3lYBRlGWfOR
ZSWUXyJM7dR9cQNfwhPEHlAEPOzoT45xnG0rZKNwjQHnCSmjjrheSFwpT9TyJNHr
4Me0bVa86L3trjooPbZQJFndhU0NvyKViJ0wQWGFsemE1DRxBu0x19nfcQtfBMip
57PzawFX2RL/oHyWQVnm+MqupnjqUwiKxMctl2aD6HEal8G3TXJfmyXjj9QV6aDB
zRRpZvmSibN05/ByJsdnqPAorjwR+MTrptfgyYHUwMhsH2S3+cJHWtjULi6EsIdS
Hme93jkQZENDw0u9Qt/0woMa
=T1eN
-END PGP SIGNATURE-

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Greg Wooledge]

On Wed, Mar 31, 2021 at 12:14:59AM +0200, Moritz Kempe wrote:
> -- Firefox
> Hmm. We’re having trouble finding that site.
> 
> We can’t connect to the server at github.com.

> -- Chromium
> This site can’t be reachedCheck if there is a typo in github.com.
> DNS_PROBE_FINISHED_NXDOMAIN

> moke@rpi4-20201112:~$ host github.com
> Host github.com not found: 2(SERVFAIL)

grep ^hosts: /etc/nsswitch.conf
ls -ld /etc/resolv.conf
cat /etc/resolv.conf
dig @8.8.8.8 www.debian.org

Re: xsane can't see Brother ADS-2700W scanner

[Dan Ritter]

Charlie Gibbs wrote: 
> 
> I'm beginning to wonder, though, whether fashions are changing.
> Scanners nowadays seem to want to push data to a server, rather
> than being commanded to scan by a computer.  Is this really
> happening?  If so, whither (or should that be "wither") xsane?

In office environments, with shared resources, this is often
preferable. Having the scanner drop everything into a
samba-shared filesystem, for example...

-dsr-

Re: Temporary failure in name resolution

[Moritz Kempe]

I am experiencing a potential related issue, (Subject: DNS problems on 
Raspberry Pi 400 (Debian 10.9)" on this list)


can you please install dnsutils (sudo apt-get install dnsutils)

and try to use dig to get an ip from a domain and send us your output?

Because if i try to use host it returns

-- host github.com
Host github.com not found: 2(SERVFAIL)
--

But dig is able to get the ip

-- dig github.com
; <<>> DiG 9.16.13-Debian <<>> github.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32657
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;github.com.            IN    A

;; ANSWER SECTION:
github.com.        27    IN    A    140.82.121.3

;; Query time: 459 msec
;; SERVER: 10.0.0.1#53(10.0.0.1)
;; WHEN: Wed Mar 31 13:04:57 CEST 2021
;; MSG SIZE  rcvd: 55
--


Kind Regards

Moritz Kempe

Re: Request: A Debian public Wiki repository/bank for complex code lines with examples, scripts, self-explanatory with terminal, otherwise Minimal explanatory texts

[Susmita/Rajib]

On Wed, 31 Mar 2021 11:15:13 +0100, Darac Marjal
 wrote:
> To: debian-user@lists.debian.org
[...]
> Message-id: <[] 258050bc-618b-e8ae-6a93-fc4483c42...@darac.org.uk>
> In-reply-to: <[]
> CAEG4cZVHeUrD5Ke1iMd_MLSXuw6j8+k+AhEteKfYoQPO2v=m...@mail.gmail.com>
> References:
> 
> 
> 
> <[] CAEG4cZVHeUrD5Ke1iMd_MLSXuw6j8+k+AhEteKfYoQPO2v=m...@mail.gmail.com>


[...]
> This sounds quite similar to https://tldr.sh

:-) Shouldn't an excellent coder/scripter also contemplate, try to
step back to form a holistic picture, a Bird's Eye View? Especially,
when attention and admiration have already been drawn?

Shouldn't also mailbox be checked?

Re: backb losing its mount point

[Sharon Kimble]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Darac Marjal  writes:

Thanks for replying Darac.
  
> On 31/03/2021 09:32, Sharon Kimble wrote:
>>
>> I'm hoping that you folks can help me with a problem that is now
>> happening reasonably regularly, actually twice.
>>
>> I have 2 data drives on my system /mnt/backa and /mnt/backb. Both are
>> 4tb drives, with backa being 2.74tb and backb 2.81tb.
>
> It might be helpful to see the relevant lines from your /etc/fstab.
>
- --8<--- current fstab ---start->8---
/dev/sda2   /mnt/backb  ext4defaults,nofail,x-gvfs-show 0 2
/dev/sdb2   /mnt/backa  ext4defaults,nofail,x-gvfs-show 0 2
- --8<---cut here---end--->8---

because the system originally showed this

- --8<--- original fstab ---start->8---
/dev/sda2   /mnt/backa  ext4defaults,nofail,x-gvfs-show 0 2
/dev/sdb2   /mnt/backb  ext4defaults,nofail,x-gvfs-show 0 2
- --8<---cut here---end--->8---
  
but for some reason it mounted backb on /dev/sda2 so to regain access I
changed it to what is currently showing in fstab.
  
>
>>
>> Backb is now regularly losing its mount point when I reboot, meaning
>> that only backa is mounted, and backb holds my restic backup.
>>
>> To regain access to backb I'm having to 'sudo e2fsck -y -b 32768
>> /dev/sdc2' which rebuilds the mount point such that I can mount it on
>> reboot, as backb.
>
> Firstly, it's usually better to run the "fsck" frontend, which will
> determine which filesystem you've got and run the appropriate backend,
> but I can see that you're passing advanced parameters here, so jumping
> straight to e2fsck isn't that unusual.
>
> Secondly, you're specifying "-b 32768" which is telling fsck to use a
> secondary superblock. Why is this? Generally, the primary superblock
> should be "good enough" to repair a filesystem. The man page does state
> that the primary superblock *should* be updated after the fixes are
> complete, so this shouldn't be necessary. So, why are you having to use
> a secondary superblock? Do you know what's wrong with the primary one?
>
When the problem originally occurred this is what i did

- --8<---cut here---start->8---
 2184  2021-03-18 13:32:51 sudo mount /mnt/backb
 2185  2021-03-18 13:39:33 mount
 2186  2021-03-18 13:43:32 fdisk -l
 2187  2021-03-18 13:43:46 sudo fdisk -l
 2188  2021-03-18 13:48:05 sudo lshw 
 2189  2021-03-18 13:54:04 sudo fdisk /dev/sdc
2192  2021-03-18 14:10:04 sudo mount /mnt/backb
 2193  2021-03-18 14:11:58 sudo fsck /mnt/backb
 2194  2021-03-18 14:12:48 sudo e2fsck -b 32768 /mnt/backb
 2195  2021-03-18 14:13:10 sudo e2fsck -b 32768 /dev/sdc
 2196  2021-03-18 14:13:58 sudo e2fsck -b 8193 /dev/sdc
 2197  2021-03-18 14:18:46 sudo mke2fs -n /dev/sdc2
 2198  2021-03-18 14:19:16 sudo mke4fs -n /dev/sdc2
 2199  2021-03-18 14:19:54 sudo mke2fs -n /dev/sdc2
2202  2021-03-18 14:02:17 glances
 2203  2021-03-18 14:19:33 man mke2fs
 2204  2021-03-18 13:54:51 sudo fdisk /dev/sdc2
 2205  2021-03-18 13:31:11 sudo gparted
2210  2021-03-18 14:32:49 sudo mke2fs -n /dev/sdc2
 2211  2021-03-18 14:34:32 sudo e2fsck
 2212  2021-03-18 14:35:14 sudo e2fsck p
 2213  2021-03-18 14:35:31 sudo e2fsck /dev/sdc -p
 2214  2021-03-18 14:29:51 sudo gparted
 2215  2021-03-18 14:36:28 sudo e2fsck -b 32768 /dev/sdc2
 2216  2021-03-18 14:45:56 man e2fsck
 2217  2021-03-18 14:46:38 sudo e2fsck -y -b 32768 /dev/sdc2
- --8<---cut here---end--->8---
  

>
>>
>> So how do I stop it happening again please? And what is the cause of it
>> all? Should I physically unmount the drives before rebooting?
>
> The answers you seek should already be logged somewhere.  Try the following:
>
> $ journalctl -b -u mnt-backb.mount        # 
> This will show output from
> attempts to mount /mnt/backb since the current bootup

- --8<---cut here---start->8---
journalctl -b -u mnt-backb.mount
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.
  Pass -q to turn off this notice.
- -- Journal begins at Wed 2021-02-24 17:51:13 GMT, ends at Wed 2021-03-31 
11:08:09 BST. --
- -- No entries --
- --8<---cut here---end--->8---


  
>
> $ journalctl -b -g sdc2                              # This will grep
> the journal for all messages containing "sdc2" since the current bootup
>

- --8<---cut here---start->8---
journalctl -b -g sdc2
Hint: You are currently not seeing messages from other users and the system.
  Users in groups 'adm', 'systemd-journal' can see all messages.
  Pass -q to turn off this notice.
- -- Journal begins at Wed 2021-02-24 17:51:13 GMT, ends at Wed 2021-03-31 

Re: Request: A Debian public Wiki repository/bank for complex code lines with examples, scripts, self-explanatory with terminal, otherwise Minimal explanatory texts

[Darac Marjal]

On 31/03/2021 10:46, Susmita/Rajib wrote:
> Follow Up from https://lists.debian.org/debian-user/2021/03/msg01459.html,
>
> Motivation:
> https://lists.debian.org/debian-user/2021/03/msg01358.html
> https://lists.debian.org/debian-user/2021/03/msg01362.html
> https://lists.debian.org/debian-user/2021/03/msg01365.html
> https://lists.debian.org/debian-user/2021/03/msg01435.html
>
>
>
> Wiki is not only about wikipedia,
>
> Word wiki to signify a collaborative effort in stockpiling code
> lines (Section 2 to be referred to, for elaboration). With minimal
> explanation. Only lines of codes (more in Section 2).

This sounds quite similar to https://tldr.sh

[cut]



OpenPGP_signature
Description: OpenPGP digital signature

Request: A Debian public Wiki repository/bank for complex code lines with examples, scripts, self-explanatory with terminal, otherwise Minimal explanatory texts

[Susmita/Rajib]

Follow Up from https://lists.debian.org/debian-user/2021/03/msg01459.html,

Motivation:
https://lists.debian.org/debian-user/2021/03/msg01358.html
https://lists.debian.org/debian-user/2021/03/msg01362.html
https://lists.debian.org/debian-user/2021/03/msg01365.html
https://lists.debian.org/debian-user/2021/03/msg01435.html



Wiki is not only about wikipedia,

Word wiki to signify a collaborative effort in stockpiling code
lines (Section 2 to be referred to, for elaboration). With minimal
explanation. Only lines of codes (more in Section 2).

The best possible method of learning appears to be minimal
explanation, but exhaustive implementation of code lines in a
console/terminal.

Let (!@#$%) be replaced by the following phrase without [quote], [/quote].

[quote] with a list of all possible permutations / combinations
(henceforth, abbreviated as PC) [of options, switches, RegEx, et al,]
of basic, single code lines. List. Only. Minimal explanation. The
console shall self-explain through output.[/quote]

Section 2

The wiki would be one page for one Man Command
(internal/external). But radically different from Man Page. Minimal(or
zero) explanatory texts (!@#$%)

Then an Upper Tier of wiki page having unique combination of two
commands (internal/external) with (!@#$%)

Then a still Upper Tier of wiki page having unique combination of
three commands (internal/external) with (!@#$%)

But we could stop at some Tier until further need for complexity arises.

Books (or online bash scripting pages) are considered horrible, in the
matter of wastage of time. For coding a different set of NeuNet are
developed for abstract multi-dimensional memory space, while our
intellect tries all sorts of possible PC of each sector of this memory
space(MS) and could redefine/reorganise/compress this MS. Books
address filling up this MS inefficiently. It also causes so much
wastage of paper for so little purpose.

In order for Debian books to explain things to us, our wiki should
have specific line, section, page reference for any unique single line
of code.

Then books could be compressed to a minimal size. Wiki could be
expanded, if required.

Re: backb losing its mount point

[Darac Marjal]

On 31/03/2021 09:32, Sharon Kimble wrote:
>
> I'm hoping that you folks can help me with a problem that is now
> happening reasonably regularly, actually twice.
>
> I have 2 data drives on my system /mnt/backa and /mnt/backb. Both are
> 4tb drives, with backa being 2.74tb and backb 2.81tb.

It might be helpful to see the relevant lines from your /etc/fstab.


>
> Backb is now regularly losing its mount point when I reboot, meaning
> that only backa is mounted, and backb holds my restic backup.
>
> To regain access to backb I'm having to 'sudo e2fsck -y -b 32768
> /dev/sdc2' which rebuilds the mount point such that I can mount it on
> reboot, as backb.

Firstly, it's usually better to run the "fsck" frontend, which will
determine which filesystem you've got and run the appropriate backend,
but I can see that you're passing advanced parameters here, so jumping
straight to e2fsck isn't that unusual.

Secondly, you're specifying "-b 32768" which is telling fsck to use a
secondary superblock. Why is this? Generally, the primary superblock
should be "good enough" to repair a filesystem. The man page does state
that the primary superblock *should* be updated after the fixes are
complete, so this shouldn't be necessary. So, why are you having to use
a secondary superblock? Do you know what's wrong with the primary one?


>
> So how do I stop it happening again please? And what is the cause of it
> all? Should I physically unmount the drives before rebooting?

The answers you seek should already be logged somewhere.  Try the following:

$ journalctl -b -u mnt-backb.mount        # 
This will show output from
attempts to mount /mnt/backb since the current bootup

$ journalctl -b -g sdc2                              # This will grep
the journal for all messages containing "sdc2" since the current bootup


>
> Thanks
>   Sharon.
>




OpenPGP_signature
Description: OpenPGP digital signature

backb losing its mount point

[Sharon Kimble]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


I'm hoping that you folks can help me with a problem that is now
happening reasonably regularly, actually twice.

I have 2 data drives on my system /mnt/backa and /mnt/backb. Both are
4tb drives, with backa being 2.74tb and backb 2.81tb.

Backb is now regularly losing its mount point when I reboot, meaning
that only backa is mounted, and backb holds my restic backup.

To regain access to backb I'm having to 'sudo e2fsck -y -b 32768
/dev/sdc2' which rebuilds the mount point such that I can mount it on
reboot, as backb.

So how do I stop it happening again please? And what is the cause of it
all? Should I physically unmount the drives before rebooting?

Thanks
  Sharon.
- -- 
Debian 10.9, fluxbox 1.3.7, emacs 28.0.50, org 9.4.5
-BEGIN PGP SIGNATURE-

iQJPBAEBCgA5FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmBkM4YbHGJvdWRpY2Nh
c0Bza2ltYmxlLnBsdXMuY29tAAoJEDaBgBkK+INbUBUQAKwLJ8YF6/Bw13MKQqwZ
peDg6r7fnxXSQ4NrknjYEgSh51p9uOyY23klVYb9jSNTyKLh0XAudnq/Gv1EjVy4
7IEDl6vfSqKd+x3nPJJvsBQ9+AilOcb0PXJo2vARyuRl99y4OBFuVY+A7nNLG1Y4
lp6Sn5JvAEMf77z0mr9yDKHggg8Mdd0LGCP8L+TYEaNU3CQmVHQvQ32UQ4xnNdTv
k2jj1swMigasR8WwmZibN7m4b03OUcSpe5kH1sH/twdUHIoNzDKyIDx5ExsOfpwe
kMNrU8i9Iq+XcSLTUIZcJa7VOeIJJQ33rLRr3tLULsA/5uXlKS5PEuqI6lY/oiRD
FF1EfNnkWVrh7W2RUzXz0CbI/5UhIg+V1DvThtdQBu3nwTqmu3Ya+Os3gEYlPK/6
3WP2/Acyiq3miUVqrFvg49X2zh+as53bOwVhaCfCO6jG4MOXY+F+AZBlx1YoNlNu
YfeCakYDfk0dr5fUqs91nR554FRpPTz21MqFBP7L4FtQ9frIYRMRJuYfETEG9LM/
/hyeTP6hftUr2+W/jBU9np6VqriLMRv0qltpYLD/IQPCIz4fjDIs9KFiqAd0uaiQ
dgnjsaXyq96wp98J9dn9deZk8FyRSjMUhsxJfMn+I/YVPrHhX/xXm9nGRJEajLOD
PHcDi1mhmNKg0p7o651VclyP
=WT1I
-END PGP SIGNATURE-

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Moritz Kempe]

Am 31.03.21 um 09:23 schrieb Klaus Singvogel:

Moritz Kempe wrote:
[...]

I noticed the problem, while i was browsing the internet and got confused
because after a while some domains could not longer be found/connected to by
the browser. (On both, Firefox and Chromium)

I had similar issues, when I changed DNS configuration at my DSL router.

I enabled on my DSL router: TLS for DNS, and, parallel, switched to
public, non-censored DNS servers, as suggested by a large German computer
magazine.
I've done this too. I also activated dns over tls with a privacy dns 
server in my router but i haven't mentioned it because it, doesn't 
seemed like there was any connection between these changes. On all other 
devices this works just fine. And even when i change my dns server to 
the default one, the raspberry pi still has these problems. (I tested 
this before i wrote the first mail)

Those DNS servers were independent and respect more privacy, compared to
my ISP. But after a while I noticed, that those public DNS servers drop
requests and I saw your error messages at my side too, especially if there
were a lot of name resolutions in a short time period.


On my raspberry pi 400, this could be the case, but on my Debian Stretch 
PC it works just fine.


I do experience these issues only on my raspberry pi 400, with both of 
my operating systems.



Those errors vanished after a while (several minutes) and everything
worked as expected. But then, when resolving again a lot of domain names,
the issues were back. Especially when I download from S3 Amazon, because
the IP address for s3.[...].amazon.com changes every 10 seconds or so.


On my raspberry pi 400 they occurre and rarely fix themselves but the 
majority of these stays up for all eternity (or up to an shutdown).
It don't feels, like you described, it is more like an blocklist which 
is getting longer and longer (and forces me to use google when my 
favorite search engines are blocked).



Don't know, if both are related.

But my suggestion is to look at your DSL router: if you changed the
defaults for DNS, and, if so, switch back to original, default setting for
testing purpose.
I switched my routers dns server back to the ISPs and also rebootet my 
device.
But i wasn't able to get on github.com but at the same time i was able 
to get on the by the (German) CUII (Clearingstelle Urheberrecht im 
Internet) censored site s.to [0] which shouldn't be accessible because 
of the censoring from my ISP.

This worked with both my browsers, firefox and chromium.


Regards,
Klaus.


[0] i do not encourage anyone to watch (illegal) content on s.to, i only 
chose this domain to test if i am able to visit censored websites.

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Moritz Kempe]

Am 31.03.21 um 09:23 schrieb Klaus Singvogel:

Moritz Kempe wrote:
[...]

I noticed the problem, while i was browsing the internet and got confused
because after a while some domains could not longer be found/connected to by
the browser. (On both, Firefox and Chromium)

I had similar issues, when I changed DNS configuration at my DSL router.

I enabled on my DSL router: TLS for DNS, and, parallel, switched to
public, non-censored DNS servers, as suggested by a large German computer
magazine.
I've done this too. I also activated dns over tls with a privacy dns 
server in my router but i haven't mentioned it because it, doesn't 
seemed like there was any connection between these changes. On all other 
devices this works just fine. And even when i change my dns server to 
the default one, the raspberry pi still has these problems. (I tested 
this before i wrote the first mail)

Those DNS servers were independent and respect more privacy, compared to
my ISP. But after a while I noticed, that those public DNS servers drop
requests and I saw your error messages at my side too, especially if there
were a lot of name resolutions in a short time period.


On my raspberry pi 400, this could be the case, but on my Debian Stretch 
PC it works just fine.


I do experience these issues only on my raspberry pi 400, with both of 
my operating systems.



Those errors vanished after a while (several minutes) and everything
worked as expected. But then, when resolving again a lot of domain names,
the issues were back. Especially when I download from S3 Amazon, because
the IP address for s3.[...].amazon.com changes every 10 seconds or so.


On my raspberry pi 400 they occurre and rarely fix themselves but the 
majority of these stays up for all eternity (or up to an shutdown).
It don't feels, like you described, it is more like an blocklist which 
is getting longer and longer (and forces me to use google when my 
favorite search engines are blocked).



Don't know, if both are related.

But my suggestion is to look at your DSL router: if you changed the
defaults for DNS, and, if so, switch back to original, default setting for
testing purpose.
I switched my routers dns server back to the ISPs and also rebootet my 
device.
But i wasn't able to get on github.com but at the same time i was able 
to get on the by the (German) CUII (Clearingstelle Urheberrecht im 
Internet) censored site s.to [0] which shouldn't be accessible because 
of the censoring from my ISP.

This worked with both my browsers, firefox and chromium.


Regards,
Klaus.


[0] i do not encourage anyone to watch (illegal) content on s.to, i only 
chose this domain to test if i am able to visit censored websites.

Re: DNS problems on Raspberry Pi 400 (Debian 10.9)

[Klaus Singvogel]

Moritz Kempe wrote:
[...]
> I noticed the problem, while i was browsing the internet and got confused
> because after a while some domains could not longer be found/connected to by
> the browser. (On both, Firefox and Chromium)

I had similar issues, when I changed DNS configuration at my DSL router.

I enabled on my DSL router: TLS for DNS, and, parallel, switched to
public, non-censored DNS servers, as suggested by a large German computer
magazine.

Those DNS servers were independent and respect more privacy, compared to
my ISP. But after a while I noticed, that those public DNS servers drop
requests and I saw your error messages at my side too, especially if there
were a lot of name resolutions in a short time period.

Those errors vanished after a while (several minutes) and everything
worked as expected. But then, when resolving again a lot of domain names,
the issues were back. Especially when I download from S3 Amazon, because
the IP address for s3.[...].amazon.com changes every 10 seconds or so.

Don't know, if both are related.

But my suggestion is to look at your DSL router: if you changed the
defaults for DNS, and, if so, switch back to original, default setting for
testing purpose.

Regards,
Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

Re: probleme unsquash

[didier gaumet]

D'une manière générale je trouve que, au moins par le passé, les médias 
Live présentent plus de problèmes et moins de flexibilité d'installation 
que les médias purement dédiés à l'installation, et encore plus dans le 
cas de Debian.


Ton problème pourrait être causé par un téléchargement corrompu du média 
(as-tu vérifié une somme de contrôle?) et un nouveau téléchargement 
pourrait le solutionner. ça pourrait aussi être dû à l'utilisation d'un 
outil du genre d'Unetbootin pour créer la clé USB. Ou à un défaut dans 
les nouvelles images 10.9. Mais de toutes façons j'aurais tendance à te 
conseiller d'utiliser un vrai média d'installation plutôt qu'un media 
live pour installer

Re: Temporary failure in name resolution

[john doe]

On 3/31/2021 4:21 AM, Dan Norton wrote:

After the 10.9 upgrade, name resolution is not working for me. Does anyone else 
see this?

My desktop is a wifi server for laptop access using windows. That works OK but 
the server, attached by ethernet to the DSL modem does not get names resolved 
since the upgrade. The resolvconf program is not


With a desktop environment (Mate/Gnome...)?

installed according to whereis.


# cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 192.168.1.254

If that's not the right nameserver then what is?


IS the DNS serverat 192.168.1.254 working?



$ ping google.com
ping: google.com: Temporary failure in name resolution

$ ping -c2 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=21.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=21.2 ms

--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 2ms
rtt min/avg/max/mdev = 21.148/21.188/21.229/0.151 ms



Are those pings done on the server or on the clients?


# systemctl status systemd-resolved
shows it being active and "Processing requests...".
>
Nothing in history.log and term.log is obviously wrong to me FWIW.

# journalctl -b0
gives no clue to me.

No doubt it is something simple(tm). Where should I look or what should I 
re-read?

  - Dan Norton



Did you do a 'systemctl reboot' to restart the server?

--
John Doe

Re: Creating my first LAN

[Anssi Saari]

Brian  writes:

> Ten minutes after writing that I recollected I possess a non-working
> router. It is the first I bought (> 100 GBP) and has not yet beem
> re-cycled.
>
> My network also hasn't any spare LAN ports to connect to and some of
> the devices have beem wireless-enabled to communicate with them.
>
> Now - could I use this non-internet-capable router as a switch?

Probably. Usually LAN ports on a router are setup as a switch. The
router may have a DHCP server running though which you may want to
disable.

Re: Temporary failure in name resolution

[David Christensen]

On 3/30/21 7:21 PM, Dan Norton wrote:

After the 10.9 upgrade, name resolution is not working for me. Does anyone else 
see this?

My desktop is a wifi server for laptop access using windows. That works OK but 
the server, attached by ethernet to the DSL modem does not get names resolved 
since the upgrade. The resolvconf program is not installed according to whereis.

# cat /etc/resolv.conf
domain attlocal.net
search attlocal.net
nameserver 192.168.1.254



Have you done a cold reboot since upgrading Debian?


Do the following commands indicate everything is up to date?

# apt-get update

# apt-get upgrade


Have you changed any of the gateway settings recently?


Please verify that the DNS proxy server on the gateway is working by 
testing name resolution with another computer.



I have a ~2007 Dell Inspiron E1505 laptop with Debian 10:

2021-03-30 22:29:53 dpchrist@dipsy ~
$ cat /etc/debian_version ; uname -a
10.9
Linux dipsy 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 
GNU/Linux



I have AT U-verse residential VDSL service.  When I connect the E1505 
to the gateway via Ethernet and DHCP:


2021-03-30 22:47:40 root@dipsy ~
# ifconfig eth0
eth0: flags=4163  mtu 1500
inet 192.168.1.149  netmask 255.255.255.0  broadcast 192.168.1.255
inet6 :::::  prefixlen 64  scopeid 0x20
inet6 2600:170*::::::  prefixlen 64 
scopeid 0x0

ether **:**:**:**:**:**  txqueuelen 1000  (Ethernet)
RX packets 11184  bytes 935656 (913.7 KiB)
RX errors 0  dropped 41  overruns 0  frame 0
TX packets 1911  bytes 24 (249.5 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 17

2021-03-30 22:48:19 root@dipsy ~
# cat /etc/resolv.conf
# Generated by NetworkManager
search attlocal.net
nameserver 192.168.1.254
nameserver 2600:170*::::1


Both IPv4 and IPv6 "nameserver" addresses correspond to the LAN side of 
the gateway.  ('*' is for redacted characters.)




If that's not the right nameserver then what is?

$ ping google.com
ping: google.com: Temporary failure in name resolution

$ ping -c2 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=21.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=21.2 ms

--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 2ms
rtt min/avg/max/mdev = 21.148/21.188/21.229/0.151 ms

# systemctl status systemd-resolved
shows it being active and "Processing requests...".

Nothing in history.log and term.log is obviously wrong to me FWIW.

# journalctl -b0
gives no clue to me.

No doubt it is something simple(tm). Where should I look or what should I 
re-read?



Please run the following commands.  Use Ctrl+C to interrupt any commands 
that hang.  Reply with your complete console session -- prompts, 
keystrokes entered, and output displayed.  Redact as desired:


$ cat /etc/debian_version ; uname -a

$ ping -c 3 192.168.1.254

$ nmcli g status

$ nmcli c show

$ nmcli d show

$ host -v -t A www.debian.org 8.8.8.8

$ host -v -t A www.debian.org


David

probleme unsquash

[k6dedijon]

Bonjour,
Suite à un problème, je suis amené à réinstaller ma Debian 10.
J'ai pris l'image : debian-live-10.9.0-amd64-kde.iso
L'installation avorte sur un message disant que unsquash n'est pas installé.
Que faire ?
Merci pour vos réponses
Cassis