About Parse Ethernet frame
Parses an Ethernet frame and either shows the deduced values (Source and destination MAC, VLANs) or returns the packet data. Good for use in conjunction with the Parse IPv4, and Parse TCP/UDP recipes.
Input: text. Output: HTML with a sandboxed preview.
Format reference: Parse Ethernet frame background and specification
Example
Use “Try example” to load this public sample and its settings, then run it.
Settings used in this example
| Parameter | Example value | Input and choices |
|---|---|---|
| Input type | Hex | Raw, Hex |
| Return type | Text output | Text output, Packet data, Packet data (hex) |
Input
000000000000ffffffffffff08004500
Result
The result is shown in the preview; download it to inspect the generated content.
Parameters
| Parameter | Default value | Input and choices |
|---|---|---|
| Input type | Raw | Raw, Hex |
| Return type | Text output | Text output, Packet data, Packet data (hex) |
Before interpreting the result
Protocol parsers need the correct byte representation and framing. HTTP Request and DNS over HTTPS contact remote services only when you run them; browser network and CORS restrictions still apply.
How to use this page
- Paste your input or open a local file.
- Adjust tool options if needed, then choose Run tool.
- Copy the result or download the original output bytes.
Inputs and results are not added to the public catalogue or saved in the URL. Processing happens in your browser; HTTP Request and DNS over HTTPS send the requests you explicitly run. Files up to 128 MiB can be opened; decompression and image tools may have smaller processing limits. Large results have a shortened preview. Text and HTML downloads use UTF-8; binary downloads preserve output bytes. Pasted text follows browser newline handling; open a file when exact input bytes matter.