August 2019 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] openSUSE Router with IPV6
by James Knott 22 Aug '19

22 Aug '19

On 2019-08-20 01:05 PM, Carlos E. R. wrote: > Could it be that he will never get them, and has to use always private > addresses on the inside? Same as if he were using NAT. The ISP doesn't > want his internal machines to be directly adressable from outside. No, the problem is openSUSE does not appear to support DHCPv6-PD, which is needed to use it as a router with most ISPs. I have a block of 2^72 addresses from my ISP. Any I use within that range will be accessible from outside. There is another type of address, called Unique Local Addresses, which are not accessible from elsewhere, though they are routeable, just like RFC1918 addresses on IPv4. Also, NAT is a hack, to get around the IPv4 address shortage, so there's no need for it on IPv6. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 36

[opensuse] boot delay after changing swap partition
by gumb 22 Aug '19

22 Aug '19

On Leap 42.3 (shortly due to be updated to 15.1), in preparation I decided to change the partitioning. In view of my doubling the RAM, I created a new swap partition, /dev/sda2 on an nvme drive (I've set the swappiness=1 as it'll likely never be used, it's really just for very rare and unlikely hibernation as I have plenty of free space on this drive). After a reboot I then deleted the original swap partition on /dev/sdb2. I did all this in YaST Partitioner. Now each boot has a 1m30s delay. In boot.log there are hundreds of timed entries throughout this delay, i.e.: A start job is running for dev-sda2.device (1min 29s / 1min 30s) ending with Timed out waiting for device dev-sda2.device. Dependency failed for Resume from hibernation using device /dev/sda2. In /boot/grub2/grub.cfg I see each boot entry is appended with: resume=/dev/sda2 splash=silent quiet showopts resume=/dev/sda2 splash=silent quiet showopts resume=/dev/sda2 splash=silent quiet showopts So the string three times in succession. How can I fix this? I just want to be sure there's no broader issue with putting swap on an nvme drive before I do a fresh install of 15.1. gumb -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 6

[opensuse] Another annoying "feature" - 15.1 & KDE
by James Knott 22 Aug '19

22 Aug '19

There seems to be a bug with KDE on 15.1. Frequently, when I click on an open item on the task bar, the list of windows for that app no longer appears. However, if I just hover over it, then the windows are listed in a horizontal row. Is there anyway to fix this? At the moment, I have to log out & in. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] boot delay on 15.1
by jdd＠dodin.org 21 Aug '19

21 Aug '19

Hello, I have a long boot delay at the end of the boot procedure. dmesg say (see below). on this computer (laptop), I have both eth0 and wlan0, eth0 connected (to fiber device). AFAIK previous stop was clean idéa? thanks jdd [ 15.660665] r8169 0000:05:00.0 eth0: link up [ 16.661342] r8169 0000:05:00.0 eth0: link down [ 20.670199] r8169 0000:05:00.0 eth0: link up [ 21.673416] r8169 0000:05:00.0 eth0: link down [ 25.642446] r8169 0000:05:00.0 eth0: link up [ 26.643564] r8169 0000:05:00.0 eth0: link down [ 30.654543] r8169 0000:05:00.0 eth0: link up [ 31.655686] r8169 0000:05:00.0 eth0: link down [ 34.315896] r8169 0000:05:00.0 eth0: link up [ 352.328647] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 660.964992] BTRFS info (device sdb5): qgroup scan completed (inconsistency flag cleared) [ 667.339857] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 982.345635] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1297.341975] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1612.337921] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1859.748794] Bluetooth: RFCOMM TTY layer initialized [ 1859.748799] Bluetooth: RFCOMM socket layer initialized [ 1859.748803] Bluetooth: RFCOMM ver 1.11 [ 1894.576011] fuse init (API version 7.26) [ 1927.296063] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 9

[opensuse] Trying to activate an HE IPv6 tunnel.
by Carlos E. R. 20 Aug '19

20 Aug '19

Hi, Well, as suggested, I got an account on Hurricane Electric and I got the tunnel data. The next step is how to configure it on my router. I was reading some Spanish instructions from <https://www.redeszone.net/2019/05/05/tutorial-tunnelbroker-router-asus-ipv6/>, which are for an ASUS router. I don't find instructions for my specific router, a Comtrend VG-8050. Basically the instructions are: +++................... * Server IPv4 Address: we must indicate the IP address that appears in Tunnelbroker as "Server IPv4 Address". * Client IPv6 Address: we must indicate the IP address that appears in Tunnelbroker as "Client IPv6 Address", but without the /64 at the end. * IPv6 Prefix Length: we must indicate the /64 that we have in the final part of the IP address. Simply indicate the "64" without the bar. * Server IPv6 Address: we must indicate the IP address that appears in Tunnelbroker as "Server IPv6 Address", but without the /64 at the end, only the IP address without the prefix. * Tunnel MTU: we select the default value of the tunnel which is 1480. * Tunnel TTL: select 255 which is the default value. In the section of "IPv6 LAN Seetings" we must indicate: * LAN Prefix Length: normally in the tunnels that we create is /64, therefore, we should simply indicate "64". In case you ask for a /48, you must use this prefix. * LAN IPv6 Prefix: we must indicate the address that appears in Tunnelbroker as "Routed /64", but without the /64 at the end, and ended with "::" as you can see. (Translated with www.DeepL.com/Translator) ...................++- I don't have any of that :-( What I have is <https://susepaste.org/3886098>: +++................... IP Tunneling -- 6in4 Tunnel Configuration Name WAN WAN Dynamic IPv4 Mask Length 6rd Prefix Border Relay Address Remove [ADD] [Remove] ...................++- I click the ADD button, and I see <https://susepaste.org/9619892>: +++................... IP Tunneling -- 6in4 Tunnel Configuration Currently, only 6rd configuration is supported. Tunnel Name [....................] Mechanism: 6RD (no other choice is available) Associated WAN Interface: 6/ppp0.1 (other choices are: 3/eth0.2, 2/eth0.3, that do not seem appropriate) Associated LAN Interface: LAN/br0 (no other choices) (*) Manual (*) Automatic (does not seem to change anything) IPv4 Mask Length: [....................] 6rd Prefix with Prefix Length: [....................] Border Relay IPv4 Address: [....................] ...................++- I don't know what to do at this point. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

5 50

[opensuse] using btrfs device remove
by jdd＠dodin.org 20 Aug '19

20 Aug '19

Hello, some time ago, I used "btrfs add" to create a raid 1 for my root partition. Now I want to make a clone of the disk with clone zilla, and, of course, clonezilla don't want it. The two raid partition (each on it's own disk, of course) are not part of the image. So, I guess I need to break the raid just for the time of the clone. my config is: # btrfs fi df / Data, RAID1: total=43.00GiB, used=32.17GiB System, RAID1: total=32.00MiB, used=16.00KiB Metadata, RAID1: total=2.00GiB, used=1.14GiB GlobalReserve, single: total=84.41MiB, used=0.00B all the doc I see ask to add a path to the delete command, but what's the use? anyway the delete command seems to be deprecated and replaced by "remove" (see man page) should I run btrfs device remove /dev/sdb2 /mnt or may be btrfs device remove / I see in man: REMOVE DEVICE Device removal must satisfy the profile constraints, otherwise the command fails. For example: $ btrfs device remove /dev/sda /mnt ERROR: error removing device '/dev/sda': unable to go below two devices on raid1 In order to remove a device, you need to convert the profile in this case: $ btrfs balance start -mconvert=dup -dconvert=single /mnt $ btrfs device remove /dev/sda /mnt still the "/mnt"?? thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 13

[opensuse] NTP bogus timestamps - 15.1
by James Knott 20 Aug '19

20 Aug '19

I was just looking at some NTP packets between my openSUSE desktop system and my firewall, which has a NTP server. I see the timestamps are all bogus values. Reference ID: NULL Reference Timestamp: Jan 1, 1970 00:00:00.000000000 UTC Origin Timestamp: Jan 1, 1970 00:00:00.000000000 UTC Receive Timestamp: Jan 1, 1970 00:00:00.000000000 UTC Transmit Timestamp: Jun 23, 1983 00:21:14.440064618 UTC However, the reply from the server shows correct values. Reference ID: 132.246.11.238 Reference Timestamp: Aug 20, 2019 15:46:02.939010883 UTC Origin Timestamp: Jun 23, 1983 00:21:14.440064618 UTC Receive Timestamp: Aug 20, 2019 16:02:07.892748690 UTC Transmit Timestamp: Aug 20, 2019 16:02:07.892798979 UTC Why are the values from the client nonsense? Proper NTP operation requires accurate time stamps in both directions, to ensure accurate time. For example, the transit time is used to determine the local offset from the server. The packets between my pfSense firewall and the public NTP server show correct values. Reference ID: 132.246.11.238 Reference Timestamp: Aug 20, 2019 16:21:22.937971724 UTC Origin Timestamp: Aug 20, 2019 16:23:07.952061086 UTC Receive Timestamp: Aug 20, 2019 16:23:07.971987723 UTC Transmit Timestamp: Aug 20, 2019 16:31:44.921310040 UTC https://en.wikipedia.org/wiki/Network_Time_Protocol#Timestamps -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] When ldconfig is required?
by Oleksii Vilchanskyi 20 Aug '19

20 Aug '19

I have a CMake project that does install(TARGETS foo bar baz) where foo is an executable, bar and baz are shared libraries. foo is linked to bar and baz, bar is linked to baz. The install manifest: /usr/local/bin/foo /usr/local/lib64/libbar.so.0.0.1 /usr/local/lib64/libbar.so.0 /usr/local/lib64/libbar.so /usr/local/lib64/libbaz.so However, when I run ldd on any of foo or bar, they both cannot resolve links to their just-installed dependencies (... => "not found"). This is despite /etc/ld.so.conf containing things like /usr/local/lib64. RPATH is not hardcoded for any of the library (and I want it to stay that way, since it should work that way). One thing that resolved the dependencies was running sudo ldconfig Although that helped, I am still curious 1) why running ldconfig was necessary (I thought shared libraries are resolved at runtime through loader) 2) do I need to rerun it every time I reinstall foo, bar and baz 3) do I need to rerun it every time I install new executables or libraries under /usr/local I don't know much about how shared libraries work. Maybe I don't understand something. If so, please include some relevant educational content. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] openSUSE Router with IPV6
by Mark Petersen 20 Aug '19

20 Aug '19

With all the chatter about IPV6 lately, I'm working on getting it setup on my home network. My ISP (Charter) does provide IPV6 addresses, but I'm struggling with making this work. I have an odroid C2 ARM board that is running Tumbleweed with 2 network interfaces: eth1 onboard interface is the WAN port. Uses wicked and dhcp to get an ipv4 and ipv6 address from my isp. eth0 on a usb to ethernet adapter is the LAN port. Uses wicked with a static ipv4 address assigned. walter@c2router:~> ip a 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 e8:fc:af:c7:a8:21 brd ff:ff:ff:ff:ff:ff inet 172.16.4.1/24 brd 172.16.4.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::eafc:afff:fec7:a821/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:1e:06:36:93:44 brd ff:ff:ff:ff:ff:ff inet 75.xxx.253.3/21 brd 255.255.255.255 scope global eth1 valid_lft forever preferred_lft forever inet6 2605:xxxx:afc0:2:ed44:6b09:12ab:2754/64 scope global dynamic valid_lft 518420sec preferred_lft 518420sec inet6 fe80::21e:6ff:fe36:9344/64 scope link valid_lft forever preferred_lft forever On the LAN side, I have dnsmasq handing out ipv4 addresses and taking care of DNS. This all works great for ipv4, but my workstations on the lan only have an ipv4 address plus an fe80... ipv6 address. In my /etc/sysctl.conf I have: net.ipv4.ip_forward = 1 net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.all.accept_ra = 2 net.ipv6.conf.eth1.autoconf = 0 net.ipv6.conf.all.use_tempaddr = 0 net.ipv6.conf.default.use_tempaddr = 0 I was following this guide: https://taczanowski.net/linux-box-as-an-ipv6-router-with-slaac-and-dhcpv6-p… which was running on openSUSE 42.2 using wide-dhcpv6-client. But wide-dhcpv6 is no longer available on openSUSE. So how can I get wicked to request the prefix from my isp, forward that prefix to dnsmasq so it can hand out ipv6 addresses, and using the prefix set an ipv6 address on the lan interface? Or is there another way? Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 11

[opensuse] Apache2 with php7 under Leap 15.1
by Wolfgang Mueller 20 Aug '19

20 Aug '19

Having installed apache2 and php7 under Leap 15.1, I started apache2 using the Services Manager of yast2. But Google-chrome and Firefox do not recognize a php script. They treat it as a text file, trying to open and/or download it. What is wrong? Thanks in advance, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 12