Linux双网卡静态IP地址配置过程
• 静态IP地址配置过程说明
– 第一个网卡在安装时已经配置成静态IP地址 – 第二增加的网卡也配置成静态IP地址
• 配置过程示意图见以下Байду номын сангаасPPT中的图片
– 以RHEL AS5.32为例
进入VMware参数设置
设置VMware内存
• 内存设置
– 物理机内 存的一半
设置VMware内核数量
双网卡静态IP配置
• 重新启动网卡
双网卡静态IP配置
• 查询配置结果
双网卡静态IP配置
• 测试配置结果
• CPU数量
– 物理CPU 的核心数
准备添加网卡
添加物理网卡的连接类型—桥接
物理网卡添加成功
双网卡静态IP配置
• 启动setup命令，并在下图中选择网络配置
双网卡静态IP配置
• 选择网卡
– 光标带所在位置就为选择的网卡
双网卡静态IP配置
• 配置静态IP地址
– 用空格把Use DHCP行中的符号“*”去掉才能 配置静态IP
windows XP及Linux下双网卡配置方案
Windows XP下双网卡配置方案一、软硬件需求●硬件：一台带有双网卡的PC，其中一个连接internet；另一个接局域网hub。
其中节局域网地址为：192.168.0.1/255.255.255.0●软件：操作系统：windows XP代理软件：CCProxy二、设置CCProxy：1、服务器的安装运行下载后的Ccproxysetup.exe 安装本软件（注：现在的最新版本为CCProxy-v6.6，推荐下载网站：霏凡）安装完成后，桌面有一个CCProxy的绿色图标：双击即可启动CCProxy了（如附图）。
绿色的网格坐标将会出现，黄色的曲线表示网络数据流量。
2、客户端设置前的准备工作1)确认客户端与服务器是连通的，能够互相访问。
2)确定代理服务器地址。
代理服务器地址就是安装代理服务器的机器的网络地址。
这个地址，是指服务器在局域网中的本地IP地址。
本地IP地址可以从CCProxy的设置对话框中得到。
设置对话框中的本地IP地址一般情况下可以用"自动检测"得到。
如果服务器安装了双网卡，则需要手工选取：取消"自动检测"，从列表中选取。
如果不能确认服务器的IP地址，也可以用服务器的机器名作为代理服务器地址。
3、局域网机器设置：※对TCP/IP协议的属性进行设置：方法：右击“网上邻居”，选择“属性”，双击网卡对应的“TCP/IP协议”，选择“DNS”标签。
设置如下：选中“启用DNS”；“主机”中填入服务器名称；并在下面的“DNS服务器搜索顺序”中填入服务器的IP地址，本例为“192.168.0.1”，然后单击[填加]；单击[确定]结束DNS设置；再次单击[确定]，结束对网络属性的设置。
这时需要重新启动计算机。
※重新启动后，设置IE浏览器代理上网1）流程：IE浏览器->菜单"工具"->"Internet选项"->"连接"->"局域网设置"->选中"使用代理服务器"->"高级"->"代理服务器设置"。
linux下双网卡绑定并设置双IP
linux下双网卡绑定并设置双IP环境：双网卡服务器RHEL AS5.4目的：双网卡绑定并设置双IP配置：分为2部分：一、双网卡绑定；二、给绑定后的网卡设置双IP一、双网卡绑定1，新建个ifcfg－bond0 （cp /etc/sysconfig/network-scripts/ifcfg-eth0/etc/sysconfig/network-script/ifcfg-bond0）2,修改ifcfg－bond0文件，去掉mac地址相关信息（HW ADDR）,给个ip地址，网络地址，广播地址如下：# cat ifcfg-bond0DEVICE= bond0BOOTPROTO=staticIPADDR=192.168.80.189 //*第一个IP地址*//NETMASK=255.255.255.0 //*网络掩码*//ONBOOT=yes:wq //*保存退出*//3，修改ifcfg－eth0和ifcfg-eth1,如下：cat ifcfg-eth0cat ifcfg-eth14,修改/etc/modprobe.conf,添加如下语句：alias bond0 bondingoptions bond0 miimon=100 mode=1注释：mode可以为0，1，0为负载均衡，1为失效保护如下图：5，修改/etc/rc.d/rc.local,添加如下内容：ifenslave bond0 eth0 eth1route add -net 192.168.1.255 netmask 255.255.255.0 bond0如下图：6，重启,看能否通过ssh登陆上服务器bond0得ip(192.168.1.136),如果成功登陆或者ping通了，再查看一下连接状态ifconfig,如下图:ifconfig查看连接状态7,尝试拔掉一根网线看是否能正常登陆上去(或ping得通)，再查看一下更连接状态（cat /proc/net/bonding/bond0）如下图：8，尝试一下更换一下mode的值，再试一下。
linux双网卡双IP双网关如何配置
# Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
HOTPLUG=no
HOTPLUG=no
TYPE=Ethernet
IPADDR=192.168.1.2
NETMASK=255.255.255.0
HWADDR=d8:d3:85:fb:d4:60
GATEWAY=192.168.1.1
USERCTL=no
IPV6INIT=no
PEERDNS=yes
eth1 的配置如下，不需要配置网关
TYPE=Ethernet
IPADDR=192.168.2.2
NETMASK=255.255.255.0
USERCTL=no
IPV6INIT=no
PEERDNS=yes
Linux 命令行下添加路由，192.168.3.0 走 eth1 的网关 192.168.2.1
route add -net 192.168.3.0 netmask 255.255.255.0 dev eth1
linux双网卡双ip双网关如何配置 注意: 2张网卡,只能有1张网卡配置网关,另1张网卡不能配置网关,通过route add添加路由功能来完成第2张网卡的网关配置. 如 : eth1 (192.168.2.2)不需要配置网关,但到 192.168.3.0的网段,需要从eth1去实现通信,其余的全部走eth0网卡,eth0配置网关. eth0的配置如下,配置网关参数 [root@redhat network-scripts]# cat ifcfg-eth0 # broadcom corporation netxtreme ii bcm5709 gigabit ethernet device=eth0 bootproto=none onboot=yes hotplug=no type=ethernet ipaddr=192.168.1.2 netmask=255.255.255.0 hwaddr=d8:d3:85:fb:d4:60 gateway=192.168.1.1 userctl=no ipv6init=no peerdns=yes eth1的配置如下,不需要配置网关 [root@server network-scripts]# cat ifcfg-eth1 # broadcom corporation netxtreme ii bcm5709 gigabit ethernet device=eth1 bootproto=none onboot=yes hotplug=no type=ethernet ipaddr=192.168.2.2 netmask=255.255.255.0 userctl=no ipv6init=no peerdns=yes linux命令行下添加路由,192.168.3.0走 eth1的网关 192.168.2.1 route add -net 192.168.3.0 netmask 255.255.255.0 dev eth1 下载文档原格式( txt原格式 ,共1页)
linux双网卡绑定
一、L inux bonding研究及实现Linux Bonding本文介绍Linux（具体发行版本是CentOS5.6）下的双卡绑定的原理及实现。
Linux双网卡绑定实现是使用两块网卡虚拟成为一块网卡设备，这简单来说，就是两块网卡具有相同的IP地址而并行链接聚合成一个逻辑链路工作。
这项技术在Sun和Cisco中分别被称为Trunking和Etherchannel技术，在Linux的2.4.x及其以后的内核则称为Bonding技术。
bonding的前提条件：网卡应该具备自己独立的BIOS芯片，并且各网卡芯片组型号相同。
同一台服务器上的网卡毫无疑问是是符合这个条件的。
Bonding原理bonding的原理：在正常情况下，网卡只接收目的硬件地址(MAC Address)是自身MAC的以太网帧，过滤别的数据帧，以减轻驱动程序的负担；但是网卡也支持另外一种被称为混杂promisc的模式，可以接收网络上所有的帧，bonding就运行在这种模式下，而且修改了驱动程序中的mac地址，将两块网卡的MAC地址改成相同，可以接收特定MAC的数据帧。
然后把相应的数据帧传送给bond驱动程序处理。
为方便理解bonding的配置及实现，顺便阐述一下Linux的网络接口及其配置文件。
在Linux 中，所有的网络通讯都发生在软件接口与物理网络设备之间。
与网络接口配置相关的文件，以及控制网络接口状态的脚本文件，全都位于/etc/sysconfig/netwrok-scripts/ 目录下。
网络接口配置文件用于控制系统中的软件网络接口，并通过这些接口实现对网络设备的控制。
当系统启动时，系统通过这些接口配置文件决定启动哪些接口，以及如何对这些接口进行配置。
接口配置文件的名称通常类似于ifcfg-<name>，其中<name> 与配置文件所控制的设备的名称相关。
在所有的网络接口中，最常用的就是以太网接口ifcfg-eth0，它是系统中第一块网卡的配置文件。
Linux系统配置双网卡绑定bond0
Linux系统配置双⽹卡绑定bond01、bonding简述双⽹卡配置设置虚拟为⼀个⽹卡实现⽹卡的冗余，其中⼀个⽹卡坏掉后⽹络通信仍可正常使⽤，实现⽹卡层⾯的负载均衡和⾼可⽤性。
现在⼀般的企业都会使⽤双⽹卡接⼊，这样既能添加⽹络带宽，同时⼜能做相应的冗余，可以说是好处多多。
⽽⼀般企业都会使⽤linux操作系统下⾃带的⽹卡绑定模式，当然现在⽹卡产商也会出⼀些针对windows操作系统⽹卡管理软件来做⽹卡绑定（windows操作系统没有⽹卡绑定功能需要第三⽅⽀持）。
1.1 bonding原理⽹卡⼯作在混杂（promisc）模式，接收到达⽹卡的所有数据包，tcpdump⼯作⽤的也是混杂模式（promisc），将两块⽹卡的MAC地址修改为相同接收特定MAC的数据帧，然后把相应的数据帧传送给bond驱动程序进⾏处理。
1.2 Bonding模式（bonding mode）轮询策略（round robin），mode=0，按照设备顺序依次传输数据包，提供负载均衡和容错能⼒主备策略（active-backup），mode=1，只有主⽹卡处于⼯作状态，备⽹卡处于备⽤状态，主⽹卡坏掉后备⽹卡开始⼯作，提供容错能⼒异或策略（load balancing (xor)），mode=2，根据源MAC地址和⽬的MAC地址进⾏异或计算的结果来选择传输设备，提供负载均衡和容错能⼒⼴播策略（fault-tolerance (broadcast)），mode=3，将所有数据包传输给所有接⼝通过全部设备来传输所有数据，⼀个报⽂会复制两份通过bond下的两个⽹卡分别发送出去，提供⾼容错能⼒动态链接聚合（lacp），mode=4，按照802.3ad协议的聚合⾃动配置来共享相同的传输速度，⽹卡带宽最⾼可以翻倍，链路聚合控制协议（LACP）⾃动通知交换机聚合哪些端⼝，需要交换机⽀持 802.3ad协议，提供容错能⼒输出负载均衡模式（transmit load balancing），mode=5，输出负载均衡模式，只有输出实现负载均衡，输⼊数据时则只选定其中⼀块⽹卡接收，需要⽹卡和驱动⽀持ethtool命令输⼊/输出负载均衡模式（adaptive load balancing），mode=6，输⼊和输出都实现负载均衡，需要⽹卡和驱动⽀持ethtool命令2、⽹卡配置⽂件的配置2.1 配置环境 环境：系统CentOS 6.7 + 虚拟机 VMware 12 ⾄少两块物理⽹卡（VMware上添加eth0,eth1） 2.2 需要添加或修改的配置⽂件有5个（mode=1） 这5个配置⽂件是： /etc/sysconfig/network-scripts/ifcfg-eth{0,1} /etc/sysconfig/network-scripts/ifcfg-bond0 /etc/modprobe.d/dist.conf /etc/rc.local2.2.1 /etc/sysconfig/network-scripts/ifcfg-{eth0,eth1,bonding0}修改或添加提⽰：先备份好eth0和eth1，再修改这⼏个⽂件以下是修改好的三个⽹卡配置⽂件的参数[root@ant network-scripts]# vimdiff ifcfg-eth0 ifcfg-eth1 ifcfg-bond02.2.2 修改/etc/modprobe.d/dist.conf⽂件在此⽂件中添加以下内容：alias bond0 bonding，表⽰系统在启动时加载bonding模块，对外虚拟⽹络接⼝设备为 bond0miimon=100，表⽰系统每100ms监测⼀次链路连接状态，如果有⼀条线路不通就转⼊另⼀条线mode=1，表⽰绑定模式为1primary=eth0，系统⾸先eth0作为bond0接⼝与外界信息的传输接⼝2.2.3 修改配置⽂件/etc/rc.local在此⽂件中添加以下内容：modprobe bonding miimon=100 mode=12.2.4 重启⽹络（service network restart），并查看三个接⼝的mac地址使⽤ifconfig命令显⽰，bond0，eth1，eth2物理地址相同，提⽰三个⽹卡均通过⼀个ip主机端⼝与外界通信但是，我们可以看到，在mode=1的情况下，当前bond0采⽤eth0通信，实际的物理⽹卡地址见下图：3、验证⽹络的连通性没有丢包，⽹络连通性可。
linux 双网卡配置
To show all interfaces info
# ifenslave {-a|--all-interfaces}
To be more verbose
# ifenslave {-v|--verbose} ...
# ifenslave {-u|--usage} Show usage
# ifconfig bond0 down
To detach a dead interface without setting the bond device down :
# ifenslave {-d|--detach} bond0 eth0 [eth1 [eth2]...]
ifenslave --help
To create a bond device, simply follow these three steps :
- ensure that the required drivers are properly loaded :
IPADDR=10.198.85.5
NETMASK=255.255.255.0
GATEWAY=10.198.85.254
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
TYPE=Ethernet
vi ifcfg-eth0
DEVICE=eth0
HWADDR=MAC 地址
添加如下内容：
alias bond0 bonding
options bond0 miimon=100 mode=1 primary=eth0
3、编辑：
#cd /etc/sysconfig/network-scripts/
bonding双网卡配置
网络设备热备方案为了提供网络的高可用性，我们可能需要将多块网卡绑定成一块虚拟网卡对外提供服务，这样即使其中的一块物理网卡（或者其所连接的交换机）出现故障，也不会导致连接中断。
在Linux下叫bonding，效果是将两块或更多的网卡当做一块网卡使用，可以提高冗余性。
测试方案将服务器的eth0和eth1绑定成虚拟网卡bond0，bongding1服务器的虚拟网卡ip为192.168.3.60；bonding2服务器的虚拟网卡ip为192.168.3.61。
如图：一、配置双网卡绑定同一个ip地址：1.插件安装：apt-get install ifenslave2.在/etc/modules文件末尾加入：bonding3.编辑网卡配置：vi/etc/network/inerfaces:auto loiface lo inet loopbackauto bond0iface bond0 inet staticaddress 192.168.3.60netmask 255.255.252.0network 192.168.0.0broadcast 192.168.3.255gateway 192.168.0.66bond-mode 1bond-miimon 100bond-slaves nonepost-up /sbin/ifenslave bond0 eth0 eth1pre-down /sbin/ifenslave -d bond0 eth0 eth1auto eth0iface eth0 inet manualbond-master bond0bond-primary eth0 eth1auto eth1iface eth1 inet manualbond-maser bond0bond-primary eth0 eth1说明：miimon是用来进行链路监测的。
比如：miimon 100,那么系统每100 ms 监测一次链路连接状态，如果有一条线路不通就转入另一条线路；mode的值表示工作模式，常用的为0，1两种。
Linux双网卡双IP设置
Linux双网卡双IP设置电信：IP：61.147.67.189网关：61.147.67.161网通：IP：122.195.134.157网关：122.195.134.1291)添加路由表修改/etc/iproute2/rt_tables，添加内容：252 tel 电信路由表251 cnc 网通路由表2)如创建一个配置文件/etc/iproute.sh,文件权限要设置成可执行，内容如下#!/bin/ship route flush table telip route add default via 61.147.67.193 dev eth0 src 61.147.67.200 table telip rule add iif ethX table telip route flush table cncip route add default via 122.195.134.129 dev eth1 src 122.195.134.136 table cnc ip rule add iif ethX table cnc#说明：ethX 代表IP配置的网卡，比如eth0 是电信，3 /etc/wtiproute.sh#!/bin/shroute add -net 1.24.0.0 netmask 255.248.0.0 gw 122.195.134.129route add -net 1.56.0.0 netmask 255.248.0.0 gw 122.195.134.129route add -net 1.188.0.0 netmask 255.252.0.0 gw 122.195.134.129route add -net 14.204.0.0 netmask 255.254.0.0 gw 122.195.134.129route add -net 27.8.0.0 netmask 255.248.0.0 gw 122.195.134.129route add -net 27.36.0.0 netmask 255.252.0.0 gw 122.195.134.129route add -net 27.40.0.0 netmask 255.248.0.0 gw 122.195.134.129route add -net 27.50.128.0 netmask 255.255.128.0 gw 122.195.134.129route add -net 27.54.192.0 netmask 255.255.224.0 gw 122.195.134.129route add -net 27.98.224.0 netmask 255.255.224.0 gw 122.195.134.129route add -net 27.106.128.0 netmask 255.255.192.0 gw 122.195.134.129route add -net 27.115.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 27.131.220.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 27.192.0.0 netmask 255.224.0.0 gw 122.195.134.129 route add -net 36.32.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 36.248.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 42.48.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 42.63.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 42.224.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 47.153.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 47.154.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 47.200.192.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 58.16.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 58.24.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 58.30.64.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 58.30.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 58.31.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 58.68.128.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 58.68.144.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 58.83.17.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 58.116.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 58.128.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 58.144.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 58.240.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 58.248.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 58.249.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 58.252.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 59.108.32.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 59.108.64.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 59.109.64.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 59.109.80.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 60.0.0.0 netmask 255.224.0.0 gw 122.195.134.129route add -net 60.63.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 60.194.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 60.206.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 60.208.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 60.255.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 61.4.176.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 61.28.112.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 61.48.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 61.133.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 61.134.96.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 61.134.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 61.135.0.0 netmask 255.255.0.0 gw 122.195.134.129route add -net 61.137.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 61.138.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 61.138.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 61.139.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 61.148.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 61.156.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 61.158.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 61.159.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 61.161.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 61.161.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 61.162.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 61.167.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 61.168.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 61.176.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 61.179.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 61.180.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 61.181.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 61.182.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 61.189.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 61.233.16.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 61.237.224.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 61.240.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 61.240.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 61.240.232.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 61.240.240.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 61.241.64.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 61.241.128.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 61.241.192.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 61.242.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 61.242.160.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 61.242.224.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 61.243.32.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 61.243.112.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 61.243.124.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 61.243.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 61.243.192.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 101.16.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 101.44.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 101.64.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 101.72.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 103.29.16.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 103.29.132.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 110.6.0.0 netmask 255.254.0.0 gw 122.195.134.129route add -net 110.52.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 110.72.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 110.172.224.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 110.228.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 110.232.32.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 110.236.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 110.240.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 111.67.192.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 111.85.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 111.160.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 111.192.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 111.228.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 112.64.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 112.80.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 112.96.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 112.109.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 112.111.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 112.122.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 112.132.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 112.192.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 112.224.0.0 netmask 255.224.0.0 gw 122.195.134.129 route add -net 113.0.0.0 netmask 255.248.0.0 gw 122.195.134.129route add -net 113.8.0.0 netmask 255.254.0.0 gw 122.195.134.129route add -net 113.18.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 113.31.16.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 113.31.32.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 113.31.64.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 113.56.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 113.58.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 113.59.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 113.194.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 113.200.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 113.204.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 113.209.192.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 113.209.255.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 113.213.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 113.224.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 114.28.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 114.54.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 114.60.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 114.66.0.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 114.110.0.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 114.110.64.0 netmask 255.255.192.0 gw 122.195.134.129route add -net 114.112.16.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 114.112.24.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 114.112.48.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 114.112.136.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 114.112.144.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 114.112.160.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 114.112.192.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 114.113.16.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 114.113.32.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 114.113.64.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 114.113.128.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 114.113.144.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 114.113.208.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 114.113.224.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 114.114.112.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 114.118.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 114.119.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 114.132.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 114.240.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 115.35.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 115.46.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 115.48.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 115.85.192.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 115.100.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 115.102.160.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 115.102.192.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 115.103.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 115.173.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 116.2.0.0 netmask 255.254.0.0 gw 122.195.134.129route add -net 116.60.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 116.62.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 116.63.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 116.70.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 116.90.80.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 116.95.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 116.112.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 116.116.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 116.128.0.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 116.193.16.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 116.193.18.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 116.199.64.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 116.213.128.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 116.213.168.0 netmask 255.255.248.0 gw 122.195.134.129route add -net 116.213.192.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 116.213.224.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 116.213.248.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 116.217.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 116.218.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 116.242.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 116.255.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 117.8.0.0 netmask 255.248.0.0 gw 122.195.134.129route add -net 117.74.64.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 117.79.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 117.79.64.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 117.79.224.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 117.79.240.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 117.79.242.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 117.79.244.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 117.79.246.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 117.106.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 117.112.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 118.24.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 118.25.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 118.26.16.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 118.26.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 118.26.224.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 118.72.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 118.80.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 118.88.32.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 118.88.64.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 118.88.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 118.126.6.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 118.132.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 118.144.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 118.146.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 118.185.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 118.186.64.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 118.186.192.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 118.192.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 118.193.240.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 118.194.128.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 118.194.192.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 118.194.232.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 118.212.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 118.224.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 119.4.0.0 netmask 255.252.0.0 gw 122.195.134.129route add -net 119.32.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 119.32.64.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 119.32.192.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 119.33.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 119.33.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 119.33.192.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 119.36.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 119.39.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 119.40.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 119.40.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 119.42.0.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 119.44.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 119.48.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 119.57.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 119.57.64.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 119.59.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 119.62.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 119.63.32.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 119.80.32.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 119.80.56.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 119.80.64.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 119.80.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 119.88.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 119.108.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 119.112.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 119.148.160.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 119.148.162.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 119.161.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 119.161.208.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 119.161.224.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 119.162.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 119.164.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 119.176.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 119.232.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 119.233.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 119.248.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 119.253.32.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 119.253.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 119.255.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 120.0.0.0 netmask 255.240.0.0 gw 122.195.134.129route add -net 120.65.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 120.66.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 120.80.0.0 netmask 255.248.0.0 gw 122.195.134.129route add -net 120.131.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 120.131.64.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 120.131.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 120.134.62.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 120.195.0.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 120.195.32.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 121.5.0.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 121.5.16.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 121.5.32.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 121.16.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 121.52.208.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 121.55.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 121.68.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 121.79.128.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 121.79.144.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 121.100.128.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 121.100.224.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 121.101.208.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 122.0.64.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 122.10.228.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 122.10.232.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 122.10.240.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 122.11.40.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 122.11.48.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 122.49.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 122.96.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 122.102.0.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 122.102.64.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 122.112.0.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 122.112.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 122.113.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 122.136.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 122.156.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 122.188.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 122.192.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 122.200.64.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 122.248.48.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 123.4.0.0 netmask 255.252.0.0 gw 122.195.134.129route add -net 123.8.0.0 netmask 255.248.0.0 gw 122.195.134.129route add -net 123.56.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 123.56.128.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 123.98.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 123.103.2.0 netmask 255.255.254.0 gw 122.195.134.129route add -net 123.103.8.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 123.103.16.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 123.103.32.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 123.108.208.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 123.108.212.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 123.108.216.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 123.108.220.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 123.112.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 123.128.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 123.138.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 123.144.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 123.148.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 123.152.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 123.188.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 123.196.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 123.232.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 123.253.132.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 124.14.160.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 124.42.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 124.64.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 124.66.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 124.67.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 124.68.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 124.88.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 124.128.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 124.152.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 124.160.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 124.192.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 124.201.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 124.203.192.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 124.205.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 124.207.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 124.240.88.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 124.240.96.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 124.240.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 124.248.32.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 124.249.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 125.32.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 125.97.240.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 125.211.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 125.215.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 135.244.80.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 138.32.244.0 netmask 255.255.252.0 gw 122.195.134.129route add -net 140.206.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 144.211.80.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 144.211.138.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 150.255.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 153.0.0.0 netmask 255.255.0.0 gw 122.195.134.129route add -net 157.122.136.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 159.153.120.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 161.207.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 163.142.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 163.177.136.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 163.179.192.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 168.159.144.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 168.159.152.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 168.159.156.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 168.159.158.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 168.160.224.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 171.34.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 171.36.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 171.116.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 175.16.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 175.42.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 175.44.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 175.106.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 175.146.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 175.148.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 175.152.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 175.160.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 175.184.128.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 175.189.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 175.191.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 180.78.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 180.89.128.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 180.95.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 180.129.128.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 180.130.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 180.184.0.0 netmask 255.254.0.0 gw 122.195.134.129 route add -net 180.186.0.0 netmask 255.255.0.0 gw 122.195.134.129 route add -net 180.188.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 180.189.148.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 180.223.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 182.18.0.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 182.18.64.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 182.48.96.0 netmask 255.255.240.0 gw 122.195.134.129route add -net 182.50.4.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 182.50.8.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 182.50.112.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 182.50.120.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 182.50.124.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 182.54.0.0 netmask 255.255.128.0 gw 122.195.134.129 route add -net 182.61.128.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 182.61.192.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 182.88.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 182.112.0.0 netmask 255.240.0.0 gw 122.195.134.129 route add -net 182.236.160.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 183.92.0.0 netmask 255.252.0.0 gw 122.195.134.129 route add -net 183.184.0.0 netmask 255.248.0.0 gw 122.195.134.129 route add -net 192.11.23.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 192.11.26.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 192.11.39.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 192.11.236.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 192.139.135.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 192.139.136.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 192.170.79.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 194.138.203.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 202.4.252.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 202.38.8.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 202.38.147.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 202.38.161.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 202.38.164.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 202.43.144.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 202.69.4.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 202.75.208.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 202.77.39.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 202.84.16.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 202.85.208.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 202.91.176.0 netmask 255.255.248.0 gw 122.195.134.129 route add -net 202.91.184.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 202.91.186.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 202.91.190.0 netmask 255.255.254.0 gw 122.195.134.129 route add -net 202.91.224.0 netmask 255.255.240.0 gw 122.195.134.129 route add -net 202.93.252.0 netmask 255.255.252.0 gw 122.195.134.129 route add -net 202.94.1.0 netmask 255.255.255.0 gw 122.195.134.129 route add -net 202.95.0.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 202.96.0.0 netmask 255.255.192.0 gw 122.195.134.129 route add -net 202.96.64.0 netmask 255.255.224.0 gw 122.195.134.129 route add -net 202.97.128.0 netmask 255.255.128.0 gw 122.195.134.129。
linux双网卡配置
linux双⽹卡配置
⼀、VM虚拟机添加⼀个⽹络适配器。
选择⾃⼰需要的模式类型
⼆、启动虚拟机，配置⽹卡
按原先配置⽹卡的⽅式配置完（ip地址及默认⽹关还有⽹卡名不能跟原先的⼀样）
重启所有⽹卡（service network restart）后检查⽹卡
三、测试新增⽹卡环境
关闭原先⽹卡，检查新增⽹卡是否能与外⽹链接
ping外⽹后提⽰⽆法识别设备（unknown host ），表⽰⽆dns域名解析服务。
三、解决问题
1、查看⽹卡配置（cat /etc/sysconfig/network-scripts/ifcfg-eth1）
如果配置了dns，则可能是（/etc/resolv.conf）这个路径在重装时linux系统未默认分配给它dns域名解析地址，所以⼿动配置下即可
***我配置好后不知为什么必须⼿启动下才能与外⽹链接（centos6.8）centos7就不会，如果有知道的⼤佬，⿇烦给我这个菜鸟讲解下***。
Linux系统网络配置教程
Linux系统网络配置教程一、引言在现代信息技术时代，网络已经成为我们生活和工作中不可或缺的一部分。
而对于使用Linux操作系统的用户来说，正确配置网络是十分重要的。
本章将介绍Linux系统网络配置的基本步骤和常见问题解决方法。
二、网络配置概述网络配置是指将计算机与网络相连，并配置正确的网络参数，以实现与其他计算机之间的通信。
Linux系统的网络配置可分为两个方面，即物理连接和逻辑配置。
2.1 物理连接物理连接是指将计算机与网络相连的操作。
首先要确保计算机已经正确连接到局域网或因特网。
如果是有线连接，需要插入以太网线到计算机的网卡插槽和路由器的网络接口；如果是无线连接，需要确保无线网卡已经连接到正确的无线网络。
2.2 逻辑配置逻辑配置是指在物理连接完成后，需要对计算机进行相应的软件设置，以使其能够正确地与其他网络设备进行通信。
逻辑配置的主要内容包括IP地址的配置、网关的配置、DNS的配置以及防火墙的配置等。
三、IP地址配置IP地址是互联网中用于标识和定位计算机的一种地址。
在Linux系统中，可以通过以下两种方式来配置IP地址：3.1 动态IP地址配置动态IP地址配置是指使用DHCP服务器为计算机分配IP地址的方式。
DHCP是一种网络协议，它可以自动为计算机分配IP地址和其他网络配置信息。
要使用动态IP地址配置，在终端中输入以下命令：```shellsudo dhclient eth0```其中，eth0是计算机的网卡接口名，根据实际情况进行相应更改。
3.2 静态IP地址配置静态IP地址配置是指手动为计算机分配一个固定的IP地址。
这种方式适用于需要长期使用特定IP地址的情况。
要进行静态IP 地址配置，需要编辑网络配置文件。
在终端中输入以下命令：```shellsudo nano /etc/network/interfaces```在文件中添加以下配置信息：```shellauto eth0iface eth0 inet staticaddress 192.168.0.100netmask 255.255.255.0gateway 192.168.0.1```其中，eth0是计算机的网卡接口名，address是计算机的IP地址，netmask是子网掩码，gateway是网关地址。