Or, if you don't want to setup ssh on the Mac, you could write a server using nc (netcat) on the Mac and have the Pi netcat into that, sending its IP address. When it boots up, it could login (via ssh) to your Mac then the 'last' command would tell you who just logged in. FWIW, I've never found this approach particularly reliable.ģ) Another approach would be to have the Pi itself do the work. So, all you need to do is to start by pinging .100 and if that fails, try .101, and so on.Ģ) As another posted observed, you could probably, with enough finangling, get avahi/bonjour under control so that ping raspberrypi.local would work. All it does is start at a given IP address and scan upwards looking for something that responds. If it isn't, it will probably be one or two up from that.ġ) nmap doesn't do anything that you couldn't do yourself. Assuming there is only 1 client (the PI) and that the ICS is setup to hand out IP addresses starting at something like .100, then it is most likely that the Pi's IP address *is* .100. It's been a long time since I've run ICS on my Mac and/or Windows machines, and I'm not setup to test either at the moment, but it should be pretty easy to figure out which IP address(es) it has handed out. Surely, one or more of nmap, ping, or arp ought to tell you what you want to know. It's hard to say more without really knowing what OP has tried and what sort of error messages he's gotten, but it really doesn't seem like this should be very hard.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |