github/wangyu-udp2raw
1
0
Fork 0
mirror of https://github.com/wangyu-/udp2raw.git synced 2025-02-01 12:49:35 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated rst==1 (markdown)

wangyu- 2018-02-25 09:55:30 +08:00
parent 3aa9ffefe4
commit 33890881c3
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
rst==1.md

@ -1,17 +1,17 @@
You may get rst==1 in the following scenes:
##### 1. You didnt run udp2raw with `-a` option, nor did you add the iptables rule needed by udp2raw manually. Then you may get rst==1 from either of the sides.
#### 1. You didnt run udp2raw with `-a` option, nor did you add the iptables rule needed by udp2raw manually. Then you may get rst==1 from either of the sides.
In this case, you have to run udp2raw with `-a` option, or add iptables-rules manually(maybe with the help of `-g` option)
##### 2. You killed udp2raw client after a connection has already established to server. Then you may get rst==1 from server log.
#### 2. You killed udp2raw client after a connection has already established to server. Then you may get rst==1 from server log.
In this case, its as expected, you can ignore it.
##### 3. You killed udp2raw server while udp2raw client is running. Or you are using udp2raw to connect to an non-existed server. Then you may get rst==1 from client log.
#### 3. You killed udp2raw server while udp2raw client is running. Or you are using udp2raw to connect to an non-existed server. Then you may get rst==1 from client log.
Start/re-start your server. And ignore the previous rst==1 logs.
##### 4. Not covered by the above scenes, but you still got rst==1
#### 4. Not covered by the above scenes, but you still got rst==1
Maybe the NAT middle-box or firewalls is trying to obstruct your connection. You can post a Issue for help.