Reading the IP/TCP routing tables from memory (request)

Article View: net.eunice

Article #141

#141

From: Bruce Pinn
Date: Fri, 16 Nov 1984 19:21

25 lines
1454 bytes

     Our site is currently running Wollongong's IP/TCP under Eunice.  Recently
I have been attempting to port the route daemon to our machine and have run
into a number of problems.  They are

	1.  How does one read the routing tables directly from the kernel
	    code?  /dev/kmem does not exist under Eunice and hence is not
	    available for reading.

	2.  I believe that the nlist function works off of the inet.stb
	    file.  Is this correct, or am I simply on a winding trail to
	    nowhere?

Does anyone (please) know the answer to these questions, or can provide
insite into the way Wollongong reads the incore tables (they must be
reading the `inet memory' for commands like netstat, route, etc).

				Thanks in advance!

				Bruce Pinn (University of Toronto)
				...allegra!utzoo!utcs!utgumby!bwp
				...ihnp4!utcs!utgumby!bwp

p.s.  With a few minor exceptions Wollongong's IP/TCP code is really
      quite good!

Technical Details

Message-ID: <206@utcs.UUCP>

Path: arc1-ca.pugleaf.net!utzoo!utcs!bwp

Show Full Headers

Complete Article Headers

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site utcs.UUCP
Path: arc1-ca.pugleaf.net!utzoo!utcs!bwp
From: bwp@utcs.UUCP (Bruce Pinn)
Newsgroups: net.eunice
Subject: Reading the IP/TCP routing tables from memory (request)
Message-ID: <206@utcs.UUCP>
Date: Fri, 16-Nov-84 14:21:45 EST
Article-I.D.: utcs.206
Posted: Fri Nov 16 14:21:45 1984
Date-Received: Fri, 16-Nov-84 14:41:04 EST
Organization: University of Toronto - General Purpose UNIX
Lines: 25