On Wed, Aug 20, 2003 at 01:52:24PM -0400, Bret Comstock Waldow wrote: > Starting with the current setup, which is my practical lab and > classroom, how does one system find the other? All the machines are > getting their IP via DHCP, so it's not guaranteed to be the same. The > system names aren't available in any DNS scheme I know of (I'd love to > hear about a facility for this). I can put entries into /etc/hosts if > the IPs were static, but they aren't, and certainly won't be when I'm > connecting by PPP. > > We are already connecting through IM protocols, using gaim. Conceivably > I can simply tell him my IP when I connect, but I'm wondering what is > the canonical way to handle this? How do I handle it now, when the IP > is dynamic (even though it's unlikely to change I want to work on the > general solution while it's easy to do it - while I have my hands on all > the systems). The power fails here periodically, and the cable modem > he's on renegotiates it's IP each time - even that's not static. I use the free service at: http://www.dyndns.org You can have several addresses of the form: name.domain Where you choose whatever name you want (as long as it's not already taken) and where you can choose the domain from a list of about 10 or 15, including things like homelinux.com. To keep the ip up to date you can use several programs. The one I use is called ez-ipupdate. It's available as a debian package, and works pretty well. What I did before I used this sort of thing was to have a script send my ip to the computer that host my website (www.crasseux.com), and then if someone needed my ip, I would tell them to look at: http://www.crasseux.com/ip.txt But I think the dyndns.org solution is better. Bijan
Attachment:
pgpAUKEZGgacZ.pgp
Description: PGP signature