From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by dpdk.org (Postfix) with ESMTP id 848AF298F for ; Sat, 1 Oct 2016 21:54:24 +0200 (CEST) Received: by mail-wm0-f49.google.com with SMTP id k125so83383520wma.1 for ; Sat, 01 Oct 2016 12:54:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=8RGPHsOQYoS2Z3TQgd50b7WuU+ibJPG3YYCI74e8FmE=; b=N0BjrAVep2T0JWcQ9G7pvPlS/OkfCCe+VUQT9rqyJ3vuyls8yuoEZxiihYrcawO5QY Xu6zQB9gDeB4IOOLWPU57eWt7GZxk61/hwQCa+/VwwX98f+PYbr0l4U/Dr5NvwKnKthW 9Pibs7ipO+iFMXs/hseE7KK8LmFu7Mc7w+BMGImVmVzou+VeSz+i/PVQCSb+v9gLuAvn hG62/N35OiNQ/qGFC9wYL+llQl5yNx+pXMIDiajH7Vn763nrBerJyR3VG5XcHLINs5UB WyuWgvK6YOHRWiTz2slwnzvmBWB35iBaBqz7Z7KVrMCd9gfa4T8FhXWEW6BtvX2LQWCd dclA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=8RGPHsOQYoS2Z3TQgd50b7WuU+ibJPG3YYCI74e8FmE=; b=lmHcJOsB+T6ouxTZJSXfQgF5rqrh0bBLSsYjRJQGEhS/09Z4NN3ji/cvfUg8s0vKDj z62dP6fkMcEpgGJWG7VZk5TAUco2C9e1P6xluvJLpNL6ec0lZ/uEItKMNjAhhtEmBTDV tZiyWFjs2xYXnynSH1cgRisVP9ausBx60hz7rrfgioDAxEfPTwurFFIWE7plX1/5zIpk kTjkI6pd+DJ6/mIbk0wU7L5mUGrGYdRFuO6RTLgBkRonnnnox7eR0M5zBbeCyQTSxusJ 2sazBcteNxsX0k/f0FQaEX3DnaSnZ57SHR5khHb6JEqO3tL+SXAQfwd+Y2TtyEJ5lXhK 8vWQ== X-Gm-Message-State: AA6/9Rm4BUdeXy/yN9Th4rVFLfGCzqMlVRwdsBqmTVrBLTM7GymHX02wWAEz311j4SXu3B+tOIAYNfKA42H0nA== X-Received: by 10.28.55.21 with SMTP id e21mr2887477wma.80.1475351664092; Sat, 01 Oct 2016 12:54:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.73.3 with HTTP; Sat, 1 Oct 2016 12:54:23 -0700 (PDT) In-Reply-To: References: From: Alex Kiselev Date: Sat, 1 Oct 2016 22:54:23 +0300 Message-ID: To: users Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-users] bringing up kni interfaces using netlink X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2016 19:54:24 -0000 Hi! One part of my problem is solved. I've figured out the cause of renaming kni interfaces. It was due to linux udev rules. But the dpdk related part of the problem is still there: I am having troubl= es with bringing them up. They are created just fine, I can get their linux interfaces index, I can add ip addresses to them using the netlink, but have to wait some time after their creation in order to bring them up using netlink api. So, do kni interfaces really need some time to complete some kind of initialization and only then can receive "up" netlink commands? 2016-09-19 19:20 GMT+03:00 Alex Kiselev : > Hi! > > I am trying to use the linux netlink interface with kni interfaces in > order to bring them up and add ip addresses to them and I am > experiencing some strange behaviors. Could anyone help me to > understand what I am doing wrong? > > The problem is that I can=E2=80=99t bring kni interfaces up using the net= link > interface immediately after their creation. What I can is to bring > them up using the =E2=80=9Cip=E2=80=9D linux tool or I can bring them up = using netlink > after some time has passed. But when I try to up them immediately > after the creation they just stay in the =E2=80=9CDOWN=E2=80=9D state. Al= so the =E2=80=9Cip > link ls=E2=80=9D linux command freezes for about 5-7 seconds after netlin= k > commands have sent to up the kni interfaces, and one of kni interfaces > changes it=E2=80=99s name to the name of one of the pure linux interfaces > (eth3). > > P.S. I am using the DPDP 2.2.0. > > > -- > -- > Alex Kiselev --=20 -- Alexander Kiselev