August 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Now I get martians on wlan0
by Carlos E. R. 15 Aug '19

15 Aug '19

Hi, After configuring eth0 to also have an IPv6 addresses, I get martians on wlan, which configured to get address via dhcp6 only, in order to detect when/if the ISP provides it. And of course, it never gets one. Isengard:~ # iwconfig lo no wireless extensions. wlan0 IEEE 802.11 ESSID:"......." Mode:Managed Frequency:2.437 GHz Access Point: 70:8B:CD:59:88:3C Bit Rate=150 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=62/70 Signal level=-48 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:17 Missed beacon:0 eth0 no wireless extensions. Isengard:~ # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 4c:cc:6a:61:50:a1 brd ff:ff:ff:ff:ff:ff inet 192.168.1.16/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fc00::16/64 scope global valid_lft forever preferred_lft forever inet6 fe80::4ecc:6aff:fe61:50a1/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether a0:d3:7a:82:b3:4c brd ff:ff:ff:ff:ff:ff inet6 fe80::a2d3:7aff:fe82:b34c/64 scope link valid_lft forever preferred_lft forever Isengard:~ # Isengard:~ # systemctl status network ● wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled) Active: active (exited) since Tue 2019-06-25 14:15:54 CEST; 1 months 13 days ago Process: 29081 ExecReload=/usr/sbin/wicked --systemd ifreload all (code=exited, status=0/SUCCESS) Main PID: 1232 (code=exited, status=0/SUCCESS) CPU: 56ms Jun 25 14:15:54 Isengard systemd[1]: Started wicked managed network interfaces. Aug 08 00:16:49 Isengard systemd[1]: Reloading wicked managed network interfaces. Aug 08 00:17:20 Isengard wicked[24538]: eth0 device-ready Aug 08 00:17:20 Isengard wicked[24538]: eth0 up Aug 08 00:17:20 Isengard wicked[24538]: wlan0 setup-in-progress Aug 08 00:17:20 Isengard systemd[1]: Reloaded wicked managed network interfaces. Aug 08 02:37:32 Isengard systemd[1]: Reloading wicked managed network interfaces. Aug 08 02:38:03 Isengard wicked[29081]: wlan0 device-ready Aug 08 02:38:03 Isengard wicked[29081]: wlan0 setup-in-progress Aug 08 02:38:03 Isengard systemd[1]: Reloaded wicked managed network interfaces. Isengard:~ # Why the martians? How do I stop them? <3.6> 2019-08-08T02:38:03.342398+02:00 Isengard wicked 29081 - - wlan0 device-ready <3.6> 2019-08-08T02:38:03.343768+02:00 Isengard wicked 29081 - - wlan0 setup-in-progress <3.6> 2019-08-08T02:38:03.344335+02:00 Isengard systemd 1 - - Reloaded wicked managed network interfaces. <0.4> 2019-08-08T02:42:34.133900+02:00 Isengard kernel - - - [3760166.225960] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:34.133934+02:00 Isengard kernel - - - [3760166.225966] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:35.977964+02:00 Isengard kernel - - - [3760168.069377] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:35.977996+02:00 Isengard kernel - - - [3760168.069383] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:35.978000+02:00 Isengard kernel - - - [3760168.070591] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:35.978003+02:00 Isengard kernel - - - [3760168.070594] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:38.129903+02:00 Isengard kernel - - - [3760170.219883] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:38.129933+02:00 Isengard kernel - - - [3760170.219889] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:38.129938+02:00 Isengard kernel - - - [3760170.222373] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:38.129941+02:00 Isengard kernel - - - [3760170.222379] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... 192.168.1.16 is the same machine. 192.168.1.3 is the printer. (machine runs Leap 15.0) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

6 12

[opensuse] Linux Kernel Allows 0.0.0.0/8 as a Valid Address Range
by James Knott 15 Aug '19

15 Aug '19

IPv6 has been around for years. Why don't some people get with the program, instead of coming up with hacks to get around the address shortage. Even with this block, there still won't be enough IPv4 addresses just for mobile devices, let alone everything else. The longer people take to move to IPv6, the worse the problem is going to get. By comparison, on IPv6, the smallest address block, /64 provides as many addresses as the entire IPv4 address space squared. I get 256 of those /64s from my ISP. Some ISPs provide 65K of them to each customer. Why are we wasting our time trying to squeeze more life out of something that should have been retired years ago? Incidentally, this block represents less than 0.4% of the IPv4 address space. Will it really make a difference? https://www.technotification.com/2019/08/linux-kernel-allows-0-0-0-0-8-as-a… -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 59

[opensuse] Repository appears to be outdated. Consider using a different mirror or server.
by Admin Beckspaced 14 Aug '19

14 Aug '19

Dear opensuse users, since weeks I do receive this message when checking for updates: zypper up Loading repository data... Warning: Repository 'Hauptaktualisierungs-Repository (NON-OSS)' appears to be outdated. Consider using a different mirror or server. Reading installed packages... Nothing to do. The repo in question is: leap-15.0-repo-update-non-oss Hauptaktualisierungs-Repository (NON-OSS) http://download.opensuse.org/update/leap/15.0/non-oss/ Is there anything I can do to resolve this? Already cleaned the repo. Did a repo refresh. Tried the https URI Nothing actually really helped ... should I be worried about this? thanks & greetings Becki -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] geoip with 4.12.14-lp151.28.10-default
by Holger Jakob 13 Aug '19

13 Aug '19

I am considering to upgrade from 15.0 to 15.1 but cannot see the respective package to support GEOIP at the kernel level (xtables-addons-kmp-default) in the repositories. Does that mean xt_geoip.ko is not available and thus package xtables-geoip is broken in 15.1? I searched the buglist and could only find an entry for 15.0: Bug 1098188 - iptables geoip is not working kernel 4.12.14-lp150.12.4-default Does that not mean 15.1 is affected as well? Any recommendations for a work around? Holger -- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 14

[opensuse] Tumbleweed - RPM install seems stuck
by Roger Oberholtzer 13 Aug '19

13 Aug '19

I'm updating a Tumbleweed system. There were lots of updates in this one. One of them seems stuck. It is installing btrfsmaintenance-0.4.2-3.1.noarch, and nothing has happened in at least a half an hour. I see these processes running: 00:00:03 /usr/bin/python3 /usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.py 00:00:00 rpm --root / --dbpath /var/lib/rpm -U --percent --noglob --force --nodeps -- /var/cache/zypp/packages/repo-oss/noarch/btrfsmaintenance-0.4.2-3.1.noarch.rpm 00:00:00 /usr/bin/systemctl try-restart btrfsmaintenance-refresh.service btrfsmaintenance-refresh.path btrfs-balance.service btrfs-balance.timer btrfs-defrag.service btrfs-defrag.timer btrfs-scrub.service btrfs-scrub.timer btrfs-trim.service btrfs-trim.timer The times on these seem not to change. OOC, I thought I would see what /usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.py is doing. I see that it is in a read that never seems to return: strace: Process 4567 attached read(0, I am guessing/hoping that file 0 is not stdin. If it is, then the design of that script is broken if it should be run by zypper where the user cannot provide anything to stdin. I am afraid to kill the script. I surely don't want to mess up the file system! -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] Epson Inkjet Printer can't connect
by Doug McGarrett 13 Aug '19

13 Aug '19

Re: Tumbleweed: I have an Epson WP-4530 all-in-one printer/copier/scanner. The Driver is available in /usr/etcetera, and Yast claims to have installed it, and if I try to print something, the Epson is shown as a choice, but nothing happens. If I try to use XSane, a message tells me it can't find a device. Meanwhile, an HP LaserJet Pro is found and prints perfectly. But it can't scan or print in color. I've gotten used to Tumbleweed and I like it, but why won't it print? All help appreciated! --doug -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10

[opensuse] ipv6 and ssh
by gumb 12 Aug '19

12 Aug '19

I don't know much about ssh, networking and so on, just enough to have got ssh working on ipv4 between various machines both on my LAN and remotely. Now I'm wanting to try and convert everything to ipv6, since my home ISP has switched to ipv6 by default and in theory it should be simpler overall, but info when googling is limited and outdated. I've had some success already but need more info. 1) I don't fully understand how ipv6 addresses get dished out. I can see, having now set up connections on three machines on my LAN, that one address seems to be the permanent one, chosen automatically for connections, although with one PC it initially chose a different address and settled on that other one later. After looking at info in <ip a> on two machines, the address that I suppose to be the 'main' or permanent one has different things appended. On my old laptop the main one has a /128 suffix followed by 'scope global dynamic'. On my new laptop it has a /64 suffix followed by 'scope global mngtmpaddr noprefixroute dynamic'. Does 'mngtmpaddr' imply it's only temporary? 2) The machine I administer remotely in another country is connected to an ISP that provides a dynamic IP, which has caused me headaches trying to find a method of automatically obtaining the new address each time it changes. If I change over to an ipv6 connection, will they still issue a dynamic address? (I don't know if the dynamic IP is a means to conserving limited ipv4 addresses or if it serves other purposes). 3) I can ssh within my LAN using the link-local address in the console, though I find it much faster and preferable to use a graphical interface and can't find how to make Dolphin accept this address in the 'Network Folder Wizard' dialog. It must need the interface specifying but no matter how I write out the string (%eth0, square brackets, quotes, backslash escapes, etc.) it doesn't accept it. 4) If I ssh to another machine on the LAN but using the afore-mentioned 'global' main address, does this go outside of my LAN, i.e. if I'm only using PAM authentication is there a risk of this being intercepted? Cheers, gumb -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 111

[opensuse] https://bugzilla.mozilla.org/show_bug.cgi?id=700999
by Per Jessen 12 Aug '19

12 Aug '19

Carlos wrote: > I think you simply do not understand the issue. Please read the > bugzilla instead, I did not write it, perhaps you understand them > better than me. > > <https://bugzilla.mozilla.org/show_bug.cgi?id=700999> This is going off-topic, apologies. "Firefox does not appear to support IPv6 link-local addresses". I think I understand the issue perfectly well. > It has 45 entries. > For instance: 34, 37, 29, 10, 17, 32 This morning, I did quickly peruse those comments - they are all from people claiming they _need_ this functionality. In my opinion, they are ignoring the real issue - a misconfigured ipv6 network. Until the network is given a prefix, e.g. 2001:db8:1234:5678, it really is not a functioning ipv6 network. Specifically for your printer issue: run a radvd somewhere, with this config (/etc/radvd.conf) : interface eth0 { AdvSendAdvert on; AdvManagedFlag on; AdvOtherConfigFlag on; too clients { fe80:: .... your printers LL; }; prefix fc00:1234:5678:9000::/64 { AdvOnLink on; AdvAutonomous on; AdvRouterAddr off; }; }; With this, your printer is the only device that is permitted to auto-configure itself. Permitting other devices would only cause problems when you don't have any real ipv6 connectivity. I am assuming your printer does not have any desire to "phone home". The minute you start radvd, your printer will auto-configure and assign itself an address on fc00:1234:5678:9000. Grab the LL address from the label, ignoring the fe80:: part and append it to the prefix. You can now access it from your browser: http://[fc00:1234:5678:9000:21e:bff:fe08:4ccb] Or you add it to /etc/hosts and use 'bilbo6': http://bilbo6 -- Per Jessen, Zürich (15.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 14

[opensuse] What is this nfs error?
by Carlos E. R. 12 Aug '19

12 Aug '19

I got this error in the log: <0.5> 2019-08-12 10:26:17 Telcontar kernel - - - [138139.721655] rpc-srv/tcp: nfsd: got error -95 when sending 28 bytes - shutting down socket <0.5> 2019-08-12 10:26:17 Telcontar kernel - - - [138139.722238] rpc-srv/tcp: nfsd: got error -95 when sending 28 bytes - shutting down socket An awful number of them! cer@Telcontar:~> grep "nfsd: got error -95" /var/log/messages | wc -l 119341 cer@Telcontar:~> Google does not say what error -95 is about. It started this morning at 10:25, till I stopped "Stopped NFS server and services" at 10:26:17. Ie, I got spammed by 119341 lines in one minute! It happened when another machine tried to mount an NFS directory. If I try again, restarting the service, and try from client, the thing starts again. I tried restarting client nfs, does not clear the issue. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

1 1

[opensuse] NTP question
by James Knott 11 Aug '19

11 Aug '19

On my home network, I have my firewall providing NTP and in turn connecting to a public NTP server. I access my firewall NTP server by host name, which will return both IPv4 and IPv6 addresses. In watching the NTP traffic between my desktop computer and firewall, I see both IPv4 and IPv6 addresses alternately being used. Is this the way the NTP client normally works? I could understand it trying multiple addresses, if that is what I provided, but I only provide a single host name, that returns both IPv4 and IPv6 addresses. Normally, with other apps, IPv6 is preferred over IPv4. This is on openSUSE 15.1 and my firewall/router runs pfSense. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 92