My only real missing feature with my tailnet right now is the ability to somehow bridge mDNS / Bonjour.

I know those the multicast layer2 services and I can’t really run any magic reapeater on my WiFi hotspot either but it’s LITERALLY the last missing piece to have a unified virtual network of my things that works just as if I had them all home on my WiFi.

(Mainly needing it because Apple dev tools / Xcode etc. all rely on it and won’t let me simply say “connect to the device with this IP” - no idea where that feature went.. it used to be a thing).

#tailscale #mobileDev #tailnet #mDNS #bonjour #apple #xcode #xcode16

@grimmy @pidgin really like this idea, to create a wrapper lib for #mDNS to make it platform independent around well tested, platform specific libs. #rust #libp2p tries to fully reimplement #mDNS, but I had several blocking issues with it when tried to use it on the #Qaul messenger: https://github.com/libp2p/rust-libp2p/issues?q=is%3Aissue%20state%3Aopen%20author%3AT-X
Your wrapper sounds like once it works it'll really work, with a lot less bugs.

So we're looking to implement Bonjour, aka Link Local Messaging into @pidgin 3. We had this in Pidgin 2 but we're rewriting all of the protocols.

We've decided to develop a new cross platform #mDNS client library in #c, named Hiya, to make this easier and hopefully others will find it useful as well.

I put together a high level doc that could really use a sanity check from someone with more experience, so if you know mDNS well we'd appreciate any input you can provide.

https://issues.imfreedom.org/issue/HIYA-1

@flori_man bzgl. affine Nutzer, stimme ich dir auch zu. Ist noch zu schwer zu nutzen. @videolan hat discovery über #SAP / #RFC2974 und so zumindest eine klicki-bunti Lösung zum Abrufen, das es ähnlich einfach macht wie z.B. #mDNS / #DNSSD. Aber die Skalierbarkeit von #SAP (ähnlich wie bei #mDNS) lässt noch stark zu wünschen übrig.

Just released a new crate called opslag.

It's a no_std mDNS service discovery implementation in pure Rust.

I'm hacking around with some embedded STM32 hardware and I couldn't find any suitable mDNS lib for such a use case.

#rustlang #rust #mdns

https://crates.io/crates/opslag

Fixed another thing in my #homelab that I’ve been putting off for too long: Migrated the #TimeMachine server from my client network to a server VLAN thanks to the #mDNS reflector service in my #OPNsense router.

Incidentally this also resolved an #IPv6 routing issue I had with my main #KVM #hypervisor: I was unable to make its client network bridge *not* take an IPv6 address, and so when I connected to the host from my laptop, after a number of seconds the connection simply froze. Now that TimeMachine doesn’t need to be in that network anymore, I could remove that extraneous bridge interface and confirm that ssh sessions to the physical server work flawlessly over IPv6 again.

@goodthinking
Already done the same regarding hoarding #Zim files.
Other things I do are trying to use #localfirst enabled software so I can still operate and or serve this files. #reticulum is a nice to have due to its long range and low power consumption. You also could make a hacky sneaker net with #syncthing which works via #mdns in local networks to distribute info or mails (via maildir) to trusted peers. General advice play with #encryption for hdd. And read about #opsec.

Anyone else having trouble with Nanoleafs in Home Assistant?

Having two Nanoleafs: 1 Hexagon Shapes and 1 Lines. Since a couple of weeks (obviously I dont know what (I) changed... I would say: nothing 🤣), they dont work anymore via Home Assistant (and their own App).

My Access Point still says, they are connected via wifi without any trouble. ICMP Echo Requesting them, works fine (dont know which service I could check).

Thing is, out of the sudden, Home Assistant thinks, they are reachable via IPv6 (some ULA Address, not my IPv6 and that Subnet even doesnt have IPv6).

That Home Assistant Issue pointed me to mDNS: https://github.com/home-assistant/core/issues/131643

Home Assistant seems to use https://github.com/milanmeu/aionanoleaf library which doesnt correctly parse IPv6/Port things.

Im wondering, if anyone else having some strange behavior with Nanoleaf and mDNS in their network?

Just trying to figure out whats going on and it doesnt look like its only a bad library in Home Assistant (there is definitely a Bug in parsing IPv6 addresses) but some Nanoleaf Network Issues. As I mentioned: Nanoleafs sometimes doesnt report their IPv4 Address via mDNS - but still are reachble via ICMP.

#nanoleaf #ipv4 #ipv6 #mdns #multicast #icmp #smarthome #homeassistant #fedihelp

Also reported the two issues we experienced with #Qaul and #mDNS to the underlying #rust #libp2p a few days ago. And already got promising feedback. Hopefully we will be able to use Qaul's #mDNS based peer discovery soon in our #Gluon / @batadv based #Freifunk networks once they get addressed:
https://github.com/libp2p/rust-libp2p/issues/5783
https://github.com/libp2p/rust-libp2p/issues/5790

#IPv6 #multicast #offthegrid #mesh #meshnetwork

Oh - I misread a #Wireshark output. The #rust #libp2p library that #Qaul uses not only sends #mDNS of 1100 bytes, but: >4000 bytes... I missed the IP fragments before when I filtered just for the keyword "mdns" in Wireshark...

#multicast

I can't stand #mDNS. Not because it isn't useful. But because it promises something extremely convenient, then breaks all. the. time. I won't even try to rely on it anymore.

#networking

Anyone got tips on troubleshooting a process with high context switching?

It's `avahi-daemon`, so I'm guessing it's something syscall network access related? but 5353 isn't a privileged port and it should be using some kind of wait on the socket, right?

#Linux #mDNS #Avahi #AvahiDaemon #SysAdmin

Can anyone recommend a crate for mDNS resolution?

Hickory-DNS's stuff is still experimental and it's kinda beyond my ability to build it from scratch

tag anyone who can help 🙏

#Rust #RustLang #mDNS

This seems to leave our options at either having the machines themselves do DDNS with an actual public domain or I write something up to interface with the OPNsense API to manage Unbound overrides. If Unbound has a decent API it might be better to code against that. But what interface to expose? RFC2136 is theoretically the standard for DDNS but my hunch is that's about as popular as mDNS. Still, I might be able to find some existing clients or tools for that. Alternatively I could have the program browse mDNS responses and create overrides for all found, which centralizes the responsibility nicely...

#DNS #mDNS #OPNsense #Unbound #UnboundDNS

mDNS for Unbound on OPNsense might be a dead end. Looks like plenty mainstream stuff just ignores nsswitch.conf entirely. So even if I get that path working it may not take to Unbound.

DNS may be hated, but mDNS is unloved.

#Networking #DNS #mDNS #OPNsense #HomeLab

@arichtman I've recently added a short chapter about #mDNS to the #FreeBSD Handbook. Perhaps it can be of some use to you.

https://docs.freebsd.org/en/books/handbook/network-servers/#network-zeroconf

#zeroconf #freebsdhandbook

Set `nsswitch.conf` hosts to **just** `mdns` and no luck, `tcpdump` shows no packets outbound on port 5353 on the LAN interface.

How in the heck do you get this thing to do mDNS resolution?

#Networking #OPNsense #mDNS #DNS #FreeBSD #BSD

Update: no, base does not include any mDNS. I have located OPNsense-compatible ports including `avahi-app` + `nss_mdns` and `mDNSResponder(_nss)`. I'll try installing these at...not midnight.

Wait, does FreeBSD not actually have mDNS as an option at all for resolution? That would sure explain it being ignored...

https://man.freebsd.org/cgi/man.cgi?query=nsswitch.conf&apropos=0&sektion=5&manpath=FreeBSD+14.1-RELEASE&arch=default&format=html

#FreeBSD #BSD #DNS #mDNS #Networking #OPNsense

@pidgin @ffhl thanks to @wonka and @cuechan for testing it with me after all these years! This was also so far only a test between Linux systems.
I also found this still open issue in the @pidgin bug tracker, should probably have a closer look at it. https://issues.imfreedom.org/issue/PIDGIN-17771/Pidgin-Bonjour-not-working-with-ipv6
(It's been a while, but probably the issue was that that Pidgin / libpurple would only memorize one of the many #IPv6 addresses announced via #mDNS. And would then only accept Bonjour chat connections from that one address.

One of my first open source patches was for @pidgin, to fix some #IPv6 and #Bonjour / #mDNS issues in it. Bonjour chat and file transfer would allow to do so without needing a central server while we were on our decentral, layer 2 #batman_adv #meshnetwork at #Freifunk. Unfortunately we had to start filtering all #multicast in 2013 due to increased network sizes. Now, 11 years later with many new changes in #batman_adv and #Gluon we could reenable multicast at @ffhl. And Bonjour chat works again!