On Mon, 16 Jun 2008, SAMUEL Dinesh wrote: > We have the same problem as described in this link. > > http://busybox.net/lists/busybox/2008-June/031835.html > > We don't use WLAN card. Just the two Ethernet cards included in the taihu > evaluation board (ppc 405ep). > > We tried the solution supplied in the topic linked below and it worked for > us. > > Tcpdump output on the dhcp server looks pretty normal. Here's the debug > output we had before modifying clientsocket.c with(out) your code block :
[snip] > Could you please provide us an explanation for this. If removing the > code block you specified is enough, please let us know too :-) Could you please provide that trace, as Denys asked for? On Thu, 12 Jun 2008, Denys Vlasenko wrote: > > Can you collect "tcpdump -nlieth0 -s0 -vvv -xX port 67 or port 68" > output for both? Write it to a file and post it. If you don't want to make it public, please post to our private addresses. Acctualy: $ tcpdump -nlieth0 -s0 -w <filepath> 'udp and port (67 or 68)' would be more interesting. I'm interested too, as it was on my initiative that filtering code was added. Cheers, -- Cristian _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
