Alexander Tsoy

I have the same issue. Looks like this happens when VPN address and internal point-to-point addresses are the same: ``` pppd[1834278]: local IP address YY.YY.YY.YY pppd[1834278]: remote IP address XX.XX.XX.XX...

> So is it pppd doing the wrong thing then? I think pppd accepts this address from the remote peer via IPCP and then NetworkManager adds a route to it....

OK, this is what happens on my system after connecting: ``` $ ip r l ... 195.XX.XX.XX dev ppp0 proto kernel scope link src 10.3.3.33 metric 50 195.XX.XX.XX via 192.168.1.1...

Yes, I need to remove that bad route, otherwise the VPN dies.

The following patch works for me. Maybe this can be made optional via a checkbox in GUI, something like "Ignore remote peer address"? ``` diff --git a/src/nm-l2tp-pppd-plugin.c b/src/nm-l2tp-pppd-plugin.c index b7912e9..ab79772...

> is there any situation where this shouldn't be done? I think there are configurations where remote peer address acts as a gateway. However in my case I can just...

> ... `libnss_wins` and `libnss_winbind` ... These are provided by `samba-winbind-modules` package on RHEL/Fedora distros AFAIK

Note that exim also works with radiusclient-ng 0.5.x which is still shipped by most linux distributions (along with freeradius-client). In radiusclient-ng 0.5.0 library and header were renamed to libradiusclient-ng and...

Building with gcc-5 was fixed by 5852828582f556e73751076ad092f72acf7fc8b6, but it seems gcc-specific.

> Thanks for reporting. I think the following fix solve this issue. [46bed1b](https://github.com/mchehab/rasdaemon/commit/46bed1b6845bcb560d760b4cacea7df67cd6d1fd) Yes. It fixes this issue