Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #185161 > unrolled thread
| Started by | Pierre Frenkiel <pierre.frenkiel@gmail.com> |
|---|---|
| First post | 2017-08-14 11:50 +0200 |
| Last post | 2017-08-19 10:40 +0200 |
| Articles | 20 on this page of 144 — 27 participants |
Back to article view | Back to linux.debian.user
no /etc/inittab Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-08-14 11:50 +0200
Re: no /etc/inittab Erik Christiansen <dvalin@internode.on.net> - 2017-08-14 13:00 +0200
Re: no /etc/inittab Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-08-14 13:10 +0200
Re: no /etc/inittab Nicolas George <george@nsup.org> - 2017-08-14 13:40 +0200
Re: no /etc/inittab Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-08-14 13:50 +0200
Re: no /etc/inittab Brian <ad44@cityscape.co.uk> - 2017-08-14 18:10 +0200
Re: no /etc/inittab Joel Rees <joel.rees@gmail.com> - 2017-08-14 23:20 +0200
Re: no /etc/inittab Joe <joe@jretrading.com> - 2017-08-14 14:00 +0200
Re: no /etc/inittab Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-08-14 15:00 +0200
Re: no /etc/inittab Nicolas George <george@nsup.org> - 2017-08-14 15:30 +0200
Re: no /etc/inittab Joe <joe@jretrading.com> - 2017-08-14 15:50 +0200
Re: no /etc/inittab Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-08-14 16:00 +0200
Re: no /etc/inittab Darac Marjal <mailinglist@darac.org.uk> - 2017-08-14 16:10 +0200
Re: no /etc/inittab Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-08-14 16:30 +0200
Re: no /etc/inittab Darac Marjal <mailinglist@darac.org.uk> - 2017-08-14 16:40 +0200
Re: no /etc/inittab Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-08-14 18:30 +0200
Re: no /etc/inittab Henrique de Moraes Holschuh <hmh@debian.org> - 2017-08-14 16:30 +0200
Re: no /etc/inittab Joe <joe@jretrading.com> - 2017-08-14 17:30 +0200
Re: no /etc/inittab Henrique de Moraes Holschuh <hmh@debian.org> - 2017-08-14 18:20 +0200
Re: no /etc/inittab David Wright <deblis@lionunicorn.co.uk> - 2017-08-15 19:10 +0200
Re: no /etc/inittab Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-19 12:10 +0200
Re: no /etc/inittab David Wright <deblis@lionunicorn.co.uk> - 2017-08-19 22:10 +0200
Re: no /etc/inittab Joe <joe@jretrading.com> - 2017-08-19 23:00 +0200
Re: no /etc/inittab deloptes <deloptes@gmail.com> - 2017-08-14 16:30 +0200
No ifconfig [Was: no /etc/inittab] Erik Christiansen <dvalin@internode.on.net> - 2017-08-15 12:50 +0200
Re: No ifconfig [Was: no /etc/inittab] Nicolas George <george@nsup.org> - 2017-08-15 14:00 +0200
Re: No ifconfig [Was: no /etc/inittab] Erik Christiansen <dvalin@internode.on.net> - 2017-08-15 15:00 +0200
Re: No ifconfig [Was: no /etc/inittab] Dejan Jocic <jodejka@gmail.com> - 2017-08-15 15:10 +0200
Re: No ifconfig [Was: no /etc/inittab] Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-15 15:30 +0200
Re: No ifconfig [Was: no /etc/inittab] Erik Christiansen <dvalin@internode.on.net> - 2017-08-15 16:10 +0200
Re: No ifconfig [Was: no /etc/inittab] Darac Marjal <mailinglist@darac.org.uk> - 2017-08-15 16:20 +0200
Re: No ifconfig [Was: no /etc/inittab] Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-15 16:50 +0200
Re: No ifconfig Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-08-15 18:30 +0200
Re: No ifconfig Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-15 19:00 +0200
Re: No ifconfig Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-08-15 19:20 +0200
Re: No ifconfig David Wright <deblis@lionunicorn.co.uk> - 2017-08-15 20:30 +0200
Re: Re: No ifconfig [Was: no /etc/inittab] Clive Standbridge <list-user@tgstandbridges.plus.com> - 2017-08-16 10:00 +0200
Re: No ifconfig [Was: no /etc/inittab] Gene Heskett <gheskett@shentel.net> - 2017-08-16 11:00 +0200
Re: No ifconfig [Was: no /etc/inittab] <tomas@tuxteam.de> - 2017-08-16 12:00 +0200
Re: No ifconfig [Was: no /etc/inittab] Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-16 14:30 +0200
Re: Re: No ifconfig [Was: no /etc/inittab] Clive Standbridge <list-user@tgstandbridges.plus.com> - 2017-08-16 16:20 +0200
Re: Re: No ifconfig [Was: no /etc/inittab] <tomas@tuxteam.de> - 2017-08-16 16:40 +0200
Re: Re: Re: No ifconfig [Was: no /etc/inittab] Clive Standbridge <list-user@tgstandbridges.plus.com> - 2017-08-16 17:20 +0200
Re: No ifconfig Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-08-15 18:40 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-15 19:50 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-15 19:50 +0200
Re: No ifconfig David Wright <deblis@lionunicorn.co.uk> - 2017-08-15 20:20 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-15 21:00 +0200
Re: No ifconfig Brian <ad44@cityscape.co.uk> - 2017-08-15 22:00 +0200
Re: No ifconfig Curt <curty@free.fr> - 2017-08-15 22:10 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-16 04:00 +0200
Re: No ifconfig Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-15 19:50 +0200
No ifconfig [Was: no /etc/inittab] Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-28 09:40 +0200
Re: No ifconfig [Was: no /etc/inittab] Erik Christiansen <dvalin@internode.on.net> - 2017-08-15 15:30 +0200
Re: No ifconfig [Was: no /etc/inittab] Dejan Jocic <jodejka@gmail.com> - 2017-08-15 16:50 +0200
Re: No ifconfig [Was: no /etc/inittab] Nicolas George <george@nsup.org> - 2017-08-15 17:10 +0200
Re: No ifconfig [Was: no /etc/inittab] Gene Heskett <gheskett@shentel.net> - 2017-08-15 19:30 +0200
Re: No ifconfig [Was: no /etc/inittab] David Wright <deblis@lionunicorn.co.uk> - 2017-08-15 20:20 +0200
Re: No ifconfig [Was: no /etc/inittab] Gene Heskett <gheskett@shentel.net> - 2017-08-15 21:00 +0200
Re: No ifconfig [Was: no /etc/inittab] Brian <ad44@cityscape.co.uk> - 2017-08-15 21:50 +0200
Re: No ifconfig [Was: no /etc/inittab] Gene Heskett <gheskett@shentel.net> - 2017-08-16 04:00 +0200
Re: No ifconfig [Was: no /etc/inittab] Nicolas George <george@nsup.org> - 2017-08-15 20:20 +0200
Re: No ifconfig [Was: no /etc/inittab] Gene Heskett <gheskett@shentel.net> - 2017-08-15 21:00 +0200
Re: No ifconfig [Was: no /etc/inittab] Felix Miata <mrmazda@earthlink.net> - 2017-08-15 16:10 +0200
Re: No ifconfig [Was: no /etc/inittab] Henrique de Moraes Holschuh <hmh@debian.org> - 2017-08-15 16:40 +0200
No ifconfig Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-19 10:10 +0200
Re: No ifconfig Henrique de Moraes Holschuh <hmh@debian.org> - 2017-08-19 14:10 +0200
Re: No ifconfig [Was: no /etc/inittab] Gene Heskett <gheskett@shentel.net> - 2017-08-15 17:30 +0200
Re: No ifconfig [Was: no /etc/inittab] Glenn English <ghe2001@gmail.com> - 2017-08-15 18:40 +0200
Re: No ifconfig Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-19 10:40 +0200
Re: No ifconfig Zenaan Harkness <zenaan@freedbms.net> - 2017-08-19 11:40 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-19 15:30 +0200
Re: No ifconfig Nicolas George <george@nsup.org> - 2017-08-19 15:50 +0200
Re: No ifconfig Fungi4All <fungilife@protonmail.com> - 2017-08-19 16:20 +0200
Re: No ifconfig Fungi4All <fungilife@protonmail.com> - 2017-08-19 16:20 +0200
Re: No ifconfig Fungi4All <fungilife@protonmail.com> - 2017-08-19 16:30 +0200
Re: No ifconfig Nicolas George <george@nsup.org> - 2017-08-19 17:10 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-19 20:40 +0200
Re: No ifconfig Brian <ad44@cityscape.co.uk> - 2017-08-19 21:00 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-19 21:30 +0200
Re: No ifconfig Brian <ad44@cityscape.co.uk> - 2017-08-19 21:40 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-19 21:50 +0200
Re: No ifconfig Liam O'Toole <liam.p.otoole@gmail.com> - 2017-08-20 02:10 +0200
Re: No ifconfig Nicolas George <george@nsup.org> - 2017-08-19 16:50 +0200
Re: No ifconfig Ansgar Burchardt <ansgar@debian.org> - 2017-08-20 12:00 +0200
Re: No ifconfig Fungi4All <fungilife@protonmail.com> - 2017-08-21 15:30 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-19 16:30 +0200
Re: No ifconfig Brian <ad44@cityscape.co.uk> - 2017-08-19 19:50 +0200
Re: No ifconfig Erik Christiansen <dvalin@internode.on.net> - 2017-08-20 14:40 +0200
Re: No ifconfig <tomas@tuxteam.de> - 2017-08-20 14:50 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-20 17:50 +0200
Re: No ifconfig Erik Christiansen <dvalin@internode.on.net> - 2017-08-21 05:20 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-21 06:00 +0200
Re: No ifconfig Zenaan Harkness <zenaan@freedbms.net> - 2017-08-19 23:40 +0200
Re: No ifconfig Liam O'Toole <liam.p.otoole@gmail.com> - 2017-08-20 02:20 +0200
Re: No ifconfig Erik Christiansen <dvalin@internode.on.net> - 2017-08-20 14:50 +0200
Re: No ifconfig Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-21 07:20 +0200
Re: No ifconfig Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-21 15:00 +0200
Re: No ifconfig Christian Seiler <christian@iwakd.de> - 2017-08-21 15:10 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-21 17:10 +0200
Re: No ifconfig Christian Seiler <christian@iwakd.de> - 2017-08-21 18:20 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-21 19:10 +0200
Re: No ifconfig Christian Seiler <christian@iwakd.de> - 2017-08-21 19:20 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-21 19:50 +0200
Re: No ifconfig Christian Seiler <christian@iwakd.de> - 2017-08-21 20:10 +0200
Re: No ifconfig Gene Heskett <gheskett@shentel.net> - 2017-08-21 21:50 +0200
Re: No ifconfig Christian Seiler <christian@iwakd.de> - 2017-08-22 17:20 +0200
Re: No ifconfig Sven Hartge <sven@svenhartge.de> - 2017-08-22 17:20 +0200
Re: No ifconfig Eike Lantzsch <zp6cge@gmx.net> - 2017-08-21 17:30 +0200
No ifconfig Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-28 10:40 +0200
No ifconfig Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-28 10:20 +0200
Re: No ifconfig Curt <curty@free.fr> - 2017-08-21 17:30 +0200
Re: No ifconfig [Was: no /etc/inittab] David Wright <deblis@lionunicorn.co.uk> - 2017-08-15 19:10 +0200
Re: No ifconfig [Was: no /etc/inittab] Gene Heskett <gheskett@shentel.net> - 2017-08-15 19:50 +0200
Re: No ifconfig [Was: no /etc/inittab] Brian <ad44@cityscape.co.uk> - 2017-08-15 20:10 +0200
Re: No ifconfig [Was: no /etc/inittab] Gene Heskett <gheskett@shentel.net> - 2017-08-15 20:50 +0200
Re: No ifconfig [Was: no /etc/inittab] Brian <ad44@cityscape.co.uk> - 2017-08-15 21:30 +0200
Re: No ifconfig [Was: no /etc/inittab] Gene Heskett <gheskett@shentel.net> - 2017-08-16 03:40 +0200
Re: No ifconfig [Was: no /etc/inittab] David Wright <deblis@lionunicorn.co.uk> - 2017-08-15 21:30 +0200
Re: No ifconfig [Was: no /etc/inittab] Gene Heskett <gheskett@shentel.net> - 2017-08-16 03:50 +0200
Re: No ifconfig [Was: no /etc/inittab] David Wright <deblis@lionunicorn.co.uk> - 2017-08-16 06:40 +0200
Re: no /etc/inittab Brian <ad44@cityscape.co.uk> - 2017-08-14 21:30 +0200
Re: obsolete wiki (was: no /etc/inittab) Felix Miata <mrmazda@earthlink.net> - 2017-08-14 22:40 +0200
Re: obsolete wiki (was: no /etc/inittab) Brian <ad44@cityscape.co.uk> - 2017-08-14 23:20 +0200
Re: obsolete wiki Felix Miata <mrmazda@earthlink.net> - 2017-08-14 23:50 +0200
Re: obsolete wiki rhkramer@gmail.com - 2017-08-15 16:10 +0200
Re: obsolete wiki Brian <ad44@cityscape.co.uk> - 2017-08-15 19:20 +0200
Re: obsolete wiki Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-15 19:40 +0200
Re: obsolete wiki rhkramer@gmail.com - 2017-08-16 14:30 +0200
Re: obsolete wiki Brian <ad44@cityscape.co.uk> - 2017-08-16 16:20 +0200
Re: obsolete wiki Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-28 11:20 +0200
Re: obsolete wiki rhkramer@gmail.com - 2017-08-28 12:50 +0200
obsolete wiki (was: no /etc/inittab) Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-28 08:20 +0200
Re: obsolete wiki (was: no /etc/inittab) Gene Heskett <gheskett@shentel.net> - 2017-08-15 00:20 +0200
Re: obsolete wiki (no /etc/inittab) Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-19 11:50 +0200
Re: obsolete wiki (no /etc/inittab) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2017-08-19 15:10 +0200
Re: obsolete wiki (no /etc/inittab) Gene Heskett <gheskett@shentel.net> - 2017-08-19 16:00 +0200
Re: obsolete wiki (no /etc/inittab) Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-19 20:00 +0200
Re: obsolete wiki (no /etc/inittab) Gene Heskett <gheskett@shentel.net> - 2017-08-19 21:10 +0200
Re: obsolete wiki (no /etc/inittab) Brian <ad44@cityscape.co.uk> - 2017-08-19 21:30 +0200
Re: obsolete wiki (no /etc/inittab) Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-21 15:10 +0200
Re: obsolete wiki (no /etc/inittab) Gene Heskett <gheskett@shentel.net> - 2017-08-21 16:30 +0200
obsolete wiki (no /etc/inittab) Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-28 09:00 +0200
Re: no /etc/inittab Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-08-19 10:40 +0200
Page 6 of 8 — ← Prev page 1 2 3 4 5 [6] 7 8 Next page →
| From | Christian Seiler <christian@iwakd.de> |
|---|---|
| Date | 2017-08-21 18:20 +0200 |
| Subject | Re: No ifconfig |
| Message-ID | <ugXAK-6Cy-31@gated-at.bofh.it> |
| In reply to | #185648 |
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 don't know as to how ifconfig sets it up, but its a piece of cake to > edit /etc/network/interfaces to do that. If I bring in a new router, I > uncomment this stanza in the interfaces file: > ================ > #auto eth0:1 > > # to access reset to 192.168.0.1 routers/switches on the 2nd cat5 port > #iface eth0:1 inet static > #address 192.168.0.3 > #netmask 255.255.255.0 > ============== > giving me an address I can use to talk to and configure the new router. Yeah, that's the old way of doing this via an alias interface. I was talking about the new-style way of doing so though. For example: 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 doesn't explicitly bind anything). And "ip a" will show all three addresses, but "ifconfig -a" will only show the first. Alias interfaes are kind of legacy, and while they still work, they do have a couple of drawbacks: they aren't really an own interface because they share options with the interface they are based on (which can be confusing if you want to change interface options), there is no way to automatically add a new IP to a given interface without probing first which aliases have already been "used up", the alias namespace is limited by both the max length of an interface name and the limitation of the alias part itself. But don't get me wrong: if it works for you with alias interfaces, I'm certainly not going to tell you to change that - because those also do work with the "ip" utility. The major issue I "ifconfig" has here is that it doesn't see the additional IP addresses of interfaces added by other tools - so that when you rely on ifconfig you _don't_ see the actual entire network configuration of the system, but only a part of it. So it's actually counter-productive when you're troubleshooting a system. >> (2) is really bad, especially the part where it does not show >> all of the IPs that were assigned by other tools, for example > > Huh? ifconfig doesn't even need a -a option to show me eth0:1 if ts > configured and up. Yes, for alias interfaces it does. For the additional IPs added to the interface itself it doesn't. >> NetworkManager, or Debian's own ifupdown via >> /etc/network/interfaces. > > Please don't equate those two. I was talking about how these configure multiple IPs when you use them. Both use the newer kernel interface that allows you to specify multiple IPs on the same interface, while ifconfig uses the old interface that assumes a single IP per interface. And I just used the most prominent programs in Debian as examples for this, but all other management tools I know of (conman, systemd-networkd, ...) also use the newer interface. I really didn't want to discuss the merits or problems of each individual software package. Regards, Christian
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-08-21 19:10 +0200 |
| Subject | Re: No ifconfig |
| Message-ID | <ugYn8-79B-25@gated-at.bofh.it> |
| In reply to | #185654 |
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 > >> same interfaces it only shows the primary address > > > > I don't know as to how ifconfig sets it up, but its a piece of cake > > to edit /etc/network/interfaces to do that. If I bring in a new > > router, I uncomment this stanza in the interfaces file: > > ================ > > #auto eth0:1 > > > > # to access reset to 192.168.0.1 routers/switches on the 2nd cat5 > > port #iface eth0:1 inet static > > #address 192.168.0.3 > > #netmask 255.255.255.0 > > ============== > > giving me an address I can use to talk to and configure the new > > router. > > Yeah, that's the old way of doing this via an alias interface. I was > talking about the new-style way of doing so though. > > For example: > > 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 doesn't explicitly bind anything). And "ip a" will show all > three addresses, but "ifconfig -a" will only show the first. > Ok, but then how do you differentiate between the addresses without the :1 [:2 etc] notation? It doesn't seem right that is would bang all the assigned addresses with duplicate data. > Alias interfaes are kind of legacy, and while they still work, they do > have a couple of drawbacks: they aren't really an own interface > because they share options with the interface they are based on (which > can be confusing if you want to change interface options), there is no > way to automatically add a new IP to a given interface without probing > first which aliases have already been "used up", the alias namespace > is limited by both the max length of an interface name and the > limitation of the alias part itself. I haven't seen, or needed, one of the newer critters yet. But I'll be interested in the details when it does jump the fence into my domain. > But don't get me wrong: if it works for you with alias interfaces, I'm > certainly not going to tell you to change that - because those also do > work with the "ip" utility. The major issue I "ifconfig" has here is > that it doesn't see the additional IP addresses of interfaces added by > other tools - so that when you rely on ifconfig you _don't_ see the > actual entire network configuration of the system, but only a part of > it. So it's actually counter-productive when you're troubleshooting a > system. > > >> (2) is really bad, especially the part where it does not show > >> all of the IPs that were assigned by other tools, for example > > > > Huh? ifconfig doesn't even need a -a option to show me eth0:1 if ts > > configured and up. > > Yes, for alias interfaces it does. For the additional IPs added to the > interface itself it doesn't. > > >> NetworkManager, or Debian's own ifupdown via > >> /etc/network/interfaces. > > > > Please don't equate those two. > > I was talking about how these configure multiple IPs when you use > them. Both use the newer kernel interface that allows you to specify > multiple IPs on the same interface, while ifconfig uses the old > interface that assumes a single IP per interface. And I just used > the most prominent programs in Debian as examples for this, but all > other management tools I know of (conman, systemd-networkd, ...) > also use the newer interface. > > I really didn't want to discuss the merits or problems of each > individual software package. > > Regards, Thank you, Christian Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Christian Seiler <christian@iwakd.de> |
|---|---|
| Date | 2017-08-21 19:20 +0200 |
| Subject | Re: No ifconfig |
| Message-ID | <ugYwO-7cM-19@gated-at.bofh.it> |
| In reply to | #185657 |
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 assign all IPs to the interface (the first >> one being the primary and the source IP of outgoing packets where the >> program doesn't explicitly bind anything). And "ip a" will show all >> three addresses, but "ifconfig -a" will only show the first. >> > Ok, but then how do you differentiate between the addresses without > the :1 [:2 etc] notation? I don't understand the question? Where do you want to specify an address? When removing the address you just say "remove address XYZ from interface ABC". > It doesn't seem right that is would bang all the assigned addresses with > duplicate data. I don't get what you mean here. What is duplicate? If you open an outgoing connection by default the primary (first) IP that matches the outgoing subnet will be used as the source IP for that connection - but a program can override that by binding the socket to any of the other IPs of that interface. In the above example: any connection to 192.168.0.23 will by default carry the source IP 192.168.0.1, and any connection to 10.1.1.1 will by default carry the source IP 10.5.6.7. An application can create an outgoing connection with source IP 192.168.0.42 by explicitly binding the socket to that IP before making the connection. Which is kind of similar to alias interfaces: with alias interfaces the route metric of the alias interfaces relative to each other defines what IP will be used by default, but again it is possible for an application to override that by binding the socket to a specific IP address. And incoming connections are trivial anyway in these setups. >From the point of view of applications that just use the socket layer (and don't care about network interface names) the system will react in the same way whether you use multiple addresses per interface or whether you use alias interfaces. The main differences are in how it is configured and how the kernel code works. Regards, Christian
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-08-21 19:50 +0200 |
| Subject | Re: No ifconfig |
| Message-ID | <ugYZQ-7mv-5@gated-at.bofh.it> |
| In reply to | #185658 |
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.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 doesn't explicitly bind anything). And "ip a" > >> will show all three addresses, but "ifconfig -a" will only show the > >> first. > > > > Ok, but then how do you differentiate between the addresses without > > the :1 [:2 etc] notation? > > I don't understand the question? Where do you want to specify an > address? When removing the address you just say "remove address XYZ > from interface ABC". > > > It doesn't seem right that is would bang all the assigned addresses > > with duplicate data. > > I don't get what you mean here. What is duplicate? If you open an > outgoing connection by default the primary (first) IP that matches > the outgoing subnet will be used as the source IP for that > connection - but a program can override that by binding the socket > to any of the other IPs of that interface. > I'll have to study up on this "binding" and how its done. > In the above example: any connection to 192.168.0.23 will by default > carry the source IP 192.168.0.1, and any connection to 10.1.1.1 will > by default carry the source IP 10.5.6.7. An application can create > an outgoing connection with source IP 192.168.0.42 by explicitly > binding the socket to that IP before making the connection. > > Which is kind of similar to alias interfaces: with alias interfaces > the route metric of the alias interfaces relative to each other > defines what IP will be used by default, but again it is possible > for an application to override that by binding the socket to a > specific IP address. > > And incoming connections are trivial anyway in these setups. > > From the point of view of applications that just use the socket layer > (and don't care about network interface names) the system will react > in the same way whether you use multiple addresses per interface or > whether you use alias interfaces. The main differences are in how it > is configured and how the kernel code works. > > Regards, > Christian This has been an enlightening discussion, Christian, thank you for your time. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Christian Seiler <christian@iwakd.de> |
|---|---|
| Date | 2017-08-21 20:10 +0200 |
| Subject | Re: No ifconfig |
| Message-ID | <ugZjd-7Ii-39@gated-at.bofh.it> |
| In reply to | #185659 |
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 programs that make outgoing connections don't bind the outgoing socket because they don't care about which IP their packets originate from and are happy to use the OS's defaults. In case you want a pointer on how this works from a programming perspective, I can always recommend Richard Stevens's book UNIX Network Programming (_the_ book about this topic), and the manpage of the bind syscall (section 2; man 2 bind) is also a possible starting point. Regards, Christian
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-08-21 21:50 +0200 |
| Subject | Re: No ifconfig |
| Message-ID | <uh0RY-6N-15@gated-at.bofh.it> |
| In reply to | #185660 |
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 programs > might offer you configuration options for this), and most programs > that make outgoing connections don't bind the outgoing socket > because they don't care about which IP their packets originate from > and are happy to use the OS's defaults. > > In case you want a pointer on how this works from a programming > perspective, I can always recommend Richard Stevens's book UNIX > Network Programming (_the_ book about this topic), and the manpage > of the bind syscall (section 2; man 2 bind) is also a possible > starting point. > > Regards, > Christian Thank you Christian. I am up to my lower jaw in other commitments till much later today before I can follow up on the latter. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Christian Seiler <christian@iwakd.de> |
|---|---|
| Date | 2017-08-22 17:20 +0200 |
| Subject | Re: No ifconfig |
| Message-ID | <uhj8d-49K-1@gated-at.bofh.it> |
| In reply to | #185654 |
Am 2017-08-22 17:11, schrieb Sven Hartge: > Christian Seiler <christian@iwakd.de> 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 doesn't explicitly bind anything). > > No, this does not work in Stretch. Only the first address is added. To > get additional addresses, it has to look like this: > > ,---- > | auto eth0 > | iface eth0 inet static > | address 192.168.0.1/24 > | > | iface eth0 inet static > | address 192.168.0.42/24 > | > | iface eth0 inet static > | address 10.5.6.7/8 > `---- Oh yeah, sorry, I wrote that from memory and misremembered a bit. Thanks for the clarification! Regards, Christian
[toc] | [prev] | [next] | [standalone]
| From | Sven Hartge <sven@svenhartge.de> |
|---|---|
| Date | 2017-08-22 17:20 +0200 |
| Subject | Re: No ifconfig |
| Message-ID | <uhj8d-49K-3@gated-at.bofh.it> |
| In reply to | #185654 |
Christian Seiler <christian@iwakd.de> 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 doesn't explicitly bind anything). No, this does not work in Stretch. Only the first address is added. To get additional addresses, it has to look like this: ,---- | auto eth0 | iface eth0 inet static | address 192.168.0.1/24 | | iface eth0 inet static | address 192.168.0.42/24 | | iface eth0 inet static | address 10.5.6.7/8 `---- Grüße, Sven. -- Sigmentation fault. Core dumped.
[toc] | [prev] | [next] | [standalone]
| From | Eike Lantzsch <zp6cge@gmx.net> |
|---|---|
| Date | 2017-08-21 17:30 +0200 |
| Subject | Re: No ifconfig |
| Message-ID | <ugWOm-648-17@gated-at.bofh.it> |
| In reply to | #185637 |
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 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 same interface and > (worse) even if multiple IP addresses are assigned to the > same interfaces it only shows the primary address 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). I wonder which brainstorm resulted in writing ip instead of rewriting ifconfig - from scratch if necessary - with backwards compatibility. I still can't decide for myself whether having same-name-tools with subtle differences between Linux and BSD is better or not than having different tools with different names altogether and deal with it. > > (2) is really bad, especially the part where it does not show > all of the IPs that were assigned by other tools, for example > NetworkManager, or Debian's own ifupdown via > /etc/network/interfaces. Yes, and why can it not "ifconfig -A" as the BSD-ifconfig can? > There was VMS and then WNT was made - better(?) but a totally different approach - unfortunately the tools coming with WNT were crippled and not very consistent and the concept of i-nodes was implemented but never really used - but I digress. At least ip is more versatile than (Lin)-ifconfig - so there is an improvement. Will Linux now be the CTE - a totally different approach than BSD? or shall the "ux" be sacrificed by distributions and we keep the "Lin"? Linux is just the kernel. The distributions took the Linux-kernel and built a Unix-like system around it. Now it is more like they build a system according to their liking and fit it with the Linux-kernel or maybe any other in the future. That seems to be similar to the path Apple took with the Mach kernel. Kind regards, Eike -- Eike Lantzsch ZP6CGE
[toc] | [prev] | [next] | [standalone]
| From | Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> |
|---|---|
| Date | 2017-08-28 10:40 +0200 |
| Subject | No ifconfig |
| Message-ID | <ujnKq-3jU-13@gated-at.bofh.it> |
| In reply to | #185649 |
[Multipart message — attachments visible in raw view] — view raw
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|. (-:
[toc] | [prev] | [next] | [standalone]
| From | Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> |
|---|---|
| Date | 2017-08-28 10:20 +0200 |
| Subject | No ifconfig |
| Message-ID | <ujnr8-3du-81@gated-at.bofh.it> |
| In reply to | #185637 |
[Multipart message — attachments visible in raw view] — view raw
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 same interface and (worse) > even if multiple IP addresses are assigned to the same interfaces > it only shows the primary address > > (2) is really bad, especially the part where it does not show all of > the IPs that were assigned by other tools, for example NetworkManager, > or Debian's own |ifupdown| via |/etc/network/interfaces|. > Your second point is a conflation of two things. One is right, but the other is wrong. Here is what actually happens. Starting with this basis: > jdebp % ifconfig lo|head -n 4 > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > inet6 addr: ::2/128 Scope:Compat > jdebp % ip address show lo|fgrep -A 1 inet > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet 127.53.53.1/8 scope host secondary lo:0 > valid_lft forever preferred_lft forever > inet6 ::2/128 scope global > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > jdebp % |ifconfig| cannot see additional addresses assigned by the likes of |ip| in its simplest fashion, as here: > jdebp % sudo ip address add 127.53.0.1 dev lo > jdebp % ifconfig lo|head -n 4 > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > inet6 addr: ::2/128 Scope:Compat > jdebp % ip address show lo|fgrep -A 1 inet > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet 127.53.0.1/32 scope host lo > valid_lft forever preferred_lft forever > inet 127.53.53.1/8 scope host secondary lo:0 > valid_lft forever preferred_lft forever > inet6 ::2/128 scope global > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > jdebp % But it most definitely /can/ assign multiple IP addresses to a single interface, and these will be reported as such by |ip| even though |ifconfig| shows them differently: > jdebp % sudo ifconfig lo inet add 127.53.0.2 > jdebp % ifconfig lo|head -n 4 > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > inet6 addr: ::2/128 Scope:Compat > jdebp % ifconfig lo:0|head -n 2 > lo:0 Link encap:Local Loopback > inet addr:127.53.0.2 Mask:255.0.0.0 > jdebp % ip address show lo|fgrep -A 1 inet > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet 127.53.0.1/32 scope host lo > valid_lft forever preferred_lft forever > inet 127.53.53.1/8 scope host secondary lo:0 > valid_lft forever preferred_lft forever > inet 127.53.0.2/8 scope host secondary lo:1 > valid_lft forever preferred_lft forever > inet6 ::2/128 scope global > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > jdebp % Moreover, one /can/ add multiple IP addresses to an interface with |ip| in such a way that |ifconfig| sees them, by assigning labels: > jdebp % sudo ip address del 127.53.0.1/32 dev lo > jdebp % sudo ip address add 127.53.0.1 dev lo label lo:2 > jdebp % ifconfig lo:2|head -n 2 > lo:2 Link encap:Local Loopback > inet addr:127.53.0.1 Mask:255.255.255.255 > jdebp % One interesting tidbit in the aforegiven: The network mask inference calculation differs. |ip| inferred 127.53.0.1/32 whereas |ifconfig| inferred 127.53.0.2/8.
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2017-08-21 17:30 +0200 |
| Subject | Re: No ifconfig |
| Message-ID | <ugWOm-648-21@gated-at.bofh.it> |
| In reply to | #185636 |
On 2017-08-21, Greg Wooledge <wooledg@eeg.ccf.org> 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 different Linux API. Ironically, the net-tools package is >> completely Linux-specific *anyway*, so the usual argument that ifconfig >> couldn't be changed to use the other API, because it has to remain portable, >> does not hold any water. > > The basic command-line syntax of ifconfig is pseudo-standardized across > dozens of legacy Unix systems, as well as BSD. *This* is what people > are really complaining about here -- the divergence of Linux from the > rest of the Unix-speaking world (in addition to breaking backward > compatibility with itself). I have a tenuous understanding of just about everything, but I was going to mention the wiki, which seems to dilute whatever savory irony the so-called complete Linux specificity of net-tools might contain: Take into account that the interfaces provided by net-tools, to some extent are the portable ones across OSes to configure and handle some network stuff. If net-tools is considered deprecated on GNU/Linux, please do not just remove the support as that will break GNU/kFreeBSD for example which is using the compatible freebsd-net-tools, or GNU/Hurd which can use the partial support from inetutils-tools. https://wiki.debian.org/NetToolsDeprecation > E.g. Solaris 10: <http://docs.oracle.com/cd/E19253-01/816-5166/6mbb1kq31/> > E.g. HP-UX 11i: <http://nixdoc.net/man-pages/HP-UX/ifconfig.1m.html> > E.g. AIX 6.1: <https://www.ibm.com/support/knowledgecenter/en/ssw_aix_61/com.ibm.aix.cmds3/ifconfig.htm> > E.g. OpenBSD 6.1: <http://man.openbsd.org/OpenBSD-6.1/ifconfig> > > I think updating net-tools to incorporate whatever new Linux network > stack features it's currently not supporting would make a lot of > people happy, so long as it doesn't break backward compatibility. > > (Like Gene, I don't even know what those featues *are*.) > > -- Only the coward who has more fear of death than dignity can comfort himself with the fact that his body will in time live again in the grass, in the stones, in the toad. To find one's immortality in the transmutation of substances is as strange as to prophesy a brilliant future for the case after a precious violin has been broken and becomes useless. — "Ward 6"
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-08-15 19:10 +0200 |
| Subject | Re: No ifconfig [Was: no /etc/inittab] |
| Message-ID | <ueNvP-443-11@gated-at.bofh.it> |
| In reply to | #185274 |
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 ellaborate. Why should ifconfig be part of the base system? > > > > Regards, > > 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. Does ip addr ; ip -s link not work for you? Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-08-15 19:50 +0200 |
| Subject | Re: No ifconfig [Was: no /etc/inittab] |
| Message-ID | <ueO8y-4lv-25@gated-at.bofh.it> |
| In reply to | #185285 |
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, then perhaps the > > > > system is too base? > > > > > > Please ellaborate. Why should ifconfig be part of the base system? > > > > > > Regards, > > > > 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. > > Does ip addr ; ip -s link not work for you? > > Cheers, > David. It could I suppose, but thats also an extra 4" of useless fluff on my high res screen. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-08-15 20:10 +0200 |
| Subject | Re: No ifconfig [Was: no /etc/inittab] |
| Message-ID | <ueOrU-4Hl-9@gated-at.bofh.it> |
| In reply to | #185293 |
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 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, > > > > > > 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. > > > > Does ip addr ; ip -s link not work for you? > > > > Cheers, > > David. > > It could I suppose, but thats also an extra 4" of useless fluff on my > high res screen. You really wanted to say "yes" to your problem of two years standing being solved, didn't you? But it goes against the grain. :) -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-08-15 20:50 +0200 |
| Subject | Re: No ifconfig [Was: no /etc/inittab] |
| Message-ID | <ueP4C-4UD-19@gated-at.bofh.it> |
| In reply to | #185297 |
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: > > > > > 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, > > > > > > > > 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. > > > > > > Does ip addr ; ip -s link not work for you? > > > > > > Cheers, > > > David. > > > > It could I suppose, but thats also an extra 4" of useless fluff on > > my high res screen. > > You really wanted to say "yes" to your problem of two years standing > being solved, didn't you? But it goes against the grain. :) I would not go out on that limb and saw it off behind me, but if it had more labels on the output, it could be helpfull. For instance what does this line in its output for eth0 tell me, and where did it get those numbers? inet6 fe80::21f:c6ff:fe62:fcbb/64 scope link Compared to the ifconfig eth0 output, that looks to be derived from its MAC address, but how is such a determination thats its a globally unique address determined? Anyone can cause a MAC address to be spoofed. I am doing it myself so that I can change routers without loseing my ipv4 address, registered at namecheap. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2017-08-15 21:30 +0200 |
| Subject | Re: No ifconfig [Was: no /etc/inittab] |
| Message-ID | <uePHk-5pa-19@gated-at.bofh.it> |
| In reply to | #185302 |
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 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 ellaborate. Why should ifconfig be part of the base > > > > > > system? > > > > > > > > > > > > Regards, > > > > > > > > > > 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. > > > > > > > > Does ip addr ; ip -s link not work for you? > > > > > > > > Cheers, > > > > David. > > > > > > It could I suppose, but thats also an extra 4" of useless fluff on > > > my high res screen. > > > > You really wanted to say "yes" to your problem of two years standing > > being solved, didn't you? But it goes against the grain. :) > > I would not go out on that limb and saw it off behind me, Deconstruction: I *can* get a full network report out of ip but am not going to admit it. Instead, I'll throw some chaff around as a diversion. > but if it had > more labels on the output, it could be helpfull. For instance what does > this line in its output for eth0 tell me, and where did it get those > numbers? > > inet6 fe80::21f:c6ff:fe62:fcbb/64 scope link The same place ifconfig got them from, > Compared to the ifconfig eth0 output, that looks to be derived from its > MAC address, but how is such a determination thats its a globally unique > address determined? Anyone can cause a MAC address to be spoofed. I am > doing it myself so that I can change routers without loseing my ipv4 > address, registered at namecheap. Deconstruction: Look out! More chaff. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-08-16 03:40 +0200 |
| Subject | Re: No ifconfig [Was: no /etc/inittab] |
| Message-ID | <ueVtn-xg-7@gated-at.bofh.it> |
| In reply to | #185309 |
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: > > > > > 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 ellaborate. Why should ifconfig be part of the base > > > > > > > system? > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > 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. > > > > > > > > > > Does ip addr ; ip -s link not work for you? > > > > > > > > > > Cheers, > > > > > David. > > > > > > > > It could I suppose, but thats also an extra 4" of useless fluff > > > > on my high res screen. > > > > > > You really wanted to say "yes" to your problem of two years > > > standing being solved, didn't you? But it goes against the grain. > > > :) > > > > I would not go out on that limb and saw it off behind me, > > Deconstruction: I *can* get a full network report out of ip but am not > going to admit it. Instead, I'll throw some chaff around as a > diversion. > > > but if it > > had more labels on the output, it could be helpfull. For instance > > what does this line in its output for eth0 tell me, and where did it > > get those numbers? > > > > inet6 fe80::21f:c6ff:fe62:fcbb/64 scope link > > The same place ifconfig got them from, > > > Compared to the ifconfig eth0 output, that looks to be derived from > > its MAC address, but how is such a determination thats its a > > globally unique address determined? Anyone can cause a MAC address > > to be spoofed. I am doing it myself so that I can change routers > > without loseing my ipv4 address, registered at namecheap. > > Deconstruction: Look out! More chaff. If you want to see it that way, I can't stop you, but I have a netgear router I can use as my gatekeeper since both are running dd-wrt, but the netgear is telling the whole world its a Buffalo NetFinity from the MAC address its using. So the possibility is there, whether you want to admit it or not is entirely up to you. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-08-15 21:30 +0200 |
| Subject | Re: No ifconfig [Was: no /etc/inittab] |
| Message-ID | <uePHk-5pa-15@gated-at.bofh.it> |
| In reply to | #185302 |
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 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 ellaborate. Why should ifconfig be part of the base > > > > > > system? > > > > > > > > > > > > Regards, > > > > > > > > > > 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. > > > > > > > > Does ip addr ; ip -s link not work for you? > > > > > > > > Cheers, > > > > David. > > > > > > It could I suppose, but thats also an extra 4" of useless fluff on > > > my high res screen. > > > > You really wanted to say "yes" to your problem of two years standing > > being solved, didn't you? But it goes against the grain. :) > > I would not go out on that limb and saw it off behind me, but if it had > more labels on the output, it could be helpfull. For instance what does > this line in its output for eth0 tell me, and where did it get those > numbers? > > inet6 fe80::21f:c6ff:fe62:fcbb/64 scope link > > Compared to the ifconfig eth0 output, that looks to be derived from its > MAC address, but how is such a determination thats its a globally unique > address determined? Anyone can cause a MAC address to be spoofed. I am > doing it myself so that I can change routers without loseing my ipv4 > address, registered at namecheap. That's the ip6 address I just mentioned, which I use to connect machines and short-circuit the wireless legs. As you have gathered, it's just "there" for you to use, eg scp -p <file> <yourusername>@[fe80::21f:c6ff:fe62:fcbb%eth0]:/tmp/ would transfer _to_ the machine mentioned above _from_ the connected machine's eth0. Another advantage is that you don't have to disturb your normal network configuration on a different interface (ie wlan0 in my case, but it could be another nic). Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-08-16 03:50 +0200 |
| Subject | Re: No ifconfig [Was: no /etc/inittab] |
| Message-ID | <ueVD3-B6-9@gated-at.bofh.it> |
| In reply to | #185310 |
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 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 ellaborate. Why should ifconfig be part of the base > > > > > > > system? > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > 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. > > > > > > > > > > Does ip addr ; ip -s link not work for you? > > > > > > > > > > Cheers, > > > > > David. > > > > > > > > It could I suppose, but thats also an extra 4" of useless fluff > > > > on my high res screen. > > > > > > You really wanted to say "yes" to your problem of two years > > > standing being solved, didn't you? But it goes against the grain. > > > :) > > > > I would not go out on that limb and saw it off behind me, but if it > > had more labels on the output, it could be helpfull. For instance > > what does this line in its output for eth0 tell me, and where did it > > get those numbers? > > > > inet6 fe80::21f:c6ff:fe62:fcbb/64 scope link > > > > Compared to the ifconfig eth0 output, that looks to be derived from > > its MAC address, but how is such a determination thats its a > > globally unique address determined? Anyone can cause a MAC address > > to be spoofed. I am doing it myself so that I can change routers > > without loseing my ipv4 address, registered at namecheap. > > That's the ip6 address I just mentioned, which I use to connect > machines and short-circuit the wireless legs. As you have gathered, > it's just "there" for you to use, eg > > scp -p <file> <yourusername>@[fe80::21f:c6ff:fe62:fcbb%eth0]:/tmp/ > It worked after suitable customizations, but that does seem to be a needlessly complex bit of cli magic to remember with all the years on my wet ram. > would transfer _to_ the machine mentioned above _from_ the > connected machine's eth0. Another advantage is that you don't have > to disturb your normal network configuration on a different > interface (ie wlan0 in my case, but it could be another nic). > > Cheers, > David. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
Page 6 of 8 — ← Prev page 1 2 3 4 5 [6] 7 8 Next page →
Back to top | Article view | linux.debian.user
csiph-web