From: Tobias McNulty <tobias@caktusgroup.com>
To: buildroot@busybox.net
Subject: [Buildroot] udhcpc: sendto: Network is down
Date: Tue, 28 Apr 2009 16:46:47 -0400 [thread overview]
Message-ID: <49F76B37.9040601@caktusgroup.com> (raw)
I've been working with a buildroot-2009.02 environment that I built for
a TS-7400 board (uses a 2.4 kernel) quite successfully for several
months now. So far I've been configuring the board's network settings
manually using ifconfig and route.
Recently I tried to start using DHCP, but udhcpc is not happy about
something:
# ifconfig eth0 up
# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:D0:69:40:7C:D6
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:51 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:39
# udhcpc -i eth0
udhcpc (v1.13.2) started
Sending discover...
udhcpc: sendto: Network is down
Sending discover...
udhcpc: sendto: Network is down
I've verified the network is actually up (all the lights are on). If I
configure an IP address manually it works fine, e.g.:
# ifconfig eth0 192.168.1.30 up
# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: seq=0 ttl=64 time=0.000 ms
64 bytes from 192.168.1.1: seq=1 ttl=64 time=0.000 ms
64 bytes from 192.168.1.1: seq=2 ttl=64 time=0.000 ms
--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.000/0.000/0.000 ms
What could I be missing?
Thanks
Tobias
--
Tobias McNulty
Caktus Consulting Group, LLC
P.O. Box 1454
Carrboro, NC 27510
(919) 951-0052
http://www.caktusgroup.com
reply other threads:[~2009-04-28 20:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49F76B37.9040601@caktusgroup.com \
--to=tobias@caktusgroup.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.