diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2012-10-11 23:48:37 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2012-10-11 23:48:37 +0000 |
| commit | 59bca515bf66a75ffc66fdb714cebd51d8f23c87 (patch) | |
| tree | 9bbfd115b6e007e8ce01c39a200af2ebdc59d05e | |
| parent | 74558a9a615b9c733f1bcc4029d9770a3169523b (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/Can__39__t_get_pairing_to_work/comment_1_b981977b4fb942fd109c37fcf40f35d7._comment | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/forum/Can__39__t_get_pairing_to_work/comment_1_b981977b4fb942fd109c37fcf40f35d7._comment b/doc/forum/Can__39__t_get_pairing_to_work/comment_1_b981977b4fb942fd109c37fcf40f35d7._comment new file mode 100644 index 000000000..5e6690354 --- /dev/null +++ b/doc/forum/Can__39__t_get_pairing_to_work/comment_1_b981977b4fb942fd109c37fcf40f35d7._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.246.8" + subject="comment 1" + date="2012-10-11T23:48:37Z" + content=""" +It's not clear from your description whether you + +a) Started the pairing process independently on both machines... which probably doesn't work. + +b) Started pairing on one machine, and the other one noticed and popped up a pair request alert where +you re-entered the password. + +If b) didn't happen, then the the pairing broadcast is not being seen by the second machine. +You can try using tcpdump or wireshark to see the traffic. The traffic will look like this: + +<pre> +19:45:11.125893 IP 10.1.1.2.43376 > 224.0.0.1.55556: UDP, length 692 +</pre> + +If all is going well, you should be able to see that on both the machine that's initiating the pairing and the other machine. And every other machine on the network for that matter. +"""]] |