From: Andrew Lunn <andrew@lunn.ch>
To: Burl Nyswonger <burl@nyswonger.org>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Obtaining all entries from the routing table...
Date: Thu, 16 Oct 2003 07:25:00 -0000 [thread overview]
Message-ID: <20031016072508.GA32391@lunn.ch> (raw)
In-Reply-To: <Pine.LNX.4.21.0310151333020.27998-100000@mx.nyswonger.org>
On Wed, Oct 15, 2003 at 01:36:14PM -0700, Burl Nyswonger wrote:
>
> Hi,
>
> I have been digging through both the the Free/Open BSD derrived stacks as
> well as the net/common stuff and I'm not finding a way to obtain a list of
> all routes. Under linux, this information is available via the /proc
> filesystem, under other OS's it is available through similar means, or
> through an ioctl interface, or sysctl(), etc...
>
> What gives? Am I missing something?
Yep, dig a bit deeper....
1) The FreeBSD has sysctl is you enable it.
2) Both stacks support ioctl calls to get/set this information.
3) Take a look at show_network_tables() in support.c for the FreeBSD stack.
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-10-16 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 3:49 Burl Nyswonger
2003-10-16 7:25 ` Andrew Lunn [this message]
2003-10-23 0:28 ` [ECOS] stdout/stderr and CRLF translations Burl Nyswonger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031016072508.GA32391@lunn.ch \
--to=andrew@lunn.ch \
--cc=burl@nyswonger.org \
--cc=ecos-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).