[Ariel Burbaickij <ariel.burbaickij@xxxxxxxxx>]

>The *first* thing you'll have to delve into is support for transmitting MTP2 packets on whatever OS you were >planning to run tcpreplay....

 

Well, part of this delving will be, of course, pursuing the way of the weak one instead of going for full-blown support for MTP2 as a first step-- just using dummy SCTP header as I am not that much interested in MTP2 itself  but just in what appears in higher layers, i.e. MTP3 and particularily -- SCCP.

 

 

/wbr

Ariel Burbaickij

On Tue, Mar 5, 2013 at 8:52 AM, Guy Harris <guy@xxxxxxxxxxxx> wrote:

On Mar 4, 2013, at 10:24 PM, Ariel Burbaickij <ariel.burbaickij@xxxxxxxxx> wrote:

> That is why I asked then:
>  Does it mean that the development of wireshark/wiretap
>  and tcpreplay happens in totally independent way?
> in order to be sure that this is indeed what (somewhat sadly) happens.

I'm actually very happy that Wireshark can develop independently of libpcap, as it means that Wireshark isn't limited to reading pcap and pcap-ng files.  Other people are probably happy about it too, for the same reason.

> So, looks like I will have to delve deeper in this DLT plugin stuff.

The *first* thing you'll have to delve into is support for transmitting MTP2 packets on whatever OS you were planning to run tcpreplay....

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe