Hello, I use tinc on asus router and it works fine. But when Irun it behind a NAT router, it only works fine when I use tcponly. If I use udp, I get this error, that the originator is not known, even it is the correct sender. Both ends have nat router. When I use tcponly all works fine. Any idea how i can use udp? ALBI...
On Sat, May 26, 2007 at 01:22:41PM +0200, Albi Rebmann wrote:> I use tinc on asus router and it works fine. > But when Irun it behind a NAT router, it only works fine when I use tcponly. > If I use udp, I get this error, that the originator is not known, even > it is the correct sender. > Both ends have nat router. > When I use tcponly all works fine. > Any idea how i can use udp?You should set up port forwarding on both NAT routers. The issue can be fixed in tinc, but it will require a change in the protocol, so this will not happen before version 2.0. -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus@tinc-vpn.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/20070526/9006763e/attachment.pgp
>> I use tinc on asus router and it works fine. >> But when Irun it behind a NAT router, it only works fine when I use tcponly. >> If I use udp, I get this error, that the originator is not known, even >> it is the correct sender. >> Both ends have nat router. >> When I use tcponly all works fine. >> Any idea how i can use udp? > > You should set up port forwarding on both NAT routers. The issue can be > fixed in tinc, but it will require a change in the protocol, so this > will not happen before version 2.0.I have done this. But the problem will only disappear when I add tcponly. I will hope for 2.0. ALBI...