ports/99602: CUPS relaying fails

Erwin Van de Velde erwin.vandevelde at gmail.com
Thu Jun 29 11:30:20 UTC 2006


>Number:         99602
>Category:       ports
>Synopsis:       CUPS relaying fails
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jun 29 11:30:18 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Erwin Van de Velde
>Release:        FreeBSD 6.1-RELEASE-p1
>Organization:
>Environment:
FreeBSD pcfw77.cmi.ua.ac.be 6.1-RELEASE-p1 FreeBSD 6.1-RELEASE-p1 #0: Thu Jun  1 09:15:23 CEST 2006     root at xxx.xx:/usr/obj/usr/src/sys/GENERIC  i386

>Description:
When adding 
BrowseRelay 143.129.77.x 143.129.77.x
(first one being a host, second a broadcast address, different subnet)
I see the following in the cups error log:
Relaying from 143.129.77.63 to 0.0.0.2130706xxx/4294967295.4294967295.4294967295.4294967295:631 (IPv4)
2130706xxx is the ip address of the host. BrowseRelay fails to work and seems impossible to fix.

The cups relay host has no own printers, but only relays to the other subnet.
>How-To-Repeat:
Enable BrowseRelay from a host to a broadcast address.
>Fix:
FreeBSD could try to upgrade to CUPS 1.2.1 since that version is already available. However, I do not know if this bug is fixed in the newer version.
>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list