Yes both iproute2 and sitnl works perfectly as expected. Will the fix be backported to the 2.4 branch?
P.S. For the record, if the client is ics-openvpn with openvpn3, somehow you need push route (either host or subnet will do) anyway. This is not necessary with ics-openvpn with openvpn2 or OpenVPN Connect (AFAIK its core is openvpn3 as well, albeit different snapshot). The problem/behaviour is not specific to /31 subnet though, apparently. I guess the main route table is ignored/masked. On Mon, 11 Nov 2019 at 02:07, Gert Doering <g...@greenie.muc.de> wrote: > > Hi, > > On Mon, Nov 04, 2019 at 05:10:12AM +0800, Tom Yan wrote: > > So in master, when net_addr_v4_add is called in tun.c, which > > net_addr_v4_add (networking_iproute2.c or networking_sitnl.c) is > > actually used depends on how openvpn is built, right? > > Can you have a look at the current "master" branch? Antonio has ripped > out *all* broadcast setting - so this should now do /31s just fine? > > More radical than your approach, but "less old code" is better than > "yet another special condition added" :-) > > gert > -- > "If was one thing all people took for granted, was conviction that if you > feed honest figures into a computer, honest figures come out. Never doubted > it myself till I met a computer with a sense of humor." > Robert A. Heinlein, The Moon is a Harsh Mistress > > Gert Doering - Munich, Germany g...@greenie.muc.de _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
