On Thu, May 03, 2018 at 12:43:23PM +0000, chrono wrote: > Hi Ondrej, > > thanks for the quick reply. > > > > What makes me wonder is why wg0 is coming up as stubnet here, > > > while the MPLS links come up as network (stubnet 172.23.3.0/29 > > > metric 10) > > > and 172.23.3.0/29 (wg0 net) not being listed. > > > You don't see 172.23.3.0/29 as network, because these ifaces are > > configured as PtP, but still there should be 'router' line in apropriate > > router block to indicate existing PtP link. > > Yes, while trying to debug someone on #BIRD (freenode) suggested that > it may not work due to wg0 not being a broadcast interface: > > wg0 Link encap:UNSPEC HWaddr > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet addr:172.23.3.1 P-t-P:172.23.3.1 Mask:255.255.255.248 > UP POINTOPOINT RUNNING NOARP MTU:1420 Metric:1 > RX packets:102368 errors:0 dropped:0 overruns:0 frame:0 > TX packets:103213 errors:10189 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:14697260 (14.6 MB) TX bytes:14771860 (14.7 MB) > > I checked bird docs and found the interface configuration option type > and tried to set it to pointtopoint but with no success so far. Which > would be the correct setting for a wireguard interface?
PtP should be correct, but it is possible that as wireguard is a new thing, it has broken multicast handling. Generally, PtP tunnels should have no problems to use multicast - just send everything to the other side. But as the tcpdump on one side shows periodic hellos from both sides, then it is unlikely to be an issue. Also i saw that your config files do not have 'log' option, so you have no logging. You should enable logging and see if there are no error messages. Although unrelated, i would suggest to remove these OSPF options; tick 2; rfc1583compat yes; -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
