nortonham **My initial thought is it has something to do with the error "/etc/dhcpd.conf is not readable"
Almost definitely. Your wireless is working properly, but the interface is not being assigned an address:
*output of dhcpd status
And, considering that dhcpcd.conf is not readable, as you wrote below, it's not surprising.
It's a thinkpad T420. I don't have the exact wireless device name
Learn how to get it then from the terminal. Shall prove useful in future.
looking at iwn0 man page it doesn't seem like I needed to.
The network is RSN, not hidden
good to know, highlighting it as notice for others.
fconfig iwn0 up
what's that? this is not a rcvar. What you're looking for is:
But you don't need it, since you already brought it up inside ifconfig.iwn0. Pick one of the two, whatever suites you best; but as it is, the configuration is redundant.
Is this really your router's internal address? Was this automatically generated by resolvconf(8), or you edited it by hand?
Again, the configuration should either take place here or inside rc.conf. Putting
dhcp here triggers a hook for dhcpcd(8) to configure the interface and is equivalent to
dhcpcd=YES in rc.conf.
/etc/dhcpd,conf not readable
Is the comma a typo? I suppose so. Anyway, since you somehow happened to mess with /etc permissions:
$ chown root:wheel /etc/dhcpcd.conf
$ chmod 644 /etc/dhpcd.conf
However, at this point I would test all the ownership and permissions of NetBSD's standard files and directories against the common specification:
$ mtree -e -p / -f /etc/mtree/NetBSD.dist
This will return all altered permissions, ownership, paths, missing folders and files. Enjoy XD
You can get the standard dhcpcd.conf for release -9 here.