37 ms·
There are real reasons for Linux to replace ifconfig, netstat, etc
- fb03 8y agoIt's pretty clear that ip is the superior and more modern tool, i believe they could work on the presentation layer of the software tho... its output pales compared to ifconfig, as other peers have stated. that's what really gives us grumpy old sysadmins the kneejerk reactions. every time i log into a system and i have to tipo "ip a" i need to stop and try to slowly decode the unformatted soup letter that is presented instead of a nicelly formatted table like on ifconfig.
- sverige 8y agoI hear this argument a lot: this or that is the "more modern tool." The problem is I almost never see the benefits in the same way I can tell how, say, a battery-powered nail gun is superior to hammering hand-held nails. Usually it's just a hammer with a cross peen instead of a claw, painted a different color.
- ccnafr 8y agoBack in 2005 I was actually wondering why ipsuite wasn't part of standard Debian, tbh, which at the time was very big in the networking world
- tannhaeuser 8y agoIsn't the described mismatch between "reality" and what ifconfig reports once again a case of systemd (networkd) not exposing IP aliases in the traditional way, and replacing established network concepts by it's own stuff? Meant as a genuine question rather than trolling (though I know I'd hate to bow to whatever systemd comes up with rather than just using ifconfig which has worked since the begin of times) eg. there might be a material problem here in how network interfaces are presented by ifconfig.
- chousuke 8y agoNo. systemd has nothing to do with this. the issue has existed long before systemd. it's the kernel that changed to allow interfaces to have alias addresses.
- zaarn 8y agoNot that I know. Systemd itself doesn't manage networking (resolved, networkd and other services do that instead under the SD umbrella). But those work (to my knowledge) just like before (unless you setup private networking or otherwise container the thing). They just work differently on the surface. I wouldn't know of a way of exposing IP aliases in a non-traditional way as the kernel needs to know them either way.
- JdeBP 8y agoNo. The Linux kernel has two APIs, and has had since before systemd even existed. ifconfig uses the ioctl() API, which presents the concept of alias IP addresses in one way. ip uses the netlink API, which presents the concept of multiple IP addresses per interface in a different way. M. Siebenmann did include this point. * https://sourceforge.net/p/net-tools/bugs/12/ https://sourceforge.net/p/net-tools/bugs/12/ * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=359676 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=359676
- poizan42 8y agoThis begs the question of why the kernel doesn't allocate an alias for backwards compatibility when adding IP adresses through the netlink API.
- brazzledazzle 8y agoI think they are fundamentally different things. Correct me if I’m wrong, but I think a netlink alias is just an additional address and an old-school alias is more like a virtual interface.
- dvfjsdhgfv 8y agoFortunately, not in this particular case - it's just a question of incompatibility between the two APIs. If you create an alias by ifconfig eth0:0, it will be visible by ifconfig. If you add a NIC:n entry to /etc/network/interfaces, ifconfig will display it. I don't believe this API will ever get obsoleted as millions of systems use it that way.
- AnnoyingSwede 8y agoI noticed some shortcomings in ifconfig (only shows the first ip assigned to an interface if a NIC has many) so in some senses i see why it had to be updated, by i see no logical reason why both the command and the syntaxes had to change? Why not stick to the parameter standard at least?
- Xylakant 8y agoif you're changing underlying functionality, you'll have to change at least some of those parameters ("show me the first IP address" of an interface might be a contrived example). So now you have the option to slightly change the parameters and keep some, but not all of the behavior, maybe even in a slightly different way or you can have a clean break and clean up the old parameter list with all its accumulated cruft and go for a designed and thought-out interface.
- berti 8y agoThe new interface is close to plain english in most common cases, so I'd say it's a significant win.
- rmu09 8y agoWhat's all the fuzz about this "sudden" change? iproute2 is part of linux (kernel) since 1999 or so.
- exikyut 8y agoIt promptly got filed under "ah, learn that one day", then after coming up enough times got relegated to "ugh, stop bothering me about it, I'll get to it eventually" and everyone has been un-motivated-ly unimpressed about it ever since. I think.
- toxik 8y agoFWIW I can usually never get ifconfig to do what I want it to, but with ip it's usually fairly straight-forward.
- kankroc 8y agoArchlinux ships this as default now (and has for about a year) and I think Ubuntu is doing the same. Thus people are increasingly being exposed to iproute2.
- aepiepaey 8y agoI'm all for the new tools (and actually prefer ip over ifconfig). However, they really screwed up with ss: the output is really unusable/unreadable. This really only becomes obvious when you pass the -p flag, where the program information is printed on its own line. It gets slightly better if you pipe the output through cat: now the program information is printed on the same line, but the column spacing is incorrect instead. On the other hand it's nice that they kept compatibility, at least for the most common flags (e.g. -nltp does the same thing in both).
- mandelbulb 8y ago>This really only becomes obvious when you pass the -p flag, where the program information is printed on its own line. It isn't on its own line, it's just wrapped so grep works properly. >but the column spacing is incorrect instead. ss output is column-based so it is useless to bother with tools like cat for parsing. ss -p | less -S is the simplest solution for you
- aepiepaey 8y agoWhat? No. First: Apparently the ss developer(s) decided to finally fix the output in some recent version (it was changed to behave sanely somewhere between iproute2-ss161212 and iproute2-ss180402). However, if you're stuck with an older version, what I said still stands, and the below applies to those versions: > It isn't on its own line, it's just wrapped so grep works properly. While technically correct, that doesn't really matter in any practical sense, because the columns are padded so that the final column containing the program is wrapped onto the next line. When ss stdout is connected to a pipe it will produce different output: this output is much less wide, so that the program name fits onto the same line as the rest of the columns. But, as said previously, it screws up the alignment of the columns, making it impossible to quickly scan them (using your eyes). > ss output is column-based so it is useless to bother with tools like cat for parsing. What? cat doesn't do any parsing. The only reason for using cat there is to connect ss' stdout to a pipe and thus trigger its different output. > ss -p | less -S is the simplest solution for you No. '| less -S' gives no improvement over '| cat', since ss output fits onto one line without wrapping as soon as you pipe it through any other program. An actual improvement would be to instead use '| column -t', which would (mostly) fix issues with misaligned columns. Anyway, if you can, just use a modern enough ss instead (not sure when it was fixed, but iproute2-ss180402 (iproute2 4.16.0) is definitely new enough), which has sane output regardless of whether stdout is connected to a pipe or terminal.
- mercora 8y agothis makes it sound like the only thing ip does is replace ifconfig which is not the case. It is more like like a go to application to manage the network stack to some degree. You can set up various tunnel interfaces, vlans, routes, routing rules, IPsec policies, network namespaces and more. Learning how to deal with it gets you quite far. Learning how to read the help output is often enough to understand everything and definitely worth the effort, even if all you want to do is to show the assigned IP addresses... I also appreciate very much the mostly consistent syntax for various sub commands. Its often an easy guess to know how to do what...
- joosters 8y agoLearning how to read the help output is often enough I find the 'ip --help' is virtually incomprehensible, and the man page no better. There's no explanation about what the tool can do, only some machine-readable formatting of the syntax expected. This kind of documentation is useless IMO, it's actively hostile to new users.
- mercora 8y agothe help gets more specific the more complete your command gets. Try "ip link add type vlan help" for example. While i agree it does nothing to explain what the various switches do, if you know what you are trying to achieve this is most of the time enough. However i do not agree about the man pages the switches are explained there in enough detail in my opinion...
- joosters 8y agoThe switches are useless until you have an idea about what the command can do. And yet the 'IP - COMMAND SYNTAX' section has text like 'link - network device'. What the hell does that mean? So 'ip link' does what exactly? Could the developers have typed more than just two words to try to explain this command (action?) Good luck to anyone who decides to RTFM.
- sdfgdfhjdgj 8y ago
- intsunny 8y agoWhy did they have to make the output of `ss` so cumbersome? I often end up installing the legacy tooling just so I can have `netstat`
- dullgiulio 8y agoI'm a fan of 'lsof -i', in fact of lsof for anything. Makes lots of sense to treat network sockets and files as equals: that's the big idea of UNIX.
- mseebach 8y agoIt seems like a missed opportunity not to have a JSON (or other explicitly machine readable format) output option for easy scripting use through jq. Every time I need to craft a grep regex to get some trivial piece of information from one of these tools, I feel there's a bug waiting to happen (and I'm usually right).
- tracker1 8y agoI'd appreciate it... would also make generating pretty UIs around console applications easier as well.
- mvdwoord 8y agoPowershell is on linux now... ;)
- snaky 8y agoThe most underrated tool barely used outside of Windows sysadmin world.
- kchr 8y agoIn what capacity is Powershell something other than just another shell (of your choice)? Feela like Windows finally got a real CLI for API stuff - and O am glad this happened - but it's not really any different than csh, bash, zsh et cetera. A shell as a lower-level interface to your OS.
- deleted 8y ago[deleted]
- simias 8y agoI'm trying hard to fight my old muscle memory to use ip instead of ifconfig on Linux. I have a few issues though: * "ip" is useless as a keyword if you're looking for help online. It's extremely frustrating and probably my main issue actually learning how to use the damn thing. * ifconfig's output is simply more readable IMO: https://svkt.org/~simias/up/20180525-113825_ip-vs-ifconfig.png https://svkt.org/~simias/up/20180525-113825_ip-vs-ifconfig.p... . It's pretty weird that a brand new tool manages to have worse output than a venerable old unix command. Because of this I often end up configuring the network with ip only to double-check everything is right with a quick ifconfig. That's silly. I think at this point I would've preferred if they had made an "ifconfig2" instead, mostly identical to the old one but with a few breaking changes to add the missing functionality. An incremental update instead of a full rewrite. There's definitely some NIH going on.
- Faaak 8y agoExactly. Even the `ip` name is misleading as the command does much more than only ip-related things (link layer, network namespaces, tcp, …).
- nailer 8y agoAlways wondered about this - is IP 'internet protocol' or something else, since it's much lower level than IP? I've been using IP route 15 for 15, maybe 20 years now and hinestly have no idea.
- sverige 8y agoYes, it is 'internet protocol' [0] and part of TCP/IP.[1] [0] https://en.wikipedia.org/wiki/Internet_Protocol https://en.wikipedia.org/wiki/Internet_Protocol [1] https://en.wikipedia.org/wiki/Internet_protocol_suite https://en.wikipedia.org/wiki/Internet_protocol_suite
- nailer 8y agoI know what IP is. Your reference doesn't answer the question as to whether 'ip' means IP.
- IshKebab 8y agoMaybe in new tools they should randomly change the formatting every run so that people can't parse the output.
- sureaboutthis 8y ago"... an ongoing effort to obsolete the old, cross-Unix standard network administration and diagnosis commands of ifconfig, netstat and the like and replace them with fresh new Linux specific things like ss and the ip suite." Old does not mean bad but Linux chooses that path as it moves further away from UNIX and being a Unix-like system in its pursuit to be Windows.
- dijit 8y agoI would like to argue with you, but then again, systemd exists (and is thriving) while being the most windows-like software existing by default on all popular linux distributions. EDIT: I guess I have to clarify this statement a little; In Windows the concept of "logging" is up to the event manager, this mirrors journalctl. To be more precise they seem to focus on desktop operating systems with an example being the unit file itself: "The syntax is inspired by XDG Desktop Entry Specification .desktop files, which are in turn inspired by Microsoft Windows .ini files.", maybe you prefer talking about firewalld and it's "Zones" which are clearly inspired by desktop use. (Laptops more specifically). There was something that I'm forgetting though, a terminology that was only used by microsoft to describe something and systemd used exactly the same terminology. It was very esoteric terminology though, I'm trying to find a reference.
- xtrapolate 8y ago> "Old does not mean bad" It doesn't automatically mean "good" either. > "in its pursuit to be Windows" Would you please elaborate?
- gerbilly 8y agoWindows subsumes a lot of small network daemons into a monolithic process called SVCHOST.EXE. Systemd does a similar thing.
- sdfgdfhjdgj 8y agoOh come on, this FUD is getting old. At least make up something new from time to time.
- snom380 8y agoI find it more frustrating that network configuration tools seem to be added in layer after layer, like with the new netplan took in Ubuntu. To me it seems more complex than it needs to be.
- userbinator 8y agonew netplan took in Ubuntu Having fought that monstrosity very recently, I completely agree. The homepage of its site looks more like a marketing blurb than anything else, and everything about it has an unpleasant "enterprisey" feel to it. I don't care about YAML or "abstract network renderers" or whatever buzzword-compliance bingo it claims to support, I just want to configure one NIC for one static IP. The fact that Windows' networking configuration is actually easier than on "modern Linux" should be a sign that something has gone horribly wrong.
- blackhaz 8y agoWhen I started learning Linux when it was, I think, 0.99, I appreciated that so many commands where cross-Unix. It was a Unix lookalike. I could watch how something is done on one Unix, type this stuff into my Linux terminal, and get an equivalent result in Linux, and this helped a lot and created a sense of community. Now I see that Linux tears the standards apart, there are more and more obstacles with porting complex applications. More over, we can also see the emergence of "we support Ubuntu only, sorry" mentality - Linux became very diverged. I'm so happy to be using FreeBSD now on all my boxes, with it's init, ifconfig, file system hierarchy.
- maltalex 8y agoConsistency is great, but there’s a trade off between consistency and innovation. In a sense, what you’re describing is stagnation.
- moviuro 8y agoOpenBSD's ifconfig did not stagnate. It handles aliases, bridges, wifi, etc. No, the issue is that no one at GNU or Linux cares about correct, simple tools (2 APIs for networking in the kernel?! What happened to manpages?! WTF info?). And thanks to that it runs on anything. Pick your poison https://man.openbsd.org/ifconfig.8 https://man.openbsd.org/ifconfig.8
- JdeBP 8y agonet-tools is not a GNU software package, note. * https://sourceforge.net/projects/net-tools/ https://sourceforge.net/projects/net-tools/ * https://www.gnu.org/software/software.html https://www.gnu.org/software/software.html
- rkeene2 8y agoI'm not sure what the point you are making here is. The developers behind "ifconfig" on Linux could support the new API (iproute2) just as the developers behind "ifconfig" on OpenBSD updated their software to support the new kernel API as they became available.
- pulsarpietro 8y agoI am not sure it is such a big deal, the old stuff are good enough for the majority of cases, I reckon. He has probably a good point about performance, but pain versus gain I am not sure it makes a lot of sense, on average.
- klaasvakie 8y agoI've never understood the purpose of IP aliases like the "secondary em0" the author is setting up with systemd.networkd. These aliases are practically useless, you cannot bind() to them without knowing the IP, you cannot use them in firewall rules, you cannot setup dhcp for them etc. What are people using them for? I'm not sure what the low level difference is between an alias like in the article, or a "eth0:1" type alias (made with ifconfig eth0:1 xx.xx.xx.xx up), but the "eth0:1" type alias seems infinitely more useful. This is also a major deficiency of the Ubuntu 18.04 netplan implementation, it can only do the systemd.networkd type aliases and not the "eth0:1" type ones. What gives?
- linuxguy2 8y ago> What are people using them for? In my case, keepalived VRRP floating addresses.
- brazzledazzle 8y agoYep. It was kind of funny watching a couple graybeards trying to figure out how keepalived was assigning addresses and how to view them. It’s a rare treat when you can help someone like that with something they might normally help you with.
- vidarh 8y agoI've used eth0:xx style aliases for that for a decade with no problem. Do you know what the difference is?
- nailer 8y agoDont know, but when I used to do index arb trading they had vlans on virtual IPs on bonds and ifconfig simply couldn't show the addresses. 'ip' could
- dozzie 8y agoYeah, your eth0:xx is just a label (a tag of sorts) attached to the entry. Otherwise, they're exactly the same thing. You can even add an address with `ip addr add' that will be visible to ifconfig.
- wruza 8y agoWhile unrelated to subj or that new systemd wave, I want to state that almost all my sysadm skills are lost. Idk who is responsible for this and if they exists, or is it just time going, but I’m not a power user anymore. Long-term skill investments without a profession are so meaningless – ten years and you stare at the screen with no idea what to do. That was hard time and now it is all for nothing.
- gaius 8y agoI am happy to reinvest the time if the new way is significantly better, it would be worth it. But it never is, someone just got bored and decided to reinvent the wheel. Probably while thinking that they were inventing it for the first time. And we all get dragged along.
- fapjacks 8y agoBut it was adopted on it's merits and not because of politics! /s
- VLM 8y agoIf you were a productive unix sysadmin in 2008 you are a productive unix sysadmin in 2018. Its just that Linux is no longer unix-like and you've switched from using, perhaps, Debian install media in '08 to FreeBSD install media in '18. Its not really that big of a problem. Its much easier and more productive to switch to FreeBSD than to switch to ... whatever it is Linux is becoming.
- jrnichols 8y ago> If you were a productive unix sysadmin in 2008 you are a productive unix sysadmin in 2018. Unless you mention Perl to someone now, and that someone might be 10 years younger but still your manager, and they look at you like you just spoke greek.
- sverige 8y agoHa ha! Perl has become the shit test for whether I feel like dealing with certain people. "Oh, you don't use Perl?...." Not everyone, just certain ones.
- Communitivity 8y agoOk. Fully admit, old unofficial sysadmin here (50, started with computers at 10 - and I don't work as a sysadmin, but often wind up helping our sysadmin who has less experience). ifconfig, netstat, lsof are some of my top go to tools. I haven't learned the iproute suite of tools yet, but this article is prompting me to start doing that. It will be hard, my memory is fuzzy on when net-tools commands first came out..I remember using Slackware in mid 90s, but don't remember if they were in there yet, but I think I've maybe been using them for 20 years, or close to it.
- unrequited 8y agoThis is slightly off topic. Netflix has transformed the output of netstat to have more immediate visibility. Its good to have something like this. https://imgur.com/a/g8P2Nm2 https://imgur.com/a/g8P2Nm2
- brazzledazzle 8y agoThat’s pretty neat actually. Thanks for sharing.
- JdeBP 8y agoM. Siebenmann's actual main point, ignored by much of the "I do/do not like ip/ifconfig." discussion here, is that it is valid to replace ifconfig because the standard output of the command is an interface contract that is set in stone because of people using it in scripts. I disagree, on two grounds. Firstly, the ifconfig commands in the BSDs are existence proofs that this is not so. The BSD people actually have modified ifconfig to keep up with changing kernel networking abilities, and one will find the (say) FreeBSD ifconfig of today having a lot more functionality than the Linux one. The BSDs, by their very natures, kept their ifconfig tools aligned with the rest of the operating system as it changed. * https://freebsd.org/cgi/man.cgi?query=ifconfig https://freebsd.org/cgi/man.cgi?query=ifconfig * https://linux.die.net/man/8/ifconfig https://linux.die.net/man/8/ifconfig * https://unix.stackexchange.com/questions/319350/ https://unix.stackexchange.com/questions/319350/ Secondly, an aversion to breaking (badly designed) scripts is isn't really the reason that ifconfig hasn't been changed. The reason that ifconfig hasn't been changed, as evident from the net-tools bug and other discussions of this, one of which I have hyperlinked elsewhere in this discussion, is more to do with (purportedly) doing things portably and not having two disjoint code paths, one for Linux using netlink and one for everything else using ioctl. Two code paths and code that was not portable to other operating systems would be the result of adding netlink capability to net-tools's ifconfig. That reason does not itself hold water, however. The net-tools package is highly Linux-specific anyway, in the first place, so arguments about its portability are moot. Given that, the actually expressed reason for not doing this given by the developers themselves (as opposed to the differing reasons inferred by people other than the developers, the most often given one of which is directly contradicted by git repository activity as recent as 2016) founders. * https://github.com/ecki/net-tools/commits/master https://github.com/ecki/net-tools/commits/master One of the more disappointing things about Linux's ifconfig is that this: # ifconfig lo inet6 ::1 Don't know how to set addresses for family 10. # is a fairly trivial oversight in a case statement in the code, a missing case for AF_INET6, rather than a fundamental design or implementation problem, and doesn't even need the netlink API to fix. * https://sourceforge.net/p/net-tools/code/ci/master/tree/ifconfig.c#l978 https://sourceforge.net/p/net-tools/code/ci/master/tree/ifco... * https://sourceforge.net/p/net-tools/code/ci/master/tree/ifconfig.c#l807 https://sourceforge.net/p/net-tools/code/ci/master/tree/ifco...
- 8y ago
- iod 8y agoTIL: iproute2 has a color, a brief/human mode, and a one-line mode. I think I am going to be aliasing ip -color to ip from now on. $ ip -br -c a # ip -brief -color address lo UNKNOWN 127.0.0.1/8 ::1/128 eth0 DOWN wlan0 UP 192.0.2.1/24 2001:db8::1/64 fe80::1/64 $ ip -br -c l # ip -brief -color link lo UNKNOWN 00:00:00:00:00:00 <LOOPBACK,UP,LOWER_UP> eth0 DOWN 00:12:34:56:78:9a <NO-CARRIER,BROADCAST,MULTICAST,UP> wlan0 UP 12:34:56:78:9a:bc <BROADCAST,MULTICAST,UP,LOWER_UP>
- berti 8y agoThanks! Just aliased that in my .zshrc. The route object doesn't seem to do colouring sadly.
- amyjess 8y agoYou may want to consider installing cope, which colorizes the output of a number of common commands, including 'ip route'.
- agumonkey 8y agoTLDRRTFM of the day
- majewsky 8y ago"read read"?
- dak1 8y agoThis is a good reminder that defaults should be simple and human readable. Advanced options should be behind flags for power users, not the other way around.
- piotrkubisa 8y agoIndeed. I don't get it why `ip` has -brief which is not a default behavior and why -verbose flag does not exist. Also there could be a -no-color instead of -color flag.
- SCHiM 8y agoI've lost much muscle memory and skill with newer systems. When I was younger I had time for deep dives into configs/manuals/googles/mailthreads. These days my job assumes I know all the stuff and ins and outs, not having a good time re-learning everything I already know how to do... It's not new anymore and gives no joy for learning new things, no time to do it either. It sucks.
- freehunter 8y agoYeah I don’t buy into the idea that because there were some under-the-hood changes that had to be made, that means the whole application has to be thrown away and a new interface re-written. I don’t believe for a second that these developers couldn’t have dropped in a new backend and mapped the same commands to it. Putting a shinier coat of paint on the command line isn’t going to attract a wider audience, it’s just going to piss off the only people who actually use the command line regularly. The CLI is the last place you want “change for the sake of change”.
- fhayde 8y agoIMO, it's because understanding someone else's code and introducing your own changes is something that requires a considerable amount of experience and knowledge which many new developers have not acquired yet. Instead of trying to take the time to understand how to integrate the changes they're trying to make with an existing project, they create something new practically centered around this new feature and a lot of stuff gets lost along the way. At the end of the day, it's fine though. It'll either satisfy the needs of people and become a new standard or it will be satisfy edge cases and become the new thing that needs to be deprecated because no-one contributes to the project and the original maintainer has lost interest.
- NVRM 8y agoMy ancestors didn't use SS: they killed them.
- ptx 8y agoSo, to summarize, ifconfig has to be replaced because it relies on the /proc filesystem and it doesn't handle aliases? This is easily disproven: ifconfig on FreeBSD doesn't rely on /proc and handles aliases just fine. It sounds a bit like the whole OSS/ALSA discussion – some argued that ALSA was needed to replace OSS because OSS didn't support muxing multiple simultaneous audio streams, but strangely OSS on FreeBSD did support it, with no need to replace the entire audio API.
- viraptor 8y agoIsn't ifconfig on BSD just an app that happens to share the name and some syntax with the Linux ifconfig? You could map most ifconfig operations to netlink and away from /proc, but that would have other tradeoffs.
- bluGill 8y agoIt is the opposite - ifconfig on linux is an app that happens to share the name and syntax with the BSD utility. BSD sockets came first in 1983. linux re-implemented the interface from about 10 years latter (I'm not sure exactly when, I'd guess 1992 but that is a guess).
- toast0 8y agoI would say the difference is that Linux ifconfig was written once, and never modified. Get a new interface config, write a new tool (see mii-tool, iwconfig, etc) On FreeBSD (and presumably other BSDs), all of the interface configuration happens with ifconfig still, if something new comes up, it's added to the tool that already exists. There are some legitimate concerns around interfaces though -- some of the apis are either parse ifconfig's output, or copy its source code, I don't think (but could be wrong) that there's a nice machine readable way to get this information.
- yellowapple 8y ago"and presumably other BSDs" That is indeed correct in the case of OpenBSD. Halfway rolling my eyes at the article's assertion that it's better to write a new tool than actually bother to maintain the existing one when it's very possible for ifconfig to be a one-stop shop for, you know, interface configuration.
- hacknat 8y agoThe real reason there is drift in Linux tooling is because there are two communities making tools for Linux (GNU and Linux Foundation associated projects) and the two groups seem to find new reasons to hate each other every year. It’s a dumb reason for tooling to drift, but an understandable reason. I have a feeling that ifconfig and netstat will keep up fine, but that the party line will be that they are deprecated.
- sverige 8y agoYeah, SysV init is still around, udev has been renamed eudev and is still being developed, etc. Don't tell anyone in Linux officialdom, though. It upsets them.
- hexo 8y agoifconfig is obsolete for how long? 14 years or so? :)
- shiftoutbox 8y agoHi so here is something to chew on . If the “new” system is so great why do I still need the old route command to deal with multicast routes ? Also the motivation to use the “new” bsd-ish style of poking the kernel is just half baked . It’s neither new nor well planned .
- shiftoutbox 8y agoAlso when ip tools decided to implement socket filters for icmp packets . I wanted to know what’s the crazy idea was . But then someone shows me ip . Wow !
- jbschirtzinger 8y agoWhile this article makes a case for the new command, the reality is simple. I personally learned ifconfig continually in my life and so I learned how to read it and interpret what it was trying to say. It output its commands in a fairly easy to parse way. The new command, while I am sure is progressive and forward thinking, feels clunky. I often have to try to remember the name of the command itself as it is not obvious. It is a good example of a command not really doing the function of making the job easier on the network admin in favor of accommodating new conceptions of features. All the thousands of hours I spent on ifconfig are, basically, useless unless I want to be antiquated and have useless debates about standards. Basically, I just want the computer to do what I tell it with as little extra trouble as possible.
- djsumdog 8y agoI feel like systemctl and journalctl are the same way. They are terrible commands with awful usability. Having a full process control system is nice and helpful when writing a package once for several platforms, but I wish something had caught on that had better usability and didn't try to do everything from login management to filesystem mounting, but rather just process management. Where as someone could probably write a newer drop in ifconfig that uses modern kernel APIs, several people have tried to for systemd and it's just so massive no fork can keep up anymore and almost all have been abandoned.
- kevin_b_er 8y agosystemd has decided for you that these commands are better. It is now your responsibility to accept their decisions.
- bmn__ 8y agoBookmark https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ https://dougvitale.wordpress.com/2011/12/21/deprecated-linux...
- sverige 8y agoThis sort of thing is the reason I never use Linux for anything more serious than a laptop. It's impossible to know when a new table like this will become necessary to do really basic stuff that I already learned how to do years ago.
- Karunamon 8y agoAs I opened this article, I thought "I bet this is going to be related to some Goddamned systemd change". And sure enough, about halfway through: >This interface has an IP alias, set up through systemd's networkd. The amount of pain and headache this init-kitchen-sink-wannabe-thing has caused me day-to-day is incalculable.
- JdeBP 8y agoOf course, that does not say that this was a systemd change, and reading this very discussion at https://news.ycombinator.com/item?id=17151686 https://news.ycombinator.com/item?id=17151686 shows that you lose your bet.
- amyjess 8y agoMultiple IP addresses on an interface have been a thing since long before systemd existed. I remember using iproute2 to add multiple IP addresses to devices at my very first job in 2007. systemd didn't even come out until 2010.
- digi_owl 8y agoMore and more it seems that smaller users of Linux gets the shaft to placate the needs of the cloud behemoths...
- gcb0 8y agothe argument that applications using standard files must be update to another api is BS. the kernel should just map the faster api on those standard file descriptions instead... but then, the "old" files were not part of a standard to begin with... but then again, the standard, whatever it is, was never designed but agreed upon after being in use by enough people. I have no idea what to make of this. I guess I am just happy that people are moving things forward, whatever the direction.
- tomc1985 8y agothe output of 'ip address' is so much harder to parse, visually :/
- gsich 8y agoifc TAB ENTER is just so much faster then ip addr.
- WonkeyMonkey 8y agoI'm still used to typing ifconfig just out of muscle memory, but ip seems to very loosely match "ip a" will be matched the same as "ip addr" or "ip address" Learning that made me much more accepting of the new command
- joelhandwell 8y agoSo https://netplan.io/ https://netplan.io/ was invented to replace them right?
- diebir 8y agoYeah damn idiots broke ifconfig so it already misses some interfaces. Just say no to this insanity.
- deleted 8y ago[deleted]
- arpa 8y agoWell "replace" sounds very serious; but in fact iproute2 has been here long enough to have replaced stuff already. I didn't really consider myself to be a "grumpy old admin", but now I do, having used ip a lot back in 2003. I mean. 14 years have passed since I first used a mature! thing. And some people call ip fresh...
- a-dub 8y agosystemd is like the rajneeshpuram of Unix. first it's the init scripts, now they want to take away ifconfig. ask the people of Oregon how this will all work out...
- nineteen999 8y agoI've perceived an acceleration in the rate of these changes in the last 2-3 years, and have started to put at least some of it down to Linux having annihilated most of the competition in the UNIX server space. With Solaris now headed for retirement and most of the rest of the SysV ecosystem having collapsed over the preceding 20 years or so, it makes it easier for companies like Redhat to "innovate" in new directions with less pressure from developers and sysadmins alike. I'm not sure how much of this is just my imagination, but the rate at which "old world" UNIX commands and subsystems are being replaced or supplanted in Linux certainly seems to have increased. I agree with the author that some of these changes are forced by the development in the kernel itself, but I consider that part of the same phenomenon I guess.