tinc connection only usable after ping from other side
uws
uws at xs4all.nl
Fri Jan 16 14:33:18 CET 2004
På Fri, Jan 16, 2004 at 01:30:59PM +0100, Guus Sliepen skrev:
> On Fri, Jan 16, 2004 at 12:03:31PM +0000, Moritz Maisel wrote:
> > The configuration seems to be ok: The tinc-connection is set up correctly
> > and after it is set up, the server can ping the client.
> > The problem is, that after the connection is startet the client isn't
> > able to ping the server (the server doesn't answer the ping requests).
> > I first have to ping FROM the server TO the client. After that the client
> > can also ping the server and has access to the LAN.
> It's caused by a masquerading firewall on your server's side.
> Fix your masquerading firewall (look at the examples on tinc's website)
> or use TCPOnly = yes (see the documentation).
I'm experiencing exactly the same problem as Moritz Maisel does. I run a
masquerading firewall on my server host. Even when using TCPOnly = yes
(which is what I use for all my connections) the problem persists. Any clue?
mvrgr, Wouter
--
:wq mail uws at xs4all.nl
tell myself that i'm not ready yet :: i want to live -- heather nova
Tinc: Discussion list about the tinc VPN daemon
Archive: http://mail.nl.linux.org/lists/
Tinc site: http://tinc.nl.linux.org/
More information about the Tinc
mailing list