From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/2] Support IPv6 Neighbor Discovery Protocol for dhcpcd
Date: Thu, 9 May 2013 18:12:31 +0200 [thread overview]
Message-ID: <20130509161231.GA4209@siphos.be> (raw)
In-Reply-To: <518BA0A3.5040501@tresys.com>
On Thu, May 09, 2013 at 09:12:03AM -0400, Christopher J. PeBenito wrote:
> On 05/07/13 14:37, Sven Vermeulen wrote:
> > The dhcpcd client supports IPv6 NDP, but when trying to use it the request fails
> > with:
> >
> > ipv6rs: Permission denied
> >
> > In the audit log, a denial is shown about dhcpc_t wanting to create a
> > rawip_socket. After allowing this, the client succeeds.
>
> Thats odd; I don't see this on my IPv6 system. Which version of dhcpcd is this seen on? I'm using 5.6.8.
I'm using dhcpcd-5.6.4 currently; I use the "-t 5 -L --ipv6ra_own"
options.
I tried it again (disabled the rule):
* Bringing up interface eth0
* dhcp ...
* Running dhcpcd ...
dhcpcd[19528]: version 5.6.4 starting
dhcpcd[19528]: all: disabling Kernel IPv6 RA support
dhcpcd[19528]: ipv6rs: Permission denied
dhcpcd[19528]: ipv6nd: Permission denied
dhcpcd[19528]: eth0: broadcasting for a lease
dhcpcd[19528]: timed out
dhcpcd[19528]: all: restoring Kernel IPv6 RA support
* ERROR: net.eth0 failed to start
I'll update to 5.6.8 soon and see if it persists.
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2013-05-09 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 18:37 [refpolicy] [PATCH 0/2] Small dhcpc_t updates Sven Vermeulen
2013-05-07 18:37 ` [refpolicy] [PATCH 1/2] Update for pump DHCP client Sven Vermeulen
2013-05-09 13:17 ` Christopher J. PeBenito
2013-05-07 18:37 ` [refpolicy] [PATCH 2/2] Support IPv6 Neighbor Discovery Protocol for dhcpcd Sven Vermeulen
2013-05-09 13:12 ` Christopher J. PeBenito
2013-05-09 16:12 ` Sven Vermeulen [this message]
2013-05-09 16:24 ` Christopher J. PeBenito
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=20130509161231.GA4209@siphos.be \
--to=sven.vermeulen@siphos.be \
--cc=refpolicy@oss.tresys.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 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.