Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 1
    What is generating the problematic traffic? Are you certain it has the expected source address? If it's coming from a container, what is the address of that container? Note that packets coming from a container will not have the source address of your host during the routing decision.
    – larsks
    Commented Dec 30, 2023 at 22:46
  • Could be anything but for testing I've just been using an http server. The source address is that of the wireguard interface but it's leaving via the default route. That is the problem I think, I need to figure out a way to get the routing to happen once the packets have the host address...
    – TheChubbyPanda
    Commented Dec 30, 2023 at 22:53
  • Your question title is "Outgoing docker packets", which suggests you're running e.g. the http server in a container. If that's the case, you would need to match the container address in your routing rule. If you believe that's not the case, updating the question to include sufficient information for us to reproduce the problem would be helpful in formulating a complete answer.
    – larsks
    Commented Dec 30, 2023 at 22:56
  • Thanks for your comments, I've re-written the question to hopefully be more clear. I can't match the container's address because not all traffic from the container should go over the wg0 interface. Only that which originated from wg0.
    – TheChubbyPanda
    Commented Dec 30, 2023 at 23:14
  • Then you need to use the destination address in your policy rule, rather than the source address (because you want to route traffic going to the wireguard network).
    – larsks
    Commented Dec 31, 2023 at 1:22