Hi Vesta, Am 20.04.19 um 18:13 schrieb Vesta: > Hi, > > Linux version 2.6.26.5, ARM Linux Kernel on embedded device. > How to manually set up Ethernet connection from BusyBox v1.10.2 rescue shell > (ash)?
JFTR: your issue is not a busybox problem, you probably need to read up on IPv4 networking basics. > I mounted the main virtual file systems, then tried: > > # ifconfig lo 127.0.0.1 > # ifconfig eth0 hw ether 88:75:56:05:2B:24 > # ifconfig eth0 192.168.15.1 netmask 255.255.255.0 broadcast 192.168.15.255 > # ifconfig eth0 up > # route add -net 192.168.15.0/24 eth0 > # ifconfig eth0 > eth0 Link encap:Ethernet HWaddr 88:75:56:05:2B:24 > inet addr:192.168.15.1 Bcast:192.168.15.255 Mask:255.255.255.0 > UP BROADCAST RUNNING 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:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > Interrupt:22 > > # ping 192.168.15.100 > PING 192.168.15.100 (192.168.15.100): 56 data bytes > From 192.168.15.100 icmp_seq=0 timed out Everything is fine here, your device is sending out the packets, but not getting a response... > ... ... > > Device is also unreachable when ping it from computer. > ping 192.168.15.1 > connect: Network is unreachable This machine is configured wrong. It does not know how to reach 192.168.15.1 -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
