Ask Your Question

gerolima's profile - activity

2020-07-16 06:17:08 +0000 received badge  Famous Question (source)
2018-11-02 18:12:02 +0000 received badge  Notable Question (source)
2018-08-02 18:05:42 +0000 received badge  Popular Question (source)
2018-05-23 09:24:52 +0000 marked best answer How to dissect a VLAN frame based on Ethertype

Hi,

I'm trying to write a new dissector for an in-house protocol. This protocol is completely L2, there is no IP header. The frame will be dissected using a specific vlan.id, but I cannot find a way to do so... The following doesn't seem to be working:

dissector_add_uint("vlan.id", xxx_vlan, xxx_handle);

Do i need to use another library than epan/packet.h??

2018-05-23 09:24:52 +0000 received badge  Scholar (source)
2018-05-22 18:15:34 +0000 commented question How to dissect a VLAN frame based on Ethertype

thanks, it worked with dissector_add_uint("ethertype", 0xA003, xxx_handle); I just needed to update my wireshark repo

2018-05-22 18:14:52 +0000 commented answer How to dissect a VLAN frame based on Ethertype

thanks it worked. I just needed to update my git repository to the latest

2018-05-22 12:18:39 +0000 commented answer How to dissect a VLAN frame based on Ethertype

I tried that but no luck. At the moment I'm pulling the latest changes from wireshark-dev. Perhaps I'm missing somethin

2018-05-22 06:08:51 +0000 commented question How to dissect a VLAN frame based on Ethertype

Yeap, you're right, sorry I always mix up these two. The ethertype is 0xa003. To be honest, I could also use ethertype

2018-05-22 06:08:42 +0000 commented answer How to dissect a VLAN frame based on Ethertype

Ok, I'm lost here, could you please post a draft example of the code to do that?

2018-05-21 14:44:34 +0000 commented question How to dissect a VLAN frame based on Ethertype

it's just 0x8100, 802.1q type

2018-05-21 12:34:49 +0000 asked a question How to dissect a VLAN frame based on Ethertype

how to dissect a frame Hi, I'm trying to write a new dissector for an in-house protocol. This protocol is completely L