Are you using an onboard NIC? Is it a Marvell chipset? I've noticed a couple weird things like this with very particular Marvell chips. (instance where things would looks correct and it wouldn't necessarily report problems, but it would not get a gateway or wouldn't pick up an IP from DHCP.)
My solution was to toss in a PCI NIC and update the kernel. If that didn't fix it, I downloaded and installed the actual NIC module from Marvell. Chris On Tue, Jan 19, 2010 at 1:19 PM, Howard <hwh...@vcch.com> wrote: > Hey guys, > > I have a spanking new CentOS desktop install in front of me that is playing > silly with networking. The install process from DVD seems to have gone > according to plan. Yet its network configuration is not working. I've > reviewed the following: > > /etc/resolv.conf as expected > /etc/network as expected > > /etc/network-scripts/ifcfg-eth0 normal > > The results of a route command are most troubling - no default gateway even > there is one in the /etc/network file. Why does route show 169.254.0.0 > assigned to eth0? > > I just added a default route and am now able to get to the network. Is > this a know fault?? > > Howard > > -- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To post to this group, send email to nlug-talk@googlegroups.com > To unsubscribe from this group, send email to > nlug-talk+unsubscr...@googlegroups.com<nlug-talk%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > >
-- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to nlug-talk@googlegroups.com To unsubscribe from this group, send email to nlug-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en
