Project

General

Profile

Actions

Feature #9751

closed

Need an "inclusive" and "exclusive" method of specifying ports

Added by George Phillips about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Avahi
Target version:
-
Start date:
09/12/2019
Due date:
% Done:

100%

Estimated time:
Plus Target Version:

Description

At this time, Avahi doesn't seem to like to run if the "allow-interfaces" config item contains more than 33 interfaces. I suspect this is because the interface list can get very long, and ends up getting truncated. However, it will run if you invert the selection (manual configuration) using "deny-interfaces" config item. This causes a problem with larger sites having many VLANs.

Requesting a GUI option to use the "allow-interfaces" config item (as it is today) or the "deny-interfaces" option as it was in the past. Avahi has no problem running on all interfaces when using the "deny-interfaces" config item.

Actions #1

Updated by Jim Pingle about 2 years ago

  • Assignee set to Jim Pingle

Looks like Avahi fails to parse the line when the total length of the line (including "allow-interfaces=") is greater than 256 bytes.

So for this situation we'll need to have a way to specify deny interfaces instead, and allow none to be selected so it binds to all.

Actions #2

Updated by Jim Pingle about 2 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Implemented in Avahi pkg version 2.1.

Actions #3

Updated by Denny Page about 2 years ago

Good change Jim

Actions #4

Updated by George Phillips about 2 years ago

Works great now! Thanks!

Actions #5

Updated by Jim Pingle about 2 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF