On Wed, Apr 04, 2012 at 02:34:46PM +0900, Yasuoka Masahiko wrote:
> On Tue, 31 Jan 2012 13:59:17 +0100
> "Sebastian Reitenbach" wrote:
> > However, I noted with tcpdump, listening on tun0:
> >
> > # tcpdump -n -i tun0
> > tcpdump: listening on tun0, link-type LOOP
> > 13:51:15.354776
> > tcpdump
On 04/04/2012 07:34 AM, YASUOKA Masahiko wrote:
On Tue, 31 Jan 2012 13:59:17 +0100
"Sebastian Reitenbach" wrote:
However, I noted with tcpdump, listening on tun0:
# tcpdump -n -i tun0
tcpdump: listening on tun0, link-type LOOP
13:51:15.354776
tcpdump: WARNING: compensating for unaligned libpca
On Tue, 31 Jan 2012 13:59:17 +0100
"Sebastian Reitenbach" wrote:
> However, I noted with tcpdump, listening on tun0:
>
> # tcpdump -n -i tun0
> tcpdump: listening on tun0, link-type LOOP
> 13:51:15.354776
> tcpdump: WARNING: compensating for unaligned libpcap packets
> 13:51:15.354795 10.66.66.1
Hi,
On Tue, 31 Jan 2012 13:59:17 +0100
"Sebastian Reitenbach" wrote:
> However, I noted with tcpdump, listening on tun0:
> # tcpdump -n -i tun0
> tcpdump: listening on tun0, link-type LOOP
> 13:51:15.354776
> tcpdump: WARNING: compensating for unaligned libpcap packets
> 13:51:15.354795 10.66.66
On Tuesday, January 31, 2012 10:02 CET, "Sebastian Reitenbach"
wrote:
> On Monday, January 30, 2012 15:43 CET, YASUOKA Masahiko
> wrote:
>
> > On Mon, 30 Jan 2012 22:49:22 +0900 (JST)
> > YASUOKA Masahiko wrote:
> > > pipex hook in udp_usrreq() mistakenly assumed that `inp' is
> > > conn
On Monday, January 30, 2012 15:43 CET, YASUOKA Masahiko
wrote:
> On Mon, 30 Jan 2012 22:49:22 +0900 (JST)
> YASUOKA Masahiko wrote:
> > pipex hook in udp_usrreq() mistakenly assumed that `inp' is
> > connected. The hook could not use the destination address properly,
> > so it failed to find
On Mon, 30 Jan 2012 22:49:22 +0900 (JST)
YASUOKA Masahiko wrote:
> pipex hook in udp_usrreq() mistakenly assumed that `inp' is
> connected. The hook could not use the destination address properly,
> so it failed to find the pipex session. This bug caused LCP keepalive
> failures on L2TP from cli
pipex hook in udp_usrreq() mistakenly assumed that `inp' is
connected. The hook could not use the destination address properly,
so it failed to find the pipex session. This bug caused LCP keepalive
failures on L2TP from client that does LCP keepalive and uses sequence
number on the L2TP data chan