The "Static" assignment was on the hypothesis that the two IP addresses that the two machines were used to take were internal to the modem. Actually, changing from DHCP to Static has broken any connection to internet, i.e., if I understand, that "Static" is to the eth# connection, while my provider assigns me a dynamic address.
The server should only serve between the two machines at the router. Perhaps, if I understand your suggestion, the solution, any time the IP address changes, is to "You only need to reassign the keys in your "known_hosts" file appropriately." I do not intend the Apache2 for external use. Thanks francesco --- Kapil Hari Paranjape <[EMAIL PROTECTED]> wrote: > Hello, > > On Fri, 16 Mar 2007, Francesco Pietra wrote: > > It worked beautifully for a week. At a new boot > today > > the 32bit machine had taken the former IP address > of > > the 64bit machine, and viceversa. > > > A system maintainer suggested to change the eth# > > connections of the two machines (Desktopp, > > Administration, Networking) from DHCP to Static, > > This sounds like a correct suggestion. If you assign > addresses to > machines dynamically then it is difficult to treat > them as "servers" > except through some dynamic DNS services. > > > Well, I could delete all shh configuration and > keys > > and do that again, though for how long? > > You need not generate the keys again. You only need > to reassign the > keys in your "known_hosts" file appropriately. > > Hope this helps. > > Regards, > > Kapil. > P.S. I removed debian-science from the cc as I > couldn't see what it > had to do with debian-science. > -- > ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
