Project

General

Profile

Actions
Copy link

Bug #11460

closed

Adding a second peer results in Cannot allocate memory

Added by pierre gleich about 3 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
WireGuard
Target version:
-
Start date:
02/19/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
amd64

Description

One peer configured on my wg1 tunnel works fine:

wg show
interface: wg0
  public key: xxxxxxxxx
  private key: (hidden)
  listening port: 51820

peer: xxxxxxxxx
  endpoint: 1.2.3.4:51820
  allowed ips: ::/0, 0.0.0.0/0

interface: wg1
  public key: xxxxxxxxx
  private key: (hidden)
  listening port: 51821

peer: xxxxxxxxx
  allowed ips: 0.0.0.0/0

adding a second peer results in

wg show
interface: wg0
  public key: xxxxxxxxx
  private key: (hidden)
  listening port: 51820

peer: xxxxxxxxx
  endpoint: 1.2.3.4:51820
  allowed ips: ::/0, 0.0.0.0/0

Unable to access interface wg1: Cannot allocate memory

Discussion von Forum [[https://forum.netgate.com/topic/161004/wireguard-remote-access-impossible-to-connect-a-2nd-user/]]

Actions
Copy link
 #1

Updated by Jim Pingle about 3 years ago

  • Status changed from New to Rejected

You cannot have multiple peers with "0.0.0.0/0" as AllowedIPs. It's an invalid configuration, WireGuard has no way to tell what traffic belongs with which peer.

Actions
Copy link
 #2

Updated by Jim Pingle about 3 years ago

Added new issue to create input validation which will protect against this misconfiguration: #11465

Actions
Copy link

Also available in: Atom PDF