Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Why can't a WireGuard interface route packets to itself?



PPPoE is a point to point protocol and the public IP addresses 114.23.17.255 and 114.23.164.222 are normal IP addresses. 114.23.164.222 is my local IP address and 114.23.17.255 is my ISP's IP address. Both can be treated as /32.

AFAICT the important fact is that the route to 114.23.164.222 has lo0 in the Interface column meaning (according to the manual page) that lo0 will be used to reach that IP address. In your case, wg0 will be used, which means the packet will be transmitted over WireGuard to the remote end. This doesn't do what you want.

I expect that you will need to dig deeper into WireGuard. It's quite possible that this is a bug in WireGuard. Or you might just have something misconfigured. I don't know anything about WireGuard and only a little bit about PPPoE.

Cheers,
Lloyd

On 31/07/23 10:18, logothesia wrote:
Beware of possible line wrapping.

No problem :)

Destination        Gateway            Flags    Refs      Use    Mtu
114.23.17.255      114.23.164.222     UH          -        -      -  pppoe0
114.23.164.222     pppoe0             UHl         -        -      -  lo0

10/8               10.0.0.1           U           -        -      -  wg0
10.0.0.1           wg0                UHl         -        -      -  wg0

I'm not entirely sure what I'm looking at; is 114.23.17.255 a broadcast
address? I assume it's not a /24, right? In any case, 114.23.164.222
looks a lot like my 10.0.0.1, minus the interface, which is set to lo0.
Should I set mine to lo0?

127/8              127.0.0.1          UGRS        -        -  33624  lo0
127.0.0.1          lo0                UHl         -        -  33624  lo0

Barring the MTU, my loopback routes are pretty much identical.



Home | Main Index | Thread Index | Old Index