Routing HTTP Proxy Traffic to a WireGuard Gateway

Started by kozistan, December 14, 2024, 09:15:08 PM

Previous topic - Next topic
Hello all, I've been struggling for weeks with forwarding traffic to a WireGuard gateway. When I create a rule on the segment interface, it works, but it directs the entire segment to the WireGuard gateway. What I need is to configure it so that a client computer using the SwitchyOmega extension in Chrome (an HTTP proxy within the browser) on port 8100 is forwarded to this gateway.

The question is whether I need to use Squid—which, at least in the pfSense GUI, doesn't seem capable of this—or if I should use SNAT and DNAT rules to route traffic from the client, translating port 8100 to 80 and 8101 to 443, for example.

I've tried countless combinations, but none of them worked correctly, likely due to my insufficient knowledge of the issue.

In the attached screenshots, you can see the configuration of the SwitchyOmega extension in the browser, where the address 10.2.0.1 is the WireGuard gateway connection, and its physical local address is 10.2.0.2.

Would really appreciate any help with this