Multiple Wireguard Connections Question

RouterOS General
41

do you have discord if so look me up

42

OK. Might be a while or even tomorrow.

43

understood

1 Like
44

Sent you a friend request on Discord. Trying to send a message failed.

Tomorrow afternoon works for me.

45

Here’s why I think this is just some sort of routing issue for now. I can do a trace route to each of my two remote peers. 192.168.1.252 is on the “back to home” WG interface and 192.168.1.251 is on my “Wireguard Tunnels” interface:

jon@Jons-Mac-mini ~ % traceroute 192.168.216.252
traceroute to 192.168.216.252 (192.168.216.252), 64 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  0.930 ms  0.297 ms  0.270 ms
 2  192.168.1.1 (192.168.1.1)  0.284 ms !H  0.254 ms !H  0.281 ms !H
jon@Jons-Mac-mini ~ % traceroute 192.168.216.251
traceroute to 192.168.216.251 (192.168.216.251), 64 hops max, 40 byte packets
 1  192.168.1.1 (192.168.1.1)  1.024 ms  0.280 ms  0.261 ms
 2  192.168.1.1 (192.168.1.1)  0.304 ms !H  0.313 ms !H  0.276 ms !H
jon@Jons-Mac-mini ~ %

So I can get a response to trace the route, but I can’t ping either one:

jon@Jons-Mac-mini ~ % ping 192.168.216.252
PING 192.168.216.252 (192.168.216.252): 56 data bytes
92 bytes from 192.168.1.1: Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 509f   0 0000  3f  01 f8ba 192.168.1.18  192.168.216.252 

^C
--- 192.168.216.252 ping statistics ---
1 packets transmitted, 0 packets received, 100.0% packet loss
jon@Jons-Mac-mini ~ % ping 192.168.216.252
PING 192.168.216.252 (192.168.216.252): 56 data bytes
92 bytes from 192.168.1.1: Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 2e27   0 0000  3f  01 1b33 192.168.1.18  192.168.216.252 

Request timeout for icmp_seq 0
92 bytes from 192.168.1.1: Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 92fb   0 0000  3f  01 b65e 192.168.1.18  192.168.216.252 

Request timeout for icmp_seq 1
92 bytes from 192.168.1.1: Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 77ad   0 0000  3f  01 d1ac 192.168.1.18  192.168.216.252 

^C
--- 192.168.216.252 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
jon@Jons-Mac-mini ~ % ping 192.168.216.251
PING 192.168.216.251 (192.168.216.251): 56 data bytes
92 bytes from 192.168.1.1: Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 2438   0 0000  3f  01 fc12 192.168.1.18  192.168.216.251 

Request timeout for icmp_seq 0
92 bytes from 192.168.1.1: Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 d9d1   0 0000  3f  01 4679 192.168.1.18  192.168.216.251 

Request timeout for icmp_seq 1
92 bytes from 192.168.1.1: Destination Host Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 265e   0 0000  3f  01 f9ec 192.168.1.18  192.168.216.251 

^C
--- 192.168.216.251 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
jon@Jons-Mac-mini ~ %

Not quite sure why I can get a trace route but not a ping. I can’t ping either of those from the MikroTik shell either…

edited: I was ping the wrong IPs previously…still same result..