No subject

ifconfig/route/netstat, those commands are universal to all *nixes<br>
(yeah, they&#39;re still out there and it isn&#39;t the windows guys that&#=
39;ll<br>
be asked to maintain them) ;) and ip is a huge can of worms for people<br>
that aren&#39;t going there.<br>
<br>
That said, it&#39;s worth bringing up on the examdev list.<br>
<br>
Regards,<br>
<font color=3D"#888888">--<br>
G. Matthew Rice &lt;<a href=3D"mailto:mrice at lpi.org">mrice at lpi.org</a>&gt;=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0 gpg id: EF9AAD20<br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<br>
lpi-discuss mailing list<br>
<a href=3D"mailto:lpi-discuss at lpi.org">lpi-discuss at lpi.org</a><br>
<a href=3D"http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-discuss" target=
=3D"_blank">http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-discuss</a><br=
>
</div></div></blockquote></div><br>Hello,<br><br>Ip route2 is used a lot.<b=
r>You may not see it on a desktop system, but for example I install it on a=
ny system i manage because it does provide a lot of additional features to =
the classic ifconfig : it helps debuging when you have a lot of routes (ip =
route get 1.2.3.4); you can&#39;t do policy based routing without it; with =
ifconfig you have a lot of chances of not seeing additional ip addresses on=
 an interface (not &quot;aliases&quot;); and other things .<br>
<br>On the other side ifconfig will still be there for a long time just bec=
ause there is a lot of stuff referencing it and expecting to parse it&#39;s=
 output.<br><br>Regards<br>

--000e0cdf1be431764304a815ad86--