Re: Getting wg(4) NetBSD server to work with WireGuard(R) macOS client

Paul W . Rankin Sat, 11 Jan 2025 05:49:49 -0800

Alexander Nasonov <al...@yandex.ru> wrote:
> Paul W. Rankin wrote:
> >     $ ping -c5 10.2.0.1
> >     PING 10.2.0.1 (10.2.0.1): 56 data bytes
> >     Request timeout for icmp_seq 0
> >     Request timeout for icmp_seq 1
> >     Request timeout for icmp_seq 2
> >     Request timeout for icmp_seq 3
> 
> Does 'tcpdump port 9443' show any packets coming in and out?
> 
> Alex


Plenty. 1.146.105.131 is my macOS client IP and 64.176.222.118 is the
server IP:

        # tcpdump -n port 9443
        23:06:02.270381 IP 64.176.222.118.9443 > 1.146.105.131.3117: UDP, 
length 1312
        23:06:02.270603 IP 64.176.222.118.9443 > 1.146.105.131.3117: UDP, 
length 208
        23:06:02.345822 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:02.351073 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:02.460520 IP 64.176.222.118.9443 > 1.146.105.131.3117: UDP, 
length 240
        23:06:02.660933 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 144
        23:06:02.806091 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 144
        23:06:03.853190 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:03.860934 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:03.861076 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:04.485996 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:04.490892 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:05.231050 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 176
        23:06:05.470227 IP 64.176.222.118.9443 > 1.146.105.131.3117: UDP, 
length 144
        23:06:05.816085 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 144
        23:06:07.540226 IP 64.176.222.118.9443 > 1.146.105.131.3117: UDP, 
length 192
        23:06:07.720266 IP 64.176.222.118.9443 > 1.146.105.131.3117: UDP, 
length 192
        23:06:07.900173 IP 64.176.222.118.9443 > 1.146.105.131.3117: UDP, 
length 192
        23:06:07.955940 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 144
        23:06:08.006179 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:08.010887 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:08.015817 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:08.713160 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:08.721276 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 112
        23:06:10.910085 IP 64.176.222.118.9443 > 1.146.105.131.3117: UDP, 
length 144
        23:06:10.991027 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 144
        23:06:11.310851 IP 1.146.105.131.3117 > 64.176.222.118.9443: UDP, 
length 176

I also tried the macOS equiv of ping -I:

        $ ping -S 192.168.10.2 192.168.10.1
        Request timeout for icmp_seq 0
        Request timeout for icmp_seq 1
        Request timeout for icmp_seq 2
        Request timeout for icmp_seq 3
        Request timeout for icmp_seq 4

Same thing.

Btw the Wireguard IPs are 192.168.0.0 instead of 10.0.0.0 because I'm
just trying anything.

Thanks for your help :)

-- 
Paul W. Rankin
https://rnkn.xyz

Re: Getting wg(4) NetBSD server to work with WireGuard(R) macOS client

Reply via email to