DDNS Asuscomm and smb

[topoldo]

Hi all.
As a modem/router I have an Asus AC68U which gives me the opportunity to have its DDNS, ie .asuscomm.com for free. Unfortunately I see this ddns iis not supported by fvdw-sl.
Any hope to see it supported in a future version of fvdw-sl? I think Asus modem/routers are quite diffuse. Am I wrong?
A second question concerns the smb protocol. Do you plan to migrate to smb 2 or 3?
The smb1 is almost at the end of its life and one must specifically install this protocol in Win10 (build 1709) and exclude the module for its inactivation!

Regards,
Topoldo

[uelpenich]

Hi Topoldo,
what is the task you want to do? I suppose you want to have access to your nas from anywhere in the internet.
There is no need that both, the router and the nas, support DynDNS. Only one, the router or the nas, has to use the DynDNS protocol to publish the actual internet address.
In my opinion it is better the router does DynDNS because the router knows best when the IP address changes.
The VPN tunnel brings you into your local net and you have access to all devices within your local net.

[topoldo]

Tnx for the answer.
Unfortunately I decided to remove fvdw-sl 17.0 February_2018-patched because I found at least 2 important bugs which IMHO affect this distribution.
I connected "public" (open) share as disk Z: to my Win10 1709 Pro in order to have a backup of my downladed files (essentially open source, freeware and adware apps) and I noticed these two problems:
When I did this I noticed:
1. Some folders could not be copied from my PC to public share.
I refer esssentialy to these two folders:
http^3a^2f^2fads.msn.com^2fads^2f1
http^3a^2f^2fads1.msn.com^2fads^2fAFS^2fXSLs^2fBanner_Image
which are part of MSWorks 9.0 SE
2. When I tried to delete all the contents of the "public" share (ie those files which I was able to copy into) I was not able to remove some of them which appeared to be property of the linux user "topoldo" which was the name of the user I log with into my PC and was also the name of the user I created into fvdw-sl (with the same password I use in my PC) in order to be able to mount easily my private share on fvdw-sl as disk Y: on my PC for backup my files.

Regards,
Topoldo

[uelpenich]

Hi Topoldo,

DDNS Asuscomm and smb

Please use a seperate post / subject / mail for each problem. This is easier for discussions and responses. Thanks.

1. Some folders could not be copied from my PC to public share.
I refer esssentialy to these two folders:
http^3a^2f^2fads.msn.com^2fads^2f1
http^3a^2f^2fads1.msn.com^2fads^2fAFS^2fXSLs^2fBanner_Image
which are part of MSWorks 9.0 SE

http^3a^2f^2fads.msn.com^2fads^2f1 and http^3a^2f^2fads1.msn.com^2fads^2fAFS^2fXSLs^2fBanner_Image are neither files nor folders but links to internet sites. I tried both internet addresses http://ads.msn.com/ads/but my adblocker didn't allow access to it because it is mentioned in Peter Lowe’s Ad and tracking server list.

2. When I tried to delete all the contents of the "public" share (ie those files which I was able to copy into) I was not able to remove some of them

The easiest way to delete all content of a share is to delete the share and to recreate it. I know this behaviour in a slightly different context:
If you have a look to the fvdw file system on the nas you'll see all shares with its folders and files belonging to an owner root and access rights rwxrwxrwx. The individual access rights are granted in standard linux smb manner.
For some shares I found a different user with different access rights similar to your findings

which appeared to be property of the linux user "topoldo" which was the name of the user I log with into my PC and was also the name of the user I created into fvdw-sl

when I redirected the predefined windows directories as Documents, Pictures or Movies to a share. Other windows accounts or windows systems were unable to write or to change these directories or files.
As workaround I set the linux access rights back to the owner root and rwxrwxrwx rights.