On Wed, Jun 29, 2016 at 8:27 AM, Jean-Laurent Ivars
wrote:
> Hello Piba (and anyone else…)
>
> Sorry for not having answered before…
>
> To answer you questions, firstly, I’m not in a datacenter, only a client
> offices with different ISP.
>
> I agree with you double NAT is
Hello Piba (and anyone else…)
Sorry for not having answered before…
To answer you questions, firstly, I’m not in a datacenter, only a client
offices with different ISP.
I agree with you double NAT is bad but you can’t alway get rid of it… and you
should know that on one of my wan connexion I
Hi Jean-Laurent,
Op 25-6-2016 om 18:46 schreef Jean-Laurent Ivars:
You’re perfectly right i only gave extracts of the logs :) next time I’m going
to be more precise and make the capture from the beginning...
Its not that extracts are bad, just knowing what part to extract to make
it easier to
Hi Piba, (and other people)
Thank you very much for your answer !
You’re perfectly right i only gave extracts of the logs :) next time I’m going
to be more precise and make the capture from the beginning...
Anyway, as you suppose, I continue to see the same [S] paquet repeating again
and
Hi Jean-Laurent,
Op 25-6-2016 om 10:37 schreef Jean-Laurent Ivars:
This is logs generated by tcpdump from the same client machine when I try to
access the firewall thru working internet access provider :
port 2223
16:55:04.501509 IP 46.105.230.225.39304 > 192.168.101.254.2223: Flags [P.], seq
Dear list,
I apologie if the subject have already been treated…
Since the upgrade to the new version I have issue to access to the pfsense from
the outside from certain internet providers, before the upgrade it was working
correctly and since the update the port forwarding (or DMZ setting) is