02-04-2020 02:17 PM
Hello,
I believe this may have to do with editing my routing table...
I am still a newcomer to the CCNA world and I am working with the back-end of our network. My supervisor informed me that we had just purchased new IP addresses and I have confirmed with the provider that they are now usable. My question is, how can I get these IP addresses to work on my network and assign a device with one of these new ip addresses?
These are the addresses that were given:
Network: 64.183.103.x
Gateway: 64.183.103.x
Usable: 64.183.x.x THRU 64.183.x.x
/28
255.255.255.240
DNS1: 209.18.47.61
DNS2: 209.18.47.62
Solved! Go to Solution.
02-05-2020 02:19 AM
Hi,
Its better use static NAT configuration as its just 14 usable IP's are der.
Address: 64.183.103.1 01000000.10110111.01100111.0000 0001
Netmask: 255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
Wildcard: 0.0.0.15 00000000.00000000.00000000.0000 1111
=> Network: 64.183.103.0/28 01000000.10110111.01100111.0000 0000 (Class A)
Broadcast: 64.183.103.15 01000000.10110111.01100111.0000 1111
HostMin: 64.183.103.1 01000000.10110111.01100111.0000 0001
HostMax: 64.183.103.14 01000000.10110111.01100111.0000 1110
Hosts/Net: 14
You can deploy the following configuration in the ISP facing router.
ip nat inside source static <private IP> <public IP>
https://study-ccna.com/static-nat/
02-04-2020 03:04 PM
Hello,
typically, if you have more than 1 usable public IP address, you would consolidate these in a NAT pool:
ip nat pool ISP 64.183.x.x THRU 64.183.x.x netmask yyy.yyy.yyy.yyy
and the use the pool in your NAT statement:
ip nat inside source list 1 pool ISP overload
02-04-2020 03:29 PM
Thank you for the reply. A majority of this network is using 192.168.x.x for their ip addresses. Would it still work with this current config if I added those NAT commands you mentioned? Im just a little confused since we are using 192.168 and the provider gave us 64.183 addresses.
AVTA_SW_Admin-1#sh ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is 192.168.2.1 to network 0.0.0.0
S* 0.0.0.0/0 [1/0] via 192.168.2.1
10.0.0.0/30 is subnetted, 2 subnets
S 10.1.7.0 [1/0] via 192.168.2.236
S 10.1.8.0 [1/0] via 192.168.2.237
172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.16.1.0/24 is directly connected, Vlan172
L 172.16.1.1/32 is directly connected, Vlan172
C 192.168.2.0/23 is directly connected, Vlan2
192.168.2.0/32 is subnetted, 1 subnets
L 192.168.2.5 is directly connected, Vlan2
192.168.10.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.10.0/24 is directly connected, Vlan10
L 192.168.10.5/32 is directly connected, Vlan10
Thank you
02-04-2020 03:45 PM
Hello
@_Chris_ wrote:
Thank you for the reply. A majority of this network is using 192.168.x.x for their ip addresses. Would it still work with this current config if I added those NAT commands you mentioned? Im just a little confused since we are using 192.168 and the provider gave us 64.183 addresses.
So this suggests you have a upstream routing device performing NAT already, Do you have management access to this upstream routing device
02-04-2020 03:57 PM
I'm pretty sure I do. I just need to locate it. Once I do, then I could enter NAT commands in THAT device?
02-04-2020 04:15 PM - edited 02-04-2020 04:17 PM
Hello
@_Chris_ wrote:
then I could enter NAT commands in THAT device?
Not just yet, As i have stated given that you have an upstream router is already performing nat, And as the AVTA_SW_Admin router isnt pubic facing also looking at your previous posts posts on here The AVTA_SW_Admin router is either also performing nat or your upstream rtr that is public facing is performing nat for all subnets including for vlans 2,10,172.
Can you post a simple topology diagram of your network and if possible the running config of AVTA_SW_Admin and the upstream routers please.
Lastly
@_Chris_ wrote:
I'm pretty sure I do. I just need to locate it.
S* 0.0.0.0/0 [1/0] via 192.168.2.1 < this will most probably be you upstream rtr
02-04-2020 04:27 PM
I see. I will have to check it tomorrow as I have headed home for the day. - Thank you.
02-04-2020 03:18 PM - edited 02-04-2020 03:21 PM
Hello
@_Chris_ wrote:
My question is, how can I get these IP addresses to work on my network and assign a device with one of these new ip addresses?
These are the addresses that were given:
Network: 64.183.103.x
Gateway: 64.183.103.x
Usable: 64.183.x.x THRU 64.183.x.x /28
You can use a Network address translation (nat) pool as already suggested or you you statically assign individual lan host to specific public ip addresses (NAT) or Port address translation statically to specific port (PAT)
Example:
ip nat inside source static 10.10.10.100 63.189.x.x <- static nat
or
ip nat inside source static tcp 10.10.10.100 80 63.189.x.x 80 <-static pat
02-05-2020 02:19 AM
Hi,
Its better use static NAT configuration as its just 14 usable IP's are der.
Address: 64.183.103.1 01000000.10110111.01100111.0000 0001
Netmask: 255.255.255.240 = 28 11111111.11111111.11111111.1111 0000
Wildcard: 0.0.0.15 00000000.00000000.00000000.0000 1111
=> Network: 64.183.103.0/28 01000000.10110111.01100111.0000 0000 (Class A)
Broadcast: 64.183.103.15 01000000.10110111.01100111.0000 1111
HostMin: 64.183.103.1 01000000.10110111.01100111.0000 0001
HostMax: 64.183.103.14 01000000.10110111.01100111.0000 1110
Hosts/Net: 14
You can deploy the following configuration in the ISP facing router.
ip nat inside source static <private IP> <public IP>
https://study-ccna.com/static-nat/
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: