cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
358
Views
0
Helpful
1
Replies

Trying to use Netgear Hotspot for internet access 3 Cisco 2911 routers

device1001
Level 1
Level 1

I have 3 2911 routers and 2 3560 v2 L3 switches and one 2960 L2 switch. I have my network setup and everything works except I can't ping my home hotspot router or access the internet through it from anywhere on this network. . Here is my setup:

R1

s0/1/0 192.168.2.6 255.255.255.252

g0/0 192.168.4.1 255.255.255.0 --> Factory reset Cisco 3560 v2 switch here with PC connected. Can ping all except 192.168.1.1

R2

s0/1/0 192.168.2.5 255.255.255.252

s0/0/0 192.168.2.1 255.255.255.252

g0/0 192.168.3.1 255.255.255.0 --> Factory reset Cisco 2960 switch here w/PC for troubleshooting simplicity. Can ping all but 192.168.1.1  

g0/1 192.168.1.2 255.255.255.0 interface connected to my Netgear Hotspot on network 192.168.1.0/24

R3

s0/0/0 192.168.2.2 255.255.255.252

g0/0 192.168.5.1 255.255.255.0 --> Factory reset Cisco 3560 v2 switch here with PC connected. Can ping all except 192.168.1.1

I have two windows hosts I can ping all the interfaces and each host from the other and from all 3 router consoles. From R2 I can ping 192.168.1.1 which set as gateway of last resort. I can ping internet domains like google.com and facebook.com from R2 console but not R1 or R3 nor the windows host connected directly to R2 via switch. I can't ping 192.168.1.1 from R1 or R3 console nor from any windows host even if I'm connected to R2 but can ping 192.168.1.2. I can ping 192.168.1.2 from anywhere. I'm puzzled as to why I can't ping 192.168.1.1 from the PC even though its connected directly to the same router the PC is on and gateway of last resort is 0.0.0.0/0 [1/0] via 192.168.1.1 but I can ping it from the console of the router. I can ping the PC from R2 console also.  

Attached is the current running-config for R2. 

I don't have a lot of cisco experience. I'm just trying to learn as much as I can so I can attempt the CCNA cert test this summer. 

1 Reply 1

Richard Burts
Hall of Fame
Hall of Fame

Thank you for posting the router config. The problem is pretty clear. You are using private IP addressing on your interfaces (as you should be doing). The netgear knows about 192.168.1.0 since it is connected on that network. But it does not know about any other 192.168.x.x networks. When you are connected on R2 console and attempt Internet access the source address is 192.168.1.2 and netgear can respond to it. But from anywhere else the source address is some 192.168.x.x address and netgear does not know how to reach it.

The solution is to configure Network Address Translation on the interfaces of R2.

HTH

Rick
Review Cisco Networking for a $25 gift card