My understanding is that the host doesn't have an routable connection from
rdomain 0 to rdomain 1. wg1 and lo1 are specific to that rdomain, and sshd
is 'attached' to rdomain 0.
For the VM to interact directly with the host, you would have to add pair
interfaces (see ifconfig man page) to route tr
> > add 'wgrtable 0' to hostname.wg1, and search for wgrtable in `man
> > ifconfig'. it
> > sets which rdomain the actual wireguard packets transit. the wireguard
> > network and interface will be isolated to rdomain 1 while the wireguard
> > packets
> > will traverse through rdomain 0.
> >
> > t
On 2025-02-28, B. Atticus Grobe wrote:
> On Thu Feb 27, 2025 at 4:35 PM CST, alpha beta wrote:
>
> add 'wgrtable 0' to hostname.wg1, and search for wgrtable in `man ifconfig'.
> it
> sets which rdomain the actual wireguard packets transit. the wireguard
> network and interface will be isolated to
On Thu Feb 27, 2025 at 4:35 PM CST, alpha beta wrote:
> Hello, I have a single homed VM and I'm trying to isolate a wireguard
> interface inside a dedicated rdomain. All my peers except this host
> are behind NAT, and this VM has a static IP. I would like to use it
> to connect the several LANs beh
Hello, I have a single homed VM and I'm trying to isolate a wireguard
interface inside a dedicated rdomain. All my peers except this host
are behind NAT, and this VM has a static IP. I would like to use it
to connect the several LANs behind the peers. I don't necessarily
trust all the peers, thus I
5 matches
Mail list logo
