Re: ifconfig

From	Richard Kettlewell <invalid@invalid.invalid>
Newsgroups	comp.os.linux.networking
Subject	Re: ifconfig
Date	2024-09-24 08:29 +0100
Organization	terraraq NNTP server
Message-ID	<wwvv7ylcxvw.fsf@LkoBDZeT.terraraq.uk> (permalink)
References	<vc8g75$2m4k0$1@dont-email.me> <vc9t49$2vdno$4@dont-email.me> <vcah85$34j1e$4@dont-email.me> <vct60m$lcd$1@tncsrv09.home.tnetconsulting.net>

Show all headers | View raw

Grant Taylor <gtaylor@tnetconsulting.net> writes:
> 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.

I’m not sure how that would differ from the ifconfig that exists now.

> 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.

Again, how would that be any different from the ifconfig that exists
now?  AFAIK it still works as well as it always did[1], it just can’t
manage some of the more modern stuff.

[1] possibly better; it seems to know about IPv6 now and if memory
    serves, it didn’t use to

-- 
https://www.greenend.org.uk/rjk/

Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

ifconfig faeychild <faeychild@nomail.afraid.org> - 2024-09-16 15:37 +1000
  Re: ifconfig Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2024-09-16 05:46 +0000
    Re: ifconfig faeychild <faeychild@nomail.afraid.org> - 2024-09-17 07:26 +1000
    Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-16 23:57 +0000
      Re: ifconfig Jeremy Brubaker <jbrubake.362@orionarts.invalid> - 2024-10-04 15:26 +0000
      Re: ifconfig Jeremy Brubaker <jbrubake.362@orionarts.invalid> - 2024-10-04 16:25 +0000
        Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-04 20:01 +0000
          Re: ifconfig Jeremy Brubaker <jbrubake.362@orionarts.invalid> - 2024-10-08 15:18 +0000
            Re: ifconfig faeychild <faeychild@nomail.afraid.org> - 2024-10-10 08:11 +1100
              Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-10-10 00:01 +0000
  Re: ifconfig Marco Moock <mm+usenet-es@dorfdsl.de> - 2024-09-16 20:24 +0200
    Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-17 00:07 +0000
      Re: ifconfig Grant Taylor <gtaylor@tnetconsulting.net> - 2024-09-23 20:52 -0500
        Re: ifconfig Richard Kettlewell <invalid@invalid.invalid> - 2024-09-24 08:29 +0100
          Re: ifconfig Grant Taylor <gtaylor@tnetconsulting.net> - 2024-09-24 22:24 -0500
            Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-25 06:45 +0000
            Re: ifconfig Richard Kettlewell <invalid@invalid.invalid> - 2024-09-25 09:18 +0100
        Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-24 21:00 +0000
          Re: ifconfig "Carlos E.R." <robin_listas@es.invalid> - 2024-09-25 07:22 +0200
  Re: ifconfig Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-17 00:02 +0000
  Re: ifconfig not@telling.you.invalid (Computer Nerd Kev) - 2024-09-18 07:46 +1000
  Re: ifconfig Antti Talsta <atalsta@nothingtosee.org> - 2024-09-23 16:46 +0000

csiph-web