lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53A1A702.1020300@candelatech.com>
Date:	Wed, 18 Jun 2014 07:49:38 -0700
From:	Ben Greear <greearb@...delatech.com>
To:	Dan Williams <dcbw@...hat.com>
CC:	Bjørn Mork <bjorn@...k.no>,
	netdev <netdev@...r.kernel.org>
Subject: Re: How is IPv6 dhcp supposed to work?

After more printk debugging, it seems it is failing to accept the RA due to
ipv6_chk_addr failing in the ndisc_router_discovery method.

This is probably because one interface on my system is running radvd
(on one side of a veth pair), and the peer veth is supposed to be
accepting the ra.

The chk_addr is checking if the source addr for the RA is not found locally, as far
as I can tell, but in my case, it is local, and it still should be accepted.

My case is a bit special (I'm doing virtual network type things), but
maybe there is a more useful reason to allow this restriction to be
relaxed with yet another sysctl?

Thanks,
Ben

-- 
Ben Greear <greearb@...delatech.com>
Candela Technologies Inc  http://www.candelatech.com

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ