avahi VS libsixel

I don't know any that run on Windows. There's Avahi for Linux and BSD (and WSL probably), it allows manual configuration of many aspects of mDNS/DNS-SD. It won't allow multiple host names though, and it binds to interfaces, not IP addresses (or anything else you can easily create multiple instances of on Windows).

Apple literally invented CUPS, the most common Unix printing framework in use today. CUPS is the engine for iOS, MacOS, iPadOS, AirPrint, etc. I am really not interested in a debate about whether AirPrint and Apple are crappy systems or are the things to blame with my printer. I know for a fact they are not - because I am a developer and I know how mDNS works, and I know the specific problem my printer has. My Canon printer's operating system has an old, unpatched version of AVAHI that has a lot of problems playing nice with dns-sd and has a known issue with name collisions on it's own interfaces. It's no surprise it doesn't work well with AirPrint for anyone who's familiar with AVAHI.

Depending on how you have Wireguard set up, the host the end point resides on probably isn't forwarding the multicast traffic down the Wireguard tunnel. So you might need to run something like Avahi on the Wireguard endpoint and have it set up on the Wireguard interface and the interface that can see the AirPrint printer.

mDNS is multicast, but you can technically grab the packets and force it down another network. The issue is that I've not seen this implemented on OPNSense before. Others have managed to pull this off: https://www.reddit.com/r/WireGuard/comments/g80bxf/cant_get_zeroconfavahimdns_reflection_to_work/ https://github.com/lathiat/avahi/issues/262

Does the autodiscovery for NoMachine work on Wireguard VPNs as well?

I use, and love, Wireguard, but I think out of the box Wireguard does not support multicast. And I expect that NoMachine also depends on multicast to do its autodisovery. Probably with mDNS and DNS-SD.

Upon googling now, it does seem like some people have successfully been able to get multicast working over Wireguard. For example:

> Hey! Just in case you (or anyone else browsing this) still needs this, i've got avahi working over my wireguard client-to-site connection. I can access my home LAN computers using hostname.local from any VPN-connected device.

> I think the missing piece was adding 224.0.0.251/32 and ff02::fb/128 (multicast addresses) to allowed ips.

from https://www.reddit.com/r/WireGuard/comments/g80bxf/cant_get_...

Likewise, there seem to be some additional useful information relating to mDNS / Avahi on this issue on GitHub, for various situations:

https://github.com/lathiat/avahi/issues/262

And here is someone who got DLNA (which also uses multicast) working through site-to-site Wireguard VPN:

https://an0n-r0.medium.com/making-dlna-through-site-to-site-...

Unfortunate, I was hoping this was a simple issue. Looks like lots of complaints out there for apple devices having this same conflict with Avahi. Sadly, it appears there is not a clear fix at this time. Main issue thread can be found here with posts from 2017 to a couple months ago.

I think OP can run Avahi on the rPi along with the controller until the mDNS feature is released.

Turned off the HomeAssistance and Homebridge, but left the raspberry pi running. Still seeing the renames. This can be an Avahi issue, possibly this https://github.com/lathiat/avahi/issues/117. Raspbian buster has Avahi 0.7, going to check if bullseye release has 0.8.

There is another thing you can try, install avahi-daemon... link

Library you can use to generate these images:

https://github.com/saitoha/libsixel

Plenty of links to other projects.

Sixels are pixels and enjoy a wide support due to how old it is.

Kitty protocol is PNG or primitives - which BTW would make it great for a GUI library.

Different tools for different needs, but if you are going for a wide support you want something simple that doesn't have 5 different types you have to separately implement and test:

> d: Direct (the data is transmitted within the escape code itself)

> f: A simple file (regular files only, not named pipes or similar)

> t: A temporary file, the terminal emulator will delete the file after reading the pixel data. For security reasons the terminal emulator should only delete the file if it is in a known temporary directory, such as /tmp, /dev/shm, TMPDIR env var if present and any platform specific temporary directories and the file has the string tty-graphics-protocol in its full file path.

> s: A shared memory object, which on POSIX systems is a POSIX shared memory object and on Windows is a Named shared memory object. The terminal emulator must read the data from the memory object and then unlink and close it on POSIX and just close it on Windows.

> What nonsense, it takes literally 15 lines of code without using anything beyond the standard library to write a client

Conveniently taking a preencoded PNG and assuming away the necessary queries of supported protocol:

> Since a client has no a-priori knowledge of whether it shares a filesystem/shared memory with the terminal emulator, it can send an id with the control data, using the i key (which can be an arbitrary positive integer up to 4294967295, it must not be zero).

> for the kitty graphics protocol. I challenge you to match that for sixel

https://github.com/saitoha/libsixel/tree/master/perl

    use Image::LibSIXEL;

Also:

https://github.com/saitoha/libsixel

contains img2sixel, which lets you dump images to the terminal. It can also do animated GIFs.

Video:

https://github.com/saitoha/FFmpeg-SIXEL

GUI apps:

https://github.com/saitoha/SDL1.2-SIXEL

and more, linked from the libsixel repository.

Not sure of Terminal emulator capabilities on Apple devices, but thanks to https://github.com/saitoha/libsixel , several applications, including emacs very much support image output in terminals.

You don't have multi-colored terminal output? Even legacy systems have long had Sixel support.

> SIXEL is one of image formats for printer and terminal imaging introduced by Digital Equipment Corp. (DEC). Its data scheme is represented as a terminal-friendly escape sequence. So if you want to view a SIXEL image file, all you have to do is "cat" it to your terminal

https://github.com/saitoha/libsixel