🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.linux.networking
Article #263

TCP/IP via network failure

#263
From: Tony Langdon
Date: Sun, 13 Apr 1997 00:00
63 lines
2856 bytes
It's 05 Apr 97  12:39,
We'll return to wjackson@mail.interlink.net.au and All's
discussion of TCP/IP via network failure

 wj> The way i have it set up is as this:
 wj> Linux box:
 wj> IP:  172.16.0.0
          ^^^^^^^^^^

There's your problem.  You can't use .0 as a host address.  It's a
network address, and won't work as you vound out. :-)

 wj> Gateway:  111.112.113.1
 wj> (Because I am not using a gateway)

What's this address of?  If you're not using a gateway (i.e. standalone
LAN), don't put one in...

 wj> Netmask: 255.0.0.0

Doesn't match with your host address...

 wj> Nameserver: 172.16.0.1

 wj> Most of the above are the defaults from the installation.

 wj> When I try "ftp 172.16.0.0" I get "Can't assign requested address".
 wj> When I try "ftp 172.16.0.1" I get "Connection Timeout" or "ICMP
 wj> network unreachable"

 wj> Is there somethin I have forgotten to do or have missed.

I suspect you're a little confused about TCP/IP, and need a few
pointers.  I've listed a few good places to start in the next paragraph.

I suggest you have another look at the Net Howtos and take a look at the
Linux Systems Administrator's Guide.  A good beginner's book on TCP/IP
networking would come in handy too.

Also, if you describe your environment (i.e. if your LAN is standalone,
or connected to the Internet - if Internet connected, your assigned IP
addresses and netmask, ISP's IP adress and nameserver address).

The information you need is best gotten from Linux networking docs and
TCP/IP references.  Once you have a handle on the basics, then's a good
time to pop in here to ask for clarification, or simply to get a second
opinion on your setup. :-)

Good luck with your networking.

P.S.  This is not intended as a flame, or a "RTFM post".  I'm suggesting
doing a bit of reading and experimenting so you can understand TCP/IP a
little.  It comes in handy. :-)

... COFFEE.EXE not found: (A)bort, (R)etry, (F)all asleep
--
| Fidonet:  Tony Langdon 3:632/367.2
| Internet: tlang@freeway.DIALix.oz.au
|
| Freeway Internet Gateway, Melbourne, Australia.  For information about
| our services and conditions of use, e-mail:
| info@freeway.DIALix.oz.au, to receive a copy of the FAQ.
Technical Details
Message-ID: <43e_9704140746@freeway.DIALix.oz.au>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <01bc416d$0b6f1040$2d8c37cb@whack.org>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10669a,6c78c0daf085c0e8
X-Google-Attributes: gid10669a,public
X-Google-Thread: 102983,6c78c0daf085c0e8
X-Google-Attributes: gid102983,public
From: tlang@freeway.DIALix.oz.au (Tony Langdon)
Subject: TCP/IP via network failure
Date: 1997/04/13
Message-ID: <43e_9704140746@freeway.DIALix.oz.au>
X-Deja-AN: 234589728
References: <01bc416d$0b6f1040$2d8c37cb@whack.org>
Organization: Fidonet: Freeway Usenet <=> FTN gateway 
Newsgroups: comp.os.linux.networking,aus.computers.linux
X-FTN-To: wjackson@mail.interlink.net.au