Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New subnet/IP block 3

Status
Not open for further replies.
MikeWire

MikeWire

IS-IT--Management
Feb 1, 2005
33
0
0
US
Hi guys/gals,

We were assigned a new block of Ip's (216.177.187.225) and subnet 255.255.255.224(/27) and I need to config my router (config with NAT already etc.) for the second subnet. Do I use the ip route command to do this and does anyone have a sample running-config? And do you see anthing wrong with my setup?

Here's mine:

Building configuration...

Current configuration : 5169 bytes
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname Router
!
no logging buffered
enable secret 5
!
username Router

ip subnet-zero
ip name-server 216.187.160.17
ip name-server 216.187.165.2
ip dhcp excluded-address 192.168.200.1
ip dhcp excluded-address 192.168.200.108
ip dhcp excluded-address 192.168.200.102
ip dhcp excluded-address 192.168.200.48
ip dhcp excluded-address 192.168.200.78
ip dhcp excluded-address 192.168.200.99
ip dhcp excluded-address 192.168.200.73
ip dhcp excluded-address 192.168.200.67
ip dhcp excluded-address 192.168.200.68
ip dhcp excluded-address 192.168.200.71
ip dhcp excluded-address 192.168.200.72
ip dhcp excluded-address 192.168.200.75
ip dhcp excluded-address 192.168.200.76
ip dhcp excluded-address 192.168.200.6
ip dhcp excluded-address 192.168.200.5
!
ip audit notify log
ip audit po max-events 100
!
!
!
interface Ethernet0
description CRWS Generated text. Please do not delete this:192.168.200.99-255.255.255.0
ip address 192.168.200.99 255.255.255.0
ip nat inside
no cdp enable
hold-queue 32 in
hold-queue 100 out
!
interface Ethernet1
ip address 216.187.177.74 255.255.255.240
ip nat outside
no cdp enable
!
ip nat inside source list 102 interface Ethernet1 overload
ip nat inside source static tcp 192.168.200.1 25 interface Ethernet1 25
ip nat inside source static tcp 192.168.200.1 110 interface Ethernet1 110
ip nat inside source static tcp 192.168.200.108 21 interface Ethernet1 21
ip nat inside source static tcp 192.168.200.108 80 interface Ethernet1 80
ip nat inside source static tcp 192.168.200.48 3389 interface Ethernet1 3389
ip nat inside source static tcp 192.168.200.78 22 interface Ethernet1 22
ip nat inside source static tcp 192.168.200.99 23 interface Ethernet1 23
ip nat inside source static tcp 192.168.200.1 20 interface Ethernet1 20
ip nat inside source static tcp 192.168.200.1 80 216.187.177.66 80 extendable
ip nat inside source static tcp 192.168.200.1 110 216.187.177.66 110 extendable
ip nat inside source static tcp 192.168.200.1 25 216.187.177.66 25 extendable
ip nat inside source static tcp 192.168.200.1 20 216.187.177.66 20 extendable
ip nat inside source static tcp 192.168.200.1 21 216.187.177.66 21 extendable
ip nat inside source static tcp 192.168.200.1 3389 216.187.177.66 3389 extendable
ip nat inside source static tcp 192.168.200.102 80 216.187.177.69 80 extendable
ip nat inside source static tcp 192.168.200.73 3389 216.187.177.73 3389 extendable
ip nat inside source static tcp 192.168.200.67 3389 216.187.177.67 3389 extendable
ip nat inside source static tcp 192.168.200.68 3389 216.187.177.68 3389 extendable
ip nat inside source static tcp 192.168.200.71 3389 216.187.177.71 3389 extendable
ip nat inside source static tcp 192.168.200.72 3389 216.187.177.72 3389 extendable
ip nat inside source static tcp 192.168.200.75 3389 216.187.177.75 3389 extendable
ip nat inside source static tcp 192.168.200.76 3389 216.187.177.76 3389 extendable
ip nat inside source static tcp 192.168.200.6 3389 216.187.177.77 3389 extendable
ip nat inside source static tcp 192.168.200.78 80 216.187.177.78 80 extendable
ip nat inside source static tcp 192.168.200.78 22 216.187.177.78 22 extendable
ip nat inside source static tcp 192.168.200.5 3389 216.187.177.74 3389 extendable
ip nat inside source static tcp 192.168.200.103 80 216.187.177.229 80 extendable
ip nat inside source static tcp 192.168.200.104 80 216.187.177.230 80 extendable
ip nat inside source static tcp 192.168.200.105 80 216.187.177.231 80 extendable
ip nat inside source static tcp 192.168.200.106 80 216.187.177.226 80 extendable
ip nat inside source static tcp 192.168.200.107 80 216.187.177.227 80 extendable
ip nat inside source static tcp 192.168.200.48 3389 216.187.177.70 3389 extendable
ip nat inside source static tcp 192.168.200.108 80 216.187.177.232 80 extendable
ip nat inside source static tcp 192.168.200.108 21 216.187.177.232 21 extendable
ip nat inside source static tcp 192.168.200.102 80 216.187.177.228 80 extendable
ip classless
ip route 0.0.0.0 0.0.0.0 216.187.177.65
ip route 0.0.0.0 0.0.0.0 216.187.167.1
ip route 0.0.0.0 0.0.0.0 216.187.167.2
ip http server
ip pim bidir-enable
!
!
access-list 102 permit ip 192.168.200.0 0.0.0.255 any
no cdp run
banner motd ^C
$ network, then you must disconnect immediately.
^C
!
line con 0
exec-timeout 120 0
stopbits 1
line vty 0 4
exec-timeout 120 0
password 7 0213097C190F5D
login local
length 0
!
scheduler max-task-time 5000
end
 
Sort by date Sort by votes
BTW the topology is

Internet-----ISP router-----Cisco 806 our router-----Computers
 
Upvote 0 Downvote
You might want to involve your ISP...

My traceroute ends at 216.220.20.246 which I am asuming is your ISP....

Tell your ISP that you want to route 216.187.177.224/27 to 216.187.177.74.

And issue this on your router:

Code: 
no ip route 0.0.0.0 0.0.0.0 216.187.177.225

What you need to do is have the ISP put in a static route for your new subnet to your router's original outside interface address. Your router will then route the packets back out the same interface to the secondary IP network. Your NAT commands will then work as well as pinging 216.187.177.254.
 
Upvote 0 Downvote
I spoke to them yesterday and they told me that it should be ready to go because it is dual numbered. I am assuming that they have taken care of the routing, but i am not too sure. And out of curiosity why would I want to have my isp route the /27 to 216.187.177.74? Because that is a static NAT for one computer (port 3389) for RDP for remote users? I will issue the no command and if you will do a tracert again for me see what you find? Thanks for all your help!!!
 
Upvote 0 Downvote
No... That is the primary IP address of your interface.
 
Upvote 0 Downvote
Of course it is...duh I had my IP log in the other room. Thx
Here is show ip route:


Gateway of last resort is 216.187.177.65 to network 0.0.0.0

C 192.168.200.0/24 is directly connected, Ethernet0
216.187.177.0/24 is variably subnetted, 2 subnets, 2 masks
C 216.187.177.224/27 is directly connected, Ethernet1
C 216.187.177.64/28 is directly connected, Ethernet1
S* 0.0.0.0/0 [1/0] via 216.187.177.65

Does this look correct to you?
 
Upvote 0 Downvote
Thanks for your help guys I am now up and running, except for mikwire which is not resoving its DNS...but thanks again!!

Mike
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

XLNTech1
  • Locked
  • Question
Cisco Nexus 9k new admin user
Replies
0
Views
245
XLNTech1
XLNTech1
bfordz
  • Locked
  • Question
new help on setting up third party VoIP phones through Catalyst 2960x switch
Replies
0
Views
90
bfordz
bfordz
Delta5
  • Locked
  • Question
Cisco setting for automatic ip arp cache refresh
Replies
3
Views
266
iggsterman
iggsterman
telklass
  • Locked
  • Question
Network + Subnet Mask
Replies
2
Views
70
burtsbees
burtsbees
acabezas2014
  • Locked
  • Question
Create ACL for ip range
Replies
2
Views
80
acabezas2014
acabezas2014

Part and Inventory Search

Sponsor

Back
Top