Am Sonntag, 23. Juli 2017, 18:08:07 CEST schrieb gumb:
Am Mittwoch, 19. Juli 2017, 19:12:46 CEST schrieb gumb: [...]
nmcli conn show --active
NAME UUID TYPE DEVICE MyWifi 12345678-9012-3456-789abcdef01234567 802-11-wireless wlan0
nmcli conn show MyWifi | grep ipv4\.method [...] I configured a static address in NM settings, with the two nameservers
On 20/07/17 19:58, Jan Ritzerfeld wrote: listed as advised by the ISP.
Okay. Then you won't be able to use the "short" host name freebox-server for your FreeBox even if your FreeBox offers its own DNS. You could test this by creating a second NM connection for your FreeBox that uses automatic IPv4 configuration.
I can't figure out how to run the second of those nmcli commands you post above since my network name contains spaces and brackets and the command stumbles.
You could use the UUID instead of the name.
[...]
Okay. However, I don't think that its presence in your resolve.conf is necessary.
I probably confused the issue previously. The 'My domain name' I'm referring to above is my machine domain name, which I presume is added automatically to the resolv.conf file since the only one I've entered in NM configuration is 'free.fr'
Hmm. I never enter a host name during OS installation but change it later to a local name, i.e., without any '.'. Via DHCP my computer sends it name to the router and the router sends back its local domain (amongst other things):
cat /etc/HOSTNAME karl hostname -f karl.fritz.box grep search /etc/resolv.conf search fritz.box host karl karl.fritz.box has address 192.... karl.fritz.box has IPv6 address 2a0a:... host diskstation diskstation.fritz.box has address 192.... diskstation.fritz.box has IPv6 address 2a0a:...
Because of the search line in resolv.conf I don't need to specify the full host name. And the DNS of my router resolves other host names of my local network.
What I was getting at was that this domain I give my machine(s), whilst being a real domain I own, is not actually associated to my French ISP or any other service running on my machine.
Yes, and this is why I think it is not necessary to have it in your resolv.conf. And I doubt that free.fr is that useful, too. Okay, you could "ping www" instead "www.free.fr".
[...]
mafreebox.free.fr seems to resolve to a special IP address (212.27.38.253) to that all FreeBoxes will respond to if the request comes from the internal network. Since this is not a very common situation, external IP but actually internal, you could try to use freebox-server.local as a host name for FTP after stopping your SuSEfirewall2.
Yes that's the IP address I was seeing and couldn't understand if it was some additional IP held by my router or something else. If it's a shared public address it's okay.
That confused me too. But this way you can access your FreeBox without using DHCP and a local DNS.
I assume that by selecting anonymous login for both FTP and Samba this doesn't pose any threat. Allowing remote FTP access is a different thing which I haven't activated.
Correct, in general you shouldn't allow remote access to any service when selecting anonymous login.
[...] I've just run into an issue. [...] I don't think I need anything like gnome-keyring or GNOME services launching on startup just to remember an empty password.
Sorry, no idea, I don't use GNOME.
Is there a system-level configuration for logging in anonymously to a samba share at start-up? And one that would fail silently if I have the drive unplugged or I add the same configuration to my laptop?
Maybe, see below.
As for adding the external drive to my fstab via smb://192.168.0.254, aside from being not quite sure how to configure that line,
Never did this but, if AV Linux uses systemd, I assume something like that (in one line): //192.168.0.254/media /{existing path where to mount} guest,noauto,x- systemd.automount,x-systemd.idle-timeout=60,nofail 0 0 I added the "guest" option to mount it without asking for a password (man mount.cifs). The other options are explained in "man systemd.mount".
I'm not sure I want it. My main machine is a laptop with docking station. When I take the laptop elsewhere it would necessitate having the fstab line set to noauto, but then that seems to invalidate any worth of having it in the fstab.
Exactly, but systemd can mount your share only when needed and will automatically unmount it if you don't use it anymore by the following fstab options: noauto,x-systemd.automount,x-systemd.idle-timeout=60,nofail However, if AV Linux does not use systemd or you don't want to edit your fstab, use the old autofs/automount. Install autofs and add at the end of /etc/auto.master: /{existing base path for all mounts} /etc/auto.cifs --timeout 60 Then, create /etc/auto.cifs with the following content: media -fstype=cifs,guest ://192.168.0.254/media "/etc/init.d/autofs reload" and you should be able to browse to /{existing base path for all mounts}/media Gruß Jan -- Beware of altruism. It is based on self-deception, the root of all evil. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org