[FONT=inherit]#openSUSE[/FONT]](https://www.facebook.com/hashtag/opensuse?source=feed_text) [FONT=inherit]#Leap15[/FONT]](https://www.facebook.com/hashtag/leap15?source=feed_text) !!! A lot of new things at [FONT=inherit]#oSC18[/FONT]](https://www.facebook.com/hashtag/osc18?source=feed_text)
https://youtu.be/OTPc36dVg8Q Live Release
I did a final clean install this morning (local time) to a virtual machine. Install went well.
My other machines are mostly running Leap 15.0 already. My main desktop is still on 42.3, but with 15.0 installed in a different partition. I’ll switch that over in a few days.
Great, thank you and the team.
Your signature says "** Appreciate my reply? Click the star and let me know why. **I don’t see a star.
Left bottom, next to a triangle.
ty
/10characters
You are welcome.
I’ve had ktorrent running since 07:00 Mexico time today pointed at http://download.opensuse.org/distribution/leap/15.0/iso/openSUSE-Leap-15.0-DVD-x86_64.iso.torrent and nothing has happened yet. Any particular reason?
Haha. Way ahead of you…
Been running it as my main desktop for a few months in Beta, no issues at all for me, and now in the released a few days.
The only time I have been in to the 42.3 boot on my machines in the past couple months is, once a week, to run the 42.3 updates. Then, reboot right back into 15.0 when updates finished and 42.3 running is verified.
I’m not expecting any problems.
The main reason for my delay, is that I have been running KVM under 42.3. After my experience with that, I want to start over on KVM for 15.0. However, wanted to do that final 15.0 test install before I abandon 42.3 and its KVM configuration.
Every single mirror I click on to get the DVD ISO gives me an error 404. What’s gone wrong? And the Live version has only one mirror? Odd.
Yep, understood, even before you explained, but … still, could not resist a "Nyah, nyah, nyah!"lol!
It looks as if mirror-brain is having a seizure.
When I downloaded this morning, I used “wget” to download the sha256 checksum file. And the output showed that it redirected to the Princeton mirror. But now the princeton mirror is giving a 404.
So I tried “wget” again (for the sha256 file, since that is small). This time it redirected to “http://mirror.us.leaseweb.net/opensuse/distribution/leap/15.0/iso/openSUSE-Leap-15.0-DVD-x86_64.iso.sha256” which gave a 404.
Something is broken.
Am 25.05.2018 um 19:56 schrieb nrickert:
> The problem has been mentioned on the factory mailing list:
> ‘BitTorrent link for Leap 15’
> (https://lists.opensuse.org/opensuse-factory/2018-05/msg00378.html)
The Torrent works, but there is this error:
Der Tracker hat einen Fehler gesendet: “torrent not found”
Daniel
Just to update – I am now running 15.0 on my main desktop. And I updated my forum signature to match.
The biggest issue thus far, is setting up an NFS server. Yast does not know how to configure the firewall (the new firewalld) for NFS. So, for the moment, I’ve turned off the firewall. I’ll need to revisit that at some time. My home router firewall is probably sufficient protection for now.
Thanks for the reminder. 
The biggest issue thus far, is setting up an NFS server. Yast does not know how to configure the firewall (the new firewalld) for NFS. So, for the moment, I’ve turned off the firewall. I’ll need to revisit that at some time. My home router firewall is probably sufficient protection for now.
The graphical ‘firewall-config’ utility has provision for ‘nfs’ and ‘nfs3’ services in its services list.
Yes, it does. However, it is very unintuitive. I thought I had it all working, but my NFS clients could not connect until I stopped the firewall.
I tried again, and this time I got it working.
One of the first concepts is that it has a Runtime and Permanent configuration. For permanent configuration, changes will only be applied after restarting firewalld. I think by default interfaces are added to the restrictive ‘public’ zone. You can decide to use a less restrictive (eg home) zone id desired. To check which zones are active do
# firewall-cmd --get-active-zones
and check allowed services (eg ‘home’ zone) using
# firewall-cmd --zone=home --list-all
Lets assume we want to allow NFSv4 traffic for a server (port 2049)
# firewall-cmd --permanent --zone=home --add-service=nfs
Restart the firewall with
# systemctl restart firewalld
Now check allowed services again…
# firewall-cmd --zone=home --list-all
home (active)
target: default
icmp-block-inversion: no
interfaces: ppp0 eth0
sources:
services: ssh mdns samba dhcpv6-client nfs
ports:
protocols:
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
Good work.