On 19/04/15 12:05, Jeff Mitchell wrote:
>
> Unless the NAT implementation is broken. Read up a bit in the thread :-)
>
Ohh! :-)
(but there are no broken NAT implementations! Say it ain't so!)
--
Cheers
Jason Haar
Corporate Information Security Manager, Trimble Navigation Ltd.
Phone: +1 408 4
Unless the NAT implementation is broken. Read up a bit in the thread :-)
On Sat, Apr 18, 2015, 20:00 Jason Haar wrote:
> On 19/04/15 01:55, Gert Doering wrote:
> > OTOH, you'll see the behaviour in many mobile networks today: if there
> > is no traffic inside OpenVPN for a given time, like "60
On 19/04/15 01:55, Gert Doering wrote:
> OTOH, you'll see the behaviour in many mobile networks today: if there
> is no traffic inside OpenVPN for a given time, like "60 seconds" (yes,
> that short), it will time out the NAT entry and on the next packet, you
> end up with a new source port or sourc
Hi,
On Fri, Apr 17, 2015 at 07:34:36AM -0400, Jeff Mitchell wrote:
> So hopefully peer-id will fix this, but I think I'll have to send some
> feelers out to the VirtualBox guys and see if they agree that this
> sounds like some issue in their stack.
It's definintely a bug in the NAT implementatio
Hi,
On Thu, Apr 16, 2015 at 04:51:34PM -0400, Jeff Mitchell wrote:
> Any idea when 2.3.7 will be cut? You said earlier that 2.3.7 would
> have the fix (using peer-id) on the client side and git master has the
> fix on the server side. Will the peer-id server-side component make it
> in to 2.3.7 or
Hi,
On Fri, Apr 17, 2015 at 11:22:12AM -0400, Chris Ross wrote:
> At this point, I now at least know what OpenSSL and crypto libraries my
> openvpn binary is linked against and can speak more correctly about them.
Just for the record - we added code in 2.3.4 or so which will actually
tell you
