On Tue, Mar 11, 2014 at 09:32:30PM +0000, Michael Munger wrote: > Per your instructions, I changed the Subnets to single IPs. The logs show > that it was added as a /32, so that's great. I assume that since tincd is > running in router mode (default), it builds this table so there is no need to > add routes with the route command, right?
Well, you still need to make sure that there is a route to direct all the VPN traffic to the VPN interface. But if you keep the tinc-up script like you had before (with netmask 255.255.255.0), then that is indeed the case. > I still cannot ping, and I am getting "Got MTU probe length" errors in > syslog. Lots of them. I have attached the relevant sections of the log if you > wish to see them (below - I'll keep these public for future folks who post to > this list). Those are not errors, just informational messages. > For the "server": > https://www.dropbox.com/s/leojizn9mi599wf/vpnserver.log I do see an error here: Mar 11 17:22:51 web-services tinc.webservices[18869]: Executing script tinc-up Mar 11 17:22:51 web-services tinc.webservices[18869]: Script tinc-up exited with non-zero status 1 This means something went wrong executing the tinc-up script. In your first email you wrote: > root@web-services:/etc/tinc/webservices# cat tinc-up > #!/bin/bash ifconfig $INTERFACE 192.168.98.1 NETMASK 255.255.255.0 That should be two separate lines, and it should be "netmask" instead of "NETMASK": #!/bin/bash ifconfig $INTERFACE 192.168.98.1 netmask 255.255.255.0 Hopefully with that fixed, your VPN will start working. -- Met vriendelijke groet / with kind regards, Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
