This is probably a stupid question. I know (or at least I think I know or understand it) that the private IP addresses such as 192.168.10.x are normally not routed by routers.
I'm trying to setup a CISCOPro 765 router to dial over ISDN into a partner company. They gave me the IP address of their server, the ISDN number, username etc...
The setup itself is no problem, I can build the connection over ISDN, authenticate etc... But I cannot ping to their server. I think it is caused by the fact that their server has IP address 192.168.10.140, and that the router is filtering these packets going out.
Now I have 2 questions:
1. Is my diagnose correct? (The fact that it is not working because these packets are not routed due to the destination IP address?)
2. Is there a way around this with the router we have?
Routers in the Internet won't route traffic to private address space but they necessarily route to those addresses in private networks. So you probably just need some static/default routes setup on both sides of the connection.
Yes it is right, we are connecting to a private network not the internet. From an other reply I understood that the private address range is not routed when we're talking about the internet, but when we're talking about a private network then it should go through.
On Our 'server' side (NT workstation) I have setup the default gateway to the CiscoPro's ethernet. If I ping from that machine to the their server's address (192.168.10.140), the router opens up a ISDN connection as it should. But I get no reply from the their server. Based upon you answer I'd suspect the routing table setup of their server (I think their server side is a linux server and I also think that no router is involved there, just the linux server). I have enabled the packet logging of the cisco router (log packets verbose or something like that). If I look at the output of that, I only see lines where the 'Flt:' count has some number and all the other values have 0 behind it. So I was guessing that the router filtered the packets out and the problem was at our side. I do not know much about cisco routers so I have used the Cisco Fast step software to setup the router and I have selected that we are connecting to 'a unlisted ISP or corporate network' after that I selected connecting to 'remote corporate network only'. So I guess that the setup is done properly for a corporate network and not for internet use. So the private address range should not be filtered out. But again I may be wrong here.
I dont feel you're using as a external connection. However, if you are connecting thru internet you have nat the ip to public ip address on remote end. If not , check your routing table and see if you have static or dnymaic route in the router. Also, make sure server has default gatway. Hope fully it help you some. If not feel free to contact me.
wait a second, there is no router on their side? how are you dialing into them then? is there some kind of isdn card or serial device on the linux server? have then do a "netstat -r" to see if your server's address is in the routing table of the linux server.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...