Hi. On Fri, Apr 27, 2018 at 09:08:23AM +0530, Mukuntha Rajaa wrote: > > Post here contents of routing table when VPN is running -- result of > > "/sbin/ip route list", and result of "traceroute -n outlook.office365.com". > [mrajaa@mukuntha ~]$ /sbin/ip route list > default dev tun0 scope link default via 192.168.199.254 dev wlp4s0 proto > static metric 600 131.228.104.167 via 192.168.199.254 dev wlp4s0 src > 192.168.198.24 192.168.198.0/23 dev wlp4s0 proto kernel scope link src > 192.168.198.24 metric 600
Full mesh... :( Probably it should be read as follows: default dev tun0 scope link default via 192.168.199.254 dev wlp4s0 proto static metric 600 131.228.104.167 via 192.168.199.254 dev wlp4s0 src 192.168.198.24 192.168.198.0/23 dev wlp4s0 proto kernel scope link src 192.168.198.24 metric 600 No doubts, your VPN interface is "tun0", host address is 192.168.198.24, home gateway is 192.168.199.254 and vpn-server seats on 131.228.104.167. When VPN is up, it supersedes default route, making high-priority default route to VPN tunnel. So you have a routing problem, not related to mbsync. You have better to ask your corporate admins for help, because this network configuration is conceptually broken and there is no evidence how it should be changed. In general, you should have only routes to internal corporate nets through "tun0", but NOT the default route. -- Eugene Berdnikov ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
