not connecting to cisco router after upgrade to kernel 3.14.4 64 bit
my 32 bit machine worked fine after upgrade
32 bit is wireless
64 bit is wired. - realtek RTL8111/8168 controller
dhcp tries and then drops to 169.254....
sb 192.168.1.127 (reserved on cisco)
can make it work by going to static ip in rc.inet1, but only works LAN no WAN.
not running wicd or networkmanager

A couple of thoughts.
One, it helps if you tell us what you've done so far troubleshooting the issue.
two
It's unlikely that's a random number, think about where that number might be coming from.
You have the option of restarting inetd with debugging enabled (-d) and checking the syslog but I've never had to do that so I'm not sure what you'd discover.

Sometimes, those kind of bugs fix themselves by running this command again :

and then reboot.

1 members found this post helpful.

I tried stopping dhcpcd and ifconfig eth0 down and then rerun rc.inet1 - same result.
stopped dhcpcd again - eth0 d0wn - run networkmanager - never connects - keeps trying - ifconfig reports the private network number 169.254.?.? again at eth0 - I assume this means not getting an address from the router or failing to do that properly.
stop dhcpcd - stop network manager - eth0 down- tell rc.inet1.conf that dhcpcd= no ip address = 192.168.1.127 for eth0. also default gateway = 192.168.1.1. Tell resolv,.conf the nameservers it should have gotten from router. run rc.inet1. route shows correct default route and I can ping all local ips and nameservers (by number only) on the isp. I can ping this machine from other machines on the home network but cannot get any names - ie ping slackware.com fails. One assumes this is because the router is not allowing. Can hardwire to the isp(cat5) router and use the wan address and works correctly (using static my other static ip#).
Did netconfig several times (both for static and dynamic) both before and after resetting rc.inet1.conf to normal ( dhcpcd="yes" and everything else ""). same results
tried changing $TIMEOUT to 30 instead of 10 in rc.inet1. same result

rereading your posts - i left out the reboot part. dont remember exactly but did multiple times each after some modification.
ps other machine upgraded day before gets correct info from same router. i do slackpkg update, install new and upgrade-all on this other machine first always so as not to get suprises on 127. I run current on both.
havent had a chance to do anything today but am considering shutting down network and trying dhcpcd -d eth0 from command line.
Also might(not high on my list) use slacpkg with 14.1 to return machine to "stable"
If it helps - i had a hiccup on the slackpkg upgrade-all - neglected to run lilo. kernel too big - cant run second stage lilo. got it to boot by fixing boot using livedisk slacko. then ran lilo and rebooted. booting all good then.

also remember googling and trying setting ipv6 to ignore on the router - no help - maybe should rebooted the router???

So you've downed eth0 and still have the private network? If there is no other interface in ifconfig when eth0 gets downed then there shouldn't be an alias causing this trouble...wait a minute, check your routing table...

and see if the any routing table has that network in it, if it does, flush it.
Do the same for the router and reboot it (good thinking, btw)
If that doesn't work, Nh3s' idea is a good one, it's fixed issues for me as well.

thanks for the suggestions
turned off all networking with ifconfig and kill pid of dhcpcd
in terminal ran - /sbin/dhcpcd -t 90 -d eth0
the output told me that having once gotten the 169.254.. address it stubbornly wanted it everytime.
fix was to kill the lease file - rm /var/lib/dhcpcd/dhcpcd-eth0.lease
then run rc.inet1 (another adventure - see below). got my address but routing table was still a problem and resisted my attempts to reconfigure it
completely flushing it and killing eth0 and dhcpcd and rerunning rc.inet1 fixed it.
I rebooted and it still worked. So
done!

btw never make the mistake of cp rc.inet1.conf.old rc.inet1 - had to go on another machine, get another copy of n/network-scripts from slackware.com - get rc.inet1 out of it and transfer it with a stick to fix my mistake

Outstanding!

When people search this sight for answers, they often pick the resolved threads to read because... what you did worked, so if you could, mark the thread resolved to help them out.