Bug#366519: guarddog: doesn't work with zeroconf (avahi)

2008-06-04 Thread James Carr
The problem doesn't lie with Avahi and mDNS specifically, but with the Multicast Address (224.0.0.251) that it uses. Guarddog blocks (or more precisely, doesn't specifically allow) Multicast Traffic (224.0.0.0 - 239.255.255.255). There are two ways to enable it: 1) Start Guarddog as normal a

Bug#366519: guarddog: doesn't work with zeroconf (avahi)

2006-06-10 Thread Matej Cepl
On Sat 10. June 2006 07:58, Paul Cupis wrote: > Can you please use your attached rc.firewall and enable > logging, and then pass me the kernel/firewall logs from > attempts to use zeroconf/avahi with the guarddog firewall? How many megabytes of logs you want? :-) This is just my current /var/log/

Bug#366519: guarddog: doesn't work with zeroconf (avahi)

2006-06-10 Thread Paul Cupis
Matej Cepl wrote: > Package: guarddog > Version: 2.5.0-1 > Severity: normal > > Even with the attached rc.firewall customized to allow mDNS, > guarddog generated /etc/rc.firewall blocks port 5353. If you create a user-defined protocol with guarddog, it will allow the specified ports to be used to

Bug#366519: guarddog: doesn't work with zeroconf (avahi)

2006-05-09 Thread Paul Cupis
Matej Cepl wrote: > Package: guarddog > Version: 2.5.0-1 > Severity: normal > > Even with the attached rc.firewall customized to allow mDNS, > guarddog generated /etc/rc.firewall blocks port 5353. Are you modifying the rc.firewall by hand and then re-running it? This will not work, you have to us