On Wed, 9 Apr 2003, mark wrote: > Im having a similar (same?) problem starting today after upgrading. > Did you upgrade from 8.0 or fresh install? I upgraded and wonder if > thats related. Also I upgraded from the beta which further > complicates. I'm having problems with the fresh install, but I don't think my issue is with up2date anymore. The server in question is on the DMZ of our network, but other machines on the DMZ are still able to run up2date. Recently, I added another ip alias to the machine and that went smooth. But I rebooted yesterday and it came up with three default gateways?: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface X.X.X.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 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 X.X.X.1 0.0.0.0 UG 0 0 0 eth0 0.0.0.0 X.X.X.1 0.0.0.0 UG 0 0 0 eth0 0.0.0.0 X.X.X.1 0.0.0.0 UG 1 0 0 eth0 Umm... I'm no networking wizard but that doesn't seem right at all. All those three gateway's at the bottom are pointing to the same place and what's with the 169.254.0.0 Destination? I have other servers where there 's only three entries in the routing table: the network one "X.X.X.0", localhost "127.0.0.0" and the default route "0.0.0.0". Thanks for any help... --Ajay -------------------------------------------------------------------- Satyajot (Ajay) Sharma ssharma@xxxxxxx --------------------------------------------------------------------
