From: Jelle de Jong <jelledejong@powercraft.nl>
To: wireguard@lists.zx2c4.com
Subject: Re: how to forward/route/rule all traffic broadcast from an br0 to wg0
Date: Thu, 20 Feb 2020 15:40:00 +0100 [thread overview]
Message-ID: <33e4e4e3-bcc4-4ebd-23b9-abf2ffb9ed6a@powercraft.nl> (raw)
In-Reply-To: <bfa1d3ff-7885-0c68-9d74-212dec0aaed8@powercraft.nl>
Hello everyone,
Anyone that can answer the question on how to broadcast traffic like
DHCP through an excisiting wireguard connection?
Kind regards,
Jelle de Jong
On 2020-02-07 17:49, Jelle de Jong wrote:
> Hello everybody,
>
> br0 (with eth0 eth1 eth3)
> wg0 (192.168.43.10/24)
>
> dhcp-helper to forward broadcast to ip?
>
> I am looking for way to use a wireguard tunnel to route all traffic
> including dhcp broadcast from one network to an other network and create
> a form of a network bridge.
>
> I got an working wireguard client wg0 (192.168.43.10/24) that has a
> linux bridge br0 on the same system, so br0 and wg0.
>
> I can not add wg0 to the bridge because bridging is layer2.
>
> How can I use either ip route, nftables, iptables, etc to route all
> traffic on br0 to wg0.
>
> I want to runnel an dhcp and pxe boot over the br0 to wg0.
>
> Can someone share an example?
>
> Kind regards,
>
> Jelle de Jong
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-02-23 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 16:49 how to forward/route/rule all traffic broadcast from an br0 to wg0 Jelle de Jong
2020-02-20 14:40 ` Jelle de Jong [this message]
2020-02-23 10:46 ` Matthias Urlichs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33e4e4e3-bcc4-4ebd-23b9-abf2ffb9ed6a@powercraft.nl \
--to=jelledejong@powercraft.nl \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).