NAS4Free 9.2.0.1.943 Released (FreeBSD 9.2-RELEASE p3)

[vandy]

I just played around with this and found mDNSResponder is not starting in this release.

Doing a similar workaround as listed here http://sourceforge.net/p/nas4free/bugs/149/ fixes the issue.

Code: Select all

nano /var/etc/mdnsresponder.conf

example: current file shows

Code: Select all

nas4free
_device-info._tcp. local.
1
model=Xserve

and change to:

Code: Select all

nas4free
_device-info._tcp local.
1
model=Xserve

and then

Code: Select all

/usr/local/bin/mDNSResponderPosix -b -f /var/etc/mdnsresponder.conf

fixes the issue and I am able to see itunes/daap server on my network. It seems that extra"." before local. is causing problems.

[RedAntz]

Hi vandy,

Did you do full install or upgrade ?

[vandy]

Hi vandy,

Did you do full install or upgrade ?

Hi RedAntz, I did a full clean install.

[RedAntz]

Mind if I suggest you guys to carry on this WOL discussion in a new thread ? That way it is easier for topic searching and for future reference.
Moved viewtopic.php?f=58&t=5916

[OlafD01]

SUCCESS!!!!
With an added name-string in /var/etc/mdnsresponder.conf zeroconf/bonjour worked like a charm!

here --> viewtopic.php?f=78&t=5845&start=25#p32013
it's broken, : viewtopic.php?f=78&t=5847&start=25#p31998

Hi,
between .847 and .943 there's a difference in the config-file /var/etc/mdnsresponder.conf - a line is missing.

With this line added (the name of the Server), zeroconf/bonjour is working just fine ...

Code: Select all

# in .847 ##################### in .943 #################################################
                               
nas4free-v847                 #                                 <--- This line is missing
_device-info._tcp. local.     # _device-info._tcp. local.
1                             # 1
model=Xserve                  # model=Xserve
                              #
nas4free-v847                 # nas4free-v943
_http._tcp. local.            # _http._tcp. local.
80                            # 80
path=/index.php               # path=/index.php
                              #
nas4free-v847                 # nas4free-v943
_ssh._tcp. local.             # _ssh._tcp. local.
22                            # 22

To test, do modify '/var/etc/mdnsresponder.conf' and then

Code: Select all

killall -QUIT mDNSResponderPosix ; /usr/local/bin/mDNSResponderPosix -b -f /var/etc/mdnsresponder.conf

... It seems that extra"." before local. is causing problems.

Sorry, the "." after '_device-info._tcp' doesn't change anything - but an added name does,
for now - but an missing dot can cause some problems in future releases !

And if you change the name of the server, via webgui, this only changes the names within the services, but
it doesn’t add the new name at the top of the config-file, maybe that's what's broken.

Regards, OlafD01

[OlafD01]

In addition to this post: zeroconf/bonjour is working out of box - if and only if you enable AFP and specify a
Server-name there (it could be left disabled afterwards), the default one doesn't get populated - that’s a bug !

http://nas4free-943/services_afp.php > Server Name
---> if empty Server Name <---
Comment:
Name of the server. If this field is left empty the default server is specified.

Does the devs get this information or should I pm them ... ?

Regards, OlafD01

P.S.
There was a change in the source ( /trunk/build/ports/mDNSResponder/files/mdnsresponder.in ):

Code: Select all

from
67      -v "//system/hostname" -n \
68      -o "_device-info._tcp. local." -n \

to
67      -v "//afp/afpname" -n \
68      -o "_device-info._tcp. local." -n \

[bafforosso]

In addition to this post: zeroconf/bonjour is working out of box - if and only if you enable AFP and specify a
Server-name there (it could be left disabled afterwards), the default one doesn't get populated - that’s a bug ![/code]

Thank you! works like a charm with a specified AFP server name (and so does my Apple TimeMachine backup)!

[vandy]

I finally got link aggregation working. It seems the webgui doesn't modify /etc/rc.conf properly.

although setting up lag in the gui puts the correct lines in /etc/rc.conf:

Code: Select all

ifconfig_igb0="up"
ifconfig_igb1="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto lacp laggport igb0 laggport igb1"
ipv4_addrs_lagg0="192.168.1.100/24"

but the gui didn't remove the reference to the previous interface:

Code: Select all

ipv4_addrs_igb0="192.168.1.100/24"

At this state, your traffic will not be passed properly, unable to reach the nas. removing the ipv4_addrs_igb0="192.168.1.100/24" line in /etc/rc.conf fixes this and link aggregation works as it should.

edit: this also fixes the "dhcp: bad value" error during boot up.

[kernow]

What's happened to the upgrade process recently? it used to go so smoothly.

I'm on 9.1.0.1 - Sandstorm (revision 847) and have no idea how to upgrade to the latest anymore because I did it through the GUI every time and it was fine apart from backing up my config beforehand. Now I'm wary of it hosing the whole configuration.

Please make it work through the normal webgui again.

[raulfg3]

What's happened to the upgrade process recently? it used to go so smoothly.

I'm on 9.1.0.1 - Sandstorm (revision 847)

it's a bit different because you do a upgrade from BSD 9.1 to BSD 9.2 and reserved space on embeded install grow from 384MB in 9.1.0.1.847 to 1000MB in 9.2.0.1.943 so normal webGUi upgrade can be dangerous (once said it, some users upgreded and do not notice problems).

Once you finally upgrade to 9.2.0.1.943 your next updates are from webGUI like old ones.

[kernow]

Right, so I guess I should back up my config, use another usb stick in the meantime and apply config after? Use some windows imaging tool to write the file to the new USB stick?

edit: wouldn't the size difference only be a problem if your USB stick was too small? I have an 8GB one in there.

Eh, thought I'd be brave and try the webgui upgrade method. Waiting for it to come back up .. if ever


Well that worked fine, I just had to clear config and reimport the disks.

Still using fuppes? oh my god.

[davidb]

I finally got link aggregation working. It seems the webgui doesn't modify /etc/rc.conf properly.

although setting up lag in the gui puts the correct lines in /etc/rc.conf:

Code: Select all

ifconfig_igb0="up"
ifconfig_igb1="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto lacp laggport igb0 laggport igb1"
ipv4_addrs_lagg0="192.168.1.100/24"

but the gui didn't remove the reference to the previous interface:

Code: Select all

ipv4_addrs_igb0="192.168.1.100/24"

At this state, your traffic will not be passed properly, unable to reach the nas. removing the ipv4_addrs_igb0="192.168.1.100/24" line in /etc/rc.conf fixes this and link aggregation works as it should.

edit: this also fixes the "dhcp: bad value" error during boot up.

nice find, i will try this on a server of mine that LAGG hasn't worked on since about 9.1.0.1 rev431 (rev 431 is the last version that it worked for me).

[gbonny]

Running fine, iperf speeds seems to be increased a little

Anyone knows/tested whether physical RDM was fixed: http://sourceforge.net/p/nas4free/bugs/65/ ? It isn't listed as solved, though.

[anteroom]

Trying to update NAS4Free-x64-embedded-9.1.0.1.847.img (with 2x HDD on Intel Atom D410PT 2GB RAM)

I didn't noticed warning on update impossibility (seen some weird non official changelog - anyway where is always good changelog, I always trying to google it :-/) and did update via webGUI to NAS4Free-x64-embedded-9.2.0.1.943 image,
-----> FATAL ERROR on 1st boot, error on missing device or sth

So then tried to boot from fresh stick NAS4Free-x64-embedded-9.2.0.1.943 (win32 image->usb)
another -----> FATAL ERROR on 1st boot

so then I prepared another (this time liveUSB) NAS4Free-x64-LiveUSB-9.2.0.1.943.img (win32 image->usb), this time the nas4free is boting OK but when I hit '9' -> Install embedded to CF/USB ... i have only 'da0' (my two HDDs), NO 1st usb stick (which I boot from), nor 2nd usb stick (which I wan't to install onto) so can't continue update in any known way.

Appreciate for any help.

[RedAntz]

Hi anteroom,

9.1 to 9.2 is not a straightforward update due to increase of disk space required. Please read CHANGELOG here :

https://sourceforge.net/projects/nas4fr ... 2.0.1.943/