<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2448.0">
<TITLE>the further adventures of setting up Ethernet between two Linux machines</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Thanks to everyone who answered my previous question about the 486. I had, indeed, neglected to bring the interface up with ifconfig. Once I did that, horse-nettle (the 486) could telnet into its own Ethernet interface (192.168.1.2) and petunia (its younger and more technologically advanced sibling) with no problem.</FONT></P>
<P><FONT SIZE=2>Well, *almost* no problem. See, petunia didn't have any accounts with a working password, aside from root, and it wouldn't let me log in as root over the network (probably just as well). So I unplugged the keyboard and monitor from horse-nettle, plugged them into petunia, and then tried to telnet from petunia into horse-nettle. This led to the error message "telnet: Unable to connect to remote host: No route to host". I looked at the routing tables with `arp -v -n`, and got a list of 13 IP addresses (including horse-nettle's), all of them with "(incomplete)" in the HWaddress column. Then the really strange things began happening:</FONT></P>
<P><FONT SIZE=2># arp --delete 192.168.1.2</FONT>
<BR><FONT SIZE=2>SIOCDARP(pub): No such file or directory</FONT>
</P>
<P><FONT SIZE=2># route del 192.168.1.0</FONT>
<BR><FONT SIZE=2>SOICDELRT: No such process</FONT>
</P>
<P><FONT SIZE=2>What now, O network wizards?</FONT>
</P>
<P><FONT SIZE=2>Of course, fool that I was, I didn't take down the hardware address of horse-nettle's Ethernet card *before* I shut it down and unplugged the monitor from it....</FONT></P>
<P><FONT SIZE=2>--seth</FONT>
</P>
</BODY>
</HTML>