All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timo Teras <timo.teras@iki.fi>
To: netdev@vger.kernel.org
Subject: inet netconf support for send_redirects
Date: Wed, 6 May 2015 16:37:46 +0300	[thread overview]
Message-ID: <20150506163746.38d75537@vostro> (raw)

Hi,

I'm wondering if inet netconf support is planned or known will-not-add
for send_redirects (or the other missing proc/sys/ipv4/<if>/ knobs)?

I would be interested in this, and willing to implement it at least for
send_redirects. Mostly because I'd like an user-space routing daemon to
be able to control it, and run it as non-root. Now it's not possible
without dac-override capability to access proc/sys which sounds an
overkill for this purpose. Where as with netlink access the net-admin
capability is suit for the job.

Semi-relatedly, is there any specific reason why send_redirects is a
IN_DEV_ORCONF() option? Meaning that having the all/send_redirects set
to yes (the default) redirects are always sent. I would have thought
IN_DEV_ANDCONF() would make more sense in this case. Or is this just
some legacy thing?

Thanks,
Timo

             reply	other threads:[~2015-05-06 13:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 13:37 Timo Teras [this message]
2015-05-13 18:51 ` inet netconf support for send_redirects Nicolas Dichtel

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=20150506163746.38d75537@vostro \
    --to=timo.teras@iki.fi \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.