Cisco 2911 remote configuration access

Hi all,

I look after various clients in various buildings and have numerous VLANs. I need to be able to make changes to the configs on the routers as and when clients needs change. Upgrading or downgrading connection speeds etc.

I have a Cisco 2911's and need to enable off site configuration using telnet/ssh to save numerous site visits. As there is no physical hardware I can connect to internally on the network to run a session to the Cisco, I want to be able to do this from my PC remotely into the Cisco. I have a range of external IP's I can use if needed.

The management ip range is 192.168.100.0/24

ip access-list extended Reception
permit ip 192.168.100.0 0.0.0.255 host 192.168.1.240
permit icmp 192.168.100.0 0.0.0.255 host 192.168.100.253
deny   ip 192.168.100.0 0.0.0.255 192.168.0.0 0.0.255.255
permit ip any any

Many thanks
LVL 5
ncomperAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AkinsdNetwork AdministratorCommented:
Create a static NAT (port forwarding) rule on the router or firewall for port 22 (ssh) or port 23 (Telnet) pointed to your public IP to forward to the IP of your 2911
I recommend ssh. Avoid telnet over wan link as much as possible.

For ssh, configure your router or firewall for ssh support - requires crypto and certificate

If your router is not capable, then you can use telnet.
0
Soulja53 6F 75 6C 6A 61 Commented:
I'm confused by the previous comment.

Author, are you routers sitting inside the clients' lans, or are they WAN routers connected to the internet?

If internet, why not just all SSH to the external interface and create an acl only allowing SSH from your location?
0
ncomperAuthor Commented:
This is an External WAN router,

please ignore the ACL posted as these are not relevant.

I need to confirm the configuration required to allow Access over SSH to the external interface from a designated IP range (static public addresses)

Thanks
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

ncomperAuthor Commented:
.
0
Soulja53 6F 75 6C 6A 61 Commented:
Assuming you already have ssh enabled and assuming you already have an inbound acl applied to the external interface just add a permit that allows your block of ip addresses to the external interface of the router:

ex.

ip access-list extended INET
permit tcp x.x.x.x 255.255.255.248 host y.y.y.y eq 22

x being your block of ip's. y being wan ip of router
0
AkinsdNetwork AdministratorCommented:
This is over a wan link, not a tunnel.
Private IPs are not routable on the Internet

Static NAT is what is needed
He also needs to allow the public address he will be SSHing from

Take note of his comment
(I have a range of external IP I can use.....)

Maybe the author should clarify more. Are the buildings all in the same super network or are they separate (standalone) networks
0
ncomperAuthor Commented:
Hi all,

Thanks for the replies so far. Yes the buildings are completely seperate standalone networks.  Nothing tieing them together. I have ssh enabled and currently using 4 external ip's that are being used by servers internally and port forwards on those ip's and static NAT to internal ip addresses.

Hope this clarifys it some for you
0
AkinsdNetwork AdministratorCommented:
Exactly what I thought

Static NAT (a.k.a Port Forwarding) is what you need to configure as I mentioned earlier.

Commands for NAT differs depending on what platform you are using and what IOS version you are using especially for ASA firewalls

Example of the most common NAT configuration
- Web server's local address = 192.168.1.80 or 192.168.1.80
- Router with SSH enabled = 192.168.1.81
- DNS server = 192.168.1.82
- Public IP Address  = 8.8.8.8

Using the same public address, you can port forward to each device

- ip nat source inside static tcp 192.168.1.80 80 8.8.8.8 80
- ip nat source inside static tcp 192.168.1.80 443 8.8.8.8 443
- ip nat source inside static tcp 192.168.1.81 22 8.8.8.8 22
- ip nat source inside static udp 192.168.1.82 53 8.8.8.8 53
- ip nat source inside static tcp 192.168.1.81 23 8.8.8.8 53

Web url (http) to 8.8.8.8 will forward the request to 192.168.1.80
Secure Web url (https) to 8.8.8.8 will forward the request to 192.168.1.80
ssh to  8.8.8.8 will forward the request to 192.168.1.81
DNS query  to 8.8.8.8 will forward the request to 192.168.1.82
telnet to 8.8.8.8 will forward the request to 192.168.1.81

for new ios on firewall
object network SSH_Obj
host 192.168.1.81
nat (inside,outside) static interface service tcp 22 22
access-list SSH_ACL extended permit tcp any host 192.168.1.81 eq ssh

access-group SSH_ACL in interface outside
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ncomperAuthor Commented:
Thanks, ill try that
0
ncomperAuthor Commented:
Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Routers

From novice to tech pro — start learning today.