Problem forwarding traffic from Lan A to Lan B
-
I'm trying to send traffic from a client connected to LAN1 (WEB_LAN_interface) to a proxy (squid) on LAN2 (PROXY_LAN_Interface). LAN2 has to possibility to go to WAN. I've created a NAT port forward rule:
action: pass
interface: WEB_LAN_interface
Protocol: TCP
Source: single host (the client I want to forward)
Source port: any
Destination: WAN
Destination port: HTTP
Redirect target IP: Proxy on PROXY_LAN_Interface
redirect port: 3128Saving that also creates a firewall rule.
Now tailing the log on the squid proxy shows that no traffic is sent to the proxy. But if I enter a system wide proxy setting on the client, traffic starts showing up on the proxy! So it seems that the firewall rule is correct but traffic just isn't redirected if no proxy setting is entered on the client. Seems that the NAT rule is not working. I've tried endless settings but not getting it fixed. I can have it working with the proxy setting on the client but the goal is to use the proxy as transparent and handle the redirection on pfsense.
I've seen some similar questions on the forum but none of them seem to solve my problem. I did notice that on version 1.x people seem to have it working and on version 2.x not. So perhaps that has something to do with it.
Any help would be great!Regards
-
dude what?? That is not how you would do it it all.. Why are you sending it to your WAN? Just redirect the traffic to your lan 2 interface.
-
^ Where does it say he's sending it to WAN? Looks like he's intercepting HTTP traffic bound for the WAN and rerouting it to his proxy.
EvilUnicorn, unfortunately it seems like you're trying to set up a transparent proxy, which has been broken since 2.2. Many of us are experiencing the same problem - traffic is simply not rerouted to the proxy correctly. This functionality works as expected in 2.1.x, so I'd recommend using 2.1.5 if possible until this is fixed in 2.2.x. No idea if/when that will happen, however, as some of the staff posts here suggest they don't think anything's actually wrong :o
-
Destination: WAN
What kind of dest is that? It would be dest ANY? My bad on wording that wrong, why would dest be WAN is what I meant to say.
