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
### 1. **On the Target Server Running MySQL Applications:**
29
29
30
30
Configure the route commands to direct response packets to the assistant server. For example, assuming `10.110.12.18` is the IP address of the assistant server and `10.110.12.15` is the MySQL client IP address, use the following route command to direct all responses from `10.110.12.15` to the assistant server:
@@ -35,12 +35,14 @@ Configure the route commands to direct response packets to the assistant server.
35
35
36
36
`./intercept -F <filter> -i <device>`
37
37
38
-
Note that the filter format is the same as the pcap filter. For example:
38
+
Note that the filter format is the same as the pcap filter. For example:
39
39
40
40
`./intercept -i eth0 -F 'tcp and src port 3306' -d`
41
41
42
-
In this example, `intercept` will capture response packets from a TCP-based application listening on port 3306, using the eth0 network device.
43
-
42
+
In this example, `intercept` will capture response packets from a TCP-based application listening on port 3306, using the eth0 network device.
43
+
44
+
Please note that `ip_forward` is not enabled on the assistant server.
45
+
44
46
### 3. **On the Online Source Server (Root Privilege or CAP_NET_RAW Capability Required):**
45
47
46
48
a) Configure user password pairs in `conf/plugin.conf` within the installation directory.
@@ -63,25 +65,23 @@ For example (assuming 10.110.12.17 is the IP address of the target server):
63
65
64
66
`tcpcopy` captures MySQL packets (assuming MySQL listens on port 3306) on the current server, modifies them as needed, and forwards them to port 3306 on `10.110.12.17` (the target MySQL server). It also connects to `10.110.12.18` to request that `intercept` forwards the response packets to it.
65
67
66
-
67
-
68
68
## Note
69
+
69
70
1. User Accounts and Privileges: Both MySQL instances on the target and online servers must have identical user accounts and privileges, though passwords can differ.
70
71
2. Session Replay: Only complete sessions can be replayed.
71
72
3. OpenSSL Support: OpenSSL 1.1.0+ is not currently supported.
72
73
4. Password Plugin Compatibility: MySQL 8.0’s caching_sha2_password is not supported. To test MySQL 8.0 using MySQL 5.7 production flows, use mysql_native_password and ensure that all users involved in the test are configured with the mysql_native_password plugin.
73
74
5. For additional assistance, visit [tcpcopy](https://github.com/session-replay-tools/tcpcopy).
74
75
75
76
## Release History
77
+
76
78
+ 2017.03 v1.0 mysql-replay-module released
77
79
+ 2024.09 v1.0 Open source fully uses English
78
80
79
81
## Bugs and Feature Requests
80
-
Have a bug or a feature request? [Please open a new issue](https://github.com/session-replay-tools/mysql-replay-module/issues). Before opening any issue, please search for existing issues.
81
82
83
+
Have a bug or a feature request? [Please open a new issue](https://github.com/session-replay-tools/mysql-replay-module/issues). Before opening any issue, please search for existing issues.
0 commit comments