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 and failed was on CentOS stream with 4.18.0-294.el8.x86_64. many thanks, L.
Hi L.
No wireguard is a layer 3 vpn, a bridge is layer2
Cheers
Mike
> On 25 Apr 2021, at 2:02 pm, lejeczek <peljasz@yahoo.co.uk> 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 "mavclan" - would/should wireguard work that way?
> What I've tried and failed was on CentOS stream with 4.18.0-294.el8.x86_64.
>
> many thanks, L.
> 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
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 behind the question?
>
Containers. Simple (but also can be complex too as scales
easily) case where containers would be glued together and be
able to communicate across nodes/hosts via wireguard
tunnel/link.
I'm looking at it from a 'regular' admin standpoint.
Then it'd be just one wiregurard host-to-host link which all
container could utilize, as oppose to separate wireguard
for/in each container.
many thanks, L.
On Sat, 24 Apr 2021 11:11:50 +0100
lejeczek <peljasz@yahoo.co.uk> 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 "mavclan" -
> would/should wireguard work that way?
> What I've tried and failed was on CentOS stream with
> 4.18.0-294.el8.x86_64.
As others have replied, it is an L3 interface, not L2 which can join bridges.
One solution that many use is to run an L2 tunnel over WireGuard, such as
VXLAN or GRETAP. But then you lose even more MTU compared to the standard 1500.
--
With respect,
Roman
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 addresses
from it without intervention on the host.
If you want roaming addresses, you could do live route
updates on your wireguard links and host routing table
for a native L3 solution. For a pre-existing automated
solution, you can use a some kind of routing service,
usually with multiple additional layers of encapsulation,
as others have mentioned.
Regards,
ivan
On Sun, Apr 25, 2021 at 02:13:24PM +0100, lejeczek wrote:
> On 25/04/2021 13:21, Chriztoffer Hansen wrote:
> > What is your use case behind the question?
> >
> Containers. Simple (but also can be complex too as scales
> easily) case where containers would be glued together and be
> able to communicate across nodes/hosts via wireguard
> tunnel/link.
> I'm looking at it from a 'regular' admin standpoint.
> Then it'd be just one wiregurard host-to-host link which all
> container could utilize, as oppose to separate wireguard
> for/in each container.
>
> many thanks, L.