Re: cipe-win32: peer IP address (was: Communication breakdown....)|
Damion Wilson <dwilson,AT,ibl,DOT,bm>|
Mon, 14 Apr 2003 22:02:47 +0200|
Argh ! I missed that ? I'm so ashamed. It's supposed to be using the address
of the last successfully decrypted packet. You're right, of course about the
fix, which is what I thought I put in there (sigh).
On Monday 14 April 2003 04:31 pm, Christof Meerwald wrote:
> On Fri, 28 Feb 2003 14:27:08 -0400, Damion K. Wilson wrote:
> > CIPE-Win32 isn't modal like that. All it cares about is the source IP
> > address of the last correctly decrypted tunnel packet, which it uses as
> > the destination address for any outgoing packets.
> That's how it should be, but it's not how it is currently implemented. The
> current implementation (2.0-pre15) uses the address of the last received
> packet (no matter if it was correctly decrypted or not).
> Have a look at CipeSocketIO:RequestAsyncReceive: WSARecvFrom always updates
> m_PeerInfo with the address of the received packet. The obvious fix is to
> pass a temporary variable to WSARecvFrom which is only copied to m_PeerInfo
> if the packet was correctly decrypted.
> bye, Christof