[FIXED] Routing issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2015 10:21 AM - edited 03-08-2019 02:40 AM
I have a cradle point router I am trying to add to my network. I have assigned the cradlepoint an ip of 10.26.184.2 255.255.255.252. On my router (2951) I have assigned the port that connects the cradlepoint (gi0/1) an ip of 10.26.184.1 255.255.255.252. Also on my router I have assigned gi0/0 a secondary ip of 10.26.185.254 255.255.255.0 as a default gateway for the new subnet I made 10.26.185.0/24. All the addresses in this subnet will be assigned static. I have my laptop set with an ip in this subnet and plugged in to a 3750 switch. From my machine I can Ping 10.26.184.1 but not 10.26.184.2. Same on the 3750. But on the 2951 routerus I can pino my machine and I can Ping the cradlepoint. The router knows the route to the cradlepoint. But when I trace from my machine it hits the router and dies. What am I missing?
- Labels:
-
Other Switching
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2015 11:47 AM
Hi,
does the cradlepoint router know how to route back to the 10.26.185.0/24 subnet?
I guess you shloud add a static route for 10.26.185.0/24 on it pointing to 10.26.184.1?
Regards,
Milan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2015 12:21 PM
i put 10.26.185.0 255.255.255.0 10.26.184.1 (cisco router interface) into the cradlepoint. no change.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2015 01:45 PM
Hello,
Add a default route on craddle router.
Is craddle router configured in bridge mode or router mode? If you set 10.26.185.254 on 2950 and clients with IPs 10.26.185.0/24 are behind the craddle, craddle must be configured in bridge mode.
Please attach your topology so that we can get a better understanding of your new configuration,
Masoud
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2015 03:33 PM
I ended up adding a deny statement to my ACL to drop all packets NOT bound for the internet and it fixed my problem
