tinc bug (bogus connection)

[Luke Kenneth Casson Leighton]

guus,

i just compiled latest cvs: the bug is still there.

the diffs i have against what i got from cvs and what is
debian 1.0.2_2 show that the only significant addition
is of an AF_UNKNOWN and its use, and the use of a tinc-
defined sockaddrfree (and copy?)

i'm still getting some "Bogus packets" using latest cvs.

i _am_ however, it appears... just now... actually getting
valid connections... after a few abortive connection
attempts...

... but i am still back to square one on the actual packet
routing:

"Cannot route packet: unknown IPv4 destination address 192.168.1.201"


l.

-- 
-- 
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/