[Cialug] Ubuntu 9.04 udate

[Tom Sellers]

Thanks for pointing that out!  I looked at the network setup and in fact deleted the autoeth0 entry leaving only the eth0 entry.  This resolved the problem.  I can now ping this workstation and my DNS lookup works once again.  Evidently that entry was added when the machine was ugraded.  

Thanks again for jogging my memory and making me look at this!

--- On Sun, 7/5/09, kristau <kristau at gmail.com> wrote:

> From: kristau <kristau at gmail.com>
> Subject: Re: [Cialug] Ubuntu 9.04 udate
> To: "Central Iowa Linux Users Group" <cialug at cialug.org>
> Date: Sunday, July 5, 2009, 5:06 PM
> Routing looks fine, no problems
> there. The extra entry on the upgraded
> machine (169.254. . .) is just the APIPA or autoconfig IP
> address, and
> is not interfering. Otherwise, the two routing tables are
> functionally
> identical. They have the same subnet mask (/24) are on the
> same subnet
> (192.168.1.0) and are both using the same default gateway
> (192.168.1.1).
> 
> Is it just ping malfunctioning, or are you also unable to
> access
> Internet or other local systems?
> 
> On Sun, Jul 5, 2009 at 12:12 PM, Tom Sellers<tomsellers2001 at yahoo.com>
> wrote:
> >
> > Not that I understand the route information but these
> two are obviously different.
> >
> > The following is the route information from a working
> machine.
> >
> > 192.168.1.0/24 dev eth0 proto kernel scope link src
> 192.168.1.52
> > default via 192.168.1.1 dev eth0
> >
> > This is the route information from the upgraded
> machine which does not.
> >
> > 192.168.1.0/24 dev eth0 proto kernel scope link src
> 192.168.1.55 metric 1
> > 169.254.0.0/16 dev eth0 scope link metric 1000
> > default via 192.168.1.1 dev eth0 proto static
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>