mirror of
https://github.com/wangyu-/udp2raw.git
synced 2025-01-19 06:19:31 +08:00
Created Dirty experience in dealing with ISP traffic policies (markdown)
parent
e2d1989eb2
commit
14ed37d3dd
29
Dirty-experience-in-dealing-with-ISP-traffic-policies.md
Normal file
29
Dirty-experience-in-dealing-with-ISP-traffic-policies.md
Normal file
@ -0,0 +1,29 @@
|
||||
## ISP load balancing
|
||||
|
||||
sometimes you might notice:
|
||||
|
||||
1. right after you establish udp2raw connection, the packet loss is high or latency is high
|
||||
2. if you restart udp2raw with some chance it becomes significant better
|
||||
|
||||
|
||||
this is not really udp2raw's fault. This is by ISP's load balancing mechanism, sometimes you are accidently allocated to a bad link.
|
||||
|
||||
#### workaround
|
||||
|
||||
you tried to restart/reconnect udp2raw for a few times, either by kill udp2raw or by the `--fifo` option, until you believe it's good enough.
|
||||
|
||||
|
||||
## ISP punishment for long-term connection
|
||||
|
||||
sometimes you might notice:
|
||||
|
||||
1. right after you establish udp2raw connection, the packet loss and latency is good
|
||||
2. after a day, you came back you see the packet-loss or latency becomes super bad
|
||||
3. if you restart/reconnect udp2raw, it might recover.
|
||||
|
||||
|
||||
#### workaround
|
||||
|
||||
when this happens, you can manually trigger a reconnect with the `--fifo` option.
|
||||
|
||||
It's better you write a script doing this. You monitor the packet loss of udp2raw via some script, if some condition is met your script tell udp2raw to reconnect with `--fifo`
|
Loading…
x
Reference in New Issue
Block a user