Hi, it's not a good idea to distribute /32 routes around your routing domain as it will make convergence times longer and adds unnecessary load to the other routers. OSPF and other routing daemons like summary routes. I'm guessing you've assigned a 'unique' /24 network for the VPN clients which isn't used anywhere else in your organisation so the best thing to do is to create a single static route on the OBSD box for the whole /24 VPN range and distribute that using OSPF. That way other routers will learn about the OBSD box which provides access to the clients etc. leave the /32 routes on the OBSD box.. Hope this helps.
Cheers, Andy. Sent from my iPhone > On 1 Mar 2014, at 10:41, YASUOKA Masahiko <yasu...@yasuoka.net> wrote: > > On Fri, 28 Feb 2014 12:41:16 -0800 > "Paul B. Henson" <hen...@acm.org> wrote: >> I'm currently setting up an L2TP VPN with npppd. I've got the VPN piece >> working, and can send packets between the client and the openbsd box >> running the vpn. However, I'm currently using ospfd for routing between >> the rest of the network and the openbsd box, and it doesn't seem to be >> pushing routes for the IP addresses in use by the clients. > > I could repeat the problem. ospfd seems not to be able to use routes > set by npppd. The problem seems to be come from pppx(4)'s behavior of > its link state. > > Using tun(4) instead of pppx(4) avoid the problem. > > --yasuoka
