[comp.sys.ibm.pc.rt] TCP/IP on Ether & Ring.

sam@ncsuvx.ncsu.edu (Whad Upp) (06/07/88)

Nick, our problem is that we either can operate on the ethernet or the
token ring side but not both at once. Should they be different networks?
When it works on the ethernet side we have access to the world. The token
ring side looks good when it is up, also.

Can you send me the names and numbers of some IBM documentation on the
administration of TCP/IP? We only have the user documentation.

Any help is appreciated.

Sam Moore

///"Peel back the mountains peel back the sky, Stomp gravity into the floor"////
///////////////////////REM 'Feeling Gravity's Pull'/////////////////////////////
////////////////////////////////////////////////////////////////////////////////
/////////Sam/Moore/NCSU Computing Center/Raleigh, NC/sam@ncsuvx.ncsu.edu////////


Here is our /etc/net file:
================cut here==============
* /etc/net
* This file contains a stanza for each adapter card (device) that
* TCP can use.  The stanza describes the characteristics for that
* device.  


token0:
	netaddr = 128.109.153.135
	inetlen = 1576


net0:
	netaddr = 128.109.153.133
	inetlen = 1576
================cut here==============



Here is netstat output:
================cut here==============
  Proto  Recv pkts  Send pkts     Local Address          Foreign Address
  UDP            0	    0     *.69                     *..*
  TCP            0	    0     *.25                     *..*
  UDP           20	   20     *.520                    *..*
  TCP            0	    0     *.79                     *..*
  TCP            0	    0     *.21                     *..*
  UDP            0	    0     *.42                     *..*
  ICMP           0	    0     *.*                      *..*
  GGP            0	    0     *.*                      *..*
  TCP            0	    0     *.512                    *..*

		*********** INTERNET ERROR STATISTICS **********
Bad pkt len: 0	Bad proto: 5486	Bad IP hdr len: 0	Bad IP len: 0
Bad checksum: 0	Bad dest: 0	Fragments: 0		No conn: 182
Drops: 0

		**** ADDRESS RESOLUTION PROTOCOL STATISTICS ****
Send : 231	Rcv req: 1485	Rcv reply : 2	Not for me : 1482
Bad pkts: 0	Bad len: 0	Unexpected: 0


token0 : 128.109.153.135	hardware address: 50:00:5a:1a:12:df

		******* NETWORK DEVICE DRIVER STATISTICS *******
Bytes in  : 22984	Pkts in  : 240
Bytes out : 102	Pkts out : 2
Pkts dropped : 0

Interrupts : 242
    Solicited intr : 2
	Timeout : 0	Open_seq_fail : 0
	Init_fail : 0	Unpin_buf_fail : 0
    Unsolicited intr : 240
	Data avail : 240	SLIH underflow: 0	Device overflow : 0


net0 : 128.109.153.133	hardware address: 00:dd:00:3c:37:00

		******* NETWORK DEVICE DRIVER STATISTICS *******
Bytes in  : 613801	Pkts in  : 7107
Bytes out : 26122	Pkts out : 389
Pkts dropped : 0

Interrupts : 6624
    Solicited intr : 2
	Timeout : 0	Open_seq_fail : 0
	Init_fail : 0	Unpin_buf_fail : 0
    Unsolicited intr : 6622
	Data avail : 6622	SLIH underflow: 0	Device overflow : 0

		**************** VRM STATISTICS ****************


token0:
Receive interrupts: 240	Packets accepted: 240	Packets rejected: 0
Transmit interrupts: 2	Packets transmitted: 2
Ring queue full: 0	SLIH ring empty: 0	Receive overflow: 0


net0:
Receive interrupts: 6956	Packets accepted: 7111	Packets rejected: 0
Packets transmitted: 389
Collisions: 0	16_Collisions: 0	Shorted: 0	Underflow: 0
Short packets: 0	Alignment errors: 0	CRC errors: 0	Overflow : 0

		*************** Host-Gateway Table *************
		Host			Gateway		Metric


================cut here==============