tinc bug (bogus connection)

[Luke Kenneth Casson Leighton]

okay, that version still doesn't work.

i see the CHAL/resp stuff going on: the last packet sent
is a CHAL_REPLY of 43 bytes.  i see "sending 43 bytes of metadata
to host jekyl".

what i _don't_ see in the logs is the host jekyl actually _receiving_ that
packet.

instead i see a "closing connection request" by jekyl:

Aug 22 16:29:54 hyd tinc.aeon[30964]: Got CHALLENGE from jekyl
(217.43.44.75 port 655): 2
BEHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
HJHHHHHHHHHHHHHHHHH
HHHHHHHHHHHHHHHHH
Aug 22 16:29:54 hyd tinc.aeon[30964]: Sending CHAL_REPLY to jekyl
(217.43.44.75 port 655): 3 AXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Aug 22 16:29:54 hyd tinc.aeon[30964]: Sending 43 bytes of metadata to
jekyl (217 .43.44.75 port 655)
Aug 22 16:29:54 hyd tinc.aeon[30964]: Connection closed by jekyl
(217.43.44.75 port 655)


i switched over to TCP again, btw, in case it helped.


-- 
-- 
expecting email to be received and understood is a bit like
picking up the telephone and immediately dialing without
checking for a dial-tone; speaking immediately without listening
for either an answer or ring-tone; hanging up immediately and
then expecting someone to call you (and to be able to call you).
--
every day, people send out email expecting it to be received
without being tampered with, read by other people, delayed or
simply - without prejudice but lots of incompetence - destroyed.
--
please therefore treat email more like you would a CB radio
to communicate across the world (via relaying stations):
ask and expect people to confirm receipt; send nothing that
you don't mind everyone in the world knowing about...
Tinc:         Discussion list about the tinc VPN daemon
Archive:      http://mail.nl.linux.org/lists/
Tinc site:    http://tinc.nl.linux.org/