The article seems to be valid to setup a DHCP server to hand out addresses in the range 192.168.222.2-254 via en0. If this works, then after you connect your Pi, you can use ifconfig to see what IP address was assigned to en0 (I think).Īpplications -> Utilities -> Console -> system.log should contain any error messages from /usr/libexec/bootpdĪt the moment I'm sitting in a coffee shop with ONLY my Macbook Pro to play with, and no other computer systems I can attach to see if my guesses work.Īt first glance, the most obvious missing component in that page you linked to is any discussion about your Mac's own IP address. This is apparently what Internet Sharing runs. Or is this a matter of the Pi needing the DHCP server to pick its own IP address so that the Mac can connect and control the Pi ?Ĭan you just run " sudo /usr/libexec/bootpd -D -d -i en0" from a Terminal session? " man bootpd" for more information. If you use Applications -> Utilities -> Terminal -> ifconfig (After connecting the Pi to the Mac via Ethernet), does the Ethernet device (typically en0) have a self-assigned IP address (.x) that you can use from your Pi to make a connection? Yea, I think several of us were not clear on that point, and our natural bias for using WiFi dominated our brains □ But even putting that aside I want a wired connection as I find wifi rather erratic on a Pi.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |