Soft routing short IP: soft routing configuration using short IP proxy method

What exactly is the point of soft routing with short-lived IPs?

Friends who have played the network toss should understand that some special business requirements for IP replacement frequency is particularly high. For example, when doing data collection, the target site is always blocked IP, this time we have to rely on theshort-lived proxy IPto renew. Soft routing is more flexible than hardware routing and can install various plug-ins on its own, which is especially suitable for scenarios that require frequent IP switching.

Here we should focus on ipipgo's dynamic residential package, their IP survival time is adjustable from 5 minutes to 1 hour. For example, if you want to do a certain treasure commodity comparison, with soft routing automatically change IP, not only will not trigger the platform's wind control, but also to ensure that the data capture is not interrupted.

Hands-on environment installation

First, let's get clear on the guy things that need to be prepared:
- Any x86 device or virtual machine (old computers are fine)
- OpenWrt system (LEDE conversion recommended)
- ipipgo account (we recommend gripping a trial pack first)

 Install the necessary components
opkg update
opkg install luci-app-ssr-plus
opkg install curl jq to handle API returns with

Two-step key configuration

Step 1: Setting up automatic proxy IP acquisition
Go to the ipipgo backend to generate the API key, it is recommended to choose the Dynamic Residential (Standard) package, which is cost-effective. Their API return format looks like this:

{
  "proxy": "socks5://123.123.123.123.123:8888",
  "expire": 300 in seconds
}

Step 2: Switching Scripts Regularly
Create a new script in the soft route and remember to give execute permission:

! /bin/sh
API_KEY="your key"
RESP=$(curl -s "https://api.ipipgo.com/get?key=$API_KEY")
IP=$(echo $RESP | jq -r '.proxy')
sed -i "s/old IP address and port/$IP/g" /etc/config/ssr-plus
/etc/init.d/ssr-plus restart

It's safest to run this script every 4 minutes with a crontab setting that is 1 minute ahead of the IP expiration time.

Common Rollover Scene Rescue

Q：IP change and suddenly can't connect?
A: First check if the API return is normal, sometimes jq parsing will be jerky. It is recommended to add a retry mechanism in the script, 3 consecutive failures and then send an alert.

Q: Traffic running faster than expected?
A: 80% is not set the protocol type, ipipgo socks5 protocol default global traffic. If you do data collection, we suggest you add -socks5-hostname parameter in the script, which can save a lot of traffic.

There is a way to choose a package

Personally tested dynamic package, ipipgo's UK and Germany nodes have the highest success rate. They have a hidden trick: add the country=DE parameter to the API request to specify the German IP, which is not written in the official website documentation.

Guide to avoiding the pit

Don't jump over and over again in the same IP segment! Some websites will detect IP changes in the C segment. ipipgo's background can set the IP geographic distribution policy, we recommend turning on the "Uniform Distribution" switch to allow the system to automatically distribute IPs in different regions.

If you want to do high concurrency, remember to increase the ulimit value in the soft route. I've encountered the problem of proxy failure due to insufficient file descriptors, and it was as stable as an old dog after I increased the ulimit.

Finally, to tell the truth, the self-built proxy pool is really better than directly using the ready-made services. ipipgo supports hourly billing, temporary demand for a TK line, used up on the shutdown, more than those who want to pay for a year of conscience.