🚀 go-pugleaf

In article <01bc416d$0b6f1040$2d8c37cb@whack.org>, Warp wrote:
>The way i have it set up is as this:
>Linux box:
>	IP:		172.16.0.0
>	Gateway: 	111.112.113.1
>	(Because I am not using a gateway)
>	Netmask:	255.0.0.0
>	Nameserver:	172.16.0.1
>
>Most of the above are the defaults from the installation.
>
>When I try "ftp 172.16.0.0" I get "Can't assign requested address".

Anything ending in .0 is a network address.  You can't use it for a
single machine.  Change "IP" to something like 172.16.0.10

>When I try "ftp 172.16.0.1" I get "Connection Timeout" or "ICMP network
>unreachable"

Not sure there, but I expect there's a conflict due to the other problem.
The route probably isn't being set up.

So, in summary, your network should be 172.16.0.0
and your Linux box's address should be 172.16.0.X
where X is between 1 and 254.  (255 is another reserved number)

Warp wrote:
> 
> I am try to connect my linux box to my win95 system via 2xNE2000 cards.  I
> have tested the cards and they do work.
> 
> The way i have it set up is as this:
> Linux box:
>         IP:             172.16.0.0
>         Gateway:        111.112.113.1
>         (Because I am not using a gateway)
>         Netmask:        255.0.0.0
>         Nameserver:     172.16.0.1
> 
> Most of the above are the defaults from the installation.
> 
> When I try "ftp 172.16.0.0" I get "Can't assign requested address".
> When I try "ftp 172.16.0.1" I get "Connection Timeout" or "ICMP network
> unreachable"

Set your linux box's IP address to 192.168.200.x
Set your Win95 IP address to 192.168.200.y
Set your netmask to 255.255.255.0
Don't set the gateway or nameserver IP address, since you don't have
them.
x and y cannot be 0 or 254 (and x cannot be the same as y, obviously)
This is because 0 is used as network address, and 255 is a broadcast
address.  I think.

The numbers 192.168.200.0-255 are defined in an RFC as numbers that
are not present as 'real' addresses on the internet, ie. for use
in situations like yours.  You can of course use any numbers you like,
but if you connect to the internet later any IP addresses that conflict
with yours will be unreachable.

Hope this helps.

-- 
Steve Baker,  aka  bakes@corona.iinet.net.au
Your limitations are restricted by your goals, not the other way around.

Warp wrote:
> 
> I am try to connect my linux box to my win95 system via 2xNE2000 cards.  I
> have tested the cards and they do work.
> 
> The way i have it set up is as this:
> Linux box:
>         IP:             172.16.0.0
>         Gateway:        111.112.113.1
>         (Because I am not using a gateway)
>         Netmask:        255.0.0.0
>         Nameserver:     172.16.0.1
> 
> Most of the above are the defaults from the installation.
> 
> When I try "ftp 172.16.0.0" I get "Can't assign requested address".
> When I try "ftp 172.16.0.1" I get "Connection Timeout" or "ICMP network
> unreachable"
> 
> Is there somethin I have forgotten to do or have missed.
> 
> Thankyou

Hi Warp, Not too sure about your settings...Try these:-


Linux box
---------

         IP:             192.168.0.1
         Gateway:        0.0.0.0
         Netmask:        255.255.255.0
         Nameserver:     Should point to the machine with Domain Name
Services.

Win 95 box
----------

         IP:             192.168.0.2
         Gateway:        0.0.0.0	( This normally points to a router. )
         Netmask:        255.255.255.0
         Nameserver:     Should point to the machine with Domain Name
Services.


Once you have these settings in place you can use the "ping" command
from both ends to test the link. From the Linux box login and type "ping
192.168.0.2" and you should get a responce telling you about the time it
took to send and recieve the packet. Same from the Win 95 box but use
"ping 192.168.0.1".

Just for you reference the set of IP numbers I have used are public
numbers. This means that they don't conflict with any numbers used on
the internet today....

Regards

Paul MaC

Paul MaC <pm@mail.campaspe.net.au> writes:

> Just for you reference the set of IP numbers I have used are public
> numbers. This means that they don't conflict with any numbers used on
> the internet today....

Close.

There are Class A, B, and C address blocks which are "reserved" for internal
networks.

In general, this means that sane routers will drop these packets should
they make it through your firewall/router.

FYI


Saundo

--
Chris "Saundo" Saunderson       Chris.Saunderson@adelaide.maptek.com.au
Technical Support Engineer      Telephone: (08) 8379 7333
		Maptek Pty Ltd - Adelaide
"The problem with troubleshooting is that sometimes trouble shoots back."

"Warp" <wjackson@mail.interlink.net.au> writes:

>I am try to connect my linux box to my win95 system via 2xNE2000 cards.  I
>have tested the cards and they do work.

>The way i have it set up is as this:
>Linux box:
>	IP:		172.16.0.0
>	Gateway: 	111.112.113.1
>	(Because I am not using a gateway)
>	Netmask:	255.0.0.0
>	Nameserver:	172.16.0.1

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

>When I try "ftp 172.16.0.0" I get "Can't assign requested address".

Sounds like an ARP problem.
-- 
Please excuse my spelling as I suffer from agraphia see the url in my header. 
Never trust a country with more peaple then sheep.  /\ /\ /\    Buy easter
Save the ABC Is $0.08 per day too much to pay?     (  X  X  )     bilbies.
I can't walk but I can fly. It's lucky to be ducky  \/ \/ \/

Steve Baker wrote:
> 
...
> 
> The numbers 192.168.200.0-255 are defined in an RFC as numbers that
> are not present as 'real' addresses on the internet, ie. for use
> in situations like yours.  You can of course use any numbers you like,
> but if you connect to the internet later any IP addresses that conflict
> with yours will be unreachable.

I believe that sane ISPs actually reject all routing information
that comes from their dial-up clients -- precisely because of the
that problem.

-- 
Dimitri
-------
sig:
 "By US Code Title 47, Sec.227(a)(2)(B), a computer/modem/printer meet
the
  definition of a telephone fax machine.  By Sec.227(b)(1)(C), it is
unlawful
  to send any unsolicited advertisement to such equipment. By
Sec.227(b)(3)(C),
  a violation of the aforementioned Section is punishable by action to
recover
  actual monetary loss, or $500, whichever is greater, for each
violation."
(Solicited advertisements <huh?> and other such can be sent to 
  emaziuk at curtin.edu.au)

> "Warp" <wjackson@mail.interlink.net.au> writes:
> 
> >I am try to connect my linux box to my win95 system via 2xNE2000 cards.  I
> >have tested the cards and they do work.
> 
> >The way i have it set up is as this:
> >Linux box:
> >       IP:             172.16.0.0
> >       Gateway:        111.112.113.1
> >       (Because I am not using a gateway)
> >       Netmask:        255.0.0.0
> >       Nameserver:     172.16.0.1
> 
> >Most of the above are the defaults from the installation.
> 
> >When I try "ftp 172.16.0.0" I get "Can't assign requested address".
> 

Hi

You're assigning a not valid IP-Number as IP-Address. 
172.16.0.0 is a network address, not an IP-number for NICs.
Try to assign 172.16.0.2 for this NIC(network interface card).
Some informations about IP-Addresses can be found in the
subnetworking mini HOWTO. BTW you should change those addresses
to 192.168.xxx.xxx because these are for internal use and do not
exist in the normal internet.

Stephan Ullmann

The problem has been solved, many thanks to everone how assisted.

Everything hase been set up correctly now but I have to replace a network
card.

Once again Thankyou

Warp <wjackson@mail.interlink.net.au> wrote in article
<01bc416d$0b6f1040$2d8c37cb@whack.org>...
> I am try to connect my linux box to my win95 system via 2xNE2000 cards. 
I
> have tested the cards and they do work.
> 
> The way i have it set up is as this:
> Linux box:
> 	IP:		172.16.0.0
> 	Gateway: 	111.112.113.1
> 	(Because I am not using a gateway)
> 	Netmask:	255.0.0.0
> 	Nameserver:	172.16.0.1
> 
> Most of the above are the defaults from the installation.
> 
> When I try "ftp 172.16.0.0" I get "Can't assign requested address".
> When I try "ftp 172.16.0.1" I get "Connection Timeout" or "ICMP network
> unreachable"
> 
> Is there somethin I have forgotten to do or have missed.
> 
> Thankyou
> 

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.

It's 06 Apr 97  14:30,
We'll return to pm@mail.campaspe.net.au and All's
discussion of TCP/IP via network failure

 pm> IP:             192.168.0.1
 pm> Gateway:        0.0.0.0
 pm> Netmask:        255.255.255.0
 pm> Nameserver:     Should point to the machine with Domain Name
 pm> Services.

In Linux, you shouldn't need to specify a router.  Just a couple of
route commands:

route add 127.0.0.1 lo
route add 192.168.0.0 netmask 255.255.255.0 eth0

should do the trick. :-)

As for the nameserver, leave it blank if none present, and edit
/etc/resolv.conf to have the line:

order hosts

so Linux doesn't attempt to query a non-existent nameserver, and only
uses the local hosts file to resolve hostnames.

Otherwise if a nameserver is available, point it to that machine.

 pm> Win 95 box
 pm> ----------

 pm> IP:             192.168.0.2
 pm> Gateway:        0.0.0.0 ( This normally points to a router. )
 pm> Netmask:        255.255.255.0
 pm> Nameserver:     Should point to the machine with Domain Name
 pm> Services.

Or leave blank if no nameserver is present.  For 2 machines, it's
simpler to put the hostnames in /etc/hosts (Linux) and hosts.txt
(Windows). :)

 pm> Just for you reference the set of IP numbers I have used are public
 pm> numbers. This means that they don't conflict with any numbers used on
 pm> the internet today....

And should only be used for isolated networks or those behind a
firewall, where traffic can't (under normal circumstances) directly
enter the Internet.  (the Internet won't know how to route for these
addresses, so things won't work).

... "I'm out of coffee, off my medication, and you say NO mail!?!"
--
| 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.

It's 10 Apr 97  11:19,
We'll return to wjackson@powerup.com.au and All's
discussion of TCP/IP via network failure

 wj> The problem has been solved, many thanks to everone how assisted.

 wj> Everything hase been set up correctly now but I have to replace a
 wj> network card.

 wj> Once again Thankyou

Good to hear, and enjot your new network. :-)

... WINDOWS: What you throw your computer out of.
--
| 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.