|-转 v2rayN已停止工作
v2rayN停止工作，要安装.NET Framework 4.6 或者更高版本
v2rayN
Requirements
Microsoft.NET Framework 4.6or higher ...
|-转 CentOS7下解决ifconfig command not found的办法
在安装锐速遇到的问题，ifconfig命令不存在，要安装net-tool插件
注：本办法仅限于可联网的机器，即在安装时设置了IP地址和DNS可正常上网。
解决办法如下：
1、输入ip addr 确认IP地址是否设置正常，设置好如下所示，如果没有获取到IP地址则设置一个即可。
2、确认sbin目录是否存在。
cd /sbin
3、确认ifconfig命令是否未安装
在sbin目录下输入ls，可见下图所示，并没有ifconfig。
4、安装net-tool插件，此插件中带有此命令...
|-转 CentOS 7安装锐速高速上网
原文链接：https://www.dazhuanlan.com/2019/09/25/5d8adf0a3aa16/
发表于 2019-09-25
锐速serverspeeder是一款TCP网络加速软件，能在Linux系统和Windows系统的服务器中安装，安装后能启到提高网络连接稳定性、带宽利用率、低访问失败率等作用，从而提高服务器网络访问速度。锐速并非实际增大服务器带宽，只是提高网络的稳定性和利用率而已。
安装之前
锐速破解版linux一键自动安装包是由@91yun发布的，无限带宽版。锐速只支持在XEN和KVM虚拟技术价格的VPS中安装，不支持在OpenVZ虚拟技术架构的VPS安装，推荐在KVM VPS中安装。目前此一键安装包已支持在CentOS，ubuntu和debian系统中安装，而且能自动匹配服务器内核是否支持安装，如果支持就会全自动下载安装，无需任何操作；如果内核不支持，则必须更换合适的VPS内核才能完成安装。
内核支持
CentOS-6.8：2.6.32-642.el7.x86_64
CentOS-7.2：3.10.0-327.el7.x86_64
CentOS：4.4.0-x86_64-linode63
Ubuntu_14.04：4.2.0-35-generic
Debian_8：3.16.0-4-amd64
安装脚本 ...
|-原 切换使用锐速和BBR加速时遇到的问题failed to dial to (wss:// *** ) 502 Bad Gateway
failed to dial to (wss://ss.chawen.org:446/37cf03a1/) 502 Bad Gateway ...
|-转 服务器加速的解决方案
当前脚本已发布新版本，地址:
https://github.com/kuoruan/shell-scripts/raw/master/kcptun/kcptun.sh
旧仓库已废弃，以后所有的脚本都会发布到新仓库:
https://github.com/kuoruan/shell-scripts
https://github.com/kuoruan/shell-scripts/raw/master/kcptun/kcptun.sh
原文链接：https://tech.itabas.com/2016/09/06/vps/ss-speeder/
发布于 2016-09-06
根据vps的特点选择适合自己的加速方案，Openvz和Kvm以及Xen (如何检测Vps架构↓↓↓) 不同架构处理方式也是不同。
#91yun check script
wget -N --no-check-certificate https://raw.githubusercontent.com/91yun/code/master/vm_check.sh && bash vm_check.sh
net-speeder
在高延迟不稳定链路上优化单线程下载速度
开启了net-speeder的服务器上对外ping时看到的是4倍，实际网络上是2倍流量。另外两倍是内部dup出来的，不占用带宽。 另外，内部dup包并非是偷懒未判断。。。是为了更快触发快速重传的。
net-speeder不依赖ttl的大小，ttl的大小跟流量无比例关系。不存在windows的ttl大，发包就多的情况。
Installation
一键安装script
ubuntu/debian
shell wget --no-check-certificate https://raw.githubusercontent.com/tennfy/debian_netspeeder_tennfy/master/debian_netspeeder_tennfy.sh chmod a+x debian_netspeeder_tennfy.sh bash debian_netspeeder_tennfy.sh
centos
wget --no-check-certificate https://gist.github.com/LazyZhu/dc3f2f84c336a08fd6a5/rawd8aa4bcf955409e28a262ccf52921a65fe49da99/net_speeder_lazyinstall.sh sh net_speeder_lazyinstall.sh
source code make and make install
net-speed opensource
How to use
cp ./net_speeder /usr/bin
#comments:
parameter: net_speeder netdisk rule (bpf)
net_speeder venet0 "ip"
/usr/bin/net_speeder venet0 "ip"
# add netspeed to
echo 'nohup /usr/bin/net_speeder venet0 "ip" >/dev/null 2>&1 &' >> /etc/rc.local
kcptun
Kcptun是一个非常简单和快速的，基于 KCP 协议的 UDP 隧道，它可以将 TCP 流转换为 KCP+UDP 流。而 KCP 是一个快速可靠协议，能以比 TCP 浪费10%-20%的带宽的代价，换取平均延迟降低 30%-40%，且最大延迟降低三倍的传输效果。 ...
|-转 使用V2Ray的mKCP协议加速游戏
当前脚本已发布新版本，地址:
https://github.com/kuoruan/shell-scripts/raw/master/kcptun/kcptun.sh
旧仓库已废弃，以后所有的脚本都会发布到新仓库:
https://github.com/kuoruan/shell-scripts
https://github.com/kuoruan/shell-scripts/raw/master/kcptun/kcptun.sh
测试了，此方法无法上网。
V2ray报错：
[Warning] failed to handler mux client connection > v2ray.com/core/proxy/vmess/outbound: connection ends > v2ray.com/core/proxy/vmess/outbound: failed to read header > v2ray.com/core/proxy/vmess/encoding: failed to read response header > EOF
2019-11-14
用v2ray内置的mKCP加速游戏的话，配置要简单很多，但效果没有kcptun+udp2raw好。也算是一种可行的方法吧，想偷懒的话可以试试这个方法。。
安装v2ray：
apt -y update apt -y install curl bash <(curl -L -s https://install.direct/go.sh)
生成一个uuid复制下来：
cat /proc/sys/kernel/random/uuid
编辑v2ray配置文件：
nano /etc/v2ray/config.json
写入如下配置：
{ "inbounds": [ { "port": 50000, "protocol": "vmess", "settings": { "clients": [ { "id": "你的UUID", "alterId": 64 } ] }, "streamSettings": { "network":"kcp", "kcpSettings": { "mtu": 1350, "tti": 20, "uplinkCapacity": 30, "downlinkCapacity": 100, "congestion": true, "header": { "type": "utp" } } } } ], "outbounds": [ { "protocol": "freedom", "settings": {} } ] }
关于这个mKCP里面涉及到的一些可配置参数，可以参考这里：...
|-转 Quick and easy VPNs with WireGuard
If a message like the following is shown in this step:
Warning: `/etc/wireguard/wg0.conf' is world accessible
This means that the configuration file permissions are too broad - and they shouldn’t, as there’s a private key in there. This can be fixed withsudo chmod 600 /etc/wireguard/wg0.conf.
Sep 15, 2018 • Tiago Ilieve
WireGuard is the new kid on the block in the world of VPNs. It has been receiving a lot of attention lately, especially afterLinus Torvalds himself praised the projectlast month, resulting inin-depth guides about its characteristicsbeing published. The problem is thatpractical guides about its setup, including theofficial one, doesn’t show how quick and easy it is to do that. They are full of lengthy, complex and unneeded commands, when everything that is needed are simple configuration files.
This guide won’t describe how to actually install WireGuard, as this isthoroughly covered by the official documentationfor every supported platform. It consists of aloadable kernel modulethat allows virtual WireGuard network interfaces to be created. In here, an EC2 instance located in Ireland and a virtual machine (based on Vagrant/VirtualBox) in Germany, both running Ubuntu, will be connected.
The first step is to generate a pair of keys for every machine. WireGuard authentication system doesn’t rely passwords or certificates that includes hard-to-maintain Certification Authorities (CAs). Everything is done using private/public keys, like SSH authentication:
$ wg genkey | tee privatekey | wg pubkey > publickey $ ls -lh total 8.0K -rw-rw-r-- 1 ubuntu ubuntu 45 Sep 15 14:31 privatekey -rw-rw-r-- 1 ubuntu ubuntu 45 Sep 15 14:31 publickey
In the server, the/etc/wireguard/wg0.confconfiguration file will look like:
[Interface] PrivateKey = 4MtNd3vq/Zb5tc8VgoigLyuONWoCQmnzLKFNuSYLiFY= Address = 192.168.255.1/24 ListenPort = 51820 PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE; sysctl net.ipv4.ip_forward=1 PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE; sysctl net.ipv4.ip_forward=0 [Peer] PublicKey = 0+/w1i901TEFRmEcUECqWab/nwmq0dZLehMzSOKUo04= AllowedIPs = 192.168.255.2/32
Here’s an explanation of its fields:
- PrivateKeyis the server private key. It proves that the server is who it says it is, and the same will be valid for the clients on the other end. One will be able to validate the identity of the other.
- Addressis the IP and network mask for the VPN network.
- ListenPorttells in which UDP port the server will listen for connections.
- PostUpare firewall rules and system commands that are needed for the server to act as a gateway, forwarding all network traffic.PostDownwill disable them when the VPN is deactivated.eth0is the name of the main network interface, which can be something different likeens5ifsystemd’s Predictable Network Interface Namesare being used.
- PublicKeyandAllowedIPsdefines which peers can connect to this server through a combination of IPs/key pairs. It’s important to notice that the IPs defined here are within the VPN network range. Those are not the actual IPs which the client will use to connect to the server over the internet.
The client will also have a/etc/wireguard/wg0.confconfiguration file, but it will be a little bit different:
[Interface] PrivateKey = yDZjYQwYdsgDmySbUcR0X7b+rdwfZ91rFYxz6m/NT08= Address = 192.168.255.2/24 [Peer] PublicKey = e1HJ0ed/lUmCDRUGjCwFZ9Qm2Lt14jNE77TKXyIS1yk= AllowedIPs = 0.0.0.0/0 Endpoint = ec2-34-253-52-138.eu-west-1.compute.amazonaws.com:51820
ThePrivateKeyandAddressfields here have the same meaning as in the server. The difference is that theInterfacesection won’t contain the server parts, like the listening ports and firewall commands. ThePeersection contains the following fields:...
