Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site scgvaxd.UUCP
Path: utzoo!linus!decvax!ittvax!dcdwest!sdcsvax!sdcrdcf!trwrb!scgvaxd!kvc
From: kvc@scgvaxd.UUCP (Kevin Carosso)
Newsgroups: net.eunice
Subject: Re: Reading the IP/TCP routing tables from memory (request)
Message-ID: <237@scgvaxd.UUCP>
Date: Tue, 20-Nov-84 02:08:30 EST
Article-I.D.: scgvaxd.237
Posted: Tue Nov 20 02:08:30 1984
Date-Received: Wed, 21-Nov-84 05:23:59 EST
References: <>
Reply-To: kvc@scgvaxd.UUCP (Kevin Carosso)
Organization: Hughes Aircraft Co., El Segundo, CA
Lines: 15
Summary: 

In article <> bwp@utcs.UUCP (Bruce Pinn) writes:
>
>	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.

One thing to remember -- under VMS, the "kernel" is part of your
address space (it is the S0 (lower half of the upper half, actually)
part).  You can read the routing tables by simply looking at the
right address in system space.   I dunno what the address is, but
maybe Wollongong provided a link map of their driver code, which
would have the symbols and offsets of their data structures (dream
on...).

	/Kevin Carosso            allegra!scgvaxd!kvc
	 Hughes Aicraft Co.