On 5 June 2013 17:50, Ville Valkonen wrote:
>
> Hi,
>
> just confirming one thing: did you flush the pf states between the
> tests? I must admit, I mainly glanced the problem, so sorry if this is
> an old tip. This was the first thing that popped into my mind when
> reading about your solution.
>
Hi,
just confirming one thing: did you flush the pf states between the
tests? I must admit, I mainly glanced the problem, so sorry if this is
an old tip. This was the first thing that popped into my mind when
reading about your solution.
--
Sincerely,
Ville Valkonen
On 5 June 2013 22:39, Raimund
I've got the issue solved by disabling states on all rules which deal with
the tproxy.
On 4 June 2013 11:28, Raimundo Santos wrote:
> I am guessing that the problem lies with flags S/SA.
>
> Changing all rules to flags any, and the packets hits the rules, but
> things go worse: no web navigatio
I am guessing that the problem lies with flags S/SA.
Changing all rules to flags any, and the packets hits the rules, but things
go worse: no web navigation... this is driving me mad!
On 3 June 2013 13:09, Raimundo Santos wrote:
> Hi there!
>
> I asked, without an answer, something about nat-
Hi there!
I asked, without an answer, something about nat-to and real IPs. Well, I
really need an answer there, so if someone get a clue, I will be glad tho
hear :)
Now, to the new issue!
Here in our WiFi ISP we are have contracted a tproxy service from FreeBSD
Brasil. It is somehow working, but
5 matches
Mail list logo
