check you routing setup. Sometimes ifcfg-eth0. I've seen That non-route 169etc happen when an odd route cannot be found.
David Vernon <redhat ladadee com> wrote:
I have an "out of the box" but 'up2date' redhat 9 box that keeps getting a route
for the 169.254.0.0 network in its tables. I have no interface on that network.
Any idea how this route might be getting in the tables?
This is a dig on that network. I don't use ATT as an ISP.
; <<>> DiG 9.2.1 <<>> 254.169.in-addr.arpa soa
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51151
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;254.169.in-addr.arpa. IN SOA
;; ANSWER SECTION:
254.169.in-addr.arpa. 604800 IN SOA xbru.br.ns.els-gms.att.net.
rm-hostmaster.ems.att.com. 1 1800 900 604800 604800
;; AUTHORITY SECTION:
254.169.in-addr.arpa. 604800 IN NS blackhole-1.iana.org.
254.169.in-addr.arpa. 604800 IN !
NS blackhole-2.iana.org.
;; ADDITIONAL SECTION:
blackhole-1.iana.org. 630 IN A 192.175.48.6
blackhole-2.iana.org. 630 IN A 192.175.48.42
;; Query time: 127 msec
;; SERVER: 168.147.236.18#53(168.147.236.18)
;; WHEN: Tue May 20 11:08:42 2003
;; MSG SIZE rcvd: 237
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request redhat com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list