Reflection
-
Ok, i retested it now updated the to boxes to beta 3, but no sucess :-(
Should I report this as a bug (at least the not working internal NAT Rule)? -
Ok, i retested it now updated the to boxes to beta 3, but no sucess :-(
Should I report this as a bug (at least the not working internal NAT Rule)?Please post something about this, I can also do some other tests. I have 3 PPPOE conections with 3 pppoe boxes for testing.
-
Ok, i retested it now updated the to boxes to beta 3, but no sucess :-(
Should I report this as a bug (at least the not working internal NAT Rule)?Please post something about this, I can also do some other tests. I have 3 PPPOE conections with 3 pppoe boxes for testing.
check the cvstrac timeline, I believe this has been fixed.
-
check the cvstrac timeline, I believe this has been fixed.
I have checked this, but cant found anything.
I tested it with Beta3 on both boxes (I think there are no newer snapshots) and the problem still exists. -
check the cvstrac timeline, I believe this has been fixed.
I have checked this, but cant found anything.
I tested it with Beta3 on both boxes (I think there are no newer snapshots) and the problem still exists.Maybe we don't completely understand your bug, but this commit:
http://cvstrac.pfsense.com/chngview?cn=11516
fixed what I believe is what you are reporting. And it was in b3.–Bill
-
Maybe we don't completely understand your bug, but this commit:
http://cvstrac.pfsense.com/chngview?cn=11516
fixed what I believe is what you are reporting. And it was in b3.–Bill
There are too different bugs:
(Configuration: 192.168.1.2 pfsense Beta3 with a PPPOE Wan Connection as the default gateway and 192.168.1.4 pfsense running squid with a second PPPOE Wan connection.)
First. When I configure a Nat rule on the 192.168.1.2 for redirecting http traffic to 192.168.1.4:3128(squid) I get simply no HTTP Respond back so nothing works. The same NAT rule works fine, when I configure it on 192.168.1.4 and set this box as the default gateway.
The second bug has nothing to do with squid (it dos not works with or without a transparent squid).
Second. When I configure on 192.168.1.2 the second box (192.168.1.4) as a rulebased loadbalancing gateway and create a firewall rule selecting this gateway for port 80 traffic, the inbound traffic works fine, but the outbound traffic is terribly slow (<1 kb/s) after something like 64 kb. -
Ahh…yeah, you can't do that.
--Bill
-
Ahh…yeah, you can't do that.
--Bill
So, these are no bugs? Both things will not work for now, or will it never work like I desired?
Can you please explain it shortly, especially the 1 kb upload thing?Greetings, techatdd
-
Can I do that, if I add the second wan connection to the first pfsense, running there a squid and then send the squid http traffic with a rule based loadbalancing oer this connection?
-
There are too different bugs:
(Configuration: 192.168.1.2 pfsense Beta3 with a PPPOE Wan Connection as the default gateway and 192.168.1.4 pfsense running squid with a second PPPOE Wan connection.)
First. When I configure a Nat rule on the 192.168.1.2 for redirecting http traffic to 192.168.1.4:3128(squid) I get simply no HTTP Respond back so nothing works. The same NAT rule works fine, when I configure it on 192.168.1.4 and set this box as the default gateway.
You can't redirect to an internal server from inside. With reflection, it might work, but will be horribly slow. PF isn't designed for it and the NAT hooks aren't in the correct place to allow for it. We won't be changing that behaviour, it's a limitation in the OS.
The second bug has nothing to do with squid (it dos not works with or without a transparent squid).
Second. When I configure on 192.168.1.2 the second box (192.168.1.4) as a rulebased loadbalancing gateway and create a firewall rule selecting this gateway for port 80 traffic, the inbound traffic works fine, but the outbound traffic is terribly slow (<1 kb/s) after something like 64 kb.See above. Same problem.
–Bill