antmicro/packet.net

Forked from http://sourceforge.net/projects/packetnet/

packet.net's Issues

decrypting ssl responses/requests

Wireshark and other similar services allow decrypting of https responses by installing a certificate on the browser. Is there a way to do it with Packet.Net?

Load failure

When I try to load this project it keeps telling me there is a configuration failure on the packet.net project of the solution. I am unable to assign debug/release or cpu types to it. When I try to compile it says that it cannot find packet.net. I assume this is because of the configuration issues. I have tried to load this project in 2017, 2019, 2022 visual studio.

How to set TcpPacket's Options or OptionsCollection property?

It's such a great library that I'm using it well. Thank you so much.
I am looking for advice while using this library.
When I create and transmit a TCP packet, I want to set the TCP packet's Options or OptionsCollection property.
However, if i try to set Option-related parameters, an error occurs saying that memory cannot be allocated or overflowed.
By any chance, can I get some guide to setting TCP packet Options property?

Implement length checking for LLDPPacket

Verify the minimal length of a header/payload and EnsurePacketLength

Issue with UDP source and destination ports...

This is an excellent library that is really helping me understand and dissect voice over IP packets. I am having a problem with it though (it is easy to work around by the way but wanted to point it out so you are aware). These are my notes for my work around:

// This library has an issue. It is grabbing the first two bytes of the ethernet packet for the udp.SourcePort
// And bytes 3 & 4 for the upd.DestinationPort
// So this code:
// if ( (udp.SourcePort == cr2.RtpSwitchPort || udp.DestinationPort == cr2.RtpSwitchPort) && cr2.ShouldRecord == true)
// Won't work because it is grabbing the wrong bytes.
// The UDP Source and Destination ports are bytes 1&2 and 3&4, respectively of the UDP packet encapsulated inside the larger ethernet packet
// Effectively they are:
// Source port = bytes 34 & 35 and Destination port = bytes 36 & 37 of the whole network packet
// ....because the full packet not just UDP packet is being pulled into the UDP portion
// when we grab IpV4Datagram ip = packet.Ipv4; then UdpDatagram udp = ip.Udp;

Let me know what you think of this.
Thanks.
-Marco.

Add checksum recalculation to IGMPv2Packet

Executed in UpdateCalculatedValues