<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
First of all a BIG thanks to developers for great job!<br /><br />There is a main office with WG running on Lede reboot (17.01.4) with ports 51820 and 51821. Until I've two peers, one pointing to port 51820 and 2nd to 51821 everything worked fine.<br />Now I want to add another one peer to have 3 remote peers in total. The questions is:<br />should I open the new port for each remote peer to connect? It's how wg works? How to run few tunnels/peers on the same port 51820 for example? Does Cryptokey routing can work in this way over one port only instead opening third one 51822?<br /><br />As If I try to use the same port for two peers, the 2nd peer for the same port will not create interface. See evidence bellow.<br />Once ifconfig brings T1 interface up (listening on 51820 port), the TU interface can't be raised up as it listens on the same port 51820. <br /><br /># Lede reboot (17.01.4)<br />root@OpenWrt:~# wg<br />interface: T1<br /> public key: <deleted1><br /> listening port: 51820<br /><br />peer: <deleted2><br /> endpoint: x.x.13.235:56649<br /> allowed ips: p.p.5.0/24<br /> latest handshake: 45 seconds ago<br /> transfer: 150.31 KiB received, 286.11 KiB sent<br /><br />interface: RA<br /> public key: <deleted3><br /> private key: (hidden)<br /> listening port: 51821<br /><br />peer: <deleted4><br /> endpoint: x.x.125.213:51820<br /> allowed ips: p.p.30.0/24, 10.1.1.16/30<br /> latest handshake: 54 seconds ago<br /> transfer: 285.81 KiB received, 14.89 KiB sent<br /><br />interface: TU<br /> public key: <deleted5><br /> private key: (hidden)<br /> listening port: 51820 # If I use THE SAME as for T1 interface, it won't start. How to solve this?<br />peer: <deleted6><br /> endpoint: x.x.147.136:51820<br /> allowed ips: p.p.57.0/24, 10.2.1.32/30<br /><br />With p - rfc1918 private address space address is marked (local addresses)<br /><br /><br />Mon Feb 26 15:28:57 2018 daemon.notice netifd: Interface 'T' is now up<br />Mon Feb 26 15:28:57 2018 daemon.notice netifd: Network device 'T' link is up<br />Mon Feb 26 15:28:57 2018 daemon.notice netifd: Interface 'RA' is now up<br />Mon Feb 26 15:28:57 2018 daemon.notice netifd: Network device 'RA' link is up<br />Mon Feb 26 15:28:57 2018 daemon.notice netifd: Interface 'TU' is now down<br />Mon Feb 26 15:28:58 2018 daemon.notice netifd: Interface 'TU' is setting up now<br />Mon Feb 26 15:28:58 2018 daemon.notice netifd: Interface 'wan' is now up<br />Mon Feb 26 15:28:59 2018 kern.err kernel: [1972650.446719] wireguard: TU: Could not create IPv4 socket<br />Mon Feb 26 15:28:59 2018 daemon.notice netifd: Interface 'TU' is now up<br /><br />root@OpenWrt:~# ifconfig<br />RA Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00<br /> inet addr:10.1.1.16 P-t-P:10.1.1.16 Mask:255.255.255.252<br /> UP POINTOPOINT RUNNING NOARP MTU:1420 Metric:1<br /> RX packets:3 errors:0 dropped:0 overruns:0 frame:0<br /> TX packets:3 errors:0 dropped:0 overruns:0 carrier:0<br /> collisions:0 txqueuelen:1<br /> RX bytes:444 (444.0 B) TX bytes:612 (612.0 B)<br /><br />T1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00<br /> UP POINTOPOINT RUNNING NOARP MTU:1420 Metric:1<br /> RX packets:312 errors:0 dropped:0 overruns:0 frame:0<br /> TX packets:312 errors:0 dropped:0 overruns:0 carrier:0<br /> collisions:0 txqueuelen:1<br /> RX bytes:26400 (25.7 KiB) TX bytes:40164 (39.2 KiB)<br /><br />Where is TU interface? Or it can't be raised because it listens on the same port 51820 as T1 tunnel?<br /><br />Thanks You!<br /><br /><br /><br /><br /><br /><br /><br /> </body>
</html>