Norm Jacobs writes: > James Carlson wrote: > > I didn't see a reference here to RFC 1759 or 3805. Will this project > > use any of the standardized Printer MIB interfaces, or does it only > > support the enumerated vendor MIB entries and Host Resources? > > > The Printer-MIB prtInputVendorName, prtInputModel, prtInputSerialNumber, > and prtInputDescription didn't appear to be in use in the printers that > I tried so I took them out. I can add them back in as a fallback. That > will add
OK. I did some looking at some competitive products, and it seems that others are querying those values. Whether they work on printers we find interesting is perhaps another matter. > > What about Avahi? > > > Most of the printers that I have come across don't support mDNS. A > couple of the newer ones that I have tested with do. I am looking at > incorporating it as a discovery method. mDNS support should introduce a > relatively small incremental change to this case to import the necessary > interfaces and introduce an interface to control the discovery method. That seems reasonable. I was just surprised at the absence of any mention, as this was (at one point) the direction we were going for network discovery. Another source of printer discovery would be DHCP. > >> svc:/network/device-discovery:snmp org.freedesktop.Hal.Device. > >> > > > > Enabled or disabled by default? And under what system profile? > > > Disabled by default. You might want it to be enabled when configured for generic_open operation. > > Why does that need to be specified anyway? You should be able to use > > SIOCGIF* ioctls to get every bit of information needed to perform > > broadcast-based queries. > > > The default is currently all 1s, but could be auto-detected. The reason > I put in config/network was to allow for the possibility of limiting the > scope. Using all-ones though probably won't work as well as expected on multihomed systems. Trolling through the interface list will be more reliable. There's probably also a relationship here between this case and NWAM ... but I'm not sure exactly what that would be. Have you been in touch with them? -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
