mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tony Nugent <tony@growzone.com.au>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-net <linux-net@vger.kernel.org>
Subject: Re: How to programatically determine if policy-based routing is compiled into the kernel?
Date: Thu, 07 Dec 2000 18:01:27 +1000	[thread overview]
Message-ID: <200012070801.eB781RY23347@gandalf.growzone.com.au> (raw)
In-Reply-To: message-id <3A2F3FE7.5CDD0EDA@candelatech.com>  of Thu, Dec 07 00:44:39 2000

On Thu Dec 07 2000 at 00:44, Ben Greear wrote:

> I have a product that is dependent on policy-based (source routing)
> and would like to be able to scream loudly at install and startup if
> policy-based routing is not enabled in the kernel.
> 
> Is there some way to determine this?  Specifically, I'd love
> a way to find out through the /proc system, but an ioctl or
> similar call would be OK.  I'd even settle for some other tool,
> like 'ip', if I could just figure out what commands to tell it.

Run a command that attempts to use policy-based routing (doing
something "benign" like a listing).  If it fails then good chance
that it isn't compiled in :-)

[ or it may simply mean that the appropriate modules are not loaded,
so beware that one :]

That command would need to be /sbin/ip or /sbin/tc or whatever.

If you want to ferrit out what proc looks like with and without
routing policy enabled, that would be another way to do it.

Cheers
Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-12-07  8:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-07  7:44 Ben Greear
2000-12-07  8:01 ` Tony Nugent [this message]

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=200012070801.eB781RY23347@gandalf.growzone.com.au \
    --to=tony@growzone.com.au \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®