25.07 and Avahi?
-
If you're using ZFS you can test it and roll back if you need to.
-
@stephenw10
Thank you as always for the quick reply Stephen. I haven't always had the greatest luck with smooth upgrades in the past so was hoping to hear from other avahi users (Apple TVs, Airplay speakers, printers, etc.) before embarking on the upgrade process. -
@terryzb said in 25.07 and Avahi?:
Can anyone confirm whether avahi works in 25.07?
I know of no reason that Avahi would not work in 25.07. I tested Avahi in early versions of 25.07, but haven't recently so YMMV.
-
@dennypage
Thank you for the reply.I found the thread where @markster reported it stopped working after the upgrade. https://forum.netgate.com/post/1222902
-
@terryzb said in 25.07 and Avahi?:
@dennypage
Thank you for the reply.I found the thread where @markster reported it stopped working after the upgrade. https://forum.netgate.com/post/1222902
FWIW “apple mirroring or airplay does not work anymore” really wasn’t sufficient to indicate an Avahi issue, and he didn’t seem much interested in further diagnosis. Also, given his other reported issue, and a quick vlan reconfiguration, it seems possible that there may have been other items that contributed to the issues he reported.
Honestly, if Avahi were broken, I would expect to see lots of posts regarding it.
-
@dennypage
Thank you for that insight. I've always assumed that avahi wasn't a commonly installed package since I don't see much discussion about it. I will install the 25.07 update this week and report back. -
@dennypage
Last night I upgraded the 2100 via the console with pfBlockerNG and Avahi packages left in place, and after 20 minutes or so it came back up and avahi appears to be working properly. -
@dennypage
Maybe I spoke too soon... I moved a working printer (Canon MF743) from one room to another, powered it up, it connected to the same WiFi network (PRIVATE_WIFI) and I attempted to print from the LAN, but printer was not found.The network consists of a wired LAN, a PRIVATE_WIFI and a GUEST_WIFI. The LAN is 172.16.1.x, and PRIVATE_WIFI, where the printer is connected, is 172.16.10.x. The AP is an Airport Extreme set to Bridge mode. Router is a 2100 running 25.0.7.1.
Avahi is set to repeat all 3 networks. Nothing special is configured. The LAN has an allow all to any rule.
I deleted the printer from the LAN Mac's printer list and attempted to re-add it. It showed up as a Bonjour printer, but trying to add it failed with an error that there was no communication.
It gets a little weirder - if I instead added the printer via its IP address, the printer is successfully added. If I then go back to add the printer again via Bonjour it sees it and is able to add it.
Even after printing to the Bonjour added printer, I don't see any ARP Table entries for the printer.
There is a static DHCP entry for the printer but it's listed as down in DHCP Leases. The printer is set to DHCP and reports it's using that IP.
Here are my LAN and PRIVATE_WIFI rules, the Avahi configuration, the printer states and the lease. Is it strange that there are no ARP table entries for the printer or states between the LAN Mac and the printer right after printing?
What do I not have setup correctly so that I couldn't add the printer via Bonjour from the LAN? Apologies for the basic questions. It's working now but I'm interested in learning why it didn't work without first adding the printer via its IP.
-
Hi,
This is how I got my printer working across VLANs.
https://forum.netgate.com/post/1224001 -
@terryzb said in 25.07 and Avahi?:
I deleted the printer from the LAN Mac's printer list and attempted to re-add it. It showed up as a Bonjour printer, but trying to add it failed with an error that there was no communication.
First and foremost, that the printer shows up via as a Bonjour printer tells you that the mDNS information is being forwarded by Avahi.
Even after printing to the Bonjour added printer, I don't see any ARP Table entries for the printer.
The host and printer are in different network segments, yes? As such, you would not expect to see a ARP entry. ARP is only used for addresses in the local network segment.
Have you checked the firewall log? Do you have default logging enabled?
-
@dennypage
The system Logging Preferences are all enabled except for default blocks and default passes. I don't see anything unusual in the firewall logs related to the printer.I ran another test of deleting the printer, then adding it again with Bonjour and it found it and successfully connected. I then noticed on its front panel that it had lost its IP and was using a self-assigned. I don't know when this happened. I power-cycled it and forced it to renew its lease and it did. As I stated above, pfSense has a static DHCP IP set for the printer, and that's the IP the printer got, but pfSense says the lease is down as shown in the last pic above. Could this be Kea related? I've been running Kea since 24.11 and haven't noticed this issue. It's not that new of a printer.
-
@terryzb said in 25.07 and Avahi?:
I then noticed on its front panel that it had lost its IP and was using a self-assigned. I don't know when this happened.
Self assigned addresses are link local, not accessible from other network segments. That would explain why you can see it but not connect to it.
I power-cycled it and forced it to renew its lease and it did. As I stated above, pfSense has a static DHCP IP set for the printer, and that's the IP the printer got, but pfSense says the lease is down as shown in the last pic above. Could this be Kea related?
Edit: [
DHCP addresses are handed out by dhcpd, so probably not an issue with Kea. An issue with dhcpd perhaps]. My bad.Either way, outside of Avahi. Please explore the potential dhcpd issue in a new thread. Thanks.
-
@dennypage
Thank you very much for your help. -
Kea is the dhcp server if you've enabled it so I'd expect to see the printer there. The status of the IP/device is reliant on the arp table though so it could have just timed out if nothing has accessed it for a while.
But, yes, unrelated to Avahi.
-
@stephenw10 said in 25.07 and Avahi?:
Kea is the dhcp server if you've enabled it so I'd expect to see the printer there.
Ah yes, quite correct. My bad.
-
@terryzb said in 25.07 and Avahi?:
As I stated above, pfSense has a static DHCP IP set for the printer, and that's the IP the printer got, but pfSense says the lease is down as shown in the last pic above
The printer uses DHCP - and get an MAC Static lease from pfSense (using kea, or ISC).
As soon as the lease was granted, the pfSense ARP cache will 'know' about the relation MAC-printer and it's IP 172.16.10.201 address. This ARP cache will auto empty - after some 20 minutes or so (I don't recall).
If pfSense (itself) re connect to this printer, the pfSense ARP cache will contain the IP of the printer again.
But : does pfSense print ? Normally, a router firewall doesn't use a printer. So no big deal it loses the ARP cache info.
Ping from pfSense your printer, and you'll see the DHCP lease shows a green up arrow again (for a while). -
@Gertjan @stephenw10
Thank you for the explanations. I will start a new thread. -
T terryzb referenced this topic
