Hi all, I have finally got tinc working, but it?s only between server/client. Client can receive broadcast packets from server ethernet, and pings between them is fine. If I ping tinc client(192.168.88.166) from any machine in my server lan, 192.168.88.0/24, all packets timed out, and nothing received by the client. Any ideas? Thanks! Regards, Quan Zhou +------------------------+ |pub [expires 2015-09-05]| |44D2 0307 1643 E80F 2E31| |F081 FAFA 6643 7F9F D46F| +------------------------+ |qzhou at live.de | |https://keybase.io/qzhou| +------------------------+ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20150327/5023ae3d/attachment.sig>
On Fri, Mar 27, 2015 at 05:16:29PM +0800, Quan Zhou wrote:> I have finally got tinc working, but it?s only between server/client. Client can receive broadcast packets from server ethernet, and pings between them is fine. > > If I ping tinc client(192.168.88.166) from any machine in my server lan, 192.168.88.0/24, all packets timed out, and nothing received by the client. Any ideas? Thanks!Is forwarding of packets enabled on the server? Check that /proc/sys/net/ipv4/ip_forward is 1 (if not, just run echo 1 >/proc/sys/net/ipv4_ip_forward as root), and that your firewall settings also allow traffic between eth0 and tun1 (iptables -L FORWARD). -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20150331/ab43b0a6/attachment.sig>
You are right, later that day I figured out it was due to a firewall issue, I fixed that by ` # ufw allow from tun1` and everything's cool! Date: Tue, 31 Mar 2015 14:45:48 +0200 From: guus at tinc-vpn.org To: tinc at tinc-vpn.org Subject: Re: No connect to/from other machines on remote ethernet On Fri, Mar 27, 2015 at 05:16:29PM +0800, Quan Zhou wrote:> I have finally got tinc working, but it?s only between server/client. Client can receive broadcast packets from server ethernet, and pings between them is fine. > > If I ping tinc client(192.168.88.166) from any machine in my server lan, 192.168.88.0/24, all packets timed out, and nothing received by the client. Any ideas? Thanks!Is forwarding of packets enabled on the server? Check that /proc/sys/net/ipv4/ip_forward is 1 (if not, just run echo 1 >/proc/sys/net/ipv4_ip_forward as root), and that your firewall settings also allow traffic between eth0 and tun1 (iptables -L FORWARD). -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> _______________________________________________ tinc mailing list tinc at tinc-vpn.org http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20150331/b931435c/attachment.html>
Seemingly Similar Threads
- No connect to/from other machines on remote ethernet
- Unable to get IP address from DHCP on remote end.
- "route flush" does not delete routes created with -interface option
- Will this work, or have I been around too much magic smoke???
- ssh-vpn linux<->openbsd