AFP Binding Issue..

[Hassan Aftab]

Hello guys!

I have recently setup a Time Machine server, following the guide and it works fine as long as it remains on the native VLAN. I have looked on the forum and else where and can't find a similar problem.

My setup:

I am using the stable train of 9.10 (just updated to 9.10.2-U3, but the problem has been before this). Two interfaces bonded into lagg0, with multiple VLANs. I want to use the Native VLAN primarily as the management interface and doesn't want to allow users on it.

The problem:

AFP automatically binds itself to the native VLAN, after giving the following error on the VLAN I actually want to advertise Timemachine on:

Apr 24 14:47:32 nas02 afpd[4585]: No suitable network config for TCP socket

The same error also comes on other vlans.

What I have done:

Restarted the server and service.
Applied all the recent patches.
Verified lagg0 works (have set it up following the guide)


Any suggestions? Thanks

Bug: https://bugs.freenas.org/issues/23646

 

[dlavigne]

This sounds like a bug. Please create a report at bugs.freenas.org and post the issue number here.

 

[Nuc@freeNAS]

I am having the same problem. I noticed that there was no new information on your Bug report. Have your heard anything outside this channel about a possible fix?

Thanks,
T.

 

[Hassan Aftab]

Not yet, mate.
The problem seems to be with LACP interfaces.
I have another FreeNAS instance running, with the exact same configuration, but without any link aggregation, and it works fine.

I searched around a lot, but there aren't many FreeNAS users using LACP with TimeMachine (which surprises me). Right now, I have just moved on. If you come across something, please update me and we can have a chat. Thanks

@dlavigne Can you please update me with the status of this request. Thanks

 

[dlavigne]

@dlavigne Can you please update me with the status of this request. Thanks

Please add a comment to that ticket asking the dev if he's made any progress or needs any additional information.

 

[Sigurd]

Looks like I have a similar problem that I posted in the thread I created.