tinc: very interesting problem

[Guus Sliepen]

On Tue, Jan 27, 2004 at 06:08:28PM -0500, Jeremy Singer wrote:

[...]
> connects to client B and "becomes reachable". After Client B  becomes
> reachable (it is communicating over 655), noctest_svr can ping client B ,
> but client B cannot ping noctest_svr. This happens when client B is using

That sounds like a firewall dropping incomming ICMP ping packets.

> TCPONLY and when it is NOT using tcponly. If client A tries to reconnect,
> it doesnt work unless you restart TINC. Client B  never works properly at
> the same time.

That however might be a result of the fact that both clients and the
server all have Subnet = 172.16.240.0/22 in their host config files. I
think it should only be in one of them.

-- 
Met vriendelijke groet / with kind regards,
    Guus Sliepen <guus at sliepen.eu.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://brouwer.uvt.nl/pipermail/tinc/attachments/20040128/129655c6/attachment.pgp