I don't think adding a dummy endpoint would be a good idea.
If seeing logs is the problem, removing "warning" from asterisk/logger.conf on
that box might work, not sure what important things you might miss.
If you built your own AstLinux images, you could patch out that line in
Asterisk.
Lonni
Ah thanks Lonnie. Yes this is when I'm using one-way peers. Problem is that yes
Asterisk does bail quickly but then complains about it in the logs.
Two-way endpoints are out of the question unfortunately. Do you think there is
any way to fool it e.g. add a dummy endpoint or would this break stuff
Hi Michael,
That is what WireGuard does if there is no "Endpoint" and the peer route is
down.
Simple examples ...
Example #1
-- wg.conf snip (no Endpoint) --
[Peer]
## hpe-ms|pbx-pve
PublicKey = ...
AllowedIPs = 10.4.0.15/32
--
# fping 10.4.0.15
10.4.0.15: error while sending ping: Destination
> Am 15.05.2022 um 05:07 schrieb Michael Knill
> :
>
> I use Wireguard VPN’s extensively and our softswitch has many peers connected
> to it.
> One issue that is very annoying is that if a VPN route drops out of the
> routing table, rather than just Unreachable, Asterisk complains as below:
>
