On Wed, Apr 04, 2012 at 02:34:46PM +0900, Yasuoka Masahiko wrote: > On Tue, 31 Jan 2012 13:59:17 +0100 > "Sebastian Reitenbach" <[email protected]> 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 > 10.66.66.129: icmp: echo reply (DF) > > 13:51:16.334984 > > 13:51:16.334997 10.66.66.1 > 10.66.66.129: icmp: echo reply (DF) > > 13:51:17.355463 > (snip) > > The incoming packets look weird, and this is not only true for icmp, > > with tcp/udp its the same. > > Attached diff will fix the problem. > > bpf requires to use different byte order for DLT_LOOP and DLT_NULL on > address family header. pipex works with both pppx(DLT_NULL) and > tun(DLT_LOOP), so it should switch the byte order. > > ok? or comment?
Since pppx(4) is only used by npppd/pipex shouldn't we change the DLT there so that we don't need any magic inside pipex? -- :wq Claudio
