These are really useful packet dumps. They show standard 14-byte Ethernet header followed by IPv6 header.
This packet should be accepted by ethernet_input() and from there it would go to ip6_input().
If you debug stepping into your functions, where does it end up? Cheers Ivan
Date: Wed, 12 Nov 2014 00:01:42 -0700 (MST) From: mfkexpress <[email protected]> To: [email protected] Subject: Re: [lwip-users] oxff==0x60 condition do not match for received IP6 packet in tcipip_thread Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii I'm really very much confised with this p->payload. Below are the settings and received packets at my device: 1) netif->flags= NETIF_FLAG_BROADCAST | NETIF_FLAG_ETHARP | NETIF_FLAG_LINKUP 2) I printed incoming packets of my device using p->payload which appears something like below: p->payload 33 33 00 00 00 02 74 46 A0 9E 85 9B 86 DD 60 00 00 00 00 10 3A FF FE 80 00 00 00 00 00 00 64 E4 E3 51 A0 9D 5B F4 FF 02 00 00 00 00 00 00 00 00 00 00 00 00 00 02 85 00 9C E5 00 00 00 00 01 01 74 46 A0 9E 85 9B AF DD 0E D2 p->payload 33 33 00 00 00 01 74 46 A0 9E 85 9B 86 DD 60 00 00 00 00 20 3A FF FE 80 00 00 00 00 00 00 64 E4 E3 51 A0 9D 5B F4 FF 02 00 00 00 00 00 00 00 00 00 00 00 00 00 01 88 00 35 8D 20 00 00 00 FE 80 00 00 00 00 00 00 64 E4 E3 51 A0 9D 5B F4 02 01 74 46 A0 9E 85 9B 6F 23 2A 63 Now first nibble is not "6' in above packets but 30th byte is "6". Than how it will enter into IPV6 case of tcpip_thread()?? Please any soluton.. Regards, Mohsin
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
