Am Dienstag, 18. Juli 2017, 21:51:08 CEST schrieb gumb:
On 17/07/17 11:23, Jan Ritzerfeld wrote:
Am Montag, 17. Juli 2017, 00:59:01 CEST schrieb gumb:
On 16/07/17 23:59, Jan Ritzerfeld wrote: [...]
Using smb://freebox-server.local/ is the same as smb://{IP address of your Freebox} besides the mDNS host name resolution. Years ago, SuSEfirewall2 blocked the mDNS host name resolution: https://lists.opensuse.org/opensuse-security/2008-09/msg00011.html So, I assume that "ping freebox-server.local" doesn't work for you.
Your assumption is correct: ping: unknown host freebox-server.local
And after you stop the SuSEfirewall2? As root, e.g.: SuSEfirewall2 stop
Strange, I just stopped the firewall, got this:
PING freebox-server.local (192.168.0.254) 56(84) bytes of data. 64 bytes from 192.168.0.254: icmp_seq=1 ttl=64 time=0.226 ms 64 bytes from 192.168.0.254: icmp_seq=2 ttl=64 time=0.226 ms 64 bytes from 192.168.0.254: icmp_seq=3 ttl=64 time=0.196 ms 64 bytes from 192.168.0.254: icmp_seq=4 ttl=64 time=0.241 ms 64 bytes from 192.168.0.254: icmp_seq=5 ttl=64 time=0.249 ms ^C --- freebox-server.local ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4003ms rtt min/avg/max/mdev = 0.196/0.227/0.249/0.024 ms
BUT ... I then re-enabled the firewall, got identical results. So that's not the issue.
Well, I beg to differ: The nscd service caches positive host lookups for 600 seconds.
Do you have the package nss-mdns installed? If you install avahi-utils, you will be able to test mDNS directly by: avahi-resolve -n freebox-server.local
nss-mdns is installed (in addition to the -32bit version). I installed avahi-utils. Running your above command I get:
Failed to resolve host name 'freebox-server.local': Timeout reached
Even after you stopped the firewall? Because avahi-resolve won't use the nscd cache and will fail instantly in contrast to ping.
I looked under the local network mode settings on the router. It gives this:
Name of Freebox Server: Freebox Server DNS name: freebox-server mDNS name: Freebox-Server Netbios name: Freebox_Server
Interesting. Does ping freebox-server work? If so, you could try to type smb://freebox-server in Dolphin. That could work because routers often run their own DNS and offer a local domain for all DHCP clients. If so, there would be a line starting with "search" in /etc/resolv.conf.
[...] Yes. It looks like your Freebox decided to do that. It is a samba server configuration that could be turned off, but AFAIK only on your Freebox itself. Alas I don't see anywhere on the Freebox OS options to do that.
To bad. Perhaps you could start a new thread and ask if anyone has an idea to mitigate the mangling. But I didn't find a solution using google...
I tried allowing FTP on the Freebox, with anonymous login. That works fine in Dolphin and I get fast directory listings. However, if I try opening files via FTP in, say, VLC Player, it spits out: ftp error: cannot set passive mode ftp error: cannot retrieve file core error: open of `ftp://mafreebox.freebox.fr/media/Music/Collection/{path to flac file}
Try stopping your firewall. BTW, is mafreebox.freebox.fr the correct host name? Gruß Jan -- Any government that is strong enough to give the people everything they want is a government that's strong enough to take it away. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org