cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2514
Views
5
Helpful
23
Replies

Connecting to Cisco routers together

markwieseler
Level 1
Level 1

I'm trying to connect to routers together. Here is my configs. Please help..

interface GigabitEthernet0/0

ip address 192.168.192.57 255.255.255.0

duplex auto

speed auto

media-type rj45

no mop enabled

!

interface GigabitEthernet0/1

ip address 192.168.104.1 255.255.255.0

duplex auto

speed auto

media-type rj45

no mop enabled

!

interface FastEthernet1/0

ip address 192.168.96.1 255.255.252.0

duplex full

speed 100

no mop enabled

!

interface FastEthernet1/1

no ip address

shutdown

duplex auto

speed auto

!

interface FastEthernet2/0

no ip address

shutdown

duplex auto

speed auto

!

interface FastEthernet2/1

no ip address

shutdown

duplex auto

speed auto

!

ip forward-protocol nd

ip route 0.0.0.0 0.0.0.0 192.168.192.24

ip route 192.168.104.0 255.255.255.0 192.168.104.2

no ip http server

no ip http secure-server

!

!

!

ip access-list standard delete

interface FastEthernet0/0

ip address 192.168.103.3 255.255.255.0

ip nat inside

ip virtual-reassembly

duplex full

speed 100

no mop enabled

!

interface FastEthernet0/1

ip address 192.168.104.2 255.255.255.0

ip nat inside

ip virtual-reassembly

duplex full

speed 100

no mop enabled

!

router rip

version 2

network 192.168.104.0

!

ip forward-protocol nd

ip route 192.168.104.0 255.255.255.0 192.168.104.1

ip route 192.168.148.0 255.255.252.0 192.168.103.10

ip route 192.168.192.0 255.255.255.0 192.168.103.10

23 Replies 23

Peter Paluch
Cisco Employee
Cisco Employee

Mark,

You must provide more details. You have just pasted excerpts of two configuration files (not even properly separating them) and you have given us absolutely no clue as to what is the problem you are trying to solve, what have you already tried, what are the relevant command outputs and so on. We can't even try to help you further if you do not provide more specific information.

Best regards,

Peter

gig0/1 of the top config to fas0/1 of the bottom config? is that the connection between the two that isn't working?

i'm guessing the TWO 'ip nat inside' statements on the bottom config aren't helping.

Sorry about that. This is my first time posting something like this.

I have a swtich that is configured with a ip of 192.168.103.7 and I have plug a network cable into the switch and the other end into GE0/1 with a ip address of 192.168.104.1. interface GigabitEthernet0/0

ip address 192.168.192.57 255.255.255.0

interface FastEthernet1/0

ip address 192.168.96.1 255.255.252.0. The 103 switch is our QMOE switch. At the other end I have another router that I configured with a address of 192.168.104.2. From router to router I can ping the 104 network. My test workstation is on the 192.168.192.0 network and I can't ping the 104 network. Sorry so long

Hi Peter, Sorry about that. This is my first time posting something like this.

I have a swtich that is configured with a ip of 192.168.103.7 and I have plug a network cable into the switch and the other end into GE0/1 with a ip address of 192.168.104.1. interface GigabitEthernet0/0

ip address 192.168.192.57 255.255.255.0

interface FastEthernet1/0

ip address 192.168.96.1 255.255.252.0. The 103 switch is our QMOE switch. At the other end I have another router that I configured with a address of 192.168.104.2. From router to router I can ping the 104 network. My test workstation is on the 192.168.192.0 network and I can't ping the 104 network. Sorry so long

Hi Pete, Do you need anyother information from me?

Mark,

I see a number of problems in the configuration of both your routers. I will call them in the order of their configs as "R1" (first router) and "R2" (second router).

1.) The R1 does not seem to run any routing protocol and it is missing the route to the 192.168.103.0/24 network which is located at R2. The route to the network 192.168.103.0/24 shall be added on R1 statically or a routing protocol shall be used. If you decide to configure it statically, use this command on R1:

ip route 192.168.103.0 255.255.255.0 192.168.104.2

2.) The R2 contains a static route back to the network 192.168.192.0/24 but it seems to point towards an incorrect next hop. Correctly, the static route on R2 towards 192.168.192.0/24 should be configured as follows:

ip route 192.168.192.0 255.255.255.0 192.168.104.1

3.) The configuration of both R1 and R2 contains a static route to the network 192.168.104.0/24. This configuration shall be removed from both routers. The network 192.168.104.0/24 is a directly connected network and configuring it statically does not make any sense.

4.) The R2 runs the RIPv2 routing protocol. However, it seems to be largely useless because the R1 does not run RIPv2 and also, the network 192.168.103.0/24 is missing from the RIPv2 configuration on R2. Correctly, the configuration of RIPv2 on R2 should be as follows:

router rip

version 2

no auto-summary

network 192.168.104.0

network 192.168.103.0

! other networks that we want R1 to know about

The R1 should be configured at least as follows:

router rip

version 2

no auto-summary

network 192.168.104.0

If you decide to run RIPv2 on both routers, remove the static routes from both routers as they will take precedence over RIPv2-discovered routes.

I suggest correcting these errors before moving on.

Best regards,

Peter

Hi Peter, Thanks I will give this a try and let you know. Thanks

Hi Pete, I did step 3 and 4 and on 4 I removed the router rip stuff on R2. I put in the ip route 192.168.103.0 255.255.255.0 192.168.104.2 on R1 and didn't put the ip route 192.168.192.0 255.255.255.0 192.168.104.1 on R2 and I still could n't ping the 104 network from the 103 network. Please help

Mark,

Can you do the show ip route on both routers and post the output here?

Also, a complete configuration in the present version would be helpful. You may post it here as attachments.

Best regards,

Peter

Here are both configs on both routers. Thanks

Mark,

First, remove the ip nat inside commands from the interfaces Fa0/0 and Fa0/1 on the 2800 router.

Second, on your 3800 router, you are missing route to the network 192.168.103.0/24. That means that while your packets from the network 192.168.103.0/24 can reach the 3800 router when you ping 192.168.104.1, it does not know where to send replies. According to its routing table, it sends the replies using its default route out via 192.168.192.24 which is obviously incorrect. Therefore, add this command to the configuration on the 3800 router:

ip route 192.168.103.0 255.255.255.0 192.168.104.2

Let me know if it started working.

Best regards,

Peter

Hi Peter, I will try this in about 15 min and let you know.

Hi Peter, Still a no go. Here what it is when I do the ip route. We do have one Sonicwall on we side. Could there be a route in there that messing this up? I also did remove the nat stuff on the 2800. Thanks

Mark,

At least the routing table looks correctly now.

Okay, let's try this one. On the 2800 router, try using these two commands:

ping 192.168.104.1

ping 192.168.104.1 source fa0/0

The first command should succeed. The second command will send pings using the source address from the interface fa0/0, that is, 192.168.103.3. I am very interested in knowing if the second command also worked.

Best regards,

Peter

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco