Hi Jason,
Thanks for your input. I agree with you.
But I could have the peers based on table routing and marking packets,
were all the traffic (0.0.0.0/0) would be routed based on the prior
conditions (tables and marking).
I'm doing one interface per peer right now, but I thought it could
Hi Bruno,
You can't set multiple peers to use 0.0.0.0/0 at the same time on the
same interface. How would it be able to choose which peer to send
traffic to then? Instead, if you want some kind of redundancy or
bonding, you can try using multiple interfaces, and then use whatever
traditional
Hi,
> Is it possible to achieve that with wireguard?
You need to set up multiple wireguard interfaces (on different ports of
course).
Then you can use traditional Linux routing techniques.
--
-- Matthias Urlichs
___
WireGuard mailing list
Hello,
I'm trying to set up a policy-based routing on a wireguard instance. I
didn't want to call it server, because it acts more like a proxy.
Let's say I have 6 peers plus this wireguard server.
Peer 2 Peer 3 Peer 4
