Kindly refer to the following thread for a subsequent discussion: http://www.nabble.com/forum/ViewPost.jtp?post=9306384&framed=y
Jonathan Larmour wrote: > > Ashish Anand wrote: >> >> >> Jonathan Larmour wrote: >>> The real problem appears to be that the telnet SYN is never even seen. >>> >>> >> >> I get the same output, when I send the SYN packet to the board: not for >> us, >> not bouncing it off... > > No, that message is in connection with the multicast broadcast. See > ip_input() in core/ipv4/ip.c: it will output one line of debug for each > netif it attempts to match the IP packet's destination address against. > And > then if it doesn't match any of them, it says "ip_input: packet not for > us.\n". But all these messages are in the context of one single packet. > > Jifl > -- > eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts > Meet us at Embedded Systems Conference - SV, April 3rd-5th. Stand #2248 > Company legal info, address and number: http://www.ecoscentric.com/legal > ------["The best things in life aren't things."]------ Opinions==mine > > > _______________________________________________ > lwip-users mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/lwip-users > > -- View this message in context: http://www.nabble.com/eCos---PPP---TCP---LwIP-tf3219708.html#a9306816 Sent from the lwip-users mailing list archive at Nabble.com. _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
