Thank you for the quick response.
>I assume you mean GRE over IPv4.
>Be more specific and let me know what RFC describes the protocol (RFC 1702 or RFC 2784).
>Currently, you can interpret the GRE datagram by the taking the IPv4 datagram's payload and parse it yourself.
Yes, and it is exactly what I am trying to do. But problem is that I can reasonably easy parse GRE header but the GRE payload (encapsulated IPv4 datagram) needs to be parsed too. It is very tempting to use IpV4Datagram class but it does not allow instantiation
from the buffer. Thus I have either to implement custom IpV4Datagramor use non-public constructor "internal IpV4Datagram(byte, int, int)". Both options are doable but not particularly elegant. Is there any way to instantiate IpV4Datagram
fm the buffer and offset?
>Until you've mentioned it, there was no plan to add support for this protocol. I see no reason not to support this protocol so please add it as an issue in the Issue Tracker (with as many details you can like RFCs and the different layers combination
support you want) and it would probably be supported in a future version.
I definitely will.