Hide Forgot
Description of problem: Spooled print won't start printing due to an extraneous routing table entry. Deleting the extraneous entry allows printing. I don't know if it is cups that makes the extraneous routing table entry. Version-Release number of selected component (if applicable): Version : 1.4.6 Vendor: Fedora Project Release : 1.fc14 Build Date: Fri Jan 7 03:43:02 2011 How reproducible: Send print to a network printer when an extraneous routing table entry exists. I don't know what causes the extraneous entry. After deleting the bad entry, it shows up again. Steps to Reproduce: 1. Observe extraneous routing table entry 2. Spool print file to network printer. 3. Actual results: File is spooled to printer. Status of spooled entry is: Printing. File never prints. Expected results: File should print. Additional info: # service NetworkManager status NetworkManager is stopped # service network status Configured devices: lo eth0 eth1 Currently active devices: lo eth1 eth0 # service cups status cupsd (pid 4497) is running... # lpq lp is ready and printing Rank Owner Job File(s) Total Size active blackbu 51 (stdin) 12288 bytes # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.90.113.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.251.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.90.113.1 0.0.0.0 UG 0 0 0 eth1 After this command printing starts and works fine: # route del -net 169.254.0.0 netmask 255.255.0.0 dev eth1 eth1 is the interface to my ISP. eth0 is the interface to my internal subnet. I suspect the invalid 169.254.0.0 ... eth1 entry might be getting set outside of cups. If that's the case I presume this bug should be reassigned to the appropriate culprit. If I can get clues as to where/why the bad routing entry gets set, I will add such info to this bug.
How have you set up networking? By the look of it, you are not using NetworkManager (as that service is stopped). Did you adjust configuration files by hand, or use some other tool to configure networking?
How have you set up networking? By the look of it, you are not using NetworkManager (as that service is stopped). True. Did you adjust configuration files by hand, or use some other tool to configure networking? By hand using a script I developed. # cfgnw -L tennw cat hosts-tennw 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 cs4.cs cs4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 aaa.bbb.ccc.5 cs5 cs5.cs aaa.bbb.ccc.4 cs4 cs4.cs aaa.bbb.ccc.3 cs3 cs3.cs aaa.bbb.ccc.2 cs2 cs2.cs 208.67.220.220 resolver2.opendns.com 208.67.222.222 resolver1.opendns.com cat ifcfg-eth0-tennw DEVICE=eth0 BOOTPROTO=none BROADCAST=aaa.bbb.ccc.255 IPADDR=aaa.bbb.ccc.4 NETMASK=255.255.255.0 NETWORK=aaa.bbb.ccc.0 ONBOOT=yes USERCTL=no PEERDNS=no TYPE=Ethernet cat ifcfg-eth1-tennw DEVICE=eth1 BOOTPROTO=none BROADCAST=aaa.bbb.ccc.255 IPADDR=aaa.bbb.ccc.44 NETMASK=255.255.255.0 NETWORK=aaa.bbb.ccc.0 ONBOOT=yes USERCTL=no PEERDNS=no TYPE=Ethernet cat network-tennw NETWORKING=yes HOSTNAME=cs4.cs FORWARD_IPV4= DOMAINNAME= GATEWAY=aaa.bbb.ccc.1 GATEWAYDEV=eth1 TIMESERV=aaa.bbb.ccc.18 DESC="" cat resolv.conf-tennw ; DNS servers nameserver 208.67.220.220 # resolver2.opendns.com nameserver 208.67.222.222 # resolver1.opendns.com # domain isp.net # search isp.net nameserver aaa.bbb.ccc.1 # ns1.isp.net nameserver aaa.bbb.ccc.2 # ns2.isp.net
ifup eth1 causes this entry: 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 ifdown eth1 removes the entry. So this is presumably not a cups bug. By doing ifdown then ifup the unwanted routing entry comes after the eth0 entry. So the eth1 entry no longer causes problems with cups. Based on what I read about 169.254.0.0/16, creation of this entry on ifup is perhaps not a bug. I'm thinking it may be appropriate to close this bug. However, it provides useful workaround info for someone with a config similar to mine. # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.90.113.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.251.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 0.0.0.0 10.90.113.1 0.0.0.0 UG 0 0 0 eth1 # ifdown eth1 # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.251.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 # ifup eth1 # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.90.113.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.251.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
OK, changing component to initscripts (which owns /sbin/ifup) to verify that there's no bug there.
What's the output of 'ip route ls' when you have these routes?
ip route ls 10.90.113.0/24 dev eth1 proto kernel scope link src 10.90.113.44 192.168.251.0/24 dev eth0 proto kernel scope link src 192.168.251.4 169.254.0.0/16 dev eth0 scope link metric 1002 169.254.0.0/16 dev eth1 scope link metric 1003 default via 10.90.113.1 dev eth1
Given that they have different metrics (causing the eth0 route to be preferred over the eth1 route), this shouldn't cause any issues. Are you printing via link-local/mDNS?
Originally the eth1 route came first. A workaround is to ifdown eth1; ifup eth1 causing eth0 to then be preferred. Printing is configured: hp:/net/HP_LaserJet_P1505n?ip=169.254.181.246
With both routes in the table, but eth1 first, can you ping the printer?
>> With both routes in the table, but eth1 first, can you ping the printer? No. ifup/ifdown leaves eth1 second. route del/add was able to get eth1 first. # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.90.113.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.251.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 0.0.0.0 10.90.113.1 0.0.0.0 UG 0 0 0 eth1 # route del -net 169.254.0.0 netmask 255.255.0.0 dev eth1 # route add -net 169.254.0.0 netmask 255.255.0.0 dev eth1 # netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.90.113.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.251.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.90.113.1 0.0.0.0 UG 0 0 0 eth1 # # # ping 169.254.181.246 PING 169.254.181.246 (169.254.181.246) 56(84) bytes of data. From 10.90.113.44 icmp_seq=2 Destination Host Unreachable ^C --- 169.254.181.246 ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms # route del -net 169.254.0.0 netmask 255.255.0.0 dev eth1 # ping 169.254.181.246 PING 169.254.181.246 (169.254.181.246) 56(84) bytes of data. 64 bytes from 169.254.181.246: icmp_req=1 ttl=255 time=1.05 ms 64 bytes from 169.254.181.246: icmp_req=2 ttl=255 time=0.214 ms ^C --- 169.254.181.246 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 0.214/0.633/1.053/0.420 ms
I discovered a clean solution to the problem of cups trying to access the printer via 169.254.0.0/24 on the wrong interface. I simply add: NOZEROCONF=true to the appropiate file: /etc/sysconfig/network-scripts/ifcfg-eth* in my case eth1 The use of NOZEROCONF can be confusing. Setting it to yes, no, or anything gives the same result i.e. disabling Zero Configuration Network (ZEROCONF). Perhaps someone can figure out a way to improve the documentation. I think it makes sense to convert this bug to a documentation enhancement bug. These all come up empty: zgrep NOZEROCONF $(rpm -ql initscripts | grep /man) zgrep NOZEROCONF $(rpm -ql cups | grep /man) zgrep NOZEROCONF /usr/share/doc/cups-{[0-9]*,libs*} It is documented here: zgrep NOZEROCONF /usr/share/doc/initscripts-*/* However, knowing to look for NOZEROCONF can be a hurdle (was for me). Also, knowing where to look can be a hurdle.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping