On Wed, Sep 22, 2004 at 06:56:30PM +1000, Ray Phillips wrote:
[...]
> (The three NICs are in adjacent PCI slots and, strangely, when 
> viewing the PC from the rear ex0 is on the left, ex2 is in the 
> middle, and ex1 is on the right.  I thought they'd be in order from 
> left to right.)

dmesg will answer that.

> This works fine--it's possible to ping any machine from any other and 
> telnet and ftp between them.  I didn't go to the trouble of modifying 
> their /etc/hosts files or setting up bind on one of them, so I've had 
> to use IP numbers to specify the machine I want to connect to and use 
> the -n switch for  ping  and  route  and -N for telnet.  (I couldn't 
> see a switch like that for ftp; is there one?)
> 
> I don't understand why, even when using -N, it takes so long to 
> establish a telnet session in this situation.  There's a long delay 
> (perhaps a minute or more) after the 'Escape character is' line.  Why 
> would that be?

Because -N switch tells the client not to do lookups.  The server still
does them.

Same applies for ftp.

[...]
> Actually, the IP numbers I've shown above aren't the ones I used at 
> first.  To begin with I assigned two of the non-router PCs IP numbers 
> from two of our public subnets and gave one a private IP number. 
> That setup was OK except it wasn't possible to ftp to the PC with a 
> private IP number; however it could be ping'ed and telnet'ed to, and 
> it could ftp to any of the other machines.  This is what would happen:
> 
> % ftp 192.168.37.1
> Connected to 192.168.37.1.
> 
> 421 Service not available, remote server timed out. Connection closed.
> ftp>

Routing issue, most certainly.

Quentin Garnier.