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"
> 1) run dhcp-server on tap0 (using separate terminal session) after that
> when tap0 is configured and up. You will see its log messages on stderr
> (-d -f options). Have you set INTERFACES variable?
>
> 2) run dhclient for tap0, again (using sepatare terminal session) again
> do not forking (-d) and you should see then that dhcp server offers IP
> and dhclient get it.
This is where I see a problem. When I ran dhclient on tap0 (_AFTER_
configuring tap0
with a valid static IP addr), I see that the IP addr of tap0 is unset
first and then dhclient
starts sending DHCP DISCOVER packets over it....
Did you observe similar behaviour in your machine too?
Thanks,
-mandeep
>
> This is that sandbox.
>
>> $ sudo dhclient -d tap0
>> There is already a pid file /var/run/dhclient.pid with pid 9903
>
>> Listening on LPF/tap0/26:5d:5f:e5:65:1e
>> Sending on ? LPF/tap0/26:5d:5f:e5:65:1e
>> Sending on ? Socket/fallback
>> DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 5
>> DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 7
>
> I do not see that client got IP. May be you hit ^C too early?
>
> try again starting ?with
>
> sudo killall dhcpd dhcpd3 dhclient dhclient3
> sudo ifdown tap0
> sudo ifup tap0
>
> 1)...
>
> 2)...
>
> 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