Hot Downloads

Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: Confused on ip default-network

Confused on ip default-network 7 years 4 weeks ago #31665

  • pedenski
  • pedenski's Avatar
  • Offline
  • Frequent Member
  • Posts: 75
  • Karma: 0
Guys, I tried searching here but i cant find a topic that clearly explain about ip default-network command. been reading some topics about default-network. But until now, I still dont get the concept behind..



in this picture, you can see the R1 has made a command for ip default-networkm 10.0.0.0, which means it becomes the gateway of last resort to network 10.0.0.0




in here, when we check on R3's routing table, we can see that the gateway of last resort is R1 to network 0.0.0.0


so a ping confirms that it can connect outside.
means that when a packets destined for another subnet it uses the link to R1 to reach 10.1.1.1

But a ping to 168.13.200.1 fails!?! how come ?!?! ~__~


so the book says, that if you configure an ip classless command
itll eventually make a successful ping..

now my question is, if ping 10.1.1.1 can be reached using R3, using the default route of R1 to connect outside.. then how come a ping to 168.13.200.1 fails which has a default route to R1 also.
but after configuring an ip classless the ping works..

i dont really get the logic behind it..
The administrator has disabled public write access.

Re: Confused on ip default-network 7 years 4 weeks ago #31679

  • Perlhack
  • Perlhack's Avatar
  • Offline
  • Frequent Member
  • Posts: 49
  • Karma: 0
What about layer 2 in this case? If you are running "no ip classless" it does not impact the routing table but does impact routing decisions when using VLSM. The routing decision can only account for 168.13.0.0 (this is how 168.13.200.1 is being accounted) because of "no ip classless". Every interface on R3 is in the major net. The decision for ethernet is to ARP for this address or inverse arp on your frame-relay serial link. There is no routing if it "thinks" the network is directly connected. It can route via the default route to the 10.1.1.1 address because there is no directly connected 10 network on the router. If you put a loopback interface on R3 of 10.100.100.100/8 with "no ip classless" can you still reach 10.1.1.1 via R1?

Enter "ip classless" and now routing decisions can be made with VLSM, and it can account for all the networks as they show in the table. It can see past the major net block.

Cheers,
PH
The administrator has disabled public write access.

Re: Confused on ip default-network 7 years 3 weeks ago #31684

  • pedenski
  • pedenski's Avatar
  • Offline
  • Frequent Member
  • Posts: 75
  • Karma: 0
are you saying that the routing protocol being used doesnt know about VLSM?

im sorry but i dont get your point.. im very slow.. >,<
The administrator has disabled public write access.

default network 7 years 3 weeks ago #31686

It seems that, the pic you posted is from Cisco press book ICND-2, and for complete network diag see page no.186, under topic static route

From your given conf. it is clear that R3 learns a default route from R1 using RIP, R3 lists the destination of the default route (0.0.0.0) and the next-hop router, which is R1 in this case (168.13.100.1), as highlighted in your pic.

In your 2nd pic R3 is configured to use classful routing.
With classful routing, the router first matches the Class A, B, or C network number in which a destination resides. If the Class A, B, or C network is found, (In R3 show Ip route command showing 168.13.0.0 network i.e. found in R3 routing table) Cisco IOS Software then looks for the specific subnet number. If it isn’t
found, the packet is discarded, as is the case with the ICMP echoes sent with the ping 168.13.200.1 command.

However, with classful routing, if the packet does not match a
Class A, B, or C network in the routing table, and a default route exists, the default route is indeed used—which is why R3 can forward the ICMP echoes sent by the successful ping 10.1.1.1 command.

after confuguring IP classless command, In classless routing Cisco IOS Software looks for the best match, ignoring class rules. If a default route exists, with classless routing, the packet always at least matches the default route. If a more specific
route matches the packet’s destination, that route is used.

I hope so this explanation will help you to clear your concept.

Regards,
Swapnil

[/img][/list]
The administrator has disabled public write access.

Re: Confused on ip default-network 7 years 3 weeks ago #31687

  • pedenski
  • pedenski's Avatar
  • Offline
  • Frequent Member
  • Posts: 75
  • Karma: 0
In your 2nd pic R3 is configured to use classful routing.

how can you tell if the router is using a classful? is it because its using RIP? or because the ip default-network 10.0.0.0 is configured?
The administrator has disabled public write access.

Default Network. 7 years 3 weeks ago #31720

Dear, In your 2nd pic it is absolutely showing that, R3 configured with classful routing.

see the sentence :-
168.13.0.0/24 is subnetted, 4 subnets

Also network diag. showing that entire network is a classful network.

Regards,
Swapnil
The administrator has disabled public write access.
  • Page:
  • 1
  • 2
Time to create page: 0.083 seconds

CCENT/CCNA

Cisco Routers

  • SSL WebVPN
  • Securing Routers
  • Policy Based Routing
  • Router on-a-Stick

VPN Security

  • Understand DMVPN
  • GRE/IPSec Configuration
  • Site-to-Site IPSec VPN
  • IPSec Modes

Cisco Help

  • VPN Client Windows 8
  • VPN Client Windows 7
  • CCP Display Problem
  • Cisco Support App.

Windows 2012

  • New Features
  • Licensing
  • Hyper-V / VDI
  • Install Hyper-V

Linux

  • File Permissions
  • Webmin
  • Groups - Users
  • Samba Setup