Enable flooding of "unknown-unicast" packets from the server to
all connected clients (+tap).
These are packets that are sent to an unknown destination MAC address
and which are not broadcast/multicast packets. "Normal" switches also
flood these packets, which allows client-to-client MAC learning without
having to have an initial broadcast packet.
Without the patch, the p2mp tap server will only forward such packets
to the tap interface on the host.
This is only active if --client-to-client is configured on the server.
Signed-off-by: Gert Doering <g...@greenie.muc.de>
---
src/openvpn/multi.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/src/openvpn/multi.c b/src/openvpn/multi.c
index 55c167b..aa5ae26 100644
--- a/src/openvpn/multi.c
+++ b/src/openvpn/multi.c
@@ -2689,6 +2689,13 @@ multi_process_incoming_link(struct multi_context *m,
struct multi_instance *inst
}
c->c2.to_tun.len = 0;
}
+ else
+ {
+ /* flood "unknown unicast" packets */
+ msg(D_MULTI_LOW, "MULTI: unknown unicast
destination [%s], flood",
+ mroute_addr_print(&src, &gc));
+ multi_bcast(m, &c->c2.to_tun, m->pending,
NULL);
+ }
}
}
#ifdef ENABLE_PF
--
2.7.3
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
