05-16-2018 08:52 AM - edited 03-08-2019 03:02 PM
Hi
I'm trying to setup my first home lab but I'm having an issue with telnet from my home network. I have successful connected an router 2811, switch 3560v2 and an pc1. 2811 gets internet access form my home router (netgear) and switch and pc1 gets access through 2811. I can ping 2811 from pc1(192.168.2.2) and have access through telnet. When I try to telnet from pc2(192.168.1.2) to 2811 it doesn't work, however I can ping 2811 and I get answer but no telnet connection. Thank you in advance!
Here is config print:
Solved! Go to Solution.
05-16-2018 12:32 PM
I believe that the drawing is pretty clear that the router is learning an IP address in the 192.168.1 network via dhcp. So the default route should be ok.
I suspect that the issue with telnet is that the 2811 is configured to do address translation for EVERY packet with source address in 192.168.2 to any destination and is therefore translating the telnet traffic. You probably want to change the ACL so that it does not translate traffic to the 192.168.1 network.
HTH
Rick
05-16-2018 11:43 AM
Hello,
the default route looks odd, since you don't have a local interface in the same segment:
ip route 0.0.0.0 0.0.0.0 192.168.1.254
There needs to be an interface in the 192.168.1.0/24 range on your 2811 in order for the default route to work.
On the VTYlines, configure the line in bold:
line vty 0 4
password cisco
login
transport input telnet
05-16-2018 12:32 PM
I believe that the drawing is pretty clear that the router is learning an IP address in the 192.168.1 network via dhcp. So the default route should be ok.
I suspect that the issue with telnet is that the 2811 is configured to do address translation for EVERY packet with source address in 192.168.2 to any destination and is therefore translating the telnet traffic. You probably want to change the ACL so that it does not translate traffic to the 192.168.1 network.
HTH
Rick
05-17-2018 03:10 AM
05-17-2018 05:38 AM
You are welcome. I am glad that my suggestions were helpful.
HTH
Rick
05-18-2018 06:43 AM
Hi again
Now I have another issue. Telnet works now from pc 192.168.1.2 but pc 192.168.2.2 lost the internet access. It works with permit any, but when I change back to permit 192.168.1.2 it doesn't.
05-18-2018 07:03 AM
The issue here is that you are now using the same access list for two different purposes. In the original post you used access list 1 for the purpose of controlling address translation. There was no access class on your vty lines.
I suggested that the problem was that access list 1 used permit any and this results in translating the attempt to telnet. You then made several changes in the config. You added access class on the vty and you have access class use the same ACL as address translation and you changed access list 1 to remove permit any and replace it with a permit for pc1. The result of this is that traffic from 192.168.2.2 is no longer translated and therefore no longer has Internet access.
I am not sure why you added access class. But using the same access list for both purposes creates this problem. If you want to keep using access class then it needs an ACL different from what nat uses.
HTH
Rick
05-18-2018 07:22 AM
05-21-2018 08:16 AM
To respond to your question we need to understand what you will use the access lists for. When an access list is configured it does not do anything on its own. The access list must be applied to something. In the original post you have access list 1 and applied it to address translation. Then you changed the access list and applied the access list to access class. It appears that you were using the same access list for two purposes, which might be all right if the logic in the access list was appropriate for both purposes. But the logic that you need for address translation is probably not the same logic that you need for access class.
The simple answer to your question is that yes you can add access list 2 and keep access list 1. But the really correct answer to the question depends on how you will apply each of the ACL.
HTH
Rick
05-23-2018 04:05 AM - edited 05-23-2018 11:23 PM
Here is my next challenge
I have added two more of each to my lab setup: routers, switches an pc/laptops, and here is what i have done so far. All routers/pc have internet access, R2 and R3 using ip nat inside on serial ports to get access from R1. Everything works like it should, telnet, ping (from pc 1,2 and 3 to all switches and routers). However from my HomePC i can only telnet into R1 (192.168.1.88) and ping works also. What do i have to do to get the access to 192.168.2, 192.168.3 and 192.168.4 from my HomePC?
here is my static routing setup and the acl on R1:
ip route 0.0.0.0 0.0.0.0 192.168.1.254
ip route 11.0.0.0 255.0.0.0 11.0.0.1
ip route 12.0.0.0 255.0.0.0 12.0.0.2
ip route 192.168.4.0 255.255.255.0 11.0.0.1
ip route 192.168.3.0 255.255.255.0 12.0.0.2
!
access-list 1 permit any
05-23-2018 11:34 AM - edited 05-23-2018 12:42 PM
Is there anyone who can help me? I have tried back and forward with ip route and acl but I'm probably doing it wrong.
05-23-2018 11:52 AM
Hello,
is this a Packet Tracer project ? If so, post the project (pkt) file (rename the .pkt to .jpg first, otherwise the system won't let you upload)...
05-23-2018 01:52 PM - edited 05-24-2018 02:32 AM
Hi
Its a real setup, with real routers, switches and laptops in my basement. Packet tracer is just for showing purpose and its not fully complete.
05-23-2018 11:55 AM
Your new config changes mention networks 11.0.0.0 and 12.0.0.0. But I do not see them in your diagram. What are they? Where are they?
HTH
Rick
05-23-2018 12:30 PM - edited 05-24-2018 02:34 AM
Its serial connections between R2, R1 and R3. I have updated my screenshot a little. It should be enough now.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide