Re: [9fans] Hooking a Plan9 Terminal to the Network

Re: [9fans] Hooking a Plan9 Terminal to the Network

[anothy]

in my local setup, i use the following to get around
ip/ipconfig not looking at the ndb files. it's a
small change to /bin/[cpu,term]rc :

	ndb/cs
	sysname=`{cat /dev/sysname}
	myip=`{ndb/query sys $sysname ip}
	ip/ipconfig ether /net/ether0 $myip 255.255.255.0 >/dev/null >[2=1]
	ndb/dns -r

and everything seems happy with this. this allows me
to share the files accross multiple machines. maybe
the subnet mask and gateway could be gotten via ndb,
but i've not tried that.
-α.

Re: [9fans] Hooking a Plan9 Terminal to the Network

[arisawa]

Hello,

anothy@cosym.net wrote:
>in my local setup, i use the following to get around
>ip/ipconfig not looking at the ndb files. it's a
>small change to /bin/[cpu,term]rc :
>
>	ndb/cs
>	sysname=`{cat /dev/sysname}
>	myip=`{ndb/query sys $sysname ip}
>	ip/ipconfig ether /net/ether0 $myip 255.255.255.0 >/dev/null
>[2=1]
>	ndb/dns -r

How about the bellow:

switch($ipconfig){
case local
        eval `{ndb/ipquery sys $sysname ip}
        eval `{ndb/ipquery sys $sysname ipgw}
        eval `{ndb/ipquery sys $sysname ipmask}
        ip/ipconfig -g $ipgw ether /net/ether0 add $ip $ipmask
case dhcp
        ip/ipconfig >/dev/null >[2=1]
}

and in plan9.ini:

ipconfig=dhcp

or

ipconfig=local



Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp

[9fans] Hooking a Plan9 Terminal to the Network

[Mark C. Otto]

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

I need some hints checking out my 3COM 3C905-TX ethernet card or setting up my
/lib/ndb/local file.  The card passes the 3Com diagnostic tests. I used a

ether0=type=elnk3

in my plan9.ini file, and plan9 boots with it,

#l0: elnk3: 10Mbps port 0xFCC0 irq9: 0060083FF7AE

I get a

ndb/dns: can't read my ip address

error.

For now I am just trying to attach my terminal to our network.  I do not
have a cpu, file, or auth server yet.  I can use ndb/ipquery to get our dns
servers,
my ip address, domain, network, and gateway from the ether net address.

To see if the ether net worked, I tried telnet and traceroute to my linux box,

telnet net!bfbooby
telnet: connection timed out (connect 164.159.212.30!23)

ip/traceroute -d bfbooby
interrupted
*
interrupted
*
...

Are there other diagnostics to work on or should I be looking for a problem in
my /lib/ndb/local.  I attached my /lib/ndb/local and plan9.ini files.  Thanks.

Mark

P.S. I am suprised that ndb/ipquery is case sensitive (BFBooby isn't found but
bfbooby is.) when internet addresses aren't.

[-- Attachment #2: plan9.ini --]
[-- Type: text/plain, Size: 272 bytes --]

bootfile=sdC0!9fat!9pcdisk
#bootfile=fd0!9pcdisk.gz
bootdisk=local!#S/sdC0/fs
*nomp=1
distname=plan9
partition=new
monitor=multisync75
#vgasize=640x480x8
vgasize=1024x768x8
mouseport=ps2
#ether0=type=NE2000 nodummyrr
ether0=type=elnk3
debug=1









[-- Attachment #3: local --]
[-- Type: text/plain, Size: 957 bytes --]


#
#  files comprising the database, use as many as you like, see ndb(6)
#
database=
	file=/lib/ndb/local
	file=/lib/ndb/common

# Fish and Wildlife Service Network
ipnet=fwsnet ip=164.159.0.0
	ipmask=255.255.0.0
	ipsubmask=255.255.255.0
	dns=dns.irm.r9.fws.gov pref=1
	dns=pandion.er.usgs.gov  pref=2
	smtp=164.159.176.1
	dnsdomain=fws.gov
dom=dns.irm.r9.fws.gov ip=164.159.176.1
dom=pandion.er.usgs.gov ip=159.189.24.1

# MBMOLNET: With netmask of .192, for computers 0-63.  How can I have .91?
#	fs=bfbooby.irm.r9.fws.gov
ipnet=mbmolnet ip=164.159.212.0
	ipmask=255.255.255.0
	pop3=164.159.212.10
	dnsdomain=irm.r9.fws.gov
	dnsdomain=fws.gov

# My Dell 410 MTS workstation with Linux
ip=164.159.212.30 sys=bfbooby
	dom=bfbooby.irm.r9.fws.gov
	ipgw=164.159.212.62

# my first plan9 terminal
ip=164.159.212.91 sys=mbooby
	dom=mbooby.irm.r9.fws.gov
	dom=mbooby.fws.gov
	ipgw=164.159.212.126
	ether=0060083ff7ae

Re: [9fans] Hooking a Plan9 Terminal to the Network

[Mark C. Otto]

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

Re: [9fans] Hooking a Plan9 Terminal to the Network

[Scott Schwartz]

>> I originally assumed that ip/ipconfig would use /lib/ndb/local, since I had
>> configured the network there.

Doesn't the manpage say something to that effect?  In any case, it
probably ought to do that, as long as it does all the other stuff that
it does.