This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: TAP device not created on running "ping_test"
On Fri, Jul 24, 2009 at 4:23 PM, Sergei
Gavrikov<sergei.gavrikov@gmail.com> wrote:
> Mandeep Sandhu wrote:
>> My system also has the tun device:
>> $ ls -l /dev/net/tun
>> crw-rw-rw- 1 root root 10, 200 2009-07-17 09:57 /dev/net/tun
>>
>> Now when I run the ping_test app, I see both the "ecossynth" and
>> "rawether" process's running, but no tap device is created! Shouldn't
>> the rawether proc open the tun device which will result in the tap3
>> device being created?
>
> Hi Mandeep
>
> I would narrow a circle. First, try to bring up and configure any tapN
> device on a host handy (without rawether and eCos app). Test then that
> interface. I found that `tunctl' utility is very useful for that. I'd
> installed it from sources, but, the utility exists in the Ubuntu's
> `uml-utilities' package.
>
> I want to believe that is host-side issue. It's just command to start
>
> man tunctl
>
> Create (tunctl), configure (ifconfig/route) e.g. tap0 device and check
> that works as you could expect (ping). Then go to eCos network tests.
Ok. Will do.
-mandeep
>
> Sergei
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss