From 827b093d3bcaebfc16be017a009a9ae0c2a0c17a Mon Sep 17 00:00:00 2001 From: "https://openid.fmarier.org/" Date: Sun, 12 May 2013 08:37:39 +0000 Subject: [PATCH] Added a comment: Make sure your network is correctly set up in the first place! --- ...comment_7_17d44229e4fa46c50815672b96a9735a._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/assistant/local_pairing_walkthrough/comment_7_17d44229e4fa46c50815672b96a9735a._comment diff --git a/doc/assistant/local_pairing_walkthrough/comment_7_17d44229e4fa46c50815672b96a9735a._comment b/doc/assistant/local_pairing_walkthrough/comment_7_17d44229e4fa46c50815672b96a9735a._comment new file mode 100644 index 0000000000..84a921eab2 --- /dev/null +++ b/doc/assistant/local_pairing_walkthrough/comment_7_17d44229e4fa46c50815672b96a9735a._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="https://openid.fmarier.org/" + nickname="fmarier" + subject="Make sure your network is correctly set up in the first place!" + date="2013-05-12T08:37:38Z" + content=""" +It turns out that my internal network had badly broken IPv6 configs between the boxes. That was interfering with the multicast packets but not with anything else since all of my other internal traffic is over IPv4. + +Getting rid of these static IPv6 addresses has solved my problem. Local pairing is now working as advertised :) +"""]]