Re: nmcli and gateway question
On Wed, Aug 5, 2020 at 3:49 PM Ed Greshko wrote: > On 2020-08-05 21:02, Tom H wrote: >> >> Hopefully Todd, the OP, realized that you were implying that he >> might not have "systemd-resolved" running... > > Hopefully > > I may be dense, but it seems to me there is no particular advantage > to using resolvectl, or getent over the "ip route" command to learn > the IP address of the gateway. For my $ those give too little info > to understand how traffic may be routed. And that is what I am > normally also wanting to know when looking at a gateway. But that > may just be me. The complaint was that the iproute tools spit out too much information. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: nmcli and gateway question
On Fri, Aug 7, 2020 at 1:05 AM ToddAndMargo via users wrote: > On 2020-08-05 02:09, Tom H wrote: >> On Tue, Aug 4, 2020 at 1:32 AM ToddAndMargo via users >> wrote: >>> On 2020-08-03 03:40, Tom H wrote: "resolvectl query _gateway" will tell you that the gateway's set to X ip address, but only if you have "myhostname" in "nsswitch.conf". >>> >>> I think I misunderstand. >>> >>> $ resolvectl query _gateway >>> _gateway: resolve call failed: Could not activate remote peer. >> >> grep myhostname /etc/nsswitch.conf > > $ grep myhostname /etc/nsswitch.conf > hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname As Ed G's pointed out, you need "systemd-resolved" to be running to be able to use "resolve". You can use "getent ..." or even "ping -c1 _gateway". ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: nmcli and gateway question
On 2020-08-07 18:48, Tom H wrote: > On Fri, Aug 7, 2020 at 1:05 AM ToddAndMargo via users > wrote: >> On 2020-08-05 02:09, Tom H wrote: >>> On Tue, Aug 4, 2020 at 1:32 AM ToddAndMargo via users >>> wrote: On 2020-08-03 03:40, Tom H wrote: > "resolvectl query _gateway" will tell you that the gateway's set > to X ip address, but only if you have "myhostname" in > "nsswitch.conf". I think I misunderstand. $ resolvectl query _gateway _gateway: resolve call failed: Could not activate remote peer. >>> grep myhostname /etc/nsswitch.conf >> $ grep myhostname /etc/nsswitch.conf >> hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname > As Ed G's pointed out, you need "systemd-resolved" to be running to be > able to use "resolve". > > You can use "getent ..." or even "ping -c1 _gateway". He keeps saying he doesn't want to use ping as he isn't interested in what I would term "up". :-) -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: nmcli and gateway question
On Fri, Aug 7, 2020 at 5:19 AM ToddAndMargo via users wrote: > On 2020-08-06 16:54, Ed Greshko wrote: >> >> I suppose you missed the discussion about resolvectl needing to work >> with systemd-resolved.service. >> >> So, to use resolvectl you need to have systemd-resolved.service >> running. It is disabled by default. > > What would it give me? It's a caching dns resolver, like dnsmasq, but it runs on 127.0.0.53. You can't simply enable and start "systemd-resolved.service". If you're using NM, as I seem to remember that you are, you have to set NM to use "systemd-resolved". You *_MIGHT_* also need to change the "/etc/resolv.conf" symlink the first time that you run with this setup. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: nmcli and gateway question
On 2020-08-07 18:44, Tom H wrote: > On Wed, Aug 5, 2020 at 3:49 PM Ed Greshko > wrote: >> On 2020-08-05 21:02, Tom H wrote: >>> Hopefully Todd, the OP, realized that you were implying that he >>> might not have "systemd-resolved" running... >> Hopefully >> >> I may be dense, but it seems to me there is no particular advantage >> to using resolvectl, or getent over the "ip route" command to learn >> the IP address of the gateway. For my $ those give too little info >> to understand how traffic may be routed. And that is what I am >> normally also wanting to know when looking at a gateway. But that >> may just be me. > The complaint was that the iproute tools spit out too much information. Oh, I thought the complaint was that nmcli, at least the command I used, gave too much info. Granted, I was giving a command which returned all the info I though the OP wanted. FWIW, I only use nmcli to create, edit, control connections/devices under the control of NetworkManager. I don't use, and wouldn't use, nmcli to search/determine how things are configured on a system I'm not familiar with. Each tool has some "drawbacks" unless you are aware of their use cases or have a clear understanding of what you need/want to know. For example, [egreshko@meimei ~]$ resolvectl query _gateway _gateway: 192.168.1.1 -- link: enp2s0 192.168.2.5 -- link: wlp4s0 2001:b030:112f::1 -- link: enp2s0 Returns a list of "default gateways". But, it doesn't tell you which will actually be used. [egreshko@meimei ~]$ ip -br -4 route show | grep default default via 192.168.1.1 dev enp2s0 proto static metric 100 default via 192.168.2.5 dev wlp4s0 proto dhcp metric 600 Tells one the same, but does have the metric so you know which route would be used first. But you can't, at least I've not found a way, to list both IPv4 and IPv6 routes with the same command. And even both of those, as written, don't show Host routes which also need a "gateway" but not one which is "default" netstat -rn is sorta fine for IPv4, but spits out too much for my taste with IPv6. I don't normally care about scope link info. It also has a Flag of U which can confuse since some docs say "route is up" and other documentation say "route is valid". It can lead some to think that it may mean the physical gateway device is "up" and working. It also lacks a metricbut I suppose most setups are rather straight-forward. I still prefer the "ip route" command because you know at a glance all devices being used, their associated IP address, and the routes along with their metric. Anyway, at the risk of offending some family members, all of this comes under the heading of "There is more than one way to skin a cat". :-) -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Error: failed to find VPN plugin for ovpn.
After successfully testing an OpenVPN link on a x86_64, I get the following error on aarch64, as root: # nmcli connection import type ovpn file .ovpn Error: failed to find VPN plugin for ovpn. Both systems have openvn, NetworkManager-openvpn, and NetworkManager-openvpn- gnome packages installed. journalctl -f is completely silent, during this. The only thing I can think of: the x86_64 server is headless, but has a user session autologging into a desktop, on the console. The aarch64 VM is also headless. In both cases I'm ssh-ing in. Maybe something gets started when there's a desktop login, that's required for this. The only thing I see running, on the x86_64 server is nm-applet, that surely can't be required. The x86_64 server desktop login is not a root login, but I can ssh to the x86_64 server, as root, and install the same ovpn connection without any issues. pgpWebRjzDJvm.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Error: failed to find VPN plugin for ovpn.
On 2020-08-07 21:45, Sam Varshavchik wrote: > After successfully testing an OpenVPN link on a x86_64, I get the following > error on aarch64, as root: > > # nmcli connection import type ovpn file .ovpn > Error: failed to find VPN plugin for ovpn. > > Both systems have openvn, NetworkManager-openvpn, and > NetworkManager-openvpn-gnome packages installed. > > journalctl -f is completely silent, during this. > > The only thing I can think of: the x86_64 server is headless, but has a user > session autologging into a desktop, on the console. The aarch64 VM is also > headless. In both cases I'm ssh-ing in. Maybe something gets started when > there's a desktop login, that's required for this. The only thing I see > running, on the x86_64 server is nm-applet, that surely can't be required. > The x86_64 server desktop login is not a root login, but I can ssh to the > x86_64 server, as root, and install the same ovpn connection without any > issues. > Don't have a aarch64 system. But, just to make sure, do these exist? /usr/lib64/NetworkManager/libnm-vpn-plugin-openvpn.so /usr/lib64/openvpn/plugins /usr/lib64/openvpn/plugins/openvpn-plugin-auth-pam.so /usr/lib64/openvpn/plugins/openvpn-plugin-down-root.so -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: [fedora-arm] Re: Error: failed to find VPN plugin for ovpn.
Peter Robinson writes: > > After successfully testing an OpenVPN link on a x86_64, I get the following > > error on aarch64, as root: > > > > # nmcli connection import type ovpn file .ovpn > > Error: failed to find VPN plugin for ovpn. > > So having tried that same command with a openvpn profile I use daily I > had a look at the manual [1] to check to see if I could list plugins. > It mentioned "type values are the same as for vpn-type option in nmcli > connection add" so checking that out I got a lst of the following > types "vpn-type > vpnc|openvpn|pptp|openconnect|openswan|libreswan|ssh|l2tp|iodine|..." > > That gave me a slightly different error related to my actual config, > but to start it seems you need to substitute ovpn for openvpn in you > command line. Once I exported it from the other machine properly a "nmcli connection import type openvpn file test.ovpn" worked as expected on an aarch64 machine. Yup. Rookie error. I got mixed up between the .ovpn extension, and the "openvpn" plugin name. pgpEszqmv8KmS.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: nmcli and gateway question
On 2020-08-07 03:50, Ed Greshko wrote: On 2020-08-07 18:48, Tom H wrote: On Fri, Aug 7, 2020 at 1:05 AM ToddAndMargo via users wrote: On 2020-08-05 02:09, Tom H wrote: On Tue, Aug 4, 2020 at 1:32 AM ToddAndMargo via users wrote: On 2020-08-03 03:40, Tom H wrote: "resolvectl query _gateway" will tell you that the gateway's set to X ip address, but only if you have "myhostname" in "nsswitch.conf". I think I misunderstand. $ resolvectl query _gateway _gateway: resolve call failed: Could not activate remote peer. grep myhostname /etc/nsswitch.conf $ grep myhostname /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname As Ed G's pointed out, you need "systemd-resolved" to be running to be able to use "resolve". You can use "getent ..." or even "ping -c1 _gateway". He keeps saying he doesn't want to use ping as he isn't interested in what I would term "up". :-) I am after "configured" not "functioning" ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: nmcli and gateway question
On 2020-08-08 05:42, ToddAndMargo via users wrote: > On 2020-08-07 03:50, Ed Greshko wrote: >> On 2020-08-07 18:48, Tom H wrote: >>> On Fri, Aug 7, 2020 at 1:05 AM ToddAndMargo via users >>> wrote: On 2020-08-05 02:09, Tom H wrote: > On Tue, Aug 4, 2020 at 1:32 AM ToddAndMargo via users > wrote: >> On 2020-08-03 03:40, Tom H wrote: >>> "resolvectl query _gateway" will tell you that the gateway's set >>> to X ip address, but only if you have "myhostname" in >>> "nsswitch.conf". >> I think I misunderstand. >> >> $ resolvectl query _gateway >> _gateway: resolve call failed: Could not activate remote peer. > grep myhostname /etc/nsswitch.conf $ grep myhostname /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname >>> As Ed G's pointed out, you need "systemd-resolved" to be running to be >>> able to use "resolve". >>> >>> You can use "getent ..." or even "ping -c1 _gateway". >> >> He keeps saying he doesn't want to use ping as he isn't interested in what I >> would term "up". :-) >> > > I am after "configured" not "functioning" > OK. I've got plenty of experience in producing non-functioning configurations. :-) :-) -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
udev change?
I've got udev scripts that were working until I installed an update today. Way down at the end of a chain of scripts udev starts, it sets DISPLAY and runs a program (RepetierHost) when I plug in my 3d printer USB cable. Did something change in udev to make it impossible to start X11 programs now? It does run the script which invokes mono to execute the .exe file, and that script produces zero errors, I just don't have the program pop up on my screen any longer. If I run the RepetierHost script from an xterm, it works fine and the program starts up no problem. This web page describes the scripts in detail: https://tomhorsley.com/hardware/solidoodle/solidoodle-udev.html ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Missing a CPU after the 5.7 kernels??
Have a old quad core system that I've had since Fedora 10 I believe. Recently, upgraded to Fedora 31, and it was still seeing all 4 cores. Run BOINC, and recently notice that it was only showing 3 cpus running? Machine is one of the 5 computers I have at house, but is headless and access remotely via VNC. Other systems all show the right number of cpus after updates, so not sure what might cause the issue. The results of lshw-gui shows the 4 cores, but the dmesg shows only CPU 0 - 2. Didn't notice this until the 5.7 kernel change, but not sure exactly which update caused the change. Any ideals what could fix this, or how to get specific reasons it might have happened. Other machines are newer, some dual and one other quad core. So, just this one?? Info from lshw-gui and dmesg product: AMD Phenom(tm) II X4 955 Processor vendor: Advanced Micro Devices [AMD] bus info: cpu@0 version: AMD Phenom(tm) II X4 955 Processor serial: To Be Filled By O.E.M. slot: AM2 size: 3200MHz capacity: 3200MHz width: 64 bits clock: 200MHz capabilities: 64bits extensions (x86-64), mathematical co-processor, FPU exceptions reporting, wp, virtual mode extensions, debugging extensions, page size extensions, time stamp counter, model-specific registers, 4GB+ memory addressing (Physical Address Extension), machine check exceptions, compare and exchange 8-byte, on-chip advanced programmable interrupt controller (APIC), fast system calls, memory type range registers, page global enable, machine check architecture, conditional move instruction, page attribute table, 36-bit page size extensions, clflush, multimedia extensions (MMX), fast floating point save/restore, streaming SIMD extensions (SSE), streaming SIMD extensions (SSE2), HyperThreading, fast system calls, no-execute bit (NX), multimedia extensions (MMXExt), fxsr_opt, pdpe1gb, rdtscp, 64bits extensions (x86-64), multimedia extensions (3DNow!Ext), multimedia extensions (3DNow!), constant_tsc, rep_good, nopl, nonstop_tsc, cpuid, extd_apicid, pni, monitor, cx16, popcnt, lahf_lm, cmp_legacy, svm, extapic, cr8_legacy, abm, sse4a, misalignsse, 3dnowprefetch, osvw, ibs, skinit, wdt, hw_pstate, vmmcall, npt, lbrv, svm_lock, nrip_save, CPU Frequency scaling configuration: cores: 4 enabledcores: 4 dmesg | grep -i CPU [0.092368] smpboot: Allowing 6 CPUs, 3 hotplug CPUs [0.097494] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:6 nr_cpu_ids:6 nr_node_ids:1 [0.098234] percpu: Embedded 55 pages/cpu s188416 r8192 d28672 u262144 [0.098239] pcpu-alloc: s188416 r8192 d28672 u262144 alloc=1*2097152 [0.098240] pcpu-alloc: [0] 0 1 2 3 4 5 - - [0.155390] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1 [0.166771] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=6. [0.166773] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6 [0.281801] smpboot: CPU0: AMD Phenom(tm) II X4 955 Processor (family: 0x10, model: 0x4, stepping: 0x2) [0.282522] smp: Bringing up secondary CPUs ... [0.282522] node #0, CPUs: #1 #2 [0.285583] smp: Brought up 1 node, 3 CPUs [0.288816] cpuidle: using governor menu [0.289646] mtrr: your CPUs had inconsistent fixed MTRR settings [0.289646] mtrr: probably your BIOS does not setup all CPUs. [0.487753] cryptd: max_cpu_qlen set to 1000 [1.487099] microcode: CPU0: patch_level=0x01db [1.487103] microcode: CPU1: patch_level=0x01db [1.487108] microcode: CPU2: patch_level=0x01db [2.775723] [drm] GART: num cpu pages 131072, num gpu pages 131072 [2.792713] radeon :01:05.0: fence driver on ring 0 use gpu addr 0xac00 and cpu addr 0x(ptrval) [2.794881] radeon :01:05.0: fence driver on ring 5 use gpu addr 0xc0056038 and cpu addr 0x(ptrval) [9.987542] acpi_cpufreq: overriding BIOS provided _PSD data [ 10.196935] k10temp :00:18.3: unreliable CPU thermal sensor; monitoring disabled Thanks. ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mi...@guam.net mailto:msetze...@gmail.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ ___ users mailing list --
Dnfdragora Fails With Unexpected error:
Hi, Dnfdragora shows the above message when run from the CLI after it has parsed all the available repositories. How do I identify whether it is an issue with one of the repositories being used (without disabling all repositories or moving them to another directory) or whether it is an internal error? regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Missing a CPU after the 5.7 kernels??
On 2020-08-08 09:09, Michael D. Setzer II via users wrote: > Have a old quad core system that I've had since Fedora 10 I believe. > Recently, upgraded to Fedora 31, and it was still seeing all 4 cores. > > Run BOINC, and recently notice that it was only showing 3 cpus > running? Machine is one of the 5 computers I have at house, but is > headless and access remotely via VNC. Other systems all show the right > number of cpus after updates, so not sure what might cause the issue. > The results of lshw-gui shows the 4 cores, but the dmesg shows only > CPU 0 - 2. Didn't notice this until the 5.7 kernel change, but not sure > exactly which update caused the change. While it is headless, would there be any chance of booting a live-image to run a 5.6 kernel to verify that and older kernel still detects 4? -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: nmcli and gateway question
On Fri, 2020-08-07 at 14:42 -0700, ToddAndMargo via users wrote: > I am after "configured" not "functioning" Just wondering, do you work for Microsoft? ;-) -- uname -rsvp Linux 3.10.0-1127.18.2.el7.x86_64 #1 SMP Sun Jul 26 15:27:06 UTC 2020 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: nmcli and gateway question
On 2020-08-07 21:05, Tim via users wrote: On Fri, 2020-08-07 at 14:42 -0700, ToddAndMargo via users wrote: I am after "configured" not "functioning" Just wondering, do you work for Microsoft? ;-) Chuckle. Check out my signature block! -- ~~ When you say, "I wrote a program that crashed Windows," people just stare at you blankly and say, "Hey, I got those with the system, for free." -- Linus Torvalds ~~ ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: nmcli and gateway question
On 2020-08-07 16:28, Ed Greshko wrote: On 2020-08-08 05:42, ToddAndMargo via users wrote: On 2020-08-07 03:50, Ed Greshko wrote: On 2020-08-07 18:48, Tom H wrote: On Fri, Aug 7, 2020 at 1:05 AM ToddAndMargo via users wrote: On 2020-08-05 02:09, Tom H wrote: On Tue, Aug 4, 2020 at 1:32 AM ToddAndMargo via users wrote: On 2020-08-03 03:40, Tom H wrote: "resolvectl query _gateway" will tell you that the gateway's set to X ip address, but only if you have "myhostname" in "nsswitch.conf". I think I misunderstand. $ resolvectl query _gateway _gateway: resolve call failed: Could not activate remote peer. grep myhostname /etc/nsswitch.conf $ grep myhostname /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname As Ed G's pointed out, you need "systemd-resolved" to be running to be able to use "resolve". You can use "getent ..." or even "ping -c1 _gateway". He keeps saying he doesn't want to use ping as he isn't interested in what I would term "up". :-) I am after "configured" not "functioning" OK. I've got plenty of experience in producing non-functioning configurations. :-) :-) This stuff goes into my iptables firewall script. It is "presumed" that the networking is done correctly, although I print out instructions on how to correct things when I find them missing/mis-configured. Ya, I am pretty good at those "non-functioning configurations" too. :'( ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
