Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!network.ucsd.edu!usc!elroy.jpl.nasa.gov!ames!bionet!raven.alaska.edu!skyfire.uacn.alaska.edu!sxjcb
From: sxjcb@skyfire.uacn.alaska.edu (Jay C. Beavers)
Newsgroups: comp.unix.bsd
Subject: 386BSD 0.1 & FTP
Summary: Cannot get FTP to work
Keywords: 386BSD FTP
Message-ID: <sxjcb.24.711418490@skyfire.uacn.alaska.edu>
Date: 18 Jul 92 00:14:50 GMT
Sender: news@raven.alaska.edu (USENET News System)
Organization: University of Alaska Computer Network
Lines: 27
Nntp-Posting-Host: skyfire.uacn.alaska.edu
First off, great job Bill & Lynne!
Secondly, I'm opting to install 386BSD via FTP. I have a 3c503 card that I
have changed the jumpers on to conform to 386BSD. When I boot from the HD
after installing Tiny 386BSD, all goes well. My 3c503 card is recognized as
ec0 and all that good stuff.
I have an ip number of 137.229.10.85 assigned to my machine on a network
where our internet gateway is 137.229.10.5. I then type:
ifconfig ec0 137.229.10.85 -- looks good, ifconfig ec0 shows config
route add default 137.229.10.5 -- good as far as I can tell, no errors
ftp 128.252.135.4 -- this is wuarchive, a site with 386BSD
Connect: Connection timed out
ftp> open 137.229.10.39 -- .10.39 is a local host I have an acct on
Connect: Connection timed out
So, I'm lost here. It looks good to me and as far as I know I should be
able to reach 10.39 with no routing tables at all. Can anyone guess what
might be up?
- jcb
______________________________________________________________________________
|
Jay C. Beavers | sxjcb@orca.alaska.edu
University of Alaska Computer Network | sxjcb@alaska.bitnet
______________________________________|_______________________________________