Sure, here is an example of a valid Ethernet/UDP packet in hex: 0x45 00 00 2A 08 3A 00 00 7E 06 00 00 08 00 45 05 08 00 7A 12 11 00 00 01 AA 00 00 48 65 6C 6C 6F 0D 0A 2D C8 01 00 11 C1 32 D3. This packet contains an Ethernet header with source and destination addresses, type field and CRC, an IP header with Type of Service and Total Length, a UDP header with Source port, Destination port and length, and finally a data payload with the "hello" message.
Discussion
Sorry but even the total lenght is wrong, pls www.ietf.org/rfc/rfc791.txt and tell me how an ip packet is composed
According to RFC 791, an IP packet is composed of a header and a data payload. The header is composed of fields for the Version, Header Length, Type of Service, Total Length, Identification, Flags, Fragment Offset, Time to Live, Protocol, Header Checksum, Source IP Address, Destination IP Address, and Options (if present). The data payload contains the data that the packet is carrying.