From owner-freebsd-net@freebsd.org Mon Jul 20 12:05:28 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23DE39A6A3D for ; Mon, 20 Jul 2015 12:05:28 +0000 (UTC) (envelope-from wangzheng@jrq.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 088C211A4 for ; Mon, 20 Jul 2015 12:05:28 +0000 (UTC) (envelope-from wangzheng@jrq.com) Received: by mailman.ysv.freebsd.org (Postfix) id 075F99A6A3C; Mon, 20 Jul 2015 12:05:28 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1A249A6A3B for ; Mon, 20 Jul 2015 12:05:27 +0000 (UTC) (envelope-from wangzheng@jrq.com) Received: from smtpproxy9.qq.com (smtpproxy9.qq.com [113.108.67.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ECB42119F for ; Mon, 20 Jul 2015 12:05:25 +0000 (UTC) (envelope-from wangzheng@jrq.com) X-QQ-mid: bizesmtp7t1437393841t306t066 Received: from [10.1.20.49] (unknown [218.17.161.94]) by esmtp4.qq.com (ESMTP) with id ; Mon, 20 Jul 2015 20:04:00 +0800 (CST) X-QQ-SSF: 00400000012000F0F812000A0000000 X-QQ-FEAT: Tas2jRaQZEOExdd8zjJENWNPXxOEBM/rUmfg+45/tBdUjeAQQg2pSKD97evV7 gDAB45CdWFOhlgOE/0+OBHR9nGCKA19W0H4oojYT6zdoOeK6sBkcdU6ggb6aArTdRb4FSR2 Ejo1nCLRpjwJZmq9NGjW4Ni4LtLuRUxSYz+xRT9WONXv9LUqpuJrcvoiFgnZdi41XEAZrgH pnh9pyeSE0U6Qqt1l9iTgAIb6LIXENsk9XLsS6EcAmdFbMiTo5+ThijTSoL6x264= X-QQ-GoodBg: 2 From: arthurwang Message-Id: Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Subject: Two netmap issues : 1. "protocol 0000 is buggy" , 2: network applications stuck Date: Mon, 20 Jul 2015 20:04:00 +0800 References: <8714904D-22E4-4738-ABF8-C42ACACFEF3B@jrq.com> To: net@freebsd.org, rizzo@iet.unipi.it In-Reply-To: <8714904D-22E4-4738-ABF8-C42ACACFEF3B@jrq.com> X-Mailer: Apple Mail (2.2098) X-QQ-SENDSIZE: 520 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 12:05:28 -0000 Hi , I=E2=80=99m new to netmap , =E2=80=9Ca novel framework for fast = packet I/O=E2=80=9D accroding to = http://info.iet.unipi.it/~luigi/netmap/#85cb = , :). Im doing a test = for its bridge.c example program , which do a bridging(namely proxying , = I suppose ) job between NIC and host stack ,by running =E2=80=9C./bridge= -i net map:ethic=E2=80=9D from command line , and I have two problems = : Problem 1 :=20 It issues =E2=80=9Cprotocol 0000 is buggy=E2=80=9D once per = second , seems not running correctly, by contrast to the normal state , = under which print =E2=80=9Cpoll timeout =E2=80=9C once per 2.5 seconds . = This issue not always exist.=20 Here is the procedure to reproduce: 1> install a centOS 6.5 on vmware fusion 7( host: mbp ) =20 2> download kernel 2.6.32.67 from kernel.org = , compile & install it, reboot the guest OS.=20 3> clone netmap from https://github.com/ppLorins/netmap = , unpack & compile it , insert the = netma.ko to kernel. 4> compile the bridge.c example=20 5> run example with =E2=80=9C./bridge -i netmap:eth0=E2=80=9D Thus , it will print the error message =E2=80=9Cprotocol 0000 is = buggy=E2=80=9D , I explore it by google for quite a long time, found = nothing .=20 Environment info about the guestOS centOS6.5 , from a =E2=80=9Cn= ame -a=E2=80=9D call : =20 Linux localhost.localdomain 2.6.32.67 #1 SMP Fri Jul 17 08:41:59 = CEST 2015 i686 i686 i386 GNU/Linux As for the NIC driver , I have no idea about it but it was = simulated by vmware, sorry for this ,but if you need extra information = about it , tell me how to view it by command line , and I will reply as = soon as possible .=20 Problem 2:=20 Even though Problem 1 not exists , the program also appears to be = something wrong , Here are what I found : 1> ping request from another machine can return normally ( same as I = supposed ) =20 =20 2> new tcp connection(requested by telnet, destination port is 22 ) = can be successfully established from other machine ( same as I = supposed ) =20 3> existing session (pts/0 , pts/1 ) founded by a precede ssh call = , are stuck , cannot enter any character or get any response into/from = screen. (confusing) 4> new ssh request (represents all tcp applications ), cannot = get response and timed out. (confusing ) In my assumption, there should be no difference with or without the = bridge program running , for the upper layer network applications = .Since bridge just acts as a proxy between NIC and host stack ,and do = nothing except that . Thus all ip(ping) or tcp(ssh) layer = applications should act as normal , but unfortunately just part of them = are okay . Can anyone help ? I know there are few people using netmap , it=E2=80= =99s quite a novel technique for network application=E2=80=A6. Thanks a lot. =20 =E2=80=94 ArthurWang =E2=80=94 Best Regards