January 2023 - openSUSE Users - openSUSE Mailing Lists

[oS-en] Question about dnsmasq + bind
by Carlos E. R. 08 Jan '23

08 Jan '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I wrote in /etc/dnsmasq.conf server=/valinor/192.168.1.16 with the intention that queries on that domain are sent to another local machine. When using dig, the output doesn't show the query going out: cer@Telcontar:~> dig minas-tirith.valinor ; <<>> DiG 9.16.33 <<>> minas-tirith.valinor ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52223 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 6e6f1dc5bde493460100000063bb05c29c04986062a34595 (good) ;; QUESTION SECTION: ;minas-tirith.valinor. IN A ;; ANSWER SECTION: minas-tirith.valinor. 86400 IN A 192.168.1.129 ;; Query time: 3 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Jan 08 19:04:50 CET 2023 ;; MSG SIZE rcvd: 93 cer@Telcontar:~> However, if I comment out the line: #server=/valinor/192.168.1.16 then the host is not found: cer@Telcontar:~> host -v minas-tirith.valinor Trying "minas-tirith.valinor" Host minas-tirith.valinor not found: 3(NXDOMAIN) Received 38 bytes from 127.0.0.1#53 in 0 ms Received 38 bytes from 127.0.0.1#53 in 0 ms cer@Telcontar:~> dig minas-tirith.valinor ; <<>> DiG 9.16.33 <<>> minas-tirith.valinor ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 649 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;minas-tirith.valinor. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Jan 08 19:04:15 CET 2023 ;; MSG SIZE rcvd: 49 cer@Telcontar:~> So it is working, but dig doesn't show the query being done to another machine in my LAN. Why? What have I misunderstood? Is there a command or method that will trace where the question is being sent? - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY7sHvhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVFw8AniZFLj6kXQZe0KzbEoRg 6hk7w85bAJ4tFXmctxx2hk0fU+rvMAmZkVtgQw== =0poo -----END PGP SIGNATURE-----

1 0

gui program can't resolve hostname
by Istvan Gabor 07 Jan '23

07 Jan '23

Hello: I have an openSUSE Leap 15.1 system where the VoIP program IHU (I hear you) works.I also have another Leap 15.1 installation where the program doesn't work, it exits with error, it can't resolve any hostame. It can't resolve either localhost or any valid hostname in the network. It works if I use direct IP address. Command line tools ping and host can resolve hostnames. How could I trace what causes the error? It must be some difference in some configuration or the installed packages between the two 15.1 systems. The IHU program is:ihu-0.6.0-lp151.2.6.x86_64. I use networkmanager for networking.This is how the program runs:1. using IP address:> ihu --nogui --call 127.0.0.1Starting IHU without GUI...Press CTRL-C to terminateMon Dec 26 19:11:48 2022 - Contacting 127.0.0.1...Warning: Mon Dec 26 19:11:48 2022 - CALL to 127.0.0.1 (127.0.0.1)Mon Dec 26 19:11:48 2022 - Closing communication...Mon Dec 26 19:11:50 2022 - 127.0.0.1 rejected the call.Warning: Mon Dec 26 19:11:50 2022 - HANG UP with 127.0.0.1: 0 bytes received, 6 bytes sent2. using localhost> ihu --nogui --call localhostStarting IHU without GUI...Press CTRL-C to terminateError: can't resolve localhostABORTED.Error: can't resolve localhost> ping localhostPING localhost (127.0.0.1) 56(84) bytes of data.64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.042 ms64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.051 ms64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.035 ms> host localhostlocalhost has address 127.0.0.1localhost has IPv6 address ::1localhost mail is handled by 1 localhost.Any suggestion would be appreciated.Thanks,Istvan

10 19

Note - Pico/embedded builders: cross-arm-none-eabi-binutils-2.39 new warning RWX LOAD section warning
by David C. Rankin 05 Jan '23

05 Jan '23

All, and those that use cross-arm-none-eabi-binutils to build for Raspberry Pico, etc. The new version of ld in binutils will emit a warning about a LOAD segment with RWX permissions, e.g. /usr/lib64/gcc/arm-none-eabi/10/../../../../arm-none-eabi/bin/ld: warning: rtos-blink.elf has a LOAD segment with RWX permissions This is a known issue, see: https://github.com/raspberrypi/pico-sdk/issues/1029 The warning can be disabled as specified in the thread: # in pico-sdk/src/rp2_common/pico_standard_link/CMakeLists.txt target_link_options(pico_standard_link INTERFACE "LINKER:--no-warn-rwx-segments") # or for a specific executable in a local CMakeLists.txt target_link_options(hello_world PRIVATE "LINKER:--no-warn-rwx-segments") Updates tonight from the current user builds for cross-arm-none-eabi-binutils finally brought it in for openSUSE. I doubt many will see this, just thought I would pass it along for those tinkering with embedded systems using openSUSE as the build platform to save you a few minutes searching. (and if you haven't played with the $4 pico, this little thing with the dual-core RP2040 processor running at 133MHz, 2M flash memory, 26 GPIO pins, etc -- it's a whole lot of fun if you like that kind of thing... For $2 more you can get the Pico_w with Wifi :) (and no, I have no involvement with the company, just an openSUSE tinkerer...) -- David C. Rankin, J.D.,P.E.

1 0

wicked ifup -> device-not-running <>- ip up -> working
by Simon Becherer 03 Jan '23

03 Jan '23

Hi, i updated a not so often used laptop (last update done 01/2022 to the actual tumbleweed 20221228 after restarting i have no network adapters UP if it is working, it looks like this: ================================================ wicked ifstatus all lo up link: #1, state up type: loopback config: compat:suse:/etc/sysconfig/network/ifcfg-lo leases: ipv4 static granted leases: ipv6 static granted addr: ipv4 127.0.0.1/8 [static] addr: ipv6 ::1/128 [static] enp3s0 enslaved link: #2, state up, mtu 1500, master bond0 type: ethernet, hwaddr 18:67:b0:b9:a6:58 config: compat:suse:/etc/sysconfig/network/ifcfg-enp3s0 wlp2s0 up link: #3, state up, mtu 1500 type: wireless, state established, ssid XAuaLiwaru9835, WPA2-PSK+WPA-PSK config: compat:suse:/etc/sysconfig/network/ifcfg-wlp2s0 bond0 up link: #4, state up, mtu 1500 type: bond, mode active-backup, hwaddr 18:67:b0:b9:a6:58 config: compat:suse:/etc/sysconfig/network/ifcfg-bond0 leases: ipv4 static granted addr: ipv4 192.168.0.23/24 [static] route: ipv4 default via 192.168.0.99 [static] ==================================== it is configured that if cable (enp3s0) is plugged in, it will use cable, and if not plugged in it will switch to whireless (wlp2s0) ==================================== if its not working (before starting manually) it has the status: "device-not-running" for enp3s0 wlp2s0 and bond0 ==================================== after playing around i found out that the command: ip link set enp3s0 up ip link set wlp2s0 up will bring the network cards UP, but this i have to enter manually, AND wicked ifup enp3s0 wicked ifup wlp2s0 will NOT bring the network cards UP. (therefore wicked will during boot hang and run out of time, then boot continues ========================================== here from boot: Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked AutoIPv4 supplicant service... Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked DHCPv4 supplicant service... Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked DHCPv6 supplicant service... Dez 29 21:54:08 becherer7 systemd[1]: Started wicked DHCPv6 supplicant service. Dez 29 21:54:08 becherer7 systemd[1]: Started wicked DHCPv4 supplicant service. Dez 29 21:54:08 becherer7 systemd[1]: Started wicked AutoIPv4 supplicant service. Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked network management service daemon... Dez 29 21:54:08 becherer7 systemd[1]: Started wicked network management service daemon. Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked network nanny service... Dez 29 21:54:08 becherer7 systemd[1]: Started wicked network nanny service. Dez 29 21:54:08 becherer7 systemd[1]: Starting wicked managed network interfaces... Dez 29 21:54:38 becherer7 wicked[1227]: lo up Dez 29 21:54:38 becherer7 wicked[1227]: enp3s0 device-not-running Dez 29 21:54:38 becherer7 wicked[1227]: wlp2s0 device-not-running Dez 29 21:54:38 becherer7 wicked[1227]: bond0 device-not-running Dez 29 21:54:38 becherer7 systemd[1]: Finished wicked managed network interfaces. ================================================= and here when i try manually using wicked: Dez 29 22:19:14 becherer7 wickedd-nanny[1226]: device wlp2s0: call to org.opensuse.Network.Interface.waitLinkUp() failed: General failure Dez 29 22:19:14 becherer7 wickedd-nanny[1226]: wlp2s0: failed to bring up device, still continuing Dez 29 22:19:19 becherer7 wickedd-nanny[1226]: device enp3s0: call to org.opensuse.Network.Interface.waitLinkUp() failed: General failure Dez 29 22:19:19 becherer7 wickedd-nanny[1226]: enp3s0: failed to bring up device, still continuing =================================================== what is wrong here? before update, always the network was running after boot. NOW its only running after i hack in the "ip link....." command. did anybody have me an info how i could start the network again, during boot, AND why did the "wicked ifup..." will not work?? is this a bug? or a configuration problem? some other systems i have updated did not show this problem. they are also running wicked. but did not have a wifi inside (using a bridge and an enslaved network-adapter). regards, simoN -- www.becherer.de

5 12

No directory ownership on CIFS mount
by gumb 02 Jan '23

02 Jan '23

I have some directories that seem to be missing ownership. The files within them are all attributed to an owner but some (not all) of the directories themselves have an 'empty' owner, at least when viewed within Dolphin file manager. I've already run this command, as root, from the top-level directory: > chown -R 4242:fbox_cifs media/ but this doesn't enforce user 4242 as the owner of all the directories, only the files within them. How can I correct this? I'll send more detail if necessary but maybe there's a simple solution without me having to post several more paragraphs. gumb

3 4