23 Jul 96 , Dave Freeman did fondle the keyboard and wrote to me!:
 Yowser & greets Dave!,

 DF> (Obviously I'm a bit behind on this thread here so just ignore me if
 DF> this has already been mentioned...)

 RVR>> I don't run a subnet, the IP's are basically an extention of
 RVR>> ion.com.au

 RVR>> Route's are as below:

 DF> I couldn't reassemble the table into something that makes a lot of
 DF> sense after it was reflowed (just a reminder that to preserve table
 DF> layouts you should leave a space at the start of each line...).

Sorry, I thought I checked that originally - such a while back I can't
really remember....

 DF> One thing that I couldn't clearly see though, you need an IP address
 DF> for each _interface_ rather than an IP address for each machine.  So,
 DF> if your Win95 machine uses an ethernet you have an IP address for that
 DF> ethernet.  Then your Amiga should have an IP address for it's ethernet
 DF> and _another_ IP for it's PPP dialup.  Any routing statements and the
 DF> like must take this into account.

Ahh! Here's this point again. There seems to be 2 groups of thinking when
it comes to TCP. One group, to which you seem to belong, believes that your
interface needs a separate IP, the other group do not support this theory.

I belong to the "other" group :)

Logically speaking, your interface is not an address, so why does it need
an address allocated? You are basically saying I need 4 IP's for my 2
machines. True this will work but it is not really needed. The computer is
the address, it is what processes the TCP packets and protocols.

I look at it as if I only had a ppp link to my ISP then I would need 2
addresses, one for the Amiga and one for the PPP. But this is not the case,
the ppp is the same IP as my computer, it is given (in the state of dynamic
connections) by the ISP and is the address used to contact any TCP related
programs on my machine.

Also, my ISP (and a few others I have seen) run extra machines for their
own purposes off their server, this is usually done with ethernet cards.
They only give the machine connected an IP, they don't allocate addresses
to the actual ethernet connection other than to give it the machines IP.

I did however try this on my network, but it produced no better result. The
fault does lie in the sanaII driver for the Quicknet card and it's way of
interpreting packets (still waiting for the fix). The machines will talk
with their already allocated IP's, I just can't send to the PC any packet
greater than 1352bytes as windows cannot determine the packet after it
exceeds this size.

So my setup and routing table has been fine since day 1 (AFAIK) - it's just
a matter of waiting now...

Cheers,       __
             /_/                 
            / \*icta*...

--- Spot 1.3a #506