I found after checking cables, among other things it turned out despite the fact I could wirelessly connect to my router, a router reset actually resolved the problem.
A dead giveaway that the issue was the router was that even when setting a static ip I couldn't ping my router using LAN only. Another dead giveaway was that on the router I specifically dedicated an ip to the LAN connection outside of my DHCP range. EG: DHCP should have returned the dedicated IP address, but instead was giving the junk address, whereas my wireless card using DHCP was retrieving it's own dedicated address perfectly fine.
Connect to your router (possibly w/ another computer) and dedicate an IP address to each device you'd like to test (outside of the DHCP range so you'll have a definitive confirmation DHCP worked and recognized your device's MAC address), similarly do the same w/ a wireless device, then make sure all of them are using DHCP. If some wireless vs wired device is working where another is not, (EG DHCP is definitely working) your router may be at fault.
If you find this is the case, know your frustration isn't in vain because even if you manually configured the right IP to start with your router effectively was a brick the entire time, no amount of software steps would've solved the issue.
Note: as far as I can tell it seems other people with this sort of issue complain about cabling, which is why I brought it up. Whereas for me it turned out my router was on the fritz, I have no idea but it could be a bad cable/port that could cause this.
If worst comes to worst, you may need to find an old router to see if it has the same issue.
If the absolute worst comes to worst, you may need a new lan card...
169.254.x.x are addresses given when your device fails to retrieve an ip address from a DHCP server (your router). EG. If you've gotten so far as to find out you're being handed a
169.254.x.x address, you're more than likely having a hardware problem, either
- find out if a wireless device or card works w/ DHCP enabled (your router for some reason is no longer handling DHCP requests via lan or...potentially more like in my case) or
- set a static ip and see if you can bypass the issue by ignoring
DHCP, you can avoid ip collisions w/
arp -a (you may need a second device).