Re: [drones-discuss] Wireshark support for MAVLink

[Meier Lorenz]

Hi Victor,

The MAVLink mailing list is the better place for MAVLink questions - due to the high traffic on drones-discuss, lots of the people working with the protocol prefer the specialised list.

There is Wireshark support in the repo, and there is a recent PR improving it here:

https://github.com/mavlink/mavlink/pull/301

I would appreciate if you could provide some testing and feedback.

Cheers,

Lorenz

On 18 Dec 2014, at 05:42, Víctor MV <v.may...@gmail.com> wrote:

Hi,

Has anyone added support for MAVLink on Wireshark? If not I can spend some time this Christmas looking at it and hopefully improve my understanding of the protocol.

Cheers,

Víctor.

--
You received this message because you are subscribed to the Google Groups "drones-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drones-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Víctor MV]

Thanks Lorenz, will do.

[Arthur Benemann]

Might I suggest that we add the following to the end of the mavlink wlua script? This binds port 14550 to the mavlink disector, so messages from mavproxy.py can be decoded in real time without any extra setup.

-- bind protocol to UDP port 14550

udp_table = DissectorTable.get("udp.port")

udp_table:add(14550,mavlink_proto)

2014-12-17 23:14 GMT-08:00 Víctor MV <v.may...@gmail.com>:

Thanks Lorenz, will do.

--
Sie erhalten diese Nachricht, weil Sie in Google Groups E-Mails von der Gruppe "MAVLink" abonniert haben.
Wenn Sie sich von dieser Gruppe abmelden und keine E-Mails mehr von dieser Gruppe erhalten möchten, senden Sie eine E-Mail an mavlink+u...@googlegroups.com.
Weitere Optionen finden Sie unter https://groups.google.com/d/optout.

--

Arthur Benemann

[Arthur Benemann]

Like this:
https://github.com/mavlink/mavlink/pull/304

--

Arthur Benemann

[Víctor MV]

Minor typo with the instructions.

Arthur I'd suggest we don't hardcode the port number. We can follow up the discussion in the pull request.