有没有支持双WAN接入的软路由啊！

apeng

我来的晚,听说你病了,现在怎么样了呀

jk0wg

QUOTE (liusimin @ May 2 2005, 02:10 AM)
强烈建议jk0wg写一篇关于centos的教程我已经尝试写脚本做这个可惜脚本总是不能通过又是什么原因呢？
不知道姐姐有QQ吗?? 我的哪个CentOS是朋友帮忙做的..  你告诉我QQ.我叫我朋友跟你探讨.. 他是个LINUX爱好者..   他在CU那里的LINUX版里叫platinum他这几天在忙着实验failover  过几天他回来这个论坛的..

524100jing

没钱买硬的,就来软的了

fntkw

没钱买硬的,就来软的了

ycfei

找了一些策略路由的东西。。希望对大家有用。
touch /var/lock/subsys/local
#!/bin/sh
/sbin/modprobe ip_tables
/sbin/modprobe ip_nat_ftp
/sbin/modprobe ip_conntrack_ftp
/sbin/iptables -F
/sbin/iptables -F -t nat
/sbin/iptables -X
/sbin/iptables -Z

/sbin/iptables -P INPUT ACCEPT
/sbin/iptables -P FORWARD ACCEPT
/sbin/iptables -P OUTPUT ACCEPT

echo "1"> /proc/sys/net/ipv4/ip_forward

#/sbin/iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
#/sbin/iptables -A FORWARD -s 0/0 -d 0/0 -j ACCEPT

#NAT
iptables -A POSTROUTING -t nat -s 192.168.100.0/24 -o eth0 -j SNAT --to-source 61.156.35.114
iptables -A POSTROUTING -t nat -s 192.168.100.0/24 -o eth0 -j SNAT --to-source 61.156.35.114

#default  route
ip route replace default via 192.168.0.1 dev eth1

#default route 100
ip route add 0/0 via 192.168.0.1 dev eth1 table 100
ip route flush cache

#ip rule add pref 10 from 218.6.2.211 table 10
#ip route replace default via 218.6.2.1 dev eth1 table 10
#ip route add 218.6.2.0 dev eth1 src 218.6.2.211
#ip route add 10.0.0.0 dev eth2 src 10.0.0.2

#Add the route rules for the  CNC addresses
ip rule add to 60.0.0.0/13 table 100
ip rule add to 60.8.0.0/15 table 100
ip rule add to 60.10.0.0/16 table 100
ip rule add to 60.12.0.0/16 table 100
ip rule add to 60.13.0.0/18 table 100
ip rule add to 60.13.128.0/17 table 100
ip rule add to 60.16.0.0/12 table 100
ip rule add to 60.208.0.0/13 table 100
ip rule add to 60.216.0.0/15 table 100
ip rule add to 60.220.0.0/14 table 100
ip rule add to 61.48.0.0/13 table 100
ip rule add to 61.133.0.0/17 table 100
ip rule add to 61.135.0.0/16 table 100
ip rule add to 61.136.64.0/18 table 100
ip rule add to 61.137.128.0/17 table 100
ip rule add to 61.138.0.0/17 table 100
ip rule add to 61.138.128.0/18 table 100
ip rule add to 61.139.128.0/18 table 100
ip rule add to 61.148.0.0/15 table 100
ip rule add to 61.156.0.0/16 table 100
ip rule add to 61.158.128.0/17 table 100
ip rule add to 61.159.0.0/18 table 100
ip rule add to 61.161.0.0/18 table 100
ip rule add to 61.161.128.0/17 table 100
ip rule add to 61.167.0.0/16 table 100
ip rule add to 61.168.0.0/16 table 100
ip rule add to 61.176.0.0/16 table 100
ip rule add to 61.179.0.0/16 table 100
ip rule add to 61.180.128.0/17 table 100
ip rule add to 61.181.0.0/16 table 100
ip rule add to 61.182.0.0/16 table 100
ip rule add to 61.189.0.0/17 table 100
ip rule add to 202.96.0.0/18 table 100
ip rule add to 202.96.64.0/19 table 100
ip rule add to 202.97.128.0/17 table 100
ip rule add to 202.98.0.0/19 table 100
ip rule add to 202.99.0.0/16 table 100
ip rule add to 202.102.128.0/18 table 100
ip rule add to 202.102.224.0/19 table 100
ip rule add to 202.106.0.0/16 table 100
ip rule add to 202.107.0.0/17 table 100
ip rule add to 202.108.0.0/16 table 100
ip rule add to 202.110.0.0/17 table 100
ip rule add to 202.110.192.0/18 table 100
ip rule add to 202.111.128.0/18 table 100
ip rule add to 218.7.0.0/16 table 100
ip rule add to 218.8.0.0/14 table 100
ip rule add to 218.12.0.0/16 table 100
ip rule add to 218.24.0.0/14 table 100
ip rule add to 218.28.0.0/15 table 100
ip rule add to 218.56.0.0/14 table 100
ip rule add to 218.60.0.0/15 table 100
ip rule add to 218.67.128.0/17 table 100
ip rule add to 218.68.0.0/15 table 100
ip rule add to 221.0.0.0/14 table 100
ip rule add to 221.4.0.0/15 table 100
ip rule add to 221.6.0.0/16 table 100
ip rule add to 221.7.0.0/18 table 100
ip rule add to 221.7.64.0/19 table 100
ip rule add to 221.7.128.0/17 table 100
ip rule add to 221.8.0.0/15 table 100
ip rule add to 221.10.0.0/16 table 100
ip rule add to 221.11.128.0/18 table 100
ip rule add to 221.11.0.0/17 table 100
ip rule add to 221.11.192.0/19 table 100
ip rule add to 221.12.0.0/17 table 100
ip rule add to 221.12.128.0/18 table 100
ip rule add to 221.13.0.0/18 table 100
ip rule add to 221.13.64.0/19 table 100
ip rule add to 221.13.128.0/17 table 100
ip rule add to 221.14.0.0/15 table 100
ip rule add to 221.192.0.0/14 table 100
ip rule add to 221.196.0.0/15 table 100
ip rule add to 221.198.0.0/16 table 100
ip rule add to 221.199.0.0/19 table 100
ip rule add to 221.199.32.0/20 table 100
ip rule add to 221.199.128.0/18 table 100
ip rule add to 221.199.192.0/20 table 100
ip rule add to 221.200.0.0/14 table 100
ip rule add to 221.204.0.0/15 table 100
ip rule add to 221.207.0.0/18 table 100
ip rule add to 221.208.0.0/14 table 100
ip rule add to 221.212.0.0/15 table 100
ip rule add to 221.216.0.0/13 table 100
ip rule add to 222.128.0.0/12 table 100
ip rule add to 222.160.0.0/15 table 100
ip rule add to 222.162.0.0/16 table 100
ip rule add to 222.163.0.0/19 table 100

yftg

这样做游戏肯定会掉线的，这种是通过流量来判断使用哪条线路，当一个游戏玩家在一条线上的时候，带宽不够，或者此条线路的会话数达到一定程度后，下一个会话连接就会跑到另外一条线路上，这样掉线肯定是必然的了，想不掉线有一个办法，让电信那边帮你把两个ip调试成双路返回路有就可以了~acl表里面写一些基于ip地址优先会话选择ip的规格就可以了~或者直接在ros里面写，但双路返回路有必须要电信那边帮你做~

张浩峰

不知道楼上的“双路返回路”是指什么意思？

limeng23

对了老大的病已经恩 久 到底好了没有呀 大家好想你的
既然ros可以用策略 linux也可以用策略 那这个所谓的cenos应该也可以吧

basmplmki

CentOS是什么东东哦?

好用么?哪里有介绍?

swei

可以限制IP的下载速度吗？