Does anyone know where I can obtain source code for a simple DHCP server?
or in the buildroot release you may find something in buildroot/package/dhcp, select it, build the target and check the output in output/build. In the older release of Linux distribution you find something in user/dhcp*
I usually get dynamic IP for my target board at the bootloader stage, with the utility in u-boot, type "dhcp" in the u-boot command line, will this help you?
Thank you Mr. Wu for the help.
I have been working with multiple BF537 Stamp boards and using a 5-port Hub (using standard patch cables)
I can communicate with all the connected boards and our development PC. Using a cross-over cable I can FTP code to a single board connected to the development PC.
However, if I try to connect two BF537 boards together with a cross-over cable, I cannot communicate one board to another over the ethernet ports. Everything (ping, simple server-client software) that works with the hub will not work when two boards are connected together. Any ideas?
Where does is the linux kernel and rootfs loaded from when two boards connected via a cross cable, from the Flash? Have you run ifconfig on each of the board to check if the ethernet configuration looks good?
For the test I used two newly purchased boards with the old version of uClinux in on board flash. Yes, ifconfig was used to set fixed IP for each board and shows eth0 to be up on both boards. Neither linkon or activity LEDs are active. Is this a kernal configuration problem or ethernet hardware ?
Thank you for replying.
With proper ifconfig I am able to ping from one board to another with a cross cable. Here is what I deed:
1)I am booting kernel and rootfs from ramboot, loading uImage from tftp server, instead of the Flash.
2)power on two boards separately with ramboot as usual, run ifconfig and see two boards has different IP address, at this moment each of them has a ethernet cable connected to a the host PC via a switch
3)keep the power on, remove the two boards from ethernet switch, connect them with a cross cable instead, upon the connection of cross cable, get prompt of the eth0 up as expected. ifconfig to check the ip adress is normal
4)ping one board from another and get normal replies.
I would suggest you to check the same and verify your cable is working fine. I was testing on the 2011R1 release but there should be no difference with other versions.
Thank you Mr. Wu. I will run use this method when I get to my lab this morning. Maybe the old releases contained in the flash are the problem.
Retrieving data ...