Network Engineering Stack Exchange is a question and answer site for network engineers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am looking a L2/L3 switch spec. which says it supports 256 Router Legs and maximum of 32 Static routes.

Can somebody explain with an example, what is the difference between router leg and static route?

share|improve this question

By "router leg" they mean a (directly) connected route (and use a strange way of putting it).

What is a connected route compared to a static route?

Connected route (router leg)

A connected route is a route that points to an interface. For example if you configure on (ethernet) interface Gi0/1 the directly connected route (the "router leg") is

If the router wants to send a packet to a host in the network it will do a L2 (Layer2) lookup (ARP for IPv4, ND for IPv6) on the Gi0/1 interface to find the MAC address of the host. It will then send the packet to the MAC address.

One-liner: Connected routes point to an interface, next-hop for packet will be resolved at L2 by ARP/ND on the respective interface.

Static route

A static route points to an IP address. For example you could have route pointing to The router will send packets for hosts in the network to

For this to work itself must be part of a connected route so that the router can find the right L2 next-hop for the packets.

One-liner: Static routes point to an IP next-hop. The IP next-hop itself will be resolved by L2 lookup on the interface the connected route for the next-hop points to.

One thing you should ask your vendor: If the specs are for IPv4 and for IPv6, and if not how many IPv6 routes you can have for each of the different types.

share|improve this answer

In addition, static route can also point to a local interface.

1- Static with next-hop as a local interface:

Example: ip route G0/1

For every destination in, the router will consider it directly connected to G0/1 and will send an ARP request, and will add an ARP entry when responded.

2- Static with next-hope as IP

Example: ip route

Now, the router does not need to send an ARP request for every destination in, the router will use the L2 address of next-hop (will resolve it once and then re-use ARP cache)


"interface as next-hop" will build huge arp table and its not recommended if local interface (G0/1) connects to a huge network like internet provider or ISP gateway router. ARP table will keep increasing for every new destination on the internet and will eat up all the memory to a chocking point. Its ok to use on a p2p connection though. And it also requires proxy-arp to be enabled on the gateway router.

"IP as next-hop" on the other hand uses a single ARP entry, thats is for the gateway IP (

share|improve this answer
The next-hop as interface is a feature that not all vendors support. On Cisco you can do it (on some platforms), but Juniper for example has no such feature. – Sebastian Jul 7 '14 at 8:03
good to know, thanks – dragon Jul 23 '14 at 11:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.