From: Matthew Hall <mhall@mhcomputing.net>
To: peter green <plugwash@p10link.net>
Cc: debian-ipv6@lists.debian.org, netdev@vger.kernel.org
Subject: Re: bad interaction between privacy extensions, prefix lifetimes and protocols that maintain long-term connections.
Date: Mon, 9 Jan 2017 13:41:42 -0800 [thread overview]
Message-ID: <20170109214142.GA6465@mhcomputing.net> (raw)
In-Reply-To: <9769f6b7-946c-1279-110f-15de8ec40022@p10link.net>
On Sat, Jan 07, 2017 at 03:16:06PM +0000, peter green wrote:
> For the main MAC-based address the valid_lft is always short but it is
> updated by new RAs so the address remains valid.
>
> However privacy addresses inherit their valid_lft from the main MAC-based
> address and unlike the main address it is not updated causing the addresses
> to time out. I believe that the timeout of these privacy addresses is what
> is causing my repeated disconnections from IRC.
Privacy addresses generally cause me nothing but absolute misery.
Despite the MAC address problem I usually end up disabling them just to be
able to survive without losing my sanity due to issues like this one.
I have had all kinds of applications not work reliably because of them.
Including Google Chrome / Chromium etc. IRC also seems like a likely victim,
but I wouldn't have noticed because I use it from a system with a static
address.
Perhaps a workaround would be using the MAC address override ability in the
interfaces file pre-up script with "ip link set eth0 address 02:01:02:03:04:08".
Randomly generate one fake MAC per boot.
Matthew.
next prev parent reply other threads:[~2017-01-09 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 15:16 bad interaction between privacy extensions, prefix lifetimes and protocols that maintain long-term connections peter green
2017-01-09 21:41 ` Matthew Hall [this message]
2017-01-11 8:54 ` Bjørn Mork
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=20170109214142.GA6465@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=debian-ipv6@lists.debian.org \
--cc=netdev@vger.kernel.org \
--cc=plugwash@p10link.net \
/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;
as well as URLs for NNTP newsgroup(s).