Koozali.org formerly Contribs.org

Avahi sur SME

Offline STRyk

  • ****
  • 184
Re: Avahi sur SME
« Reply #15 on: August 03, 2021, 11:53:43 PM »
Nous n'avancerons pas car demain il y aura encore autre chose et encore demain.

C'est incohérent de lâcher les "anciens" car la réalité c'est qu'ils existent encore.

J'efface Koozali 10.
Merci tout de même.

Offline STRyk

  • ****
  • 184
Re: Avahi sur SME
« Reply #16 on: September 08, 2021, 03:08:37 AM »
1 fonctionne bien sur un RAID (qui est un protocol de redondance de disque) ne veut rien dire, avahi est un service de resolution de nom….
Je viens seulement de comprendre que tu n'a pas compris mon texte car je parlais de "Linux unRAID" : https://unraid.net/
J'aimerai bien comprendre comment faire fonctionner Avahi sur SME 9.2 pour les anciennes machines.
Mais je passe des heures et je tourne en rond. Je ne vois toujours pas pourquoi ca ne marche pas alors que sur unRAID c'est très bien implanté et fonctionne simplement.

Offline ReetP

  • *
  • 2,958
Re: Avahi sur SME
« Reply #17 on: September 08, 2021, 12:05:57 PM »
I would like to understand how to make Avahi work on SME 9.2 for old machines.
But I spend hours and go around in circles.

Yup - and wasting your time on an unsupported operating system to cater for an ancient unsupported machine with an unsupported OS. No one here is going to help you with it for reasons we have already explained. Please stop asking or the topic will be locked.

I still don't see why it doesn't work when on unRAID it is very well established and just works.

Because Unraid is a "paid" system and has full time developers who have decided to implement it.

We are part time, not paid, and none of us have any use for Avahi on v10 and therefore no inclination to implement it. We have more urgent things to do. Personally I am still working on Affa, PHPKi, Ipsec VPN and some other stuff because I need them myself, and others need them too.

You have a few options.

Do it yourself on v9. You are on your own. Don't ask any more questions about it please.
Do it yourself on v10 as a contribution. You may get some assistance with your code, but no one is going to write it for you.
Pay someone else to write it for you.
Open a New Feature Request and if anyone here ever has any time or inclination they may one day look at it in the future. but it is unlikely.

For a starter on v10 you can read this:


You would probably need these from 'base' repo' at a minimum:


You then need to work how to:

Create a Koozali config entry including status, TCP/UDP port access etc e.g. stuff like this, though it needs more:

Code: [Select]
config set avahi-daemon service status enabled TCPPort 5353 UDPPort 5353 access public
signal-event remoteaccess-update
systemctl restart avahi-daemon.service
systemctl status -l avahi-daemon.socket avahi-daemon.service

(restart gets basic Avahi about up and running - I could see the server for a while in Finder on this Mac but it has gone again as it was a swift hack. Beyond that, good luck)

Create a new Koozali systemd service to run the service properly - see wiki - it needs modifying from the web page above
Understand what needs to go in the configuration files
Template your configuration files
How to automatically populate the configuration files when the system is updated so it works with other Koozali services - they have to work together or things like DNS will break.
Create config files to advertise services. Work out how to get file shares working with something like afp to support ancient unsupported bricks.

You need to read some of these and realise you will also need netatalk/afp for older machines as modern ones use SMB2+ and that makes this all irrelevant for modern machinery. You will probably have to build your own RPMS for that.




This article is very old and has been rendered obsolete for OS X 10.9 Mavericks and above. Apple uses v2 of the Samba protocol, dubbed SMB2 for file sharing by default now, which includes many technical advantages over AFP. On Ubuntu, the Samba package can be easily installed and configured to provide connectivity between Ubuntu und Mac OS X out of the box.

You should follow the steps in the following article only if you want to setup a Mac with an OS X version below 10.9. or you are absolutely sure you want to use AFP for file sharing.

So you will then need to work out how to advertise and allow secure access to the file shares. This is absolutely a non trivial, time consuming, and therefore expensive set of tasks.

I am one of the only devs here with a Mac, and I have zero experience or interest in Avahi/Netatalk..... I can use SMB and that is all that is required for me to work.

I've given you as much help and time as I can afford. This is a really complicated subject, hence you are struggling, and it will be cheaper and easier to just go buy a newer machine. But the beauty of open source is that the choice is yours.

Finally, please don't ask about v9.x again. If you have specific code or technical queries on v10 that are not answered in the wiki then please ask.

Good luck with your endeavours.

1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions of software
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation

Offline Jean-Philippe Pialasse

  • *
  • 1,867
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Avahi sur SME
« Reply #18 on: September 08, 2021, 01:53:53 PM »
dire cela fonctionne sur une distribution basée sur slackware sans plus d’info sur la version n’est pas tres pertinent.
C’est comme dire que le nouveau Flight Simulator ne marche pas sur MacOs 11 alors qu’il marche sur windows.

Encore une fois nous ne pouvons que t’inviter à comprendre le protocol plutôt que d’installer au hasard et espérer que cela marche.

entre autre tu as besoin de comprendre comment marche un réseau, à quoi sert un firewall, et comment le configurer pour des besoins spécifiques.