*
https://lists.debian.org/debian-user/2017/08/msg01613.html
*
https://news.ycombinator.com/item?id=17152738
*
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274269
* https://news.ycombinator.com/item?id=17151922
Since I needed an |ifconfig| with a more BSD-like interface /a
Eike Lantzsch:
Yes, I ask myself why this isn't possible on Linux:
ifconfig enp3s0 inet alias 192.168.12.206 netmask 255.255.255.0
while it is perfectly possible on OpenBSD (with the correct device of
course).
It's possible if you spell it |inet add| instead of |inet alias|. (-:
Christian Seiler:
From my personal experience, the following two things are features I'm
actually using regularly and that don't work with it:
1.
IPv6 doesn't really work properly (as explained elsewhere by other
people in this thread)
2.
Can't add multiple IP addresses to the s
Greg Wooledge:
wooledg:~$ ip link
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: mtu 1500 qdisc pfifo_fast state UP
mode DEFAULT group default qlen 1000
link/ether a0:8c:fd:c3:89:e0 brd
Am 2017-08-22 17:11, schrieb Sven Hartge:
Christian Seiler wrote:
auto eth0
iface eth0 inet static
address 192.168.0.1/24
address 192.168.0.42/24
address 10.5.6.7/8
This will work, and it will assign all IPs to the interface (the first
one being the primary and the source IP of outgoi
Christian Seiler wrote:
> auto eth0
> iface eth0 inet static
> address 192.168.0.1/24
> address 192.168.0.42/24
> address 10.5.6.7/8
> This will work, and it will assign all IPs to the interface (the first
> one being the primary and the source IP of outgoing packets where the
> program do
On Monday 21 August 2017 14:05:48 Christian Seiler wrote:
> On 08/21/2017 07:40 PM, Gene Heskett wrote:
> > I'll have to study up on this "binding" and how its done.
>
> Note that that's something a program can do if it wants to, but not
> something you can generically configure (though individual
On 08/21/2017 07:40 PM, Gene Heskett wrote:
> I'll have to study up on this "binding" and how its done.
Note that that's something a program can do if it wants to, but not
something you can generically configure (though individual programs
might offer you configuration options for this), and most
On Monday 21 August 2017 13:19:11 Christian Seiler wrote:
> On 08/21/2017 07:07 PM, Gene Heskett wrote:
> > On Monday 21 August 2017 12:11:38 Christian Seiler wrote:
> >> On 08/21/2017 05:03 PM, Gene Heskett wrote:
> >> iface eth0 inet static
> >> address 192.168.0.1/24
> >> address 192.168.0.
On 08/21/2017 07:07 PM, Gene Heskett wrote:
> On Monday 21 August 2017 12:11:38 Christian Seiler wrote:
>
>> On 08/21/2017 05:03 PM, Gene Heskett wrote:
>> iface eth0 inet static
>> address 192.168.0.1/24
>> address 192.168.0.42/24
>> address 10.5.6.7/8
>>
>> This will work, and it will assi
On Monday 21 August 2017 12:11:38 Christian Seiler wrote:
> On 08/21/2017 05:03 PM, Gene Heskett wrote:
> > On Monday 21 August 2017 09:08:11 Christian Seiler wrote:
> >> 2. Can't add multiple IP addresses to the same interface and
> >> (worse) even if multiple IP addresses are assigned to the
On 08/21/2017 05:03 PM, Gene Heskett wrote:
> On Monday 21 August 2017 09:08:11 Christian Seiler wrote:
>> 2. Can't add multiple IP addresses to the same interface and
>> (worse) even if multiple IP addresses are assigned to the
>> same interfaces it only shows the primary address
>
> I do
On Monday, 21 August 2017 15:08:11 -04 Christian Seiler wrote:
> Am 2017-08-21 14:50, schrieb Greg Wooledge:
> > [missing features in ifconfig]
> > (Like Gene, I don't even know what those featues *are*.)
>
> From my personal experience, the following two things are
> features I'm actually using
On 2017-08-21, Greg Wooledge wrote:
> On Mon, Aug 21, 2017 at 05:58:43AM +0100, Jonathan de Boyne Pollard wrote:
>> van Smoorenburg init and systemd actually have nothing whatsoever to do with
>> it. ifconfig uses one Linux API for sending information to and from the
>> kernel, ip uses a differen
On Monday 21 August 2017 09:08:11 Christian Seiler wrote:
> Am 2017-08-21 14:50, schrieb Greg Wooledge:
> > [missing features in ifconfig]
> > (Like Gene, I don't even know what those featues *are*.)
>
> From my personal experience, the following two things are
> features I'm actually using regul
From: ans...@debian.org
> To: Fungi4All
> debian-user\@lists.debian.org
>
> Fungi4All writes:
>>> Never. Debian developers are not your lackeys.
>>
>> Unless you are willing to pay more than n s a sys tem d red hat and they can
>> become "your" lackeys.
>
> Could you take your crazy conspiracy
Am 2017-08-21 14:50, schrieb Greg Wooledge:
[missing features in ifconfig]
(Like Gene, I don't even know what those featues *are*.)
From my personal experience, the following two things are
features I'm actually using regularly and that don't work
with it:
1. IPv6 doesn't really work properly
On Mon, Aug 21, 2017 at 05:58:43AM +0100, Jonathan de Boyne Pollard wrote:
> van Smoorenburg init and systemd actually have nothing whatsoever to do with
> it. ifconfig uses one Linux API for sending information to and from the
> kernel, ip uses a different Linux API. Ironically, the net-tools pa
Erik Christiansen:
Gene, ifconfig is SysV flavoured, so not favoured on the Systemd
journey, AIUI.
van Smoorenburg init and systemd actually have nothing whatsoever to do
with it. ifconfig uses one Linux API for sending information to and
from the kernel, ip uses a different Linux API. I
On Sunday 20 August 2017 23:14:06 Erik Christiansen wrote:
> On 20.08.17 11:41, Gene Heskett wrote:
> > Having a decent recipe for setting up my local network to ipv6, I'd
> > feel a lot more comfortable and capable of dealing with ipv6 when
> > ipv6 is the operating network on the other side of m
On 20.08.17 11:41, Gene Heskett wrote:
> Having a decent recipe for setting up my local network to ipv6, I'd feel
> a lot more comfortable and capable of dealing with ipv6 when ipv6 is the
> operating network on the other side of my router. 150 miles away is NOT
> on the other side of my router.
On Sunday 20 August 2017 08:30:05 Erik Christiansen wrote:
> On 19.08.17 18:40, Brian wrote:
> > I know this thread has been a long, interesting and involved one but
> > it included this:
> >
> > https://lists.debian.org/debian-user/2017/08/msg00798.html
> >
> > To remind ourselves (about why net
On 19.08.17 09:26, Gene Heskett wrote:
> On Saturday 19 August 2017 04:15:42 Jonathan de Boyne Pollard wrote:
> > That is, in fact, what the BSD people did. On FreeBSD and OpenBSD,
> > for examples, modern ifconfig has fully functional IPv6 capability,
> > with parameters like (to pick just some a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Aug 20, 2017 at 10:30:05PM +1000, Erik Christiansen wrote:
[...]
> Any reasonable reader of this thread accepts that it should not be in
> the base distro, I'm certain. It would be an act of generosity to old
> fogeys to include it in the sta
On 19.08.17 18:40, Brian wrote:
> I know this thread has been a long, interesting and involved one but it
> included this:
>
> https://lists.debian.org/debian-user/2017/08/msg00798.html
>
> To remind ourselves (about why net-tools is not in the base system):
>
> Indeed. It shouldn't, and it d
Fungi4All writes:
>> Never. Debian developers are not your lackeys.
>
> Unless you are willing to pay more than n s a sys tem d red hat and they can
> become "your" lackeys.
Could you take your crazy conspiracy theories somewhere else? I'm also
very tempted to suggest contacting a mental health
On 2017-08-19, Gene Heskett wrote:
> On Saturday 19 August 2017 04:15:42 Jonathan de Boyne Pollard wrote:
>
>> Glenn English:
>> > I've written many scripts over the years, using ifconfig and others,
>> > and having everything broken now is a major PITA.
>> >
>> > I very much agree that sysV init
On 2017-08-19, Brian wrote:
(...)
> network-mangler? This demonstrates a disdain for the work put into
> making networking comfortable on Debian. It also probably infers a
> lack of any deep understanding of how the software works.
s/infers/implies
Other than that, +1
--
Liam
On Sat, Aug 19, 2017 at 10:23:37AM -0400, Gene Heskett wrote:
> On Saturday 19 August 2017 09:30:10 Nicolas George wrote:
>
> > Le duodi 2 fructidor, an CCXXV, Gene Heskett a écrit :
> > > So when do we get that ported and into debian, replacing this
> > > gibberish generator called ip, so we can
On Saturday 19 August 2017 15:38:14 Brian wrote:
> On Sat 19 Aug 2017 at 15:26:02 -0400, Gene Heskett wrote:
> > On Saturday 19 August 2017 14:57:46 Brian wrote:
> > > /etc/hosts files advocated? What is wrong with using avahi-demon?
> > > This is 2017.
> >
> > For starters, it seems not to want t
On Sat 19 Aug 2017 at 15:26:02 -0400, Gene Heskett wrote:
> On Saturday 19 August 2017 14:57:46 Brian wrote:
>
> > /etc/hosts files advocated? What is wrong with using avahi-demon?
> > This is 2017.
>
> For starters, it seems not to want to use 192.168 addresses very well. I
> run it, but no c
On Saturday 19 August 2017 14:57:46 Brian wrote:
> On Sat 19 Aug 2017 at 14:38:57 -0400, Gene Heskett wrote:
> > On Saturday 19 August 2017 10:49:57 Nicolas George wrote:
> > > Le duodi 2 fructidor, an CCXXV, Fungi4All a écrit :
> > > > >> Unless you are willing to pay more than n s a sys tem d re
On Sat 19 Aug 2017 at 14:38:57 -0400, Gene Heskett wrote:
> On Saturday 19 August 2017 10:49:57 Nicolas George wrote:
>
> > Le duodi 2 fructidor, an CCXXV, Fungi4All a écrit :
> > > >> Unless you are willing to pay more than n s a sys tem d red hat
> > > >> and they can become "your" lackeys.
> >
On Saturday 19 August 2017 10:49:57 Nicolas George wrote:
> Le duodi 2 fructidor, an CCXXV, Fungi4All a écrit :
> > >> Unless you are willing to pay more than n s a sys tem d red hat
> > >> and they can become "your" lackeys.
> > >
> > > Suggesting that the Debian developers who chose to use syste
On Sat 19 Aug 2017 at 10:23:37 -0400, Gene Heskett wrote:
> On Saturday 19 August 2017 09:30:10 Nicolas George wrote:
>
> > Le duodi 2 fructidor, an CCXXV, Gene Heskett a écrit :
> > > So when do we get that ported and into debian, replacing this
> > > gibberish generator called ip, so we can jus
Le duodi 2 fructidor, an CCXXV, Fungi4All a écrit :
> >> Unless you are willing to pay more than n s a sys tem d red hat and they
> >> can
> >> become "your" lackeys.
> > Suggesting that the Debian developers who chose to use systemd did so
> > because they are corrupt and were payed by RedHat in
Le duodi 2 fructidor, an CCXXV, Fungi4All a écrit :
> Unless you are willing to pay more than n s a sys tem d red hat and they can
> become "your" lackeys.
Suggesting that the Debian developers who chose to use systemd did so
because they are corrupt and were payed by RedHat instead is libelous
an
> From: geo...@nsup.org
> To: Fungi4All
> debian-user@lists.debian.org , Gene Heskett
>
>
> Le duodi 2 fructidor, an CCXXV, Fungi4All a écrit :
>> Unless you are willing to pay more than n s a sys tem d red hat and they can
>> become "your" lackeys.
>
> Suggesting that the Debian developers who
On Saturday 19 August 2017 09:30:10 Nicolas George wrote:
> Le duodi 2 fructidor, an CCXXV, Gene Heskett a écrit :
> > So when do we get that ported and into debian, replacing this
> > gibberish generator called ip, so we can just get back to doing the
> > things we want to do with a computer?
>
>
> From: fungil...@protonmail.com
> To: debian-user@lists.debian.org
> Gene Heskett
>
>> From: geo...@nsup.org
>> To: Gene Heskett
>> debian-user@lists.debian.org
>>
>> Le duodi 2 fructidor, an CCXXV, Gene Heskett a écrit :
>>> So when do we get that ported and into debian, replacing this gibberi
> From: geo...@nsup.org
> To: Gene Heskett
> debian-user@lists.debian.org
>
> Le duodi 2 fructidor, an CCXXV, Gene Heskett a écrit :
>> So when do we get that ported and into debian, replacing this gibberish
>> generator call ip, so we can just get back to doing the things we want
>> to do with a
Le duodi 2 fructidor, an CCXXV, Gene Heskett a écrit :
> So when do we get that ported and into debian, replacing this gibberish
> generator call ip, so we can just get back to doing the things we want
> to do with a computer?
Never. Debian developers are not your lackeys.
--
Nicolas George
On Saturday 19 August 2017 04:15:42 Jonathan de Boyne Pollard wrote:
> Glenn English:
> > I've written many scripts over the years, using ifconfig and others,
> > and having everything broken now is a major PITA.
> >
> > I very much agree that sysV init and those old commands were a mess,
> > espe
On Sat, 19 Aug 2017, Jonathan de Boyne Pollard wrote:
> Henrique de Moraes Holschuh:
> > [...] and the only reason we had to keep it around by default [...] was
> > broken by GNU upstream when it took ifconfig out of the bit-rot pit hell
> > and started maintaining it again.
>
> net-tools is not a
On Sat, Aug 19, 2017 at 09:15:42AM +0100, Jonathan de Boyne Pollard wrote:
> Glenn English:
>
> > I've written many scripts over the years, using ifconfig and others, and
> > having everything broken now is a major
> > PITA.
> >
> > I very much agree that sysV init and those old commands were a
Glenn English:
I've written many scripts over the years, using ifconfig and others,
and having everything broken now is a major PITA.
I very much agree that sysV init and those old commands were a mess,
especially with the introduction of ipv6. But I'd have more inclined
to fix what was ther
Henrique de Moraes Holschuh:
[...] and the only reason we had to keep it around by default [...]
was broken by GNU upstream when it took ifconfig out of the bit-rot
pit hell and started maintaining it again.
net-tools is not a GNU Software package.
* https://sourceforge.net/projects/net-tools
> Much less was I trying to criticize you,
Oh I didn't think you were :-)
> Just trying to raise awareness about (the few) shell variation idiosyncracies
> I know about, to help making people's lives easier.
Sounds good to me.
--
Cheers,
Clive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Aug 16, 2017 at 02:56:01PM +0100, Clive Standbridge wrote:
>
> > The "declare", OTOH, is pretty Bashist. But it can be replaced by
> > a simple "echo":
>
> True. It was just a convenient way of showing that the variable hadn't
> absorbed any
> The "declare", OTOH, is pretty Bashist. But it can be replaced by
> a simple "echo":
True. It was just a convenient way of showing that the variable hadn't
absorbed any white space.
Besides, I was just picking up the "Bash can't do it" gauntlet. I'd
often prefer awk in such a situation (like
On Wed, Aug 16, 2017 at 11:58:06AM +0200, to...@tuxteam.de wrote:
> oldIFS="$IFS"; IFS=': '; ip -o link | while read num interface other;
> do echo "$interface"; done; IFS="$oldIFS"
ip -o link | while IFS=' :' read -r _ i _; do echo "<$i>"; done
There's no need to set IFS globally and then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Aug 16, 2017 at 04:58:24AM -0400, Gene Heskett wrote:
> On Wednesday 16 August 2017 03:28:43 Clive Standbridge wrote:
>
> > oldIFS="$IFS"; IFS=': '; ip -o link | while read num interface other;
> > do declare -p interface; done; IFS="$oldIFS"
On Wednesday 16 August 2017 03:28:43 Clive Standbridge wrote:
> oldIFS="$IFS"; IFS=': '; ip -o link | while read num interface other;
> do declare -p interface; done; IFS="$oldIFS"
Now thats an interesting bit of bashism, and deeper into it than I have
waded. But for this local network, I know w
> wooledg:~$ ip -o link | awk -F": " '{print $2}'
> lo
> eth0
>
> The only other scripting language I know that can do splitting with
> multi-character separators is perl.
>
> wooledg:~$ ip -o link | perl -ne '@x=split(/: /); print $x[1], "\n"'
> lo
> eth0
>
> Bash and Tcl can't do it, at least
On Tue 15 Aug 2017 at 21:49:31 (-0400), Gene Heskett wrote:
> On Tuesday 15 August 2017 15:28:32 David Wright wrote:
>
> > On Tue 15 Aug 2017 at 14:48:50 (-0400), Gene Heskett wrote:
> > > On Tuesday 15 August 2017 14:00:50 Brian wrote:
> > > > On Tue 15 Aug 2017 at 13:46:20 -0400, Gene Heskett wr
On Tuesday 15 August 2017 16:01:25 Curt wrote:
> On 2017-08-15, Gene Heskett wrote:
> >> > > If this still isn't what you want, tell us what you *do* want.
> >> >
> >> > An ifconfig style output by default.
> >>
> >> Then why not use ifconfig?
> >
> > Of course I do, since ipv4 is the local metho
On Tuesday 15 August 2017 15:46:15 Brian wrote:
> On Tue 15 Aug 2017 at 14:53:39 -0400, Gene Heskett wrote:
> > On Tuesday 15 August 2017 14:19:37 David Wright wrote:
> > > On Tue 15 Aug 2017 at 13:24:56 (-0400), Gene Heskett wrote:
> > > > On Tuesday 15 August 2017 10:48:12 Nicolas George wrote:
On Tuesday 15 August 2017 15:28:32 David Wright wrote:
> On Tue 15 Aug 2017 at 14:48:50 (-0400), Gene Heskett wrote:
> > On Tuesday 15 August 2017 14:00:50 Brian wrote:
> > > On Tue 15 Aug 2017 at 13:46:20 -0400, Gene Heskett wrote:
> > > > On Tuesday 15 August 2017 13:07:38 David Wright wrote:
>
On Tuesday 15 August 2017 15:23:44 Brian wrote:
> On Tue 15 Aug 2017 at 14:48:50 -0400, Gene Heskett wrote:
> > On Tuesday 15 August 2017 14:00:50 Brian wrote:
> > > On Tue 15 Aug 2017 at 13:46:20 -0400, Gene Heskett wrote:
> > > > On Tuesday 15 August 2017 13:07:38 David Wright wrote:
> > > > > O
On 2017-08-15, Gene Heskett wrote:
>> > >
>> > > If this still isn't what you want, tell us what you *do* want.
>> >
>> > An ifconfig style output by default.
>>
>> Then why not use ifconfig?
>
> Of course I do, since ipv4 is the local method.
>>
But it's deprecated and is no longer provided in t
On Tue 15 Aug 2017 at 14:51:48 -0400, Gene Heskett wrote:
> On Tuesday 15 August 2017 14:16:15 David Wright wrote:
>
> > On Tue 15 Aug 2017 at 13:49:23 (-0400), Gene Heskett wrote:
> > > On Tuesday 15 August 2017 13:46:37 Greg Wooledge wrote:
> > > > On Tue, Aug 15, 2017 at 01:41:16PM -0400, Gene
On Tue 15 Aug 2017 at 14:53:39 -0400, Gene Heskett wrote:
> On Tuesday 15 August 2017 14:19:37 David Wright wrote:
>
> > On Tue 15 Aug 2017 at 13:24:56 (-0400), Gene Heskett wrote:
> > > On Tuesday 15 August 2017 10:48:12 Nicolas George wrote:
> > > > L'octidi 28 thermidor, an CCXXV, Erik Christi
On Tue 15 Aug 2017 at 14:48:50 (-0400), Gene Heskett wrote:
> On Tuesday 15 August 2017 14:00:50 Brian wrote:
>
> > On Tue 15 Aug 2017 at 13:46:20 -0400, Gene Heskett wrote:
> > > On Tuesday 15 August 2017 13:07:38 David Wright wrote:
> > > > On Tue 15 Aug 2017 at 11:23:41 (-0400), Gene Heskett wr
On Tue 15 Aug 2017 at 14:48:50 -0400, Gene Heskett wrote:
> On Tuesday 15 August 2017 14:00:50 Brian wrote:
>
> > On Tue 15 Aug 2017 at 13:46:20 -0400, Gene Heskett wrote:
> > > On Tuesday 15 August 2017 13:07:38 David Wright wrote:
> > > > On Tue 15 Aug 2017 at 11:23:41 (-0400), Gene Heskett wro
On Tuesday 15 August 2017 14:19:37 David Wright wrote:
> On Tue 15 Aug 2017 at 13:24:56 (-0400), Gene Heskett wrote:
> > On Tuesday 15 August 2017 10:48:12 Nicolas George wrote:
> > > L'octidi 28 thermidor, an CCXXV, Erik Christiansen a écrit :
> > > > Around 30 years of familiarity across many *n
On Tuesday 15 August 2017 14:16:15 David Wright wrote:
> On Tue 15 Aug 2017 at 13:49:23 (-0400), Gene Heskett wrote:
> > On Tuesday 15 August 2017 13:46:37 Greg Wooledge wrote:
> > > On Tue, Aug 15, 2017 at 01:41:16PM -0400, Gene Heskett wrote:
> > > > While STILL not giving me the local ipv4 addr
On Tuesday 15 August 2017 14:01:28 Nicolas George wrote:
> L'octidi 28 thermidor, an CCXXV, Gene Heskett a écrit :
> > Nicolas: The nearest ipv6 address to me is likely 150 miles north,
> > in Pittsburgh PA. Its all ipv4 here in WV AFAIK.
>
> You seem to be under the misapprehension that the polic
On Tuesday 15 August 2017 14:00:50 Brian wrote:
> On Tue 15 Aug 2017 at 13:46:20 -0400, Gene Heskett wrote:
> > On Tuesday 15 August 2017 13:07:38 David Wright wrote:
> > > On Tue 15 Aug 2017 at 11:23:41 (-0400), Gene Heskett wrote:
> > > > On Tuesday 15 August 2017 07:33:53 Nicolas George wrote:
On Tue 15 Aug 2017 at 19:13:54 (+0200), Pierre Frenkiel wrote:
> On Tue, 15 Aug 2017, Greg Wooledge wrote:
>
> >On Tue, Aug 15, 2017 at 06:24:42PM +0200, Pierre Frenkiel wrote:
> >>On Tue, 15 Aug 2017, Greg Wooledge wrote:
> >>
> >>>ip -o link | awk -F": " '{print $2}'
> >>
> >> and even shorter:
On Tue 15 Aug 2017 at 13:24:56 (-0400), Gene Heskett wrote:
> On Tuesday 15 August 2017 10:48:12 Nicolas George wrote:
>
> > L'octidi 28 thermidor, an CCXXV, Erik Christiansen a écrit :
> > > Around 30 years of familiarity across many *nix flavours.
> >
> > You said it: the only superiority of ifc
L'octidi 28 thermidor, an CCXXV, Gene Heskett a écrit :
> Nicolas: The nearest ipv6 address to me is likely 150 miles north, in
> Pittsburgh PA. Its all ipv4 here in WV AFAIK.
You seem to be under the misapprehension that the policy of Debian
development revolves around your personal perceived ne
On Tue 15 Aug 2017 at 13:49:23 (-0400), Gene Heskett wrote:
> On Tuesday 15 August 2017 13:46:37 Greg Wooledge wrote:
>
> > On Tue, Aug 15, 2017 at 01:41:16PM -0400, Gene Heskett wrote:
> > > While STILL not giving me the local ipv4 addresses and netmasks of
> > > those interfaces.
> >
> > If you
On Tue 15 Aug 2017 at 13:46:20 -0400, Gene Heskett wrote:
> On Tuesday 15 August 2017 13:07:38 David Wright wrote:
>
> > On Tue 15 Aug 2017 at 11:23:41 (-0400), Gene Heskett wrote:
> > > On Tuesday 15 August 2017 07:33:53 Nicolas George wrote:
> > > > L'octidi 28 thermidor, an CCXXV, Erik Christi
On Tuesday 15 August 2017 13:46:37 Greg Wooledge wrote:
> On Tue, Aug 15, 2017 at 01:41:16PM -0400, Gene Heskett wrote:
> > While STILL not giving me the local ipv4 addresses and netmasks of
> > those interfaces.
>
> If you want the IPv4 address, netmask, and transfer stats, try:
>
> ip -s addr
>
On Tuesday 15 August 2017 13:07:38 David Wright wrote:
> On Tue 15 Aug 2017 at 11:23:41 (-0400), Gene Heskett wrote:
> > On Tuesday 15 August 2017 07:33:53 Nicolas George wrote:
> > > L'octidi 28 thermidor, an CCXXV, Erik Christiansen a écrit :
> > > > If it's no longer part of the base system, th
On Tue, Aug 15, 2017 at 01:41:16PM -0400, Gene Heskett wrote:
> While STILL not giving me the local ipv4 addresses and netmasks of those
> interfaces.
If you want the IPv4 address, netmask, and transfer stats, try:
ip -s addr
Note that the netmask is shown in CIDR notation (e.g. /23) rather
tha
On Tuesday 15 August 2017 12:38:49 Pierre Frenkiel wrote:
> On Tue, 15 Aug 2017, Greg Wooledge wrote:
> > wooledg:~$ netstat -in
> > Kernel Interface table
> > Iface MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP
> > TX-OVR Flg eth0 1500 8254258 0 0 0 7682795
On Tuesday 15 August 2017 10:48:12 Nicolas George wrote:
> L'octidi 28 thermidor, an CCXXV, Erik Christiansen a écrit :
> > Around 30 years of familiarity across many *nix flavours.
>
> You said it: the only superiority of ifconfig over iproute2 is
> tradition and familiarity of long-time users. O
On Tue, 15 Aug 2017, Greg Wooledge wrote:
On Tue, Aug 15, 2017 at 06:24:42PM +0200, Pierre Frenkiel wrote:
On Tue, 15 Aug 2017, Greg Wooledge wrote:
ip -o link | awk -F": " '{print $2}'
and even shorter:
ip -o link | cut -d : -f 2
They are not equivalent. Yours leaves extra whitespac
On Tue 15 Aug 2017 at 11:23:41 (-0400), Gene Heskett wrote:
> On Tuesday 15 August 2017 07:33:53 Nicolas George wrote:
>
> > L'octidi 28 thermidor, an CCXXV, Erik Christiansen a écrit :
> > > If it's no longer part of the base system, then perhaps the system
> > > is too base?
> >
> > Please ellab
On Tue, Aug 15, 2017 at 06:24:42PM +0200, Pierre Frenkiel wrote:
> On Tue, 15 Aug 2017, Greg Wooledge wrote:
>
> > ip -o link | awk -F": " '{print $2}'
>
> and even shorter:
> ip -o link | cut -d : -f 2
They are not equivalent. Yours leaves extra whitespace.
wooledg:~$ ip -o link | cut -d
On Tue, 15 Aug 2017, Greg Wooledge wrote:
wooledg:~$ netstat -in
Kernel Interface table
Iface MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 8254258 0 0 0 7682795 0 0 0 BMRU
lo 65536 579959 0 0 057
On Tue, Aug 15, 2017 at 3:23 PM, Gene Heskett wrote:
> Because ip is a pain in the ass to make it run, and still gives grossly
> incomplete information?
>
> In 2 years, I have yet to get a full network report out of ip such as
> ifconfig gives.
How about fixing ip? Like 'ip --config'? Or just 'i
On Tue, 15 Aug 2017, Greg Wooledge wrote:
ip -o link | awk -F": " '{print $2}'
and even shorter:
ip -o link | cut -d : -f 2
BTW, I suggest to abandon, in the subject, the reference to the
OP's subject ("was ..."), as this thread has really
nothing to do with inittab stuff
On Tuesday 15 August 2017 07:33:53 Nicolas George wrote:
> L'octidi 28 thermidor, an CCXXV, Erik Christiansen a écrit :
> > If it's no longer part of the base system, then perhaps the system
> > is too base?
>
> Please ellaborate. Why should ifconfig be part of the base system?
>
> Regards,
Becau
L'octidi 28 thermidor, an CCXXV, Erik Christiansen a écrit :
> Around 30 years of familiarity across many *nix flavours.
You said it: the only superiority of ifconfig over iproute2 is tradition
and familiarity of long-time users. On the other hand, ifconfig is
technically inferior on most if not a
On 15-08-17, Erik Christiansen wrote:
> On 15.08.17 15:03, Dejan Jocic wrote:
> > And what exactly do you miss in ifconfig and net-tools package, that you
> > can not do with ip, which is part of iproute2 package that comes as part
> > of base system?
>
> Around 30 years of familiarity across many
On Tue, Aug 15, 2017 at 03:14:02PM +0100, Darac Marjal wrote:
> Have you looked at "ip -s link"? It's not quite as easy to parse as "netstat
> -in", but all the information's there.
Actually, "ip -o link" is a step in the right direction:
wooledg:~$ ip -o link
1: lo: mtu 65536 qdisc noqueue stat
On Tue, 15 Aug 2017, Felix Miata wrote:
> >> > Please ellaborate. Why should ifconfig be part of the base system?
Indeed. It shouldn't, and it doesn't anymore. Maybe net-tools should
be part of the *standard* system, but it certainly does not belong to
the *base* system anymore.
*base* is "what
On Tue, Aug 15, 2017 at 09:29:37AM -0400, Greg Wooledge wrote:
On Tue, Aug 15, 2017 at 03:03:35PM +0200, Dejan Jocic wrote:
And what exactly do you miss in ifconfig and net-tools package, that you
can not do with ip, which is part of iproute2 package that comes as part
of base system?
What ipr
Dejan Jocic composed on 2017-08-15 15:03 (UTC+0200):
> Erik Christiansen wrote:
>> Nicolas George wrote:
>> > Please ellaborate. Why should ifconfig be part of the base system?
>> With pleasure. It is the most basic and useful *nix networking tool,
>> traditional since well back in the last mil
On 15.08.17 09:29, Greg Wooledge wrote:
> wooledg:~$ netstat -in
> Kernel Interface table
> Iface MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
> eth0 1500 8254258 0 0 0 7682795 0 0 0
> BMRU
> lo 65536 579959 0 0 0
On Tue, Aug 15, 2017 at 03:03:35PM +0200, Dejan Jocic wrote:
> And what exactly do you miss in ifconfig and net-tools package, that you
> can not do with ip, which is part of iproute2 package that comes as part
> of base system?
What iproute2 and net-tools are BOTH missing is a sane, script-friend
On 15.08.17 15:03, Dejan Jocic wrote:
> And what exactly do you miss in ifconfig and net-tools package, that you
> can not do with ip, which is part of iproute2 package that comes as part
> of base system?
Around 30 years of familiarity across many *nix flavours. If the package
builders are more f
On 15-08-17, Erik Christiansen wrote:
> On 15.08.17 13:33, Nicolas George wrote:
> > L'octidi 28 thermidor, an CCXXV, Erik Christiansen a écrit :
> > > If it's no longer part of the base system, then perhaps the system is
> > > too base?
> >
> > Please ellaborate. Why should ifconfig be part of th
On 15.08.17 13:33, Nicolas George wrote:
> L'octidi 28 thermidor, an CCXXV, Erik Christiansen a écrit :
> > If it's no longer part of the base system, then perhaps the system is
> > too base?
>
> Please ellaborate. Why should ifconfig be part of the base system?
With pleasure. It is the most basi
L'octidi 28 thermidor, an CCXXV, Erik Christiansen a écrit :
> If it's no longer part of the base system, then perhaps the system is
> too base?
Please ellaborate. Why should ifconfig be part of the base system?
Regards,
--
Nicolas George
On 14.08.17 16:23, deloptes wrote:
> Erik Christiansen wrote:
>
> > Now, if that brings back ifconfig as well, I won't have to rummage about
> > finding which package that might be in.
> >
>
> $ dpkg -S /sbin/ifconfig
> net-tools: /sbin/ifconfig
>
> should be installed manually as it is no long
98 matches
Mail list logo
