Yes, this packet enters into ethernet_input(), but after that it goes to
ip_input() which I really wondered how it was going there thought they IPV6
packets only.
But later I found that there was no case for IPV6 in ethernet_input(), so I
added case for ETHTYPE_IPV6 and called ip6_input() it.
I think there must be some patch for it.
With above case added, now my input packet even reaches nd6_input() and from
there appropriate reply packet is also formed.
But still that reply packet (q->payload) is not received on my PC.
Because I found that in all outgoing packets, IP6 Header Version remains "0"
which I think should be "6".
Regards,
Mohsin
On Nov 13, 2014 9:57 PM, "Ivan Delamer-2 [via lwIP]"
<[email protected]> wrote:
>
> 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 <[hidden email]>
> > To: [hidden email]
> > Subject: Re: [lwip-users] oxff==0x60 condition do not match for
> > received IP6 packet in tcipip_thread
> > Message-ID: <[hidden email]>
> > 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
> [hidden email]
> https://lists.nongnu.org/mailman/listinfo/lwip-users
>
>
> ________________________________
> If you reply to this email, your message will be added to the
--
View this message in context:
http://lwip.100.n7.nabble.com/oxff-0x60-condition-do-not-match-for-received-IP6-packet-in-tcipip-thread-tp23481p23510.html
Sent from the lwip-users mailing list archive at Nabble.com.
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
