Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Wireshark build #182

Merged
merged 1 commit into from
Jan 31, 2023

Conversation

Demogorgon314
Copy link
Member

@Demogorgon314 Demogorgon314 commented Jan 31, 2023

Motivation

The Pulsar Wireshark plugin has not been maintained for a long time,
the Pulsar protobuf command and Wireshark header file have been updated.

Modifications

  1. Fix protobuf file path
  2. Fix the Wireshark header
  3. Fix README base path

Documentation

  • doc-required
    (Your PR needs to update docs and you will update later)

  • doc-not-needed
    (Please explain why)

  • doc
    (Your PR contains doc changes)

  • doc-complete
    (Docs have been already added)

@Demogorgon314 Demogorgon314 self-assigned this Jan 31, 2023
@BewareMyPower BewareMyPower added this to the 3.2.0 milestone Jan 31, 2023
@BewareMyPower BewareMyPower added the bug Something isn't working label Jan 31, 2023
#include <epan/proto.h>
#include <epan/value_string.h>
#include <glib.h>
#include <ws_version.h>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This header does not work for the wireshark-dev (3.2.3) on Ubuntu. It seems to be caused by the breaking change of the wireshark.

Anyway, currently we can focus on the wireshark 4.x support. So this comment is not a blocker.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we can fix it for old version support later if necessary.

@BewareMyPower BewareMyPower merged commit dd649f5 into apache:main Jan 31, 2023
@Demogorgon314 Demogorgon314 deleted the fix-wireshark-4.0-build branch January 31, 2023 07:29
BewareMyPower added a commit to BewareMyPower/pulsar-client-cpp that referenced this pull request Jan 31, 2023
### Motivation

apache#182 fixes the Wireshark
build process on macOS. However, it breaks the compatibility with some
Wireshark distributions like the default Wireshark 3.2.3 on Ubuntu
20.04. The reason is some Wireshark distributions use `config.h` to
record the versions, while other might use `ws_version.h`.

See
https://listman.redhat.com/archives/libvir-list/2020-September/msg00377.html
for a similar fix.

### Modifications

Try to find the `ws_version.h` first, if it's not found, find the
`config.h`.

To be more user friendly:
- Separate the dissector from the whole project so that we can build the
  dissector without building the Pulsar C++ client.
- Refactor the README of the Wireshark dissector by focusing on how to
  use.
BewareMyPower added a commit to BewareMyPower/pulsar-client-cpp that referenced this pull request Jan 31, 2023
### Motivation

apache#182 fixes the Wireshark
build process on macOS. However, it breaks the compatibility with some
Wireshark distributions like the default Wireshark 3.2.3 on Ubuntu
20.04. The reason is some Wireshark distributions use `config.h` to
record the versions, while other might use `ws_version.h`.

See
https://listman.redhat.com/archives/libvir-list/2020-September/msg00377.html
for a similar fix.

### Modifications

Try to find the `ws_version.h` first, if it's not found, find the
`config.h`. Add the workflow to verify it can be built on Ubuntu.

To be more user friendly:
- Separate the dissector from the whole project so that we can build the
  dissector without building the Pulsar C++ client.
- Refactor the README of the Wireshark dissector by focusing on how to
  use.
BewareMyPower added a commit to BewareMyPower/pulsar-client-cpp that referenced this pull request Jan 31, 2023
### Motivation

apache#182 fixes the Wireshark
build process on macOS. However, it breaks the compatibility with some
Wireshark distributions like the default Wireshark 3.2.3 on Ubuntu
20.04. The reason is some Wireshark distributions use `config.h` to
record the versions, while other might use `ws_version.h`.

See
https://listman.redhat.com/archives/libvir-list/2020-September/msg00377.html
for a similar fix.

### Modifications

Try to find the `ws_version.h` first, if it's not found, find the
`config.h`. Add the workflow to verify it can be built on Ubuntu.

To be more user friendly:
- Separate the dissector from the whole project so that we can build the
  dissector without building the Pulsar C++ client.
- Refactor the README of the Wireshark dissector by focusing on how to
  use.
BewareMyPower added a commit to BewareMyPower/pulsar-client-cpp that referenced this pull request Feb 2, 2023
### Motivation

apache#182 fixes the Wireshark
build process on macOS. However, it breaks the compatibility with some
Wireshark distributions like the default Wireshark 3.2.3 on Ubuntu
20.04. The reason is some Wireshark distributions use `config.h` to
record the versions, while other might use `ws_version.h`.

See
https://listman.redhat.com/archives/libvir-list/2020-September/msg00377.html
for a similar fix.

### Modifications

Try to find the `ws_version.h` first, if it's not found, find the
`config.h`. Add the workflow to verify it can be built on Ubuntu.

To be more user friendly:
- Separate the dissector from the whole project so that we can build the
  dissector without building the Pulsar C++ client.
- Refactor the README of the Wireshark dissector by focusing on how to
  use.

### Verifications

Add a workflow to build Wireshark dissector on both Ubuntu and macOS.
BewareMyPower added a commit to BewareMyPower/pulsar-client-cpp that referenced this pull request Feb 2, 2023
### Motivation

apache#182 fixes the Wireshark
build process on macOS. However, it breaks the compatibility with some
Wireshark distributions like the default Wireshark 3.2.3 on Ubuntu
20.04. The reason is some Wireshark distributions use `config.h` to
record the versions, while other might use `ws_version.h`.

See
https://listman.redhat.com/archives/libvir-list/2020-September/msg00377.html
for a similar fix.

### Modifications

Try to find the `ws_version.h` first, if it's not found, find the
`config.h`. Add the workflow to verify it can be built on Ubuntu.

To be more user friendly:
- Separate the dissector from the whole project so that we can build the
  dissector without building the Pulsar C++ client.
- Refactor the README of the Wireshark dissector by focusing on how to
  use.

### Verifications

Add a workflow to build Wireshark dissector on both Ubuntu and macOS.
BewareMyPower added a commit that referenced this pull request Feb 3, 2023
* Support the Wireshark plugin for more Wireshark distributions

### Motivation

#182 fixes the Wireshark
build process on macOS. However, it breaks the compatibility with some
Wireshark distributions like the default Wireshark 3.2.3 on Ubuntu
20.04. The reason is some Wireshark distributions use `config.h` to
record the versions, while other might use `ws_version.h`.

See
https://listman.redhat.com/archives/libvir-list/2020-September/msg00377.html
for a similar fix.

### Modifications

Try to find the `ws_version.h` first, if it's not found, find the
`config.h`. Add the workflow to verify it can be built on Ubuntu.

To be more user friendly:
- Separate the dissector from the whole project so that we can build the
  dissector without building the Pulsar C++ client.
- Refactor the README of the Wireshark dissector by focusing on how to
  use.

### Verifications

Add a workflow to build Wireshark dissector on both Ubuntu and macOS.
BewareMyPower pushed a commit that referenced this pull request Feb 8, 2023
(cherry picked from commit dd649f5)
BewareMyPower added a commit that referenced this pull request Feb 8, 2023
* Support the Wireshark plugin for more Wireshark distributions

### Motivation

#182 fixes the Wireshark
build process on macOS. However, it breaks the compatibility with some
Wireshark distributions like the default Wireshark 3.2.3 on Ubuntu
20.04. The reason is some Wireshark distributions use `config.h` to
record the versions, while other might use `ws_version.h`.

See
https://listman.redhat.com/archives/libvir-list/2020-September/msg00377.html
for a similar fix.

### Modifications

Try to find the `ws_version.h` first, if it's not found, find the
`config.h`. Add the workflow to verify it can be built on Ubuntu.

To be more user friendly:
- Separate the dissector from the whole project so that we can build the
  dissector without building the Pulsar C++ client.
- Refactor the README of the Wireshark dissector by focusing on how to
  use.

### Verifications

Add a workflow to build Wireshark dissector on both Ubuntu and macOS.

(cherry picked from commit 63c4245)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment