Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!samsung!umich!umeecs!msi-s0.msi.umn.edu!cs.umn.edu!peiffer From: peiffer@cs.umn.edu (Tim Peiffer (The Net Guy)) Newsgroups: comp.dcom.lans Subject: Re: IP Addresses on WD8003E Message-ID: <1990Jul28.040707.2996@cs.umn.edu> Date: 28 Jul 90 04:07:07 GMT References: <1990Jul26.062713.24394@rfengr.com> <1990Jul27.060743.26946@spectrum.CMC.COM> Organization: University of Minnesota, Minneapolis - CSCI Dept. Lines: 44 In article <1990Jul27.060743.26946@spectrum.CMC.COM> lars@spectrum.CMC.COM (Lars Poulsen) writes: >In article <1990Jul26.062713.24394@rfengr.com> rfarris@RFEngr.com (Rick Farris) writes: [...] >So: As hard as you try, you will NOT find a place to strap your >IP address into the board. The explanation was good in that it was a good layman's description, but I see the need to have the questions answered more in terms of what to do next. The ethernet address is, as was said before, a low level address. It corresponds roughly to a hardware serial number which follows the equipment around from birth to death. The IP address is configureable vi the application's packet driver. NCSA telnet has a configuration file (config.tel) which contains all the parameters to set up the card including the IP address. An extract from the config.tel file is shown below. Tim Peiffer ----------- Tim Peiffer peiffer@cs.umn.edu or Computer Science Dept ..!rutgers!umn-cs!peiffer University of Minnesota MPLS MN 55455 ---------------------- myip=128.101.226.102 # ip types are # xx.yy.zz.qq - your IP address netmask=255.255.0.0 # needed if not using BOOTP. hardware=packet # harware choices # 3com - 3com 3c501 # 3c523 - 3com 3c523 # wd800 - Western Digitial 800E # nicpc - # nicps - # ni5210 - Micom Interlan NI5210 card -- ----------- Tim Peiffer peiffer@cs.umn.edu or Computer Science Dept ..!rutgers!umn-cs!peiffer University of Minnesota