what happen ? unresolve IPv4Packet

[Rgoogle]

what happen ? unresolve IPv4Packet

[Paul-weqe]

Have you been able to fix this @Rgoogle ?

[Rgoogle]

This is really frustrating. I ran it on another cloud computer, downloaded WinPcap and packet.lib, and then wrote it in Visual Code. But there were no red error prompts like before. When I press Ctrl to jump, it basically jumps to the #Packet property macro. It's similar to my previous error.

I'm now suspecting that these red error prompts are just a compiler issue. In reality, it can still run.

My original problem was that I didn't download WinPcap and packet.lib at first, so I'm not sure what the reason is now. The most likely possibility is that the compiler is having trouble with the code generated by the Packet macro, which the compiler can't see.

now,i had fix it in another pc

[Paul-weqe]

Hmm...so first, Windows seems to be bringing issues to more than just you (see here). The documentation will be improved on that. I am on Ubuntu so I could have been of little help anyway.

Now to the second problem. I will be using MutableEthernetPacket and EthernetPacket to illustrate. The problem comes out because the structs such as EthernetPacket and MutableEthernetPacket and the rest of the packets are not manually coded, they are generated via the Packet Macro when the library is compiled, (look here). From line 10 it describes how they are automatically generated.

Basically this means that when you look for their written code, such as by pressing Ctrl + Enter, the only place it can take you is to the Macro that produced it. If you really want to have a look at the struct that called the macro for e.g MutableEthernetPacket and EthernetPacket to be produced, most of them are inside here.

I don't know if I have answered your question correctly. If not, let me know where I can elaborate.