You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[](https://gitter.im/EIPStackGroupOpENer/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
3
-
4
-
5
1
OpENer Version 2.3.0
6
2
====================
7
3
8
4
Welcome to OpENer!
9
5
------------------
10
6
11
-
OpENer is an EtherNet/IP™ stack for I/O adapter devices; supports multiple
7
+
OpENer is an EtherNet/IP™ stack for I/O adapter devices; supports multiple
12
8
I/O and explicit connections; includes objects and services to make EtherNet/IP™-
13
-
compliant products defined in THE ETHERNET/IP SPECIFICATION and published by
9
+
compliant products defined in THE ETHERNET/IP SPECIFICATION and published by
OpENer has been developed to be highly portable. The default version targets PCs
27
-
with a POSIX operating system and a BSD-socket network interface. To test this
28
-
version we recommend a Linux PC or Windows with Cygwin (http://www.cygwin.com)
23
+
with a POSIX operating system and a BSD-socket network interface. To test this
24
+
version we recommend a Linux PC or Windows with Cygwin (http://www.cygwin.com)
29
25
installed. You will need to have the following installed:
30
26
31
27
* CMake
32
28
* gcc
33
29
* make
34
30
* binutils
35
31
* the development library of libcap (libcap-dev or equivalient)
36
-
32
+
37
33
for normal building. These should be installed on most Linux installations and
38
34
are part of the development packages of Cygwin.
39
35
40
36
If you want to run the unit tests you will also have to download CppUTest via
41
37
https://github.com/cpputest/cpputest
42
38
43
-
For configuring the project we recommend the use of a CMake GUI (e.g., the
39
+
For configuring the project we recommend the use of a CMake GUI (e.g., the
44
40
cmake-gui package on Linux, or the Installer for Windows available at [CMake](https://cmake.org/))
45
41
46
42
Compile for Linux/POSIX:
@@ -78,7 +74,7 @@ Compile for Windows XP/7/8 via Visual Studio:
78
74
e.g. ``OpENer 3``
79
75
80
76
In order to get the correct interface index enter the command ``route print`` in a command promt and search for the MAC address of your chosen network interface at the beginning of the output. The leftmost number is the corresponding interface index.
81
-
77
+
82
78
Compile for Windows XP/7/8/10 via Cygwin:
83
79
--------------------------------------
84
80
The POSIX setup file can be reused for Cygwin. Please note, that you cannot use RT mode and you will have to remove the code responsible for checking and getting the needed capabilities, as libcap is not available in Cygwin. The easier and more supported way to build OpENer for Windows is to either use MinGW or Visual Studio.
@@ -88,15 +84,15 @@ Compile for MinGW on Windows XP/7/8/10
88
84
1. Make sure 64 bit mingw is installed. (Test with gcc --version, should show x86_64-posix-seh-rev1)
89
85
2. Make sure CMake is installed. (Test with cmake --version, should be version 3.xx)
90
86
3. Change to <openerinstalldir>/bin/mingw
91
-
4. Run the command `setup_mingw.bat` in a dos command line. (Not a bash shell). If tracing is desired,
87
+
4. Run the command `setup_mingw.bat` in a dos command line. (Not a bash shell). If tracing is desired,
92
88
use the following (where the cmake parameter must be enclosed in quotes) or change the ./source/CMakeList.txt file.
93
89
```
94
90
setup_mingw.bat "-DOpENer_TRACES:BOOL=TRUE"
95
91
```
96
92
5. Run the command "make" from the same directory (./bin/mingw)
97
93
6. The opener.exe is now found in <openerinstalldir>\bin\mingw\src\ports\MINGW
98
94
7. Start it like this: "opener 192.168.250.22", where the ip address is the local computer's address on the nettwork you want to use.
99
-
95
+
100
96
Directory structure:
101
97
--------------------
102
98
- bin ... The resulting binaries and make files for different ports
@@ -115,18 +111,18 @@ Directory structure:
115
111
116
112
Documentation:
117
113
--------------
118
-
The documentation of the functions of OpENer is part of the source code. The source
119
-
packages contain the generated documentation in the directory doc/api_doc. If you
120
-
use the GIT version you will need the program Doxygen for generating the HTML
121
-
documentation. You can generate the documentation by invoking doxygen from the
114
+
The documentation of the functions of OpENer is part of the source code. The source
115
+
packages contain the generated documentation in the directory doc/api_doc. If you
116
+
use the GIT version you will need the program Doxygen for generating the HTML
117
+
documentation. You can generate the documentation by invoking doxygen from the
122
118
command line in the opener main directory.
123
119
124
120
125
121
Fuzzing
126
122
--------------
127
123
### Intro
128
-
Fuzzing is an automated testing method that directs varying input data to a program in
129
-
order to monitor output. It is a way to test for overall reliability as well as identify
124
+
Fuzzing is an automated testing method that directs varying input data to a program in
125
+
order to monitor output. It is a way to test for overall reliability as well as identify
130
126
potential security bugs.
131
127
132
128
The fuzzer we are using is AFL, a fuzzer that uses runtime guided techniques to create input for the tested program. From a high-level prespective AFL works as follows:
0 commit comments