Hi Pim, This is the packet which was encapsulated with GTP Header and sent out of the Interface. Frame size received/below is 106. Why did NIC add 0's here ? Frame size without 0's is 90 > 64 right. Thats why was suspecting VPP if it add's any extra 0'x based on flags or in some node.
0000 00 00 00 01 00 06 a0 36 9f 37 dc ec 00 00 08 00 0010 45 00 00 5a 00 00 00 00 fd 11 b4 a0 42 42 42 32 0020 42 42 42 3c 4e 98 08 68 00 46 00 79 34 ff 00 36 0030 00 00 00 01 00 00 00 85 01 00 05 00 45 00 00 1e 0040 ef 1b 40 00 3f 11 b0 0a 42 42 42 5a 0b 0c 0d 01 0050 11 5d 11 62 00 0a f8 08 48 69 *00 00 00 00 00 000060 00 00 00 00 00 00 00 00 00 00* /Akash On Tue, Oct 19, 2021 at 2:28 PM Pim van Pelt <p...@ipng.nl> wrote: > Hoi Akash, > > You asked a similar question last week. Is it still the case that you're > describing a packet which is smaller than the 64b frame size described in > IEEE 802.3? > See https://en.wikipedia.org/wiki/Ethernet_frame and a rather informative > context at > https://www.sciencedirect.com/topics/computer-science/minimum-frame-size > > If not, can you show the packet you're intending on sending, how long it > is, and how long you intend for it to be ? > > groet, > Pim > > On Tue, Oct 19, 2021 at 8:31 AM Akash S R <akashsr.akas...@gmail.com> > wrote: > >> Hi Mates, >> >> In my case, VPP is adding some 0's as extra payload onto the packet and >> sending it out to NIC which is nearly 14 - 18 bytes. What is the node which >> add's this ? >> Or b0->flags is responsible for such case? Please help >> >> >> /Akash >> >> >> >> > > -- > Pim van Pelt <p...@ipng.nl> > PBVP1-RIPE - http://www.ipng.nl/ >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20344): https://lists.fd.io/g/vpp-dev/message/20344 Mute This Topic: https://lists.fd.io/mt/86434059/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
