Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can not ping sub interface

Status
Not open for further replies.

snootalope

IS-IT--Management
Jun 28, 2001
1,706
US
At the moment, our router has a sub-interface setup like so:

interface FastEthernet0/0.1
encapsulation dot1Q 1 native
ip address 10.10.1.1 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
no cdp enable

My PC has an IP of 10.10.1.12 with the gateway set as 10.10.1.1. I can ping that interface just fine.

Now, I've added another interface:

interface FastEthernet0/0.20
encapsulation dot1Q 20
ip address 10.10.20.1 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
no cdp enable

On my PC, I configured the second nic with 10.10.20.10 and set it's gateway to 10.10.20.1.

Both devices hook up to a cisco switch, which each port has this config:

Router:
!
interface GigabitEthernet0/5
description Router
switchport mode trunk
spanning-tree portfast
!
Switch:
interface FastEthernet0/44
switchport trunk encapsulation dot1q
switchport mode trunk
no ip address
no mdix auto
spanning-tree portfast

I'm unable to ping 10.10.20.1, can someone please help me out and tell me what I'm missing here?
 
ping form your pc? which NIC does the traffic source from?
 
Yes, i can't ping 10.10.20.1 from my pc. It's the second nic in my machine. Both nics in my machine are plugged into the same switch as the router.
 
so where does the source ping come from? you need to have some routing on your box, open command prompt and paste your netstat -r

 
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.10.1.1 10.10.1.12 20
0.0.0.0 0.0.0.0 10.10.20.1 10.10.20.10 20
10.10.1.0 255.255.255.0 10.10.1.12 10.10.1.12 10
10.10.1.12 255.255.255.255 127.0.0.1 127.0.0.1 10
10.10.55.0 255.255.255.0 10.10.20.10 10.10.20.10 20
10.10.55.10 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.10.1.12 10.10.1.12 20
10.255.255.255 255.255.255.255 10.10.20.10 10.10.20.10 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.2.108 255.255.255.252 169.254.2.109 169.254.2.109 30
169.254.2.109 255.255.255.255 127.0.0.1 127.0.0.1 30
169.254.255.255 255.255.255.255 169.254.2.109 169.254.2.109 30
224.0.0.0 240.0.0.0 10.10.1.12 10.10.1.12 20
224.0.0.0 240.0.0.0 10.10.20.10 10.10.20.10 20
224.0.0.0 240.0.0.0 169.254.2.109 169.254.2.109 30
255.255.255.255 255.255.255.255 10.10.1.12 10.10.1.12 1
255.255.255.255 255.255.255.255 10.10.20.10 10.10.20.10 1
255.255.255.255 255.255.255.255 169.254.2.109 169.254.2.109 1
Default Gateway: 10.10.1.1
 
there is your problem: Default Gateway: 10.10.1.1 how can it get to the other network??
 
You would want the router to be your default gateway thus allowing your router to route to the other vlan networks.

I think the problem is in your desktop... If you setup two pc's both on different networks with the router as your GW does it work normally?

You can setup metrics within the NIC this may help!!!


[americanflag] Go Army!
Tek-TIP Member 19,650
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top