NAS4Free 9.3.0.2.1391 Released (FreeBSD 9.3-RELEASE-P13)

[zoon01]

The nas4free team has just released 9.3.0.2.1391.

NAS4Free Upgrade below 9.3.0.2.1310 is NOT possible!!!
======================================================

Upgrading NAS4Free "Embedded" or "Full" from any version below 9.3.0.2.1310 by webgui or from
LiveCD/USB is problematic, due a new size of boot partition & partition layout.
Please download and save your NAS4Free config to a safe place and backup all files from second
partition if you use boot disk as data disk.
INSTALL FROM SCRATCH IS THE ONLY WAY!
After installation you can restore your config.
Sorry for inconvenience.
! Tools to write extracted embedded file are not longer supported !
Use the liveusb/CD than.


Requirements
============
Embedded: 2GB CF/USB/SSD (NAS4free "Embedded" is Recommended Install)
Full: 4GB HDD/SSD (For developers and some advanced users, Not Recommended!)
Swap less: physical memory 2GB or higher needed.
With swap: physical memory 512MB + swap 512MB (swap 1024MB recommended).

*Note: LiveCD is not supported on swap mode except installation and upgrading.

BUILD 9.3.0.2.1391
=================
Changes:
- Upgrade to FreeBSD 9.3 RELEASE p13.
- Upgrade to Samba4.1 and add SMB3 in WebGUI.
- Convert to pkgng.
- Ability to backup and restore the encrypted configuration.
- Installation of system with GPT partition. (experimental)
- Improved WebGUI under PHP 5.6.
- Improved WebGUI with Chrome.
- Improved config restore verbose output.
- Improved ZFS pool usage/tool and import ZFS disks.
- Improved ZFS pool import on embedded.
- Improved HAST switch with net.inet.carp.preempt.
- Improved PHP session handle.
- Improved swap setting.
- Replaced /dev/md0 with xmd using LZ4 compression.
- Replaced the server certificate with 2048bits key and sha256 signature.
- Change iperf2.x for iperf3.
- Changed samba reload when changing the shares. (it takes few secs.)
- Changed rootfs layout. (2GB USB/CF is required. Full is 4GB or more.)
- Changed image files to use XZ.
- Changed net.inet.tcp.delayed_ack to 1.
- Changed boot with advskew=240 on master node. ("Switch VIP to MASTER" button will change the value)
- Changed default Map to guest in CIFS/SMB is enabled.
- Changed SMB send/recv buffer to 128480.
- Drop SSLv3 support. (HTTPS must use TLS)
- Drop LiveCD mode support with less than 2GB memory. (install/upgrade only)
Supported minimum spec except LiveCD is 512MB memory + 512MB swap device or partition.
1024MB swap device or partition is recommended.
File based swap and ZFS volume swap is not recommended.
- Add ext2/ext3/ext4 detection when importing disk.
- Add NFS v4 support.
- Add tcpdump.
- Add hostapd support. (wireless AP mode)
- Add WLAN virtual interface used for wireless device. (OPT only at this time)
- Add WebGUI access restriction.
- Add NFS support in HAST service.
- Add default swap of 512MB for LiveUSB and before user configuration.
- Adjust number of Status|Processes.
- Add MBR partition to LiveUSB.
- Add log/mirrored log support in Disks|ZFS|Pools|Tools.
- Add expires HTTP header. (some js must be force reloaded.)
- Add 10.1 bge driver & NAS4Free bge wol patch.
- Increase http upload size to 512MB.
- Remove last slash of the path added by filechooser.
- Add wait_on and spindown.
- Upgrade e2fsprogs to 1.42.12.
- Upgrade transmission to 2.84.
- Upgrade isboot to 0.2.8.
- Upgrade istgt to 20141125.
- Upgrade smartmontools 6.3
- Upgrade xmlstarlet to 1.6.1.
- Upgrade mDNSResponder to 561.1.1.
- Upgrade xmd to 0.4.2.
- Upgrade bash 4.3 to patch 33.
- Upgrade unison to 2.48.3.
- Upgrade netatalk to 3.1.7.
- Upgrade iperf3 to 3.0.11.
- Upgrade samba to 4.1.17.
- Upgrade zoneinfo to 2015b.
- Upgrade php to 5.6.7.
- Upgrade nano to 2.4.0.

Fixes:
- Can not mount(readonly) ext2/ext3/ext4 on GPT.
- Remove ZFS pool cache in ZFS pool tools and sync.
- FAT/NTFS mount does not use access restriction.
- Broken Wireless support.
- ZFS pool cache is not removed when deleting or reseting to factory default.
- Missing /etc/uams/uams_randnum.so
- Missing nutdrv_atcl_usb nut driver.
- Never reject SMB3 and sendfile combination.
- Failed to mount NTFS with read-only.
- Missing mount_fusefs in /usr/local/sbin.
- Missing usb device configuration file.
- Missing default pkg repository.
- mount_ntfs is not installed to /sbin.
- Wrong variable in HAST script.
- /boot/kernel/fuse.ko is missing.
- /etc/platform is broken on full installation.
- Some DHCP setting of WebGUI does not work.
- xmlrpc is broken.
- Missing GPT partition in Disks|ZFS|Pools|Tools.
- Switching DHCP and static IP cause unexpected behavior.
- Some drives can't get disk model/description.
- The text on graph is not sized on Chrome.
- Firmware page show incorrectly.
- ntfs-3g is broken.
- Form size is too small on Chrome.
- HAST device is not imported by import disks.
- Stop flooding "Unknown USB device" to syslog.

CIFS/SMB
========
Authentication has changed
Only Local User or Active Directory can be selected.
Anonymous access has been dropped!

Improved security WebGUI access
=============================
When you have WebGUI Login error 403?
Make shure the pc is in the same network!
by default the System|General Setup Hosts allow field is empty so any one on
the same network of LAN interface can access the WebGUI allowed.
With a space delimited set of IP or CIDR notation you can add computers from outer network.
As an example the outer IP address and LAN address for remote access.

Experimental memory disk (geom_xmd.ko)
=====================================
This version contains a special memory disk driver called "xmd".
The following are the main features.

- on-demand memory allocation and de-allocation (zero fill/TRIM support)
- on-the-fly block level compression
- multiple compression methods and levels (none, LZ4/LZ4HC, ZLIB, LZMA2)
- mixed compressed blocks (can be changed at any time by xmdconfig)
- pre-compressed mfsroot by mkuzip(8) or mkulzma(8)
- provide the ioctl interface for the xmdconfig utility like mdconfig(8)

Regards,
The NAS4Free Team

[hanson1979]

Updated my "full install" by live USB without any issue.Config restored automatically . So far it's working as it should...

[karlandtanya]

note (ref also samba section) access is by local user

Upgrade to 9.3.0.2.1391 from 9.3.0.2.1349 embedded
download embedded, extract, write to usb with win32diskimager
insert usb into running server

Code: Select all

# mkdir /mnt/da1s1a
# mount -t ufs /dev/da1s1a /mnt/da1s1a
# cp /cf/conf/config.xml /mnt/da1s1a/conf

swap usb drives and reboot. version is ...1391.

Now unable to access smb shares from windows 7 x64 clients.
deleted and re-added smb shares; no help.
tried different client computers
tried using windows explorer directly and media software called "xbmc"; neither functions

reverted to 1349 by swapping USB so old usb stick is in...

tried different client computers; all are OK
tried using windows explorer directly and media software called "xbmc"; all are OK


FWIW, here is the samba section:

Code: Select all

	<samba>
		<netbiosname>gizmonas-pri</netbiosname>
		<workgroup>workgroup</workgroup>
		<serverdesc>Primary NAS downstairs</serverdesc>
		<security>user</security>
		<maxprotocol>SMB2</maxprotocol>
		<guestaccount>ftp</guestaccount>
		<maptoguest>Never</maptoguest>
		<localmaster>yes</localmaster>
		<rcvbuf>64240</rcvbuf>
		<sndbuf>64240</sndbuf>
		<storedosattributes/>
		<largereadwrite/>
		<aiorsize>4096</aiorsize>
		<aiowsize>4096</aiowsize>
		<aiowbehind/>
		<enable/>
		<if/>
		<pwdsrv/>
		<winssrv/>
		<timesrv>no</timesrv>
		<doscharset>CP437</doscharset>
		<unixcharset>UTF-8</unixcharset>
		<loglevel>1</loglevel>
		<share>
			<uuid>f716d345-52c2-485a-bc92-e21ae5d77573</uuid>
			<name>backups</name>
			<path>/mnt/data/backups</path>
			<comment>backups</comment>
			<browseable/>
			<guest/>
			<inheritpermissions/>
			<hidedotfiles/>
			<shadowcopy/>
			<shadowformat>%Y%m%d_%H%M_autosnap_type%S</shadowformat>
			<zfsacl/>
			<hostsallow/>
			<hostsdeny/>
		</share>
		<share>
			<uuid>01b7c1f5-b91a-40b2-88dd-c14d5479bb32</uuid>
			<name>dropbox</name>
			<path>/mnt/data/dropbox</path>
			<comment>dropbox</comment>
			<browseable/>
			<guest/>
			<inheritpermissions/>
			<hidedotfiles/>
			<shadowcopy/>
			<shadowformat>%Y%m%d_%H%M_autosnap_type%S</shadowformat>
			<zfsacl/>
			<hostsallow/>
			<hostsdeny/>
		</share>
		<share>
			<uuid>07d06e3d-97b0-4509-9574-66b772f62005</uuid>
			<name>library</name>
			<path>/mnt/data/library</path>
			<comment>library</comment>
			<browseable/>
			<guest/>
			<inheritpermissions/>
			<hidedotfiles/>
			<shadowcopy/>
			<shadowformat>%Y%m%d_%H%M_autosnap_type%S</shadowformat>
			<zfsacl/>
			<hostsallow/>
			<hostsdeny/>
		</share>
		<share>
			<uuid>e3e5f7da-2b31-41aa-8111-c0bd1d8b5e5c</uuid>
			<name>media</name>
			<path>/mnt/data/media</path>
			<comment>media</comment>
			<browseable/>
			<guest/>
			<inheritpermissions/>
			<hidedotfiles/>
			<shadowcopy/>
			<shadowformat>%Y%m%d_%H%M_autosnap_type%S</shadowformat>
			<zfsacl/>
			<hostsallow/>
			<hostsdeny/>
		</share>
		<share>
			<uuid>cc4cd143-27f7-428f-b58a-e692d2341163</uuid>
			<name>scripts</name>
			<path>/mnt/data/scripts</path>
			<comment>scripts</comment>
			<browseable/>
			<guest/>
			<inheritpermissions/>
			<hidedotfiles/>
			<shadowcopy/>
			<shadowformat>%Y%m%d_%H%M_autosnap_type%S</shadowformat>
			<zfsacl/>
			<hostsallow/>
			<hostsdeny/>
		</share>
	</samba>

[zoon01]

Embedded should not be extracted and wrote by any tool! That's no longer supported because of partitions layout and other changes.

Perform embedded upgrade by webgui or use livecd/lives to do an install/upgrade.
If you do not install/upgrade as we advise you can suspect ununpredictable behaviors of the system.

Regards,
zoon01

[Lee Sharp]

Embedded should not be extracted and wrote by any tool! That's no longer supported because of partitions layout and other changes.

This is frustrating. Most of the servers I am installing to now can boot off USB just fine, but can not burn an image to USB from the CD-Rom image. (Has to do with how the BIOS sees a USB "Disk" vs how FreeBSD sees a USB "Disk.") I have to boot my desktop or laptop off a CD-Rom image to write the USB. Workable, but not as easy as it used to be.

[karlandtanya]

Embedded should not be extracted and wrote by any tool! That's no longer supported because of partitions layout and other changes.

Perform embedded upgrade by webgui or use livecd/lives to do an install/upgrade.
If you do not install/upgrade as we advise you can suspect ununpredictable behaviors of the system.

Regards,
zoon01

Unpredictable behaviours--wow.
OK, then--I have immediately shut down the backup server which was running a USB stick constructed by the Win32DiskImager

It was my (clearly incorrect) understanding that by writing the image to the stick, partitions and layouts would be whatever the developers desired and included in the image. Of course I am no developer, so I follow your instructions!

I will make a live USB or CD and then do an embedded install to a stick according to the menu.
Next I will boot the newly created USB and restore the config of the previous version which is already saved in the zfs array
And then report back what happens with SMB. At least this behaviour is very reproducible (two servers, two clients, all combinations reproduce it)

Thanks for your kind advice and your tireless work creating this excellent software then giving it away for free!

[JoseMR]

Upgraded r1349 from Web GUI without hassle.

Steps used:
1: Downloaded r1391 x64 Live CD, extracted the Embedded from CD(both files hash passed)
2: Issued a Web GUI upgrade (took just few seconds)
3: System rebooted.

All previous settings/partitions/jails has been maintained, and everything working as expected

Destination disk: WD1600BEVT (Embedded + Swap + Data)

Regards

[zoon01]

Upgraded r1349 from Web GUI without hassle.

Steps used:
1: Downloaded r1391 x64 Live CD, extracted the Embedded from CD(both files hash passed)
2: Issued a Web GUI upgrade (took just few seconds)
3: System rebooted.

All previous settings/partitions/jails has been maintained, and everything working as expected

Destination disk: WD1600BEVT (Embedded + Swap + Data)

Regards

You also could download the embedded-9.3.0.2.1391.img.xz file and flash from gui, no need to extract livecd

[JoseMR]

You also could download the embedded-9.3.0.2.1391.img.xz file and flash from gui, no need to extract livecd

Hey zoon01 i know right, i always download the LiveCD because i always test/look for bugs on a VM before anything else, so is like getting 2x1

Regards

[kkd]

hi,
embedded-9.3.0.2.1391 is perfect here.

Thanks developers

[crest]

hi,
embedded-9.3.0.2.1391 is perfect here.

Thanks developers

+1

IMPORTANT NOTE for users of the Extended GUI extension on embedded systems: before performing a firmware upgrade via the WebGUI please disable the extension temporarely, otherwise it will fail with a function verify_xz_file not found error message.

Sorry for this inconvinience, a fix for this will be available soon!

Regards
crest

[karlandtanya]

Behaviour is repeatable from 2 different Win7EntN64 (current) boxes and 1 android 4.1 phone.
Basically, by swapping back and forth between 1349 and 1391 SMB access is permitted or not (respectively).

Thanks for any help!


OK, a little more detail...

After updating to 1391...
In WIndows, I can see the server and the shares therein:
\\gizmonas-sec shows the normal list of shares as folders
But trying to open the shares I get "Windows cannot access \\gizmonas-sec\media"....0x80070035 The network path was not found.
Android also displays the server and lists the shares, but when you tap a share it says "Login fails" then suggests may be caused by "wlan is off, smb server is out of network scope, the ip is invalid, blocked by firewall, smb service is off"
Reverting to 1349 I have smb access as normal again.



And, in excruciating detail with another copy of the samba config
(note this is repeatable in 2 different servers primary & backup; just showing the samba config for the backup)

Code: Select all

	<samba>
		<netbiosname>gizmonas-sec</netbiosname>
		<workgroup>workgroup</workgroup>
		<serverdesc>Secondary NAS upstairs</serverdesc>
		<security>user</security>
		<maxprotocol>SMB2</maxprotocol>
		<guestaccount>ftp</guestaccount>
		<maptoguest>Never</maptoguest>
		<localmaster>yes</localmaster>
		<rcvbuf>64240</rcvbuf>
		<sndbuf>64240</sndbuf>
		<storedosattributes/>
		<largereadwrite/>
		<aiorsize>4096</aiorsize>
		<aiowsize>4096</aiowsize>
		<aiowbehind/>
		<if/>
		<pwdsrv/>
		<winssrv/>
		<timesrv>no</timesrv>
		<doscharset>CP437</doscharset>
		<unixcharset>UTF-8</unixcharset>
		<loglevel>1</loglevel>
		<share>
			<uuid>f716d345-52c2-485a-bc92-e21ae5d77573</uuid>
			<name>backups</name>
			<path>/mnt/data/backups</path>
			<comment>backups</comment>
			<browseable/>
			<guest/>
			<inheritpermissions/>
			<hidedotfiles/>
			<shadowcopy/>
			<shadowformat>%Y%m%d_%H%M_autosnap_type%S</shadowformat>
			<zfsacl/>
			<hostsallow/>
			<hostsdeny/>
		</share>
		<share>
			<uuid>01b7c1f5-b91a-40b2-88dd-c14d5479bb32</uuid>
			<name>dropbox</name>
			<path>/mnt/data/dropbox</path>
			<comment>dropbox</comment>
			<browseable/>
			<guest/>
			<inheritpermissions/>
			<hidedotfiles/>
			<shadowcopy/>
			<shadowformat>%Y%m%d_%H%M_autosnap_type%S</shadowformat>
			<zfsacl/>
			<hostsallow/>
			<hostsdeny/>
		</share>
		<share>
			<uuid>07d06e3d-97b0-4509-9574-66b772f62005</uuid>
			<name>library</name>
			<path>/mnt/data/library</path>
			<comment>library</comment>
			<browseable/>
			<guest/>
			<inheritpermissions/>
			<hidedotfiles/>
			<shadowcopy/>
			<shadowformat>%Y%m%d_%H%M_autosnap_type%S</shadowformat>
			<zfsacl/>
			<hostsallow/>
			<hostsdeny/>
		</share>
		<share>
			<uuid>e3e5f7da-2b31-41aa-8111-c0bd1d8b5e5c</uuid>
			<name>media</name>
			<path>/mnt/data/media</path>
			<comment>media</comment>
			<browseable/>
			<guest/>
			<inheritpermissions/>
			<hidedotfiles/>
			<shadowcopy/>
			<shadowformat>%Y%m%d_%H%M_autosnap_type%S</shadowformat>
			<zfsacl/>
			<hostsallow/>
			<hostsdeny/>
		</share>
		<share>
			<uuid>cc4cd143-27f7-428f-b58a-e692d2341163</uuid>
			<name>scripts</name>
			<path>/mnt/data/scripts</path>
			<comment>scripts</comment>
			<browseable/>
			<guest/>
			<inheritpermissions/>
			<hidedotfiles/>
			<shadowcopy/>
			<shadowformat>%Y%m%d_%H%M_autosnap_type%S</shadowformat>
			<zfsacl/>
			<hostsallow/>
			<hostsdeny/>
		</share>
		<enable/>
	</samba>

This is a followup of my previous post on the same subject; I believe I have now correctly installed N4F by reading and following the instructions
(instead of winging it!).

Note earlier 1349 of N4F was created directly from embedded using Win32DiskImager, so first correct this:

With N4F...1349 attempt to access SMB shares by Win7 & Android Clients--success.

1. Save running configuration of 1349.
2. Create live usb using NAS4Free-x64-LiveUSB-9.3.0.2.1349.
3. Boot live usb and then select option 9 & follow prompts to install embedded on another USB flash.
4. Power off and remove live
5. Boot from new embedded stick
6. Restore running configuration.
5. N4F reboots with 1349.
********At this point N4F...1349 is running in a correctly generated live USB********
7. Disable Extended GUI
8. Use "firmware upgrade" from GUI supply NAS4Free-x64-embedded-9.3.0.2.1391.img
9. N4F reboots with 1391

With N4F...1391 created as above attempt to access SMB shares by Win7 & Android Clients--fail.
FWIW, access by the N4F web gui "Advanced|File Manager" works just fine.

By reverting to 1349 using the web gui, SMB access is restored!

[karlandtanya]

I've narrowed it down to some additional package causing the issue.
I've got the following installed in a unionfs:
-zrep with ksh93 and perl5
-dnsmasq
-mysql
Also some nas4free extensions are installed
-extended-gui
-rrdgraphs

If I remove all those the problem goes away.
This weekend or next I will add them back one by one and see if I can narrow it down!

[zoon01]

I've narrowed it down to some additional package causing the issue.
I've got the following installed in a unionfs:
-zrep with ksh93 and perl5
-dnsmasq
-mysql
Also some nas4free extensions are installed
-extended-gui
-rrdgraphs

If I remove all those the problem goes away.
This weekend or next I will add them back one by one and see if I can narrow it down!

Glad you found out where the problem was.
Please inform the extension maker of broken extension.

[turdburglar]

Anyone test to see if the Samba/ZFS hanging issue still persists?

viewtopic.php?f=78&t=8340#p50626

[karlandtanya]

Glad you found out where the problem was.
Please inform the extension maker of broken extension.

As it happens, the problem was not the additional packages, but my method of installing those packages.
Briefly, by using a persistent filesystem in the zpool and unionfs to mount it above /usr/local and /var/db, I installed packages on top of N4F embedded, which packages persisted through reboots and firmware upgrades.
That worked just fine until I upgraded N4F.
HOWEVER...Turns out N4F adds stuff at runtime in /usr/local, too. Presumably because that's the correct place to do stuff like that...
So...I had parts of samba from 1349 mounted above those same parts of samba that 1391 needed!

Solution (so far) was to mount above while I add and below during normal operation (when N4F adds). Details are here, FWIW.
persistently install zrep in N4F embedded using unionfs above and below

thanks to all for your hard work and patient advice!

[kfnas]

Anyone test to see if the Samba/ZFS hanging issue still persists?

viewtopic.php?f=78&t=8340#p50626

yes, the dos attrib still makes issues, as I wrote before, I'm recomendig to disable dos attrib under the global config or under share (in case of ZFS)

just to be sure, you can attach under any share parameters following

Code: Select all

vfs objects = zfsacl
inherit permissions = yes 
store dos attributes = no
ea support = no
map archive = no
map hidden = no
map system = no
map readonly = no
nfs4:mode = special
nfs4:acedup = merge
nfs4:chown = yes

some of those parameters may be presented already under global/share, but this is sure
the displayed config is the config, where ZFS acls (NFS4 type) are natively used with SAMBA
for underlying ZFS following parameters under pool/dataset is mandatory

Code: Select all

aclinherit=passthrough
aclmode=passthrough

what I cannot understand is, why developers ignoring? my setences, results and dont even react here... same as many of my question in forum...

looks like I have to setup an account on sourceforge (where the code is distributed) to get in touch with developers? Pehraps they using this forum only as 3rd class train to answer only beginners... thus I'm not feeling like that........ who knows...

@developers please react
@all (samba) why interaction with inherit permissions = yes and inherit acl =yes does screw the inheritance (ZFS)?
my goal is to set up N4F, that ZFS ACL/inheritance are governed solely by ZFS and samba is accepting the inheritance/can modify it..
looks like only

Code: Select all

 inherit permissions = yes

is the solution, but either does not work 100%

[Earendil]

Embedded should not be extracted and wrote by any tool! That's no longer supported because of partitions layout and other changes.

Perform embedded upgrade by webgui or use livecd/lives to do an install/upgrade.
If you do not install/upgrade as we advise you can suspect ununpredictable behaviors of the system.

Regards,
zoon01

This is a shocker. I have been using Win32DiskImager and m0n0wall for ages. I tried to find out how to use LiveCD and LiveUSB and it is not clear on the website nor in the wiki. I assume when using LiveCD or LiveUSB there is an option for embedded? Maybe I gave myself an action item to let others know when I use either download to upgrade...

Still, I used Win32DiskImager on .1349 before I saw your post and this is what you get - you cannot subsequently upgrade via NAS4Free itself. At least nothing blew up, N4F runs fine as is.

NAS4Free%20embedded%20install%20with%201349.jpg

[CummingsSM]

I tried to find out how to use LiveCD and LiveUSB and it is not clear on the website nor in the wiki. I assume when using LiveCD or LiveUSB there is an option for embedded? Maybe I gave myself an action item to let others know when I use either download to upgrade...

The process of using the "Live" media to install embedded (or full) is pretty straight forward. You just boot from LiveCD or LiveUSB and then select install (option 9, IIRC) from the menu.

I did this through a virtual machine, so I essentially installed embedded straight to my USB flash drive, booted the physical system from that USB drive, configured the network adapter for DHCP and then uploaded my previously saved config from the WebGUI. I used VMWare Workstation, but you can do the same thing with free tools (VMWare Player, Hyper-V, Microsoft VirtualPC or Oracle VirtualBox). But if you have two ISB sticks or an optical drive, you can just do the install.

[alexey123]

Hi
I have strangle issue when I tried connect to NAS 9.3.0.2 - Nayla (revision 1391) 1 from my ubuntu 12.04 via krusader (ssh).

Connect to server over terminal or nautilus work without problem.
Krusader work perfect with old 9.2 based machine.
More - I create jail on 9.3.0.2 machine, enable sshd into, add user and krusader connect to jail successfully.

My question - how to give work my krusader ( I LIKE built-in editor) with 9.3 based NAS ?

[kfnas]

Hi
I have strangle issue when I tried connect to NAS 9.3.0.2 - Nayla (revision 1391) 1 from my ubuntu 12.04 via krusader (ssh).

Connect to server over terminal or nautilus work without problem.
Krusader work perfect with old 9.2 based machine.
More - I create jail on 9.3.0.2 machine, enable sshd into, add user and krusader connect to jail successfully.

My question - how to give work my krusader ( I LIKE built-in editor) with 9.3 based NAS ?

those

Code: Select all

curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1ssh-dss>aes128-ctr,aes192-ctr,aes256-ctr,chacha20-poly1305@openssh.com>aes128-ctr,aes192-ctr,aes256-ctr,chacha20-poly1305@openssh.comŐumac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1Őumac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1none,zlib@openssh.comnone,zlib@openssh.com

are supported by N4S by default (SSH-2.0-OpenSSH_6.8-hpn14v5 FreeBSD-openssh-portable-6.8.p1_4,1)

try to use DH group 14 SHA1 instead... of DH group 1 SHA1

or

edit the additional parameters under ssh service (not recomended)

Code: Select all

KexAlgorithms=diffie-hellman-group1-sha1

[alexey123]

or
edit the additional parameters under ssh service (not recomended)

Code: Select all

KexAlgorithms=diffie-hellman-group1-sha1

Thank you very match - this way work = so RECOMENDED

[kfnas]

or
edit the additional parameters under ssh service (not recomended)

Code: Select all

KexAlgorithms=diffie-hellman-group1-sha1

Thank you very match - this way work = so RECOMENDED

I would not recomend it in terms of security over internet, on the LAN it is no threat

[daoyama]

I have strangle issue when I tried connect to NAS 9.3.0.2 - Nayla (revision 1391) 1 from my ubuntu 12.04 via krusader (ssh).

Connect to server over terminal or nautilus work without problem.
Krusader work perfect with old 9.2 based machine.
More - I create jail on 9.3.0.2 machine, enable sshd into, add user and krusader connect to jail successfully.

My question - how to give work my krusader ( I LIKE built-in editor) with 9.3 based NAS ?

New OpenSSH use strong encryption only, weak protocol is rejected by default.
So you must use strong encryption (recommend) or accept weak encryption in server side (kfnas said).

[daoyama]

@developers please react
@all (samba) why interaction with inherit permissions = yes and inherit acl =yes does screw the inheritance (ZFS)?
my goal is to set up N4F, that ZFS ACL/inheritance are governed solely by ZFS and samba is accepting the inheritance/can modify it..

At this time, WebGUI can't handle fs specific code before selecting the path by the user.
Please don't assume ZFS path. We must handle UFS, NTFS and others if possible.

[kfnas]

@developers please react
@all (samba) why interaction with inherit permissions = yes and inherit acl =yes does screw the inheritance (ZFS)?
my goal is to set up N4F, that ZFS ACL/inheritance are governed solely by ZFS and samba is accepting the inheritance/can modify it..

At this time, WebGUI can't handle fs specific code before selecting the path by the user.
Please don't assume ZFS path. We must handle UFS, NTFS and others if possible.

sure! I do understand that and so long there should be share base settings differently modified by underlying ZFS/UFS/NTFS...

I'm personaly right now focused solely on ZFS for checksuming (SHA256 [I have personal bad experience with the default fletcher2), encrypting and LZ4 compression reasons running also on single drive instead of UFS where only posix acl are supported and no inheritance (some bsd forums means it should be anyway supported on the 2.0 version of UFS..it isn't..)
The goal is (doesn't matter of GUI since all extra settings might be setted via extra options) to have the ability of
-acl inheritance (NFS4) via shell
-acl inheritance (NFS4) via SAMBA
-with or without AD
I have tested a lot of setups SAMBA/ZFS to find the correct answer (yes, have to drop XATTRIB of SAMBA/DOS, but should not be the point for local auth)...
anyway.. still fighting with issues as (for instance, inheritance of read attrib is always created by samba even when parrent object does not have it..) and many more...

I would welcome an open discussion either on this forum or offline for setting the things right.. THIS would be then passed to this forum/users to correct set up small/big nas with more users then one with complex read/write allowance and diversity of user group rights...

I do need to yelly in for an audience, since this topic is a fundamental thing in NAS enviroment.. so the ZFS/backup is...

for instance a bsd guru should be able to cook with zfs and samba guru optimal settings where for instance file flags (arch), bsd set GID/SID are (SID) kernel supported and all together coocked on zfs without extra DOS attrib, while zfs upon my research on freebsd platform does not support the xattrib yet or never.... there are other options, perhaps not optimal for speed.. and performance even in small enviroment should be an concern...

where I have to ring the bell?

[hastdotwhat]

or
edit the additional parameters under ssh service (not recomended)

Code: Select all

KexAlgorithms=diffie-hellman-group1-sha1

Thank you very match - this way work = so RECOMENDED

I would not recomend it in terms of security over internet, on the LAN it is no threat

Over the Internet it's no threat either, group-1 uses the Oakley 1024-bit MODP DH group with SHA-1, neither of which are anywhere close to broken.

[NAS4Free4Me]

@ kfnas: +1 (way to stay on it and track it fully - kudos to you!)

@ devlopers: being you are working on the Beta 10.x coding this would be the PERFECT time to get this issue corrected (as described by kfnas). This way it will provide a strong foundation of the correct code to eliminate the issue (bug), and at the same time won't be an issue that was corrected mid stream. kfnas has all but outlined the entire problem so the roadmap of correction code shouldn't be that difficult. He as even gone as far as wanting an open forum or offline so the matter can be corrected. Awesome! A user offering to help, has done the majority, if not all the trouble shooting and is willing to work with you so the code can be corrected. Sound like a win win to me. Granted, it may take a bit more time to release the Beta code to Gold but this (major) issue would be finally resolved.

JMO

[daoyama]

Personally, I feel "Store DOS attributes" OFF by default is reasonable.
Do you have objection?

"Extended attributes" on ZFS page is prepared for future use, but it's not supported on 11-CURRENT!
I feel we don't need this setting.

[NAS4Free4Me]

Hi

In regards to "Store DOS attributes": No problem if set to OFF by default; but what happens when turned on? Problems or conflict? If yes, what then?

In regards to "Extended attributes": what does future use mean? Never? M$ used to declare reserved for future use, it just was never used OR if it was it was undocumented. This caused all sorts of headaches.

Regarding both: What if N4F is used in mixed OS (Window/Linux/etc - stand alone, workgroup, Server, AD, etc) environment? Windows and Linux handle attributes VERY differently and in a mixed environment this could spell disaster. Inherited rights is a norm regardless of the OS and if each OS can't tell what the other is doing then that sounds like a recipe for disaster. My fear is if N4F is going to pooch that item then people will abandon it because it's not reliable. I responded to another thread along the same lines and suggested looking at FreeNAS' code as they don't seem to be having any issues with attributes (using latest and greatest ZFS and Samba code). viewtopic.php?f=78&t=8340&start=25#p50885 Again let me state, I'm not a fan of FreeNAS (that's why I'm championing so hard to get it right in N4F), I bailed from them the instant N4F was offered.

Developers thank you so much for all the hard work you have done! Please, please don't corner's now. This issue need to be done correctly so users in mixed OS environments (or not) do not fear using N4F and know it's a solid from the get go.

Thank you in advance for reading and responding.