From: Stephen Hemminger <stephen@networkplumber.org>
To: Dani Camps <danicamps81@yahoo.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Problem with tap interface: link is not ready
Date: Mon, 23 Sep 2013 09:14:50 -0700 [thread overview]
Message-ID: <20130923091450.7615cc60@samsung-9> (raw)
In-Reply-To: <1379951507.84403.YahooMailNeo@web172101.mail.ir2.yahoo.com>
On Mon, 23 Sep 2013 16:51:47 +0100 (BST)
Dani Camps <danicamps81@yahoo.com> wrote:
>
>
> Dear all,
>
> I am not sure that I am addressing the correct mailing list. In case I am not, please accept my apologies.
>
> I am trying to create a virtual tap device that I want to add later on to a bridge. My problem is that the tap interface always appears with state disabled if I do a ´brctl showstp br0´, and no traffic reaches the bridge. After some investigation I found out that the tap interface is never up. How can I bring the tap interface up?
>
> These are my detailed steps:
>
> sudo tunctl -t tap0
> sudo ifconfig tap0 192.168.0.2/24 up
>
> But when I look at dmesg I get:
>
> ADDRCONF(NETDEV_UP): tap0: link is not ready
>
>
> Nevertheless if I do 'ifconfig tap0' it seems to indicate that the interface is up:
>
> tap0 Link encap:Ethernet HWaddr 72:a0:fb:88:95:44
> inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:500
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> But I never see a message in dmesg saying "tap0: link becomes ready." And when I add the tap0 interface it always appears disabled, so I think that the interface is never really up.
>
> My kernel is 3.0
>
> Any help to bring up the tap interface is much appreciated.
>
> Best Regards
>
> Daniel
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
The carrier state of the TAP device is up if a program has the tap device handle open.
If no program has the tap device open then carrier (IFF_RUNNING) will be down.
The bridge with STP monitors carrier state to decide whether to use the network
device.
In summary, unless you have an application using tap, the device will look
to network as if cable is unplugged.
prev parent reply other threads:[~2013-09-23 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 15:51 Problem with tap interface: link is not ready Dani Camps
2013-09-23 16:14 ` Stephen Hemminger [this message]
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=20130923091450.7615cc60@samsung-9 \
--to=stephen@networkplumber.org \
--cc=danicamps81@yahoo.com \
--cc=netdev@vger.kernel.org \
/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