From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <39F081F3.687341ED@FWS.Gov> From: "Mark C. Otto" MIME-Version: 1.0 To: 9fans@cse.psu.edu, "Forsyth, Charles" Subject: Re: [9fans] Hooking a Plan9 Terminal to the Network References: <39EF245C.6BF8351@FWS.Gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 20 Oct 2000 13:33:39 -0400 Topicbox-Message-UUID: 1a22e2f0-eac9-11e9-9e20-41e7f4b1d025 I did manage to get my plan9 terminal hooked up to the network. The error turned up to be simple after Russ pointed me to the 9fans' archives. Pip wrote about configuring ip/ipconfig: pip@namaste.stricca.org pip@namaste.stricca.org Mon, 10 Jul 2000 00:53:54 -0400 >... "can't read my ip address" And I guess it stalls for about 60 secs ? I think it tries for a minute to get your IPaddr via DHCP, but I guess that's obvious. Try the following line for your /rc/bin/termrc: ip/ipconfig -g 195.182.167.1 ether /net/ether0 add your_ip your_netmask >>[2]/tmp/ipconfig.debug.log I originally assumed that ip/ipconfig would use /lib/ndb/local, since I had configured the network there. Next, I tried the ip/ipconfig after /rc/bin/termrc had run and that had no effect. Maybe I needed to unbind the ip stack and start over. The trick is to configure your ip address in termrc during init(8), so ipconfig will not try to use DHCP. It might be worth adding a line in distribution's termrc: # Configure the ethernet, see ipconfig(8), ip(3) ip/ipconfig -g YOUR_GATEWAY ether /net/ether0 add YOUR_IP YOUR_NETMASK >>[2=1] I'll make better use of the archives next time. Thanks to Charles Forsyth for looking into the problem. Now to see if I can get my mail off a POP3 server. Mark -- Mark Otto, Biological Statistician work: 301-497-5872 Population and Habitat Assessment Section fax: 301-497-5871 Office of Migratory Bird Management e-mail: Mark_Otto@FWS.Gov U.S. Fish and Wildlife Service Department of the Interior 11500 American Holly Drive Laurel, Maryland 20708-4016