Normally, you would use routing (L3) instead of bridging (L2).
Conceptually, the connectivity should work about the same,
as long as you configure your routes and enable forwarding.
Routes need to be configured on the host, not container-only,
but if assign a subnet to a bridge, devices can use
On Sat, 24 Apr 2021 11:11:50 +0100
lejeczek wrote:
> Hi guys.
>
> Apologies, I'll bother you guys as I failed to find some
> better places to ask, I searched for forums etc. but failed.
>
> Can wiregurard ifaces be enslaved by LInux bridge? I tried
> but it did not work for me. Similarly
Hi L.
No wireguard is a layer 3 vpn, a bridge is layer2
Cheers
Mike
> On 25 Apr 2021, at 2:02 pm, lejeczek wrote:
>
> Hi guys.
>
> Apologies, I'll bother you guys as I failed to find some better places to
> ask, I searched for forums etc. but failed.
>
> Can wiregurard ifaces be enslaved
On 25/04/2021 13:21, Chriztoffer Hansen wrote:
Can wiregurard ifaces be enslaved by LInux bridge? I tried
but it did not work for me. Similarly "mavclan" -
would/should wireguard work that way?
Why would you want to enslave an L3-only capable interface to an L2 bridge?
What is your use case
> Can wiregurard ifaces be enslaved by LInux bridge? I tried
> but it did not work for me. Similarly "mavclan" -
> would/should wireguard work that way?
Why would you want to enslave an L3-only capable interface to an L2 bridge?
What is your use case behind the question?
--
Chriztoffer
Hi guys.
Apologies, I'll bother you guys as I failed to find some
better places to ask, I searched for forums etc. but failed.
Can wiregurard ifaces be enslaved by LInux bridge? I tried
but it did not work for me. Similarly "mavclan" -
would/should wireguard work that way?
What I've tried
