TLDR; Don't feed the starving Indian people... I re-added Vesta to the loop for the sake of it. That's the way to respond to a list, use CC and don't use BC. Mmmkay... ???
It is ALWAYS better to direct an improper question to a forum where it could be answered, instead of giving a direct answer; since for many people in other cultures other than the western it indirectly means they can continue sending questions to the forum where they got the first answer; believe me, I've seen this for almost 25 years now... One can in these situations suggest to try use google.com/yandex.ru/baidu.com. Howeve in this particular case luckily no harm has been done since the answer is useless. However 'tcpdump' would normally give more questions than it solves, so don't suggest advanced things for a ELI5 or in the case of basic questions; work with the material you've got. As one can see the answer itself has already been tried, with an explicit and unnecessary broadcast address. To rule out any problems with the data link in this particular case one should suggest to use 'arping' and work from there on your own. I'd also suggest upgrading both kernel and busybox to something newer, seems like the setup is almost 10 years old and *might* have bugs long gone. Just a humble ranting... (from a white man who can't jump, but code). //M Sent from my BlackBerry — the most secure mobile device Original Message From: [email protected] Sent: 24 April 2019 17:31 To: [email protected] Reply to: [email protected] Subject: Re: How to manually configure ethernet from Busybox Hello Vesta, Bad news: this is the wrong ML for this question, There is no busybox bug. Good news: i use things like: ifconfig eth0 192.168.15.1 netmask 255.255.255.0 this is a working way. Hint: you may check the connection using tcpdump. re, wh Am 20.04.2019 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)? > > 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 > ... ... > > Device is also unreachable when ping it from computer. > ping 192.168.15.1 > connect: Network is unreachable > > > Regards, > > > _______________________________________________ > busybox mailing list > [email protected] > http://lists.busybox.net/mailman/listinfo/busybox > _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
