linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: RAJESH DASARI <raajeshdasari@gmail.com>
To: Oliver Neukum <oneukum@suse.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Reg: USB network interface is down after the reboot
Date: Tue, 14 Jan 2020 10:40:14 +0530	[thread overview]
Message-ID: <CAPXMrf8PJ=+CG9TqazvbDPL1WkRNQHVTHOowr=Y_a09ULAyscw@mail.gmail.com> (raw)
In-Reply-To: <1578923319.2590.13.camel@suse.com>

Hi Oliver,

Thanks for your reply, Please find my response inline.

Thanks,
Rajesh Dasari.

On Mon, Jan 13, 2020 at 7:35 PM Oliver Neukum <oneukum@suse.com> wrote:
>
> Am Donnerstag, den 26.12.2019, 15:01 +0530 schrieb RAJESH DASARI:
> > Could someone please help, why the usb0 is down on Device A side and
> > it there is any known issue or is this  expected behaviour?
>
> Hi,
>
> the kernel cannot just set devices running. Does it work if you up
> the device (with "ip" or "ifconfig")?

Rajesh : if i make ifconfig usb0 up on device A side, device is coming
up and RUNNING bit is set,

Your device on side A has no
> IP. It cannot work.
Rajesh : If i assign the ip address to the usb0 interface then also
interface is coming up and RUNNING bit is set.
 We need to determine whether this is a kernel
> issue or your setup in user space.
Rajesh : If  i don't run ifconfig usb0 up or if i don't set the ip
address it is running bit is not set. Is it the standard behaviour.
Could you please tell me how to find out it is a user space issue or
kernel issue.
>
>         HTH
>                 Oliver
>

  reply	other threads:[~2020-01-14  5:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-26  9:31 Reg: USB network interface is down after the reboot RAJESH DASARI
2019-12-30  9:22 ` RAJESH DASARI
2020-01-13 13:48 ` Oliver Neukum
2020-01-14  5:10   ` RAJESH DASARI [this message]
2020-01-14 17:15     ` Oliver Neukum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPXMrf8PJ=+CG9TqazvbDPL1WkRNQHVTHOowr=Y_a09ULAyscw@mail.gmail.com' \
    --to=raajeshdasari@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).