similar to: FreeNAS

Displaying 20 results from an estimated 5000 matches similar to: "FreeNAS"

2012 Jul 15
0
[Freenas-announce] FreeNAS 8.2.0-RC1
Opensolaris this ain''t, but zfs-related nevertheless. ----- Forwarded message from Josh Paetzel <josh at ixsystems.com> ----- From: Josh Paetzel <josh at ixsystems.com> Date: Fri, 13 Jul 2012 12:01:24 -0700 To: freenas-announce at lists.sourceforge.net Subject: [Freenas-announce] FreeNAS 8.2.0-RC1 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120506
2018 Sep 20
2
4.8.5 + TimeMachine = Disk identity changed on every connect, cannot backup
Hi, I configured Samba 4.8.5 on Debian (Buster) with vfs_fruit as a TimeMachine destination and while it detects it and does the initial backup to some extent (30GB out of 200GB), TimeMachine then fails with a message about the disk identity having changed. Options are “don’t backup” and “backup anyway”. When using “backup anyway”, the backup creates a secondary sparse image and starts from
2016 Oct 10
0
Mac OS Timemachine over SMB
Hello Kevin, Mac OS by default looks for TimeMachine volumes over AFP not CIFS-SMB… Like you, I experimented with Samba a couple of years ago to try to get it to work anyway. With a few modifications on the client’s part and some configuration on the Samba server I got it to work… but recovery only worked for clients that I had configured in advance… Recovery with the Mac OS tools (Migration
2020 Apr 07
1
issues with Time Machine - did macOS change how they handle things?
TL;DR: Time Machine cannot create a *new* backup on my shared drive, but can add to an *existing* backup. I'm running macOS Catalina and my Time Machine backs up to a Debian 10 server with NetAtalk and Avahi. Since Mavericks macOS has preferred SMB, and given SMB is marginally faster I decided to switch to using SMB for the Time Machine shares. On a fresh AFP share I can start a new Time
2010 May 13
6
Re: Problem release that does not work
Anex. Thanks Tom. 2010/5/12 Tom Eastep <teastep@shorewall.net> > On 5/12/10 2:47 PM, Orlandinei Vujanski wrote: > > Tom, all right? > > > > Until yesterday my shorewall was working perfectly, but today it stopped > > working. I already restarted the server, already changed the rules and > > did not work. > > > > My shorewall this in 4.0.15
2011 Jan 07
3
4.4.16 RC 1 Testing Status?
Do those of you who are testing 4.4.16 RC 1 plan to do additional testing or can we consider 4.4.16 ready for release? Please let me know by close of business on Tuesday, Jan 11 if you plan additional testing. Thank you for helping with the testing effort, -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not
2011 Jan 07
3
4.4.16 RC 1 Testing Status?
Do those of you who are testing 4.4.16 RC 1 plan to do additional testing or can we consider 4.4.16 ready for release? Please let me know by close of business on Tuesday, Jan 11 if you plan additional testing. Thank you for helping with the testing effort, -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not
2011 May 18
1
Shorewall 4.4.19.4
Shorewall 4.4.19.4 is now available. Problems corrected in this update: 1) Previously, the compiler would allow a degenerate entry (only the BAND specified) in /etc/shorewall/tcpri. Such an entry now raises a compilation error. 2) Previously, it was possible to specify tcfilters and tcrules that classified traffic with the class-id of a non-leaf HFSC class. Such classes are
2012 Oct 26
0
[Freenas-announce] FreeNAS 8.3.0-RELEASE
----- Forwarded message from Josh Paetzel <josh at ixsystems.com> ----- From: Josh Paetzel <josh at ixsystems.com> Date: Fri, 26 Oct 2012 09:55:22 -0700 To: freenas-announce at lists.sourceforge.net Subject: [Freenas-announce] FreeNAS 8.3.0-RELEASE User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
2009 Jul 12
2
Shorewall 4.4.0 Beta 4
Beta 4 is now ready for testing. http://www.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta4/ ftp://ftp.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta4/ ---------------------------------------------------------------------------- P R O B L E M S C O R R E C T E D I N 4 . 4 . 0 Beta 4
2013 Nov 23
3
Shorewall 4.5.21.4
Shorewall 4.5.21.4 is now available for download. Problems corrected since 4.5.21.3: 1) The Broadcast actions have been corrected: o --dst-type BROADCAST has been removed from the IPv6 version o A superfluous DROP rule in the IPv4 version has been suppressed. 2) Previously, if an HFSC class was specified with dmax but not umax, then the firewall would fail to start with the
2012 Apr 24
0
Shorewall 4.5.3 Beta 1
Beta 1 is now available for testing. Problems Corrected: 1) This version includes all defect repairs from Shorewall 4.5.2.1 - 4.5.2.3. 2) The LOCKFILE setting in shorewall.conf and shorewall6.conf had become inadvertently undocumented. It is now documented again. New Features: 1) The ''-T'' option is now supported in the Shorewall and Shorewall6
2012 Apr 24
0
Shorewall 4.5.3 Beta 1
Beta 1 is now available for testing. Problems Corrected: 1) This version includes all defect repairs from Shorewall 4.5.2.1 - 4.5.2.3. 2) The LOCKFILE setting in shorewall.conf and shorewall6.conf had become inadvertently undocumented. It is now documented again. New Features: 1) The ''-T'' option is now supported in the Shorewall and Shorewall6
2009 Jun 30
0
Shorewall 4.4.0 Beta 3
Beta 3 is now available for testing. http://www.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta3 ftp://ftp.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta3 ---------------------------------------------------------------------------- P R O B L E M S C O R R E C T E D I N 4 . 4 . 0 Beta 3
2012 Jun 27
0
Shorewall 4.5.5.2
Shorewall 4.5.5.2 is now available for download. Problems Corrected: 1) Previously, when ipp2p was used in the /etc/shorewall/tcpri file, the generated code for saving the packet mark was clearing the connection marks fields not having to do with traffic shaping. It now only alters the traffic-shaping part of the connection mark. 2) Shorewall 4.4.11 allowed UID and GID ranges
2009 Dec 19
0
Route Filtering with Kernel 2.6.31 and later
In kernel 2.6.31, the handling of the rp_filter interface option was changed incompatibly. Previously, the effective value was determined by the setting of net.ipv4.config.dev.proxy_arp logically ANDed with the setting of net.ipv4.config.all.proxy_arp. Beginning with kernel 2.6.31, the value is the arithmetic MAX of those two values. Additionally, a ''loose'' routefiltering
2010 Nov 25
0
Shorewall in OpenSuSE repositories
Togan Muftuoglu has just informed me that Shorewall is now available in the following repositories: <http://download.opensuse.org/repositories/security:/netfilter/openSUSE_11.2> <http://download.opensuse.org/repositories/security:/netfilter/openSUSE_11.3> <http://download.opensuse.org/repositories/security:/netfilter/openSUSE_Factory> Thanks Togan!! -Tom -- Tom Eastep
2013 Mar 07
0
Shorewall 4.5.14 RC 1
In case you haven''t guessed by recent development list traffic, RC 1 is now available for testing. There are no new features since Beta 3 -- Just bug fixes. Thank you for testing, -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car
2013 Mar 07
0
Shorewall 4.5.14 RC 1
In case you haven''t guessed by recent development list traffic, RC 1 is now available for testing. There are no new features since Beta 3 -- Just bug fixes. Thank you for testing, -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car
2010 Jul 09
0
Shorewalll 4.4.11 RC 1
RC 1 is now available for testing. This version corrects several problems in Beta 3: 1) Release notes now correctly refer to FORWARD_CLEAR_MARK rather than CLEAR_FORWARD_MARK. 2) The NET3 column in /etc/shorewall/netmap now works correctly. 3) A missing closing quote in the generated script when using REQUIRE_INTERFACE=Yes has been corrected. 4) The compiler now correctly detects the