You may have already used Zeroconf technology and mDNS without realizing it.
It allows you to automatically assign a hostname of the type .local to a machine without configuring DNS, making it easy to access without knowing the IP address.
This is the case, for example, on Raspberry Pi (raspberrypi.local).
This can be particularly useful when the DHCP client is enabled on the controller; you simply enter its name to access it.
This technology can be implemented on WAGO controllers using “avahi”.
This package can be installed via an IPK.
Zeroconf/mDNS is supported (and normally enabled) on Windows, Android, and iOS machines.
To install it, go here:
It can also be useful for generic applications where you can prename your plc : .local
I could not get the avahi daemon to start on my CC100 without creating an ‘avahi’ group and user.
Is this the best solution or did I overlook the right way?
I think I should have started off by saying Thank You for making this tool available. It is exactly what I needed.
I updated the CC100 to FW30 with WAGOupload.
I installed the ipk as: root@CC100:~ opkg install -V3 avahi_repo_v1.0_armhf.ipk
Then when I went to check, it looked like the repo was installed and not the packages it contained: “root@CC100:~ opkg list_installed | grep avahi” returned ‘avahi_repo - 1.0’ so then I manually installed the parts: “opkg install /root/packages-avahi/libdaemon_0.14_armhf.ipk” +
”opkg install /root/packages-avahi/avahi_0.8_armhf.ipk”, and finally edited the groups.
So it looks like something I did broke the normal behavior the the installer script.
I will try to wipe the controller and factory reimage the OS, and then see if I can get the avahi install in a single step.