Just compiled and tested. Looking good! It’s returning only the correct
(global) address for forward queries, and returning temporary addresses for
reverse queries. Thanks for the fix, Simon!
Yours,
~ M.
On Dec 17, 2014, at 7:43 AM, Simon Kelley si...@thekelleys.org.uk wrote:
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I just pushed changes to the git repo to implement this. Michael,
please could you seen if it now behaves as you'd like?
Cheers,
Simon.
On 01/12/14 18:49, Michael Gorbach wrote:
On Nov 30, 2014, at 11:17 AM, Simon Kelley
On Nov 30, 2014, at 11:17 AM, Simon Kelley si...@thekelleys.org.uk wrote:
On 29/11/14 19:18, Michael Gorbach wrote:
Hi All,
I've got a question and potential enhancement request. It looks like
right now, the (very useful) interface-name feature pulls all
(global) addresses from the
On 01/12/14 18:49, Michael Gorbach wrote:
On Nov 30, 2014, at 11:17 AM, Simon Kelley si...@thekelleys.org.uk
wrote:
On 29/11/14 19:18, Michael Gorbach wrote:
Hi All,
I've got a question and potential enhancement request. It looks
like right now, the (very useful) interface-name feature
On 29/11/14 19:18, Michael Gorbach wrote:
Hi All,
I've got a question and potential enhancement request. It looks like
right now, the (very useful) interface-name feature pulls all
(global) addresses from the interface. One of my machines uses IPv6
privacy extensions (known in Linux as
Hi All,
I've got a question and potential enhancement request. It looks like right now,
the (very useful) interface-name feature pulls all (global) addresses from the
interface. One of my machines uses IPv6 privacy extensions (known in Linux as
use_tempaddr), which means that in addition to
