larsvoelker / fibexconverter

Convert SOME/IP config in FIBEX 4 to different configuration formats (e.g. Wireshark).

FibexConverter

Convert SOME/IP config in FIBEX 4 to different configuration formats (e.g. Wireshark).

Convert a FIBEX4 file to text:

Just call it like this:

python3 configuration_to_text.py FIBEX example-file.xml

The result will be:

example-file/text/example-file.txt

Convert a FIBEX4 file to wireshark configs:

Just call it like this:

python3 configuration_to_wireshark_config.py FIBEX example-file.xml

The results (hosts, vlanids, SOMEIP...) will be in:

example-file/wireshark/

Copy the result files to your wireshark configuration directory (e.g. ~/.config/wireshark for MacOS X or %appdata%\Wireshark for Windows).

Important:

• SOME/IP support was added to Wireshark 3.2, you need a custom plugin before.
• Wireshark loads the config on start. So you better stop Wireshark while copying the configs in.

Convert a FIBEX4 file to CSV reports:

Just call it like this:

python3 configuration_to_reports.py FIBEX example-file.xml

The result will be:

example-file/reports/

fibexconverter's Issues

TypeError: 'NoneType' object is not subscriptable

Hi,
I tried to convert the example Some/IP FIBEX configuration file from vector to wireshark config using the Fibex Converter tool.
I got the below error

TypeError: 'NoneType' object is not subscriptable

Is it a problem with my FIBEX file ? I can't able to clearly see where is the error . The same file is working fine in the CANoe simulation.

Please have a look at the attached error log file for more information
error.txt

I have also attached my FIBEX file too. I attached it as text file, you can change the extension to xml if you want to try it
FBX4_VECTOR_SOME_IP_MM.txt

dependency `isodate` really needed?

I was wondering whether non-standard library dependency isodate is really needed by running

python3 configuration_to_text.py FIBEX example-file.xml

and

python3 configuration_to_wireshark_config.py FIBEX example-file.xml

for one example fibex file with the following patch:

diff --git a/abstract_parser.py b/abstract_parser.py
index 73a2d93..82bd564 100644
--- a/abstract_parser.py
+++ b/abstract_parser.py
@@ -19,7 +19,7 @@
 # along with this program; if not, write to the Free Software
 # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
 
-import isodate
+#import isodate
 
 
 class AbstractParser(object):
@@ -99,4 +99,4 @@ class AbstractParser(object):
         s = self.get_child_text(element, childtag)
         if s is None:
             return -1
-        return (isodate.parse_duration(s)).total_seconds()
+        raise NotImplementedError

and it worked without issues.

So the question is whether we can get rid of this dependency?

module name `parser` clashes with Python standard lib module

According to https://docs.python.org/3.8/library/parser.html#module-parser module name parser i.e. parser.py is already taken by Python standard lib.

Because of that statements like

https://github.com/LarsVoelker/FibexConverter/blob/34d51b0/configuration_to_wireshark_config.py#L26

might result in unexpected outcome.
As you use from parser import * problem is not immediately recognized at import statement , but later on Python interpreter might complain about e.g. name 'parse_input_files' is not defined, because it actually used another file for this module.

See also https://chrisyeh96.github.io/2017/08/08/definitive-guide-python-imports.html#basics-of-the-python-import-and-syspath for details in which order imports are resolved.

[suggestion] Add a requirements.txt file

It would be nice to have a requirements.txt file with the python libraries used.

Thank you

Would it be possible to create github releases?

I'd like to use your tool (btw. kudos for that!) in order to generate wireshark configs in order to decode SOME/IP payload.

However, in order to use it in our build system it would be easier to reference a release of your repo (i.e. a tarball with all the sources of this release/tag) instead of a specific commit. See docs for details.

Would it be possible to create releases in this repo? For now it would be sufficient to do that once.

FIBEX4 Example File for SOME/IP

Hello,
it would be great if you could add a FIBEX 4 example File for creating a Wireshark Config File. I need it for your Wireshark 3.2 SOME/IP plugin. Or just a general guide how to set up payload dissection with the new SOME/IP plugin.