On 9/16/24 19:07, Lawrence D'Oliveiro wrote:
Here is a blog post on some of the issues why the old-style commands
don’t really work well any more: the way they get info from the
kernel is inefficient, and their traditional function also no longer
reflects the reality of how the network stack works
I largely agree with the statement. I've not yet looked at the URL.
What I don't understand is why nobody has written a wrapper that sites
in front of `ip` et al. to be called by the more traditional `ifconfig`
/ `route` et al.
Sure, there are differences. But Unix like OSs have used `ifconfig` for
40+ years to configure the network interface. I see zero reason to not
provide basic functionality in a backward compatible way.
I embraced `ip` 10-15 years ago. I've found many things that I can't do
with `ifconfig` which must be done with `ip`.
Conversely I've found a few things that must be done with `ifconfig` as
`ip` doesn't support them, mostly with non-IP protocols; IPX / DECnet / etc.
--
Grant. . . .
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)