Re: Temporary failure in name resolution
On 3/31/21 1:33 PM, David Christensen wrote: $ host -v -t A www.debian.org 192.168.1.254 Dan -- did you run the above test? This may help isolate if the problem is Debian 10 or your AT&T gateway. David
Re: Temporary failure in name resolution
On Fri, Apr 02, 2021 at 10:48:09PM -0400, Dan Norton wrote: > # cat /etc/resolv.conf > domain attlocal.net > search attlocal.net > nameserver 1.1.1.1 > nameserver 1.0.0.1 > ...and this works very well. I like it because it cuts out more > of google's monitoring of my browsing (I use Brave browser and > DuckDuckGo). > > Now what about the first two lines? What purpose? Can I cut out AT&T > also? ;) man resolv.conf search Search list for host-name lookup. By default, the search list contains one entry, the local domain name. It is determined from the local hostname returned by gethostname(2); the local domain name is taken to be everything after the first '.'. Finally, if the hostname does not contain a '.', the root domain is assumed as the local domain name. [...] The domain directive is an obsolete name for the search direc‐ tive that handles one search list entry only. Those lines do nothing, unless you routinely type commands like "ssh lemon" or "ping pineapple" with no dots in the hostname. In that case, assuming the hosts are not defined in /etc/hosts, the resolver will try to look up "lemon.attlocal.net" or "pineapple.attlocal.net" or whatever. Remember that something will probably overwrite your changes to the resolv.conf file, unless you take preemptive steps.
Re: Temporary failure in name resolution
Alexander V. Makartsev on Sat, 3 Apr 2021 01:17:59 +0500 wrote: "On 02.04.2021 22:56, Dan Norton wrote: Alexander V. Makartsev wrote Wed, 31 Mar 2021 10:16:08 +0500: "Is "192.168.1.254" an IP address of your DSL modem? If you don't need to resolve hostnames from you local network, like "somepc1.attlocal.net" and only want to access the Internet, you can configure one or more of the public DNS servers. From Google [1]: 8.8.8.8 8.8.4.4 >From CloudFlare [2]: 1.1.1.1" I don't know. I did not put that line in /etc/resolv.conf. When I get more time I may remove it and see what happens. If you didn't put that line in /etc/resolv.conf, then probably it was configured by DHCP client, which used the information send by your DSL modem. That would explain "attlocal.net" lines. Do you have administrative access to your DSL modem's configuration web interface? Or is it a leased device that was configured by your ISP and you don't have the option to configure it?" The modem is leased from my ISP. It was installed by an AT&T employee contracted by the ISP. It's possible he configured it but I don't know. Alexander also said: "If you have the access to DSL modem, you can configure its DHCP server to always send proper DNS server addresses, like "1.1.1.1", "8.8.8.8", instead of "192.168.1.254". Alternatively, and if you don't have the access to DSL modem, you can modify "dhclient.conf" file to effectively override name server addresses sent by your modem with known good ones. This procedure is described in Debian Wiki. [1] Basically, all you have to do is add at the end of the file this string: supersede domain-name-servers 1.1.1.1,1.0.0.1,8.8.8.8,8.8.4.4;" After looking at dhclient.conf and reading the comments, I decided to leave dhclient.conf alone remove the line: nameserver 192.168.1.254 from resolv.conf so that now: # cat /etc/resolv.conf domain attlocal.net search attlocal.net nameserver 1.1.1.1 nameserver 1.0.0.1 ...and this works very well. I like it because it cuts out more of google's monitoring of my browsing (I use Brave browser and DuckDuckGo). Now what about the first two lines? What purpose? Can I cut out AT&T also? ;) - Dan
Re: Temporary failure in name resolution
On Fri, Apr 02, 2021 at 05:36:51PM -0400, rhkra...@gmail.com wrote: > On Friday, April 02, 2021 04:35:58 PM Greg Wooledge wrote: > > >2) would the caching feature be bypassed if your computer used the > > >public > > > > > > DNS name servers (e.g., 8.8.8.8, 8.8.4.4, and 1.1.1.1)? (Or if they were > > > listed before the modem IP address?) > > > > You would be using the cached results stored by those external > > nameservers. Those are *extremely* popular nameservers, so one may > > assume they will have basically the entire Internet namespace cached > > most of the time. > > Thanks! > > I guess I phrased my question poorly -- I wondered if that would bypass the > cache (if present) in the DSL modem? Yes. You would not be talking to the router's nameserver at all. Home router DNS services tend to be mediocre at best, and usually they simply forward your requests to your ISP's nameservers, and *those* tend to be problematic at times too (depending on the ISP). That's two layers of questionable things to worry about. That's why multiple people have suggested editing your resolv.conf, to stop using the router's nameserver which seems to be causing (or at least contributing to) the problem. If you don't want to use Google's or Cloudflare's public nameservers, you can always run your own. There are several different caching recursive nameserver packages available in Debian. Pick one, install it, put "nameserver 127.0.0.1" in your resolv.conf, and you're all set... until your DHCP client overwrites your changes. That's when you use one of the wiki's suggestions for how to keep your changes intact.
Re: Temporary failure in name resolution
On Friday, April 02, 2021 05:15:55 PM Alexander V. Makartsev wrote: > On 03.04.2021 01:15, rhkra...@gmail.com wrote: > > Sort of building on this question, and just trying to educate myself, if > > the > > > > DSL modem had a caching nameserver: > > 1) would your computer need to specify the IP of that modem > > (presumably) > > > > 192.168.1.254 to take advantage of the caching? > > Most of SOHO class routers\modems don't offer fully-fledged DNS server > and domain name caching features. > They act as relays, simply redirecting DNS requests to the nearest > configured domain name server. > But if some device offers such features like domain name caching, then > yes, you will have to specify the IP of that device to take advantage of > the caching. Ahh, ok, good, thanks (that answers my question). > > 2) would the caching feature be bypassed if your computer used the > > public > > > > DNS name servers (e.g., 8.8.8.8, 8.8.4.4, and 1.1.1.1)? (Or if they were > > listed before the modem IP address?) > > Yes, it would be bypassed since you asking completely different domain > name server to resolve your DNS requests. Ahh, ok, good, thanks (that answers my question). > An example: If you have a local network with a several hosts and want to > address these hosts by their domain names, > you will have to setup local domain name server which will resolve local > domain name requests and redirect non-local domain ones. > In this case, you will have to specify only one IP address of that local > DNS, because public domain name servers don't know anything about host > names in your local domain.
Re: Temporary failure in name resolution
On Friday, April 02, 2021 04:35:58 PM Greg Wooledge wrote: > On Fri, Apr 02, 2021 at 04:15:07PM -0400, rhkra...@gmail.com wrote: > > Sort of building on this question, and just trying to educate myself, if > > the > > > > DSL modem had a caching nameserver: > >1) would your computer need to specify the IP of that modem > >(presumably) > > > > 192.168.1.254 to take advantage of the caching? > > Regardless of whether the router's nameserver is forward-only or caching, > you would still need to put its IP address in the resolv.conf file of > each client that intends to use it. Normally this is done by advertising > it via DHCP. > > >2) would the caching feature be bypassed if your computer used the > >public > > > > DNS name servers (e.g., 8.8.8.8, 8.8.4.4, and 1.1.1.1)? (Or if they were > > listed before the modem IP address?) > > You would be using the cached results stored by those external > nameservers. Those are *extremely* popular nameservers, so one may > assume they will have basically the entire Internet namespace cached > most of the time. Thanks! I guess I phrased my question poorly -- I wondered if that would bypass the cache (if present) in the DSL modem?
Re: Temporary failure in name resolution
On 03.04.2021 01:15, rhkra...@gmail.com wrote: Sort of building on this question, and just trying to educate myself, if the DSL modem had a caching nameserver: 1) would your computer need to specify the IP of that modem (presumably) 192.168.1.254 to take advantage of the caching? Most of SOHO class routers\modems don't offer fully-fledged DNS server and domain name caching features. They act as relays, simply redirecting DNS requests to the nearest configured domain name server. But if some device offers such features like domain name caching, then yes, you will have to specify the IP of that device to take advantage of the caching. 2) would the caching feature be bypassed if your computer used the public DNS name servers (e.g., 8.8.8.8, 8.8.4.4, and 1.1.1.1)? (Or if they were listed before the modem IP address?) Yes, it would be bypassed since you asking completely different domain name server to resolve your DNS requests. An example: If you have a local network with a several hosts and want to address these hosts by their domain names, you will have to setup local domain name server which will resolve local domain name requests and redirect non-local domain ones. In this case, you will have to specify only one IP address of that local DNS, because public domain name servers don't know anything about host names in your local domain. -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: Temporary failure in name resolution
On Fri, Apr 02, 2021 at 04:15:07PM -0400, rhkra...@gmail.com wrote: > Sort of building on this question, and just trying to educate myself, if the > DSL modem had a caching nameserver: > >1) would your computer need to specify the IP of that modem (presumably) > 192.168.1.254 to take advantage of the caching? Regardless of whether the router's nameserver is forward-only or caching, you would still need to put its IP address in the resolv.conf file of each client that intends to use it. Normally this is done by advertising it via DHCP. >2) would the caching feature be bypassed if your computer used the public > DNS name servers (e.g., 8.8.8.8, 8.8.4.4, and 1.1.1.1)? (Or if they were > listed before the modem IP address?) You would be using the cached results stored by those external nameservers. Those are *extremely* popular nameservers, so one may assume they will have basically the entire Internet namespace cached most of the time.
Re: Temporary failure in name resolution
On 02.04.2021 22:56, Dan Norton wrote: Alexander V. Makartsev wrote Wed, 31 Mar 2021 10:16:08 +0500: "Is "192.168.1.254" an IP address of your DSL modem? If you don't need to resolve hostnames from you local network, like "somepc1.attlocal.net" and only want to access the Internet, you can configure one or more of the public DNS servers. From Google [1]: 8.8.8.8 8.8.4.4 From CloudFlare [2]: 1.1.1.1" I don't know. I did not put that line in /etc/resolv.conf. When I get more time I may remove it and see what happens. If you didn't put that line in /etc/resolv.conf, then probably it was configured by DHCP client, which used the information send by your DSL modem. That would explain "attlocal.net" lines. Do you have administrative access to your DSL modem's configuration web interface? Or is it a leased device that was configured by your ISP and you don't have the option to configure it? If you have the access to DSL modem, you can configure its DHCP server to always send proper DNS server addresses, like "1.1.1.1", "8.8.8.8", instead of "192.168.1.254". Alternatively, and if you don't have the access to DSL modem, you can modify "dhclient.conf" file to effectively override name server addresses sent by your modem with known good ones. This procedure is described in Debian Wiki. [1] Basically, all you have to do is add at the end of the file this string: supersede domain-name-servers 1.1.1.1,1.0.0.1,8.8.8.8,8.8.4.4; [1] https://wiki.debian.org/resolv.conf#Modifying_.2Fetc.2Fdhcp.2Fdhclient.conf -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: Temporary failure in name resolution
On Friday, April 02, 2021 01:56:19 PM Dan Norton wrote: > Alexander V. Makartsev wrote Wed, 31 Mar 2021 10:16:08 +0500: > > "Is "192.168.1.254" an IP address of your DSL modem? > If you don't need to resolve hostnames from you local network, like > "somepc1.attlocal.net" and only want to access the Internet, you can > configure one or more of the public DNS servers. From Google [1]: > 8.8.8.8 8.8.4.4 > From CloudFlare [2]: > 1.1.1.1" > > I don't know. I did not put that line in /etc/resolv.conf. When I get > more time I may remove it and see what happens. Sort of building on this question, and just trying to educate myself, if the DSL modem had a caching nameserver: 1) would your computer need to specify the IP of that modem (presumably) 192.168.1.254 to take advantage of the caching? 2) would the caching feature be bypassed if your computer used the public DNS name servers (e.g., 8.8.8.8, 8.8.4.4, and 1.1.1.1)? (Or if they were listed before the modem IP address?)
Re: Temporary failure in name resolution
Alexander V. Makartsev wrote Wed, 31 Mar 2021 10:16:08 +0500: "Is "192.168.1.254" an IP address of your DSL modem? If you don't need to resolve hostnames from you local network, like "somepc1.attlocal.net" and only want to access the Internet, you can configure one or more of the public DNS servers. From Google [1]: 8.8.8.8 8.8.4.4 From CloudFlare [2]: 1.1.1.1" I don't know. I did not put that line in /etc/resolv.conf. When I get more time I may remove it and see what happens. - Dan
Re: Temporary failure in name resolution
David Wright wrote on Thu, 1 Apr 2021 11:50:56 -0500: "I don't recall your answering Alexander's question: what benefit are you getting from those two lines? Do you have a number of machines at home that are being placed in that domain, whose names you resolve with att's help?" I don't know, except that having nameserver 1.1.1.1 and 1.0.0.1 in /etc/resolv.conf as Felix suggested results in successful name resolution. My setup is an AT&T BGW210 modem connected by ethernet cable to a desktop which serves wifi for printing and ISP access to my wife's Windows laptop. Before I tried solving the name resolution problem, systemd-resolved may have been disabled(?). I might have enabled it, I'm not sure. # cat /etc/nsswitch.conf # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: compat systemd group: compat systemd shadow: compat gshadow:files hosts: files mdns4_minimal [NOTFOUND=return] dns networks: files protocols: db files services: db files ethers: db files rpc:db files netgroup: nis HTH - Dan
Re: How I scan, was Re: xsane can't see Brother ADS-2700W scanner
On Wed 31 Mar 2021 at 17:05:57 -0400, Stefan Monnier wrote: [...] > 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 :-( There appear to be three aspects to solving this problem: 1. SANE detecting when a scanner button is pressed. 2. A button press being captured and known to the system. 3. Activation of a script. I can see 3 being solvable but how about 1 and 2? -- Brian.
Re: Converting markdown to PDF
Paul M Foster writes:
On Thu, Apr 01, 2021 at 10:46:09PM +0200, Linux-Fan wrote:
[...]
> pdflatex is provided by package texlive-latex-base.
>
> Some hints about which packages might be needed can be seen in pandoc's
> "Suggests":
>
> ~$ aptitude show pandoc
[snip]
Thanks. When I used "-t latex" and tried outputting to PDF after installing
some of these dependencies, I did get a PDF. Unfortunately, it looks about
as horrible as most LaTeX docs. I'll keep tweaking it.
Yes, I do not like the default style either :)
There are multiple options to change the appearance without digging too
deeply into the generated LaTeX code. E.g. I use a wrapper script for the
following command:
pandoc \
-t latex \
-f
markdown+compact_definition_lists+tex_math_single_backslash+link_attributes \
-V papersize=a4 \
-V classoption=DIV10 \
-V fontsize=12pt \
-V documentclass=scrartcl \
-V fontfamily=kpfonts \
-V babel-otherlangs=greek \
-V babel-newcommands=\\usepackage{teubner} \
-V toc-depth=1 \
-V x-masysma-logo=/usr/share/mdvl-d5man2/tplpdf/logo_v2 \
-V x-masysma-icon=/usr/share/mdvl-d5man2/tplpdf/masysmaicon \
--default-image-extension=pdf \
--template=/usr/share/mdvl-d5man2/tplpdf/masysma_d5man.tex \
--resource-path="$(dirname "$1")" \
-o "$(basename "$1").pdf" \
"$1"
Some of the `-V` options improve (IMHO) the output style. The choice of font
already makes a huge difference (but is also a matter of tast!).
Additionally, I use an own “template” file to do some advanced things like
add logos/icons etc. If you are interested in an example, see
https://github.com/m7a/bo-d5man2/tree/master/d5manexportpdf
HTH
Linux-Fan
öö
[...]
pgpcLbF9G7FPS.pgp
Description: PGP signature
Re: xsane can't see Brother ADS-2700W scanner
On Fri 02 Apr 2021 at 15:27:48 +0500, Alexander V. Makartsev wrote: > On 02.04.2021 06:11, Charlie Gibbs wrote: > > On 2021-04-01 3:51 a.m., Brian Potkin wrote: > > > > > Hello Charlie, > > > > > > It would appear that you are not subscribed to debian-user. Have you > > > seen all the replies to your post that await you there? > > > > Yes, I have. I just haven't had time to act on them. I did download > > a driver from the Brother site but it had no effect. I suspect there's > > something I'll have to do with xsane to get it to find the scanner. > I've poked that driver a bit and it looks like only USB-connection is well > supported, and there is no "Scan from your Computer (Linux)" section in the > manual either. [1] > There is a mention about "conf_ip" utility, but it looks like Brother began > to implement "Direct Scan over Network" feature and never finished. > You might try to follow the instructions from "How to Install" section [2] > and setup IP address of the scanner on PC: > $ sudo conf_ip 192.168.xxx.xxx > > All things considered, it might be indeed easier to setup FTP/SFTP or CIFS > (Samba) server on your PC and create a scanner profile to scan directly into > FTP directory or SMB share. [3] > Even workflow looks more efficient that way: > [Go to scanner] > [Place documents] > [Select profile] > [Start scanning] > > [Retrieve documents] > [Go back to PC] > In comparison to: > [Go to scanner] > [Place documents] > [Go back to PC] > [Select profile] > > [Start scanning] > [Go to scanner] > [Retrieve documents] > [Go back to PC] > > > [1] > https://support.brother.com/g/s/id/htmldoc/ads/cv_ads2200/uke/index.html?c=eu_ot&lang=en&prod=ads2700w_us_eu_as#GUID-323B4D6E-6CAF-4A35-B1AC-7F8F110EAE06_25 > [2] > https://support.brother.com/g/b/downloadhowto.aspx?c=eu_ot&lang=en&prod=ads2700w_us_eu_as&os=128&dlid=dlf103479_000&flang=4&type3=566 > [3] > https://support.brother.com/g/s/id/htmldoc/ads/cv_ads2200/uke/index.html?c=eu_ot&lang=en&prod=ads2700w_us_eu_as#GUID-286EDD29-0309-47AD-82F6-94D735A816D0_36 Although using the Brother driver appears the natural solution to the issue, I would stronly suggest Eduardo M KALINOWSKI's advice to use sane-airscan as the first avenue of approach. * sane-airscan is a free, well-supported SANE backend. * The manual for the ADS-2700W indicates it supports scanning from an iPhone. This is only possible if the scanner supports the eSCL protocol. * sane-airscan also understands the eSCL protocol and should be able to talk to the scanner. * Downloading, installing and testing sane-airscan is a ten minute task. Note: Xsane communicates with a scanner via a SANE backend. If the latter is suboptimal, Xsane can do nothing about it. -- Brian.
Re: Moving from iptables to nftables
On 02.04.2021 14:23, William Torrez Corea wrote: Actually i'm moving/migrating from the old iptables/xtables (legacy) world to the new nftables framework. I execute step by step the migration process: 1. generate a translation of an iptables/ip6tables command to know the nftables equivalent 2. Translate the whole ruleset in a single run I using the nf_tables compat backend. I suppose that translation to native nftables syntax is done if available but I don't get any result. *sudo ebtables-nft -L* * * *Bridge table: filter Bridge chain: INPUT, entries: 0, policy: ACCEPT Bridge chain: FORWARD, entries: 0, policy: ACCEPT Bridge chain: OUTPUT, entries: 0, policy: ACCEPT* Are you sure you need a ruleset for ethernet bridges (ebtables-nft) and not for packet filtering and NAT (iptables-nft)? -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: Moving from iptables to nftables
On 4/2/21 12:23 PM, William Torrez Corea wrote: > Actually i'm moving/migrating from the old iptables/xtables (legacy) > world to the new nftables framework. > > I execute step by step the migration process: > > 1. generate a translation of an iptables/ip6tables command to know the > nftables equivalent > 2. Translate the whole ruleset in a single run > > I using the nf_tables compat backend. I suppose that translation to > native nftables syntax is done if available but I don't get any result. > > *sudo ebtables-nft -L* > * > * > *Bridge table: filter > > Bridge chain: INPUT, entries: 0, policy: ACCEPT > > Bridge chain: FORWARD, entries: 0, policy: ACCEPT > > Bridge chain: OUTPUT, entries: 0, policy: ACCEPT* > > Hi William, if your firewall configuration is not too complex then you can use "gufw" GUI program to set up your firewall. gufw is GUI for ufw (Ubuntu FireWall) and both are available in Debian repository. HTH Kind regards Georgi
Re: xsane can't see Brother ADS-2700W scanner
On 02.04.2021 06:11, Charlie Gibbs wrote: On 2021-04-01 3:51 a.m., Brian Potkin wrote: Hello Charlie, It would appear that you are not subscribed to debian-user. Have you seen all the replies to your post that await you there? Yes, I have. I just haven't had time to act on them. I did download a driver from the Brother site but it had no effect. I suspect there's something I'll have to do with xsane to get it to find the scanner. I've poked that driver a bit and it looks like only USB-connection is well supported, and there is no "Scan from your Computer (Linux)" section in the manual either. [1] There is a mention about "conf_ip" utility, but it looks like Brother began to implement "Direct Scan over Network" feature and never finished. You might try to follow the instructions from "How to Install" section [2] and setup IP address of the scanner on PC: $ sudo conf_ip 192.168.xxx.xxx All things considered, it might be indeed easier to setup FTP/SFTP or CIFS (Samba) server on your PC and create a scanner profile to scan directly into FTP directory or SMB share. [3] Even workflow looks more efficient that way: [Go to scanner] > [Place documents] > [Select profile] > [Start scanning] > [Retrieve documents] > [Go back to PC] In comparison to: [Go to scanner] > [Place documents] > [Go back to PC] > [Select profile] > [Start scanning] > [Go to scanner] > [Retrieve documents] > [Go back to PC] [1] https://support.brother.com/g/s/id/htmldoc/ads/cv_ads2200/uke/index.html?c=eu_ot&lang=en&prod=ads2700w_us_eu_as#GUID-323B4D6E-6CAF-4A35-B1AC-7F8F110EAE06_25 [2] https://support.brother.com/g/b/downloadhowto.aspx?c=eu_ot&lang=en&prod=ads2700w_us_eu_as&os=128&dlid=dlf103479_000&flang=4&type3=566 [3] https://support.brother.com/g/s/id/htmldoc/ads/cv_ads2200/uke/index.html?c=eu_ot&lang=en&prod=ads2700w_us_eu_as#GUID-286EDD29-0309-47AD-82F6-94D735A816D0_36 -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Moving from iptables to nftables
Actually i'm moving/migrating from the old iptables/xtables (legacy) world to the new nftables framework. I execute step by step the migration process: 1. generate a translation of an iptables/ip6tables command to know the nftables equivalent 2. Translate the whole ruleset in a single run I using the nf_tables compat backend. I suppose that translation to native nftables syntax is done if available but I don't get any result. *sudo ebtables-nft -L* *Bridge table: filterBridge chain: INPUT, entries: 0, policy: ACCEPTBridge chain: FORWARD, entries: 0, policy: ACCEPTBridge chain: OUTPUT, entries: 0, policy: ACCEPT* -- With kindest regards, William. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
