On 2016-04-29 12:28, Wolfgang Mueller wrote:
On 04/28/16 13:18, Carlos E. R. wrote:
On 2016-04-28 10:02, Wolfgang Mueller wrote:
Indeed, it was the SuSE firewall that caused the problems. Having stopped and disabled it, everything works o.k.
I hope that is just temporary. Rather open the ssh port and leave the firewall up.
I fear it's rather permanent, because in my internal network, consisting of four computers, I want to do on one of them all things I can do on any other of them, i.e. open all kinds of windows and perform all kinds of programs. Therefore I have connected them by nfs, each of them simultaneously acting as a server and as a client.
I think that such an excessive usage of a computer network does not tolerate any restriction imposed by a firewall (but maybe I'm wrong?)
I do the same with the firewall up, and very strict one. You can simply tell the firewall configuration that it is the internal interface. It makes things easy, but arguably not that safe.
For my security, I rely on my router AVM FRITZ!Box 3270, being AVM the most common producer of routers and having the highest reputation in Germany (https://en.avm.de/).
How often do they produce updates?
Moreover, I do not use WLAN at all, which is disabled in my router. For a remote connection in my house between different rooms and/or stories, I use Netgear Powerline (http://www.netgear.com/), which uses the existing electrical wiring and is much faster than WLAN. If I like, I can see the names of all my neighbors' WLAN connections, but mine is not among them.
IMHO, powerline networking should be forbidden. It causes radio interference. >:-) I trust that powerline thing uses strong encryption, otherwise neighbours could have a peek. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)