On Mon, 9 Feb 2015 13:02:23 -0700 Bob Proulx <bob@proulx.com> wrote: > John L. Ries wrote: > > Henrique de Moraes Holschuh wrote: > > > In Linux, you should never use ifconfig for anything... > > > > I wouldn't go that far. I think ifconfig is just fine for quickie > > diagnostics; but I would never use it as a network interface > > configuration tool if I could help it. > > The problem is that the Linux kernel has changed internally how it > does networking. Some of these changes have been incompatible with > the old ifconfig program. That can cause people using only ifconfig > to be blind to various kernel network state. > > Hey if an old school dog like me can learn to deal with 'ip' instead > of 'ifconfig' then you can too. Most useful information is provided > with these commands: > > ip addr show > ip route show > The counters are not printed with those but since I think those should > be accessed using /proc (or /sys) I am not going to contribute to > pulling those from a command. Thanks for the tips! I was modeling my script after another script that used ifconfig. I realize this isn't such a good idea, so I'll look into changing it to use /proc or /sys.
Attachment:
pgpCMiFE41mcE.pgp
Description: OpenPGP digital signature