Problems with IP addressing within the same subnet 255.255.0.0
We are trying to configure 2 c2611's to create a WAN using a point-to-point T-1. We need to know:
- Our internal IP addressing scheme uses a class b subnet mask (255.255.0.0) but our devices use addresses like 172.16.205.x or 172.16.210.xx . How can we make the router's interfaces accept this addressing scheme without changing the subnet? We need the two ethernet interfaces to be on the 172.16.0.0 network so that our servers, PBX, etc can talk to it and reach the WAN.
Is there a command we are missing to allow multiple IP Addresses within the same subnet to be programmed on interfaces E0/0 and E0/1 on the same router. Each time we program E0/1 we get a message saying 172.16.0.0 overlaps with Ethernet0/0. We have other brands of routers in house that allow us to use different IP's on the same subnet but there is a command that has to be issued to allow this to happen. Can anyone point me in the right direction?
Re: Problems with IP addressing within the same subnet 255.255.0
Each of your router's interfaces need to be addressed with unique IP networks. If this is not possible for your current addressing or system requirement you can bridge with your router to allow this 172.16.0.0/16 to span both ethernet interfaces. I would recommend breaking this up into smaller subnetworks if possible.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...