So I am a returning user to ARCH, and using my raspi as motivation to finally escape ubutnu (again) . However I am off to a rough start. I loaded up the latest image on an SD card from a mac mini, connected my rapsi to my ubuntu laptop, shared the entwork and pluggdd it in, annnnnd nada. Could not connect to the raspi over the network. I figured I was screwing up the sharing settings so I plugged the rapsi into my verizon router directly, which is running a DHCP server and plugged it into the nearest PC for power. Still can't find it on the network (used zenmap, as well as trying to just SSH directly to root@alarmpi) and did not find it. I blamed the router, so I unplugged it again and hooked it up to my access point which is a router running DDWRT as a dumb connection to the main wirelss network. It just lets my non-wireless devices connect to the home network, its on the same subnet, does not have dhcp etc etc. Still CANT FIND IT on the network.
So I caved in and went to radio shack and bought a USB keyboard, plugged the raspi into our macmini for both power and shared ethernet (none of my moniters have HDmI) and stole the TV connection and plugged it into the raspi. IT booted up happily (so hopefully those 3 or4 hard reboots didn't corrupt anything) and I used the USB keyboard to verify I could not see the local network. couldn't ping the default gateway or 8.8.8.8 so I did the only thing I knew how and ran
root@alarmpi: DHCPCD
it happily got a lease, connected to the network and is now running a full system update. Why did DHCPCD not run at boot? is DHCPCD depreciated? Should a diferent tool have run at boot time?
TL:DR:
Why does everyone elses raspi auto-connect to the network on first boot no problem, and I had to run DHCPD the first time to get it to work? Untill yesterday I didn't ahve a USB keybaord so I rely on SSH on first boot, but if it won't connect to a network that is obviously not something I can do.
holy cow that was a long first post. Sorry to bore you/thanks for theh elp!