cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
437
Views
0
Helpful
4
Replies

Interface with 2 addresses into hub routing error

robertsaye
Level 1
Level 1

Hi all,

I have a very basic setup. I have a 2621 with 2 FE ports. On one of the ports, I gave it an IP address of 10.x.x.199/16 (10.2.255.255 is our lab network). Then I gave it another IP address of 192.169.209.2/24. This is an interface on the device I am testing. I run a cable to a netgear hub, then from the hub I have cables to a switch on my lab network and a cable to my DUT.

This seems fairly straightforward so far. Now from my 2621 I can ping anywhere on the 10.2 network. From the 10.2 network, I can ping my Cisco so that connection looks fine.

My issue is on the secondary address. From my DUT I can ping this interface. But from the Cisco, I can't ping my DUT.

Here is my config:

Current configuration : 1056 bytes

!

version 12.2

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname iraq

!

no logging console

enable secret xxx

enable password *******

!

ip subnet-zero

no ip routing

!

!

no ip domain-lookup

!

call rsvp-sync

!

!

!

!

!

!

!

!

interface FastEthernet0/0

ip address 192.169.209.2 255.255.255.0 secondary

ip address 10.x.x.x.255.0.0

no ip route-cache

no ip mroute-cache

duplex auto

speed auto

!

interface FastEthernet0/0.1

no ip route-cache

no ip mroute-cache

!

interface FastEthernet0/0.2

no ip route-cache

no ip mroute-cache

!

interface FastEthernet0/1

no ip address

no ip route-cache

no ip mroute-cache

shutdown

duplex auto

speed auto

!

ip classless

ip http server

!

snmp-server community public RO

snmp-server enable traps tty

!

dial-peer cor custom

!

!

!

!

line con 0

timeout login response 300

absolute-timeout 10000

line aux 0

line vty 0

exec-timeout 0 0

password *******

login

length 0

line vty 1 4

password *******

login

!

end

Any ideas??? Thanks, Robert

4 Replies 4

mehrdad
Level 3
Level 3

Hi,

check extended ping like the below

iraq>enable

iraq#ping

Protocol [ip]:

Target IP address: 192.169.209.x

!--- The address to ping.

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: 192.169.209.2

Regards,

Mehrdad Arshad Rad

That works correctly...

iraq#ping

Protocol [ip]:

Target IP address: 192.169.209.1

Repeat count [5]:

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: 192.169.209.2

Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.169.209.1, timeout is 2 seconds:

Packet sent with a source address of 192.169.209.2

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

iraq#

I have tried adding a route for this, but can't seem to figure out the one I need.

where do you define route?

In fact when you ping your DUT interface, the source address of echo request is primary address of router, it means 10.2.x.x so when the packet receives at DUT, it hasn't any routes for it so if you define default gateway at DUT to secondary address of router (or a route for network 10.2.x.x), the ICMP reply can route to your router and your ping will be successful from your router.

That worked perfect. I added the route

ip route 10.2.4.0 255.255.255.0 192.169.209.2 20/1

And my connectivity is complete. Thank You very much!

Review Cisco Networking for a $25 gift card