On 03/12/17 21:00, Martin Buck wrote:
> [Discussion continues on openvpn-devel, see my response to Gert's message in
> this thread]
>
> Hi Antonio,
>
> sorry for the late reply, real life currently causes lots of interrupts...
no problem at all :)
without replying point by point, I would say
[Discussion continues on openvpn-devel, please drop openvpn-users when
replying]
Hi Gert,
sorry for the late reply, real life currently causes lots of interrupts...
On Tue, Nov 28, 2017 at 03:08:27PM +0100, Gert Doering wrote:
> Short answer: shortcomings in the implementation, and nobody had ti
[Discussion continues on openvpn-devel, see my response to Gert's message in
this thread]
Hi Antonio,
sorry for the late reply, real life currently causes lots of interrupts...
On Tue, Nov 28, 2017 at 10:11:57PM +0800, Antonio Quartulli wrote:
> > I'm trying to build something like a distributed
Hi,
On 28/11/17 20:47, Martin Buck wrote:
> Hi,
>
> I'm trying to build something like a distributed Ethernet switch using
> OpenVPN in bridged/TAP mode. Each OpenVPN client as well as the server
> features a LAN with several nodes, connected to OpenVPN's TAP interface
> using a Linux software br
Hi,
On Tue, Nov 28, 2017 at 01:47:47PM +0100, Martin Buck wrote:
> Are these differences to conventional Ethernet switches intentional (e.g.
> for security reasons)? If not, I could probably provide patches to fix
> them, at least for the 3rd problem.
Short answer: shortcomings in the implementat
Hi,
I'm trying to build something like a distributed Ethernet switch using
OpenVPN in bridged/TAP mode. Each OpenVPN client as well as the server
features a LAN with several nodes, connected to OpenVPN's TAP interface
using a Linux software bridge.
So far, so good. Problems start when LAN nodes s
