No nonsense, first
650) this. width = 650; "onclick = 'window. open (" http://blog.51cto.com/viewpic.php? Refimg = "+ this. src) 'border =" 0 "src =" http://img1.51cto.com/attachment/201008/170005952.jpg "alt =" "/>
Let's start with the illustration. Some projects or some families or for other reasons need to pick up several more information points, but it is not convenient to put a few more lines. Let's just pick up another soho route, let me simulate this!
First, it is impossible for r1 to configure a route to r3, because if it is the route of the entire community, it will not let you change, you can use nat to solve this problem, as long as it is a vro.
My idea is: the hosts under r2 are first converted to 192 through r2 nat. 168. 1. 5. This ip address add is directly connected to r1. There is a r1 route in the route table. When the frame arrives at r1, r1 considers it as the r2 frame and passes through the nat of r1, convert to internal global address 200. 1. 1. 2. packet encapsulation and transmission.
I don't know. Who is the internal local address in this topology? 10. 1. 1. 0/24? 192. 168. 1. 0/24?
Originally, we wanted to use gns3 to solve the problem. The Rogue's damn vps and gns took up too much cpu resources, but r2 never received the ip add allocated by r1. The rogue could only configure one, the packet tracer cannot even input "/24" as the mask, and I takes the packet tracer.
Configuration on,
This is r2, and the new soho route is added)
- Building configuration...
-
- Current configuration : 1070 bytes
- !
- version 12.2
- no service timestamps log datetime msec
- no service timestamps debug datetime msec
- service password-encryption
- !
- hostname r2
- !
- !
- !
- enable password 7 0822455D0A16
- !
- !
- ip dhcp excluded-address 10.1.1.1 10.1.1.2
- !
- ip dhcp pool abc
- network 10.1.1.0 255.255.255.0
- default-router 10.1.1.1
- dns-server 202.102.192.68
- !
- !
- !
- !
- !
- !
- !
- !
- !
- !
- !
- !
- !
- interface FastEthernet0/0
- ip address 192.168.1.5 255.255.255.0
- ip nat outside
- duplex auto
- speed auto
- !
- interface FastEthernet0/1
- no ip address
- duplex auto
- speed auto
- shutdown
- !
- interface FastEthernet1/0
- ip address 10.1.1.1 255.255.255.0
- ip nat inside
- duplex auto
- speed auto
- !
- interface FastEthernet1/1
- no ip address
- duplex auto
- speed auto
- shutdown
- !
- ip nat inside source list 100 interface FastEthernet0/0 overload
- ip classless
- ip route 0.0.0.0 0.0.0.0 FastEthernet0/0
- !
- !
- access-list 100 permit ip 10.1.1.0 0.0.0.255 any
- !
- !
- !
- !
- !
- line con 0
- exec-timeout 0 0
- password 7 08701E1D
- logging synchronous
- login
- line vty 0 4
- exec-timeout 0 0
- password 7 08701E1D
- logging synchronous
- login
- !
- !
- !
- end
This is the configuration of r1,
- r1#show run
- Building configuration...
-
- Current configuration : 1073 bytes
- !
- version 12.2
- no service timestamps log datetime msec
- no service timestamps debug datetime msec
- service password-encryption
- !
- hostname r1
- !
- !
- !
- enable password 7 0822455D0A16
- !
- !
- ip dhcp excluded-address 192.168.1.0 192.168.1.10
- !
- ip dhcp pool abc
- network 192.168.1.0 255.255.255.0
- default-router 192.168.1.1
- dns-server 202.102.192.68
- !
- !
- !
- !
- !
- !
- !
- !
- !
- !
- !
- !
- !
- interface FastEthernet0/0
- ip address 192.168.1.1 255.255.255.0
- ip nat inside
- duplex auto
- speed auto
- !
- interface FastEthernet0/1
- no ip address
- duplex auto
- speed auto
- shutdown
- !
- interface Serial0/0
- ip address 200.1.1.2 255.255.255.0
- ip nat outside
- !
- interface Serial0/1
- no ip address
- shutdown
- !
- ip nat inside source list 100 interface Serial0/0 overload
- ip classless
- ip route 0.0.0.0 0.0.0.0 200.1.1.1
- !
- !
- access-list 100 permit ip 192.168.1.0 0.0.0.255 any
- access-list 1 permit host 192.168.1.1
- !
- !
- !
- !
- !
- line con 0
- access-class 1 out
- password 7 08701E1D
- logging synchronous
- login
- line vty 0 4
- access-class 1 out
- exec-timeout 0 0
- password 7 08701E1D
- logging synchronous
- login
- !
- !
- !
- end
Let's take a look at the result. From the ping result above pc3:
- Packet Tracer PC Command Line 1.0
- PC>ipconfig /all
-
- Physical Address................: 0090.0C2E.0870
- IP Address......................: 10.1.1.4
- Subnet Mask.....................: 255.255.255.0
- Default Gateway.................: 10.1.1.1
- DNS Servers.....................: 202.102.192.68
-
-
- PC>ping 200.1.1.1
-
- Pinging 200.1.1.1 with 32 bytes of data:
-
- Request timed out.
- Reply from 200.1.1.1: bytes=32 time=140ms TTL=253
- Reply from 200.1.1.1: bytes=32 time=140ms TTL=253
- Reply from 200.1.1.1: bytes=32 time=156ms TTL=253
-
- Ping statistics for 200.1.1.1:
- Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
- Approximate round trip times in milli-seconds:
- Minimum = 140ms, Maximum = 156ms, Average = 145ms
-
- PC>
Tracert result:
- PC>tracert 200.1.1.1
-
- Tracing route to 200.1.1.1 over a maximum of 30 hops:
-
- 1 62 ms 62 ms 62 ms 10.1.1.1
- 2 125 ms 125 ms 125 ms 200.1.1.1
- 3 125 ms 141 ms 156 ms 200.1.1.1
-
- Trace complete.
Put the p.s. pkt file in the attachment. The password for telnet and console is 123, and the enable password is cisco.
This article from the "Flowers and nights" blog, please be sure to keep this http://fengyun.blog.51cto.com/532912/384182