Comment on Issue with wireguard and advance routing

• InnerScientist@lemmy.world ⁨2⁩ ⁨months⁩ ago

  Do a ping of 8.8.8.8 from your user, then open a new console and run tcpdump -i <interface> with first your uplink, then wg0. The packets should be seen on wg0 if they’re routed correctly and the problem then is on the vps side. Otherwise it’s a problem on your local config.

  source

  • Shimitar@downonthestreet.eu ⁨2⁩ ⁨months⁩ ago

    Interesting enough…

    tcpdump -i wg0 
    21:49:49.604220 IP 10.70.0.1 > dns.google: ICMP echo request, id 5337, seq 1, length 64
    21:49:49.638242 IP dns.google > 10.70.0.1: ICMP echo reply, id 5337, seq 1, length 64
    21:49:50.615200 IP 10.70.0.1 > dns.google: ICMP echo request, id 5337, seq 2, length 64
    21:49:50.648361 IP dns.google > 10.70.0.1: ICMP echo reply, id 5337, seq 2, length 64
    21:49:51.628391 IP 10.70.0.1 > dns.google: ICMP echo request, id 5337, seq 3, length 64
    21:49:51.673502 IP dns.google > 10.70.0.1: ICMP echo reply, id 5337, seq 3, length 64
    21:49:52.641711 IP 10.70.0.1 > dns.google: ICMP echo request, id 5337, seq 4, length 64
    21:49:52.673321 IP dns.google > 10.70.0.1: ICMP echo reply, id 5337, seq 4, length 64
    21:49:53.655076 IP 10.70.0.1 > dns.google: ICMP echo request, id 5337, seq 5, length 64
    21:49:53.695391 IP dns.google > 10.70.0.1: ICMP echo reply, id 5337, seq 5, length 64
    

    while on the other console, as user 1070:

     ping 8.8.8.8
    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
    

    just gets stuck there…

    This is baffling!

    source

    • InnerScientist@lemmy.world ⁨2⁩ ⁨months⁩ ago

      Try sysctl -w net.ipv4.conf.all.rp_filter=2 on the PC (not vps)

      source

      • Shimitar@downonthestreet.eu ⁨2⁩ ⁨months⁩ ago

        Yes!

        That’s it…

        How did I forgot about that?

        I assumed it was already set…

        Need to double check all my setup scripts tomorrow…

        Thanks!

        source