Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #156823 > unrolled thread

Adapter Names on Stretch

Started byTim Tepatti <ttepatti@gmail.com>
First post2015-08-26 18:50 +0200
Last post2015-08-29 00:10 +0200
Articles 20 on this page of 63 — 19 participants

Back to article view | Back to linux.debian.user


Contents

  Adapter Names on Stretch Tim Tepatti <ttepatti@gmail.com> - 2015-08-26 18:50 +0200
    Re: Adapter Names on Stretch Eike Lantzsch <zp6cge@gmx.net> - 2015-08-26 19:10 +0200
      Re: Adapter Names on Stretch Renaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org> - 2015-08-26 19:20 +0200
        Re: Adapter Names on Stretch Eike Lantzsch <zp6cge@gmx.net> - 2015-08-26 20:10 +0200
          Re: Adapter Names on Stretch "Gian Uberto Lauri" <saint@eng.it>  - 2015-08-27 09:50 +0200
            Re: Adapter Names on Stretch Erwan David <erwan@rail.eu.org> - 2015-08-27 10:10 +0200
        Re: Adapter Names on Stretch David Wright <deblis@lionunicorn.co.uk> - 2015-08-26 20:40 +0200
        Re: Adapter Names on Stretch Brian <ad44@cityscape.co.uk> - 2015-08-26 21:00 +0200
          Re: Adapter Names on Stretch Renaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org> - 2015-08-26 22:30 +0200
            Re: Adapter Names on Stretch Christian Seiler <christian@iwakd.de> - 2015-08-27 00:10 +0200
              Re: Adapter Names on Stretch Chris Bannister <cbannister@slingshot.co.nz> - 2015-08-27 01:40 +0200
    Re: Adapter Names on Stretch Charlie Kravetz <cjk@teamcharliesangels.com> - 2015-08-26 21:20 +0200
    Re: Adapter Names on Stretch Christian Seiler <christian@iwakd.de> - 2015-08-26 21:30 +0200
    Re: Adapter Names on Stretch Gary Dale <garydale@torfree.net> - 2015-08-26 22:30 +0200
      Re: Adapter Names on Stretch Renaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org> - 2015-08-26 23:00 +0200
        Re: Adapter Names on Stretch David Wright <deblis@lionunicorn.co.uk> - 2015-08-26 23:50 +0200
        Re: Adapter Names on Stretch Nicolas George <george@nsup.org> - 2015-08-27 00:00 +0200
          Re: Adapter Names on Stretch Eike Lantzsch <zp6cge@gmx.net> - 2015-08-27 01:30 +0200
            Re: Adapter Names on Stretch Renaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org> - 2015-08-27 02:10 +0200
              Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-27 03:20 +0200
                Re: Adapter Names on Stretch Renaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org> - 2015-08-27 03:30 +0200
                  Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-27 04:20 +0200
                    Re: Adapter Names on Stretch Renaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org> - 2015-08-27 12:00 +0200
                Re: Adapter Names on Stretch Lisi Reisz <lisi.reisz@gmail.com> - 2015-08-28 14:40 +0200
                  Re: Adapter Names on Stretch John Hasler <jhasler@newsguy.com> - 2015-08-28 15:10 +0200
                  Re: Adapter Names on Stretch Renaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org> - 2015-08-28 15:50 +0200
                  Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-28 16:10 +0200
          Re: Adapter Names on Stretch Chris Bannister <cbannister@slingshot.co.nz> - 2015-08-27 20:10 +0200
            Re: Adapter Names on Stretch Lisi Reisz <lisi.reisz@gmail.com> - 2015-08-28 14:50 +0200
              Re: Adapter Names on Stretch Ric Moore <wayward4now@gmail.com> - 2015-08-28 16:40 +0200
                Re: Adapter Names on Stretch David Wright <deblis@lionunicorn.co.uk> - 2015-08-28 17:30 +0200
                  Re: Adapter Names on Stretch Ric Moore <wayward4now@gmail.com> - 2015-08-28 17:50 +0200
                  Re: Adapter Names on Stretch Chris Bannister <cbannister@slingshot.co.nz> - 2015-08-29 00:10 +0200
                    Re: Adapter Names on Stretch Tixy <tixy@yxit.co.uk> - 2015-08-29 08:40 +0200
                      Re: Adapter Names on Stretch Matt Ventura <mattventura@mattventura.net> - 2015-08-29 09:30 +0200
                        Re: Adapter Names on Stretch Tixy <tixy@yxit.co.uk> - 2015-08-29 11:10 +0200
                    Re: Adapter Names on Stretch David Wright <deblis@lionunicorn.co.uk> - 2015-08-29 17:50 +0200
                Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-28 18:00 +0200
                  Re: Adapter Names on Stretch Lisi Reisz <lisi.reisz@gmail.com> - 2015-08-28 18:10 +0200
                    Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-28 19:00 +0200
                      Re: Adapter Names on Stretch Ric Moore <wayward4now@gmail.com> - 2015-08-28 19:50 +0200
                        Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-29 03:10 +0200
                          Re: Adapter Names on Stretch Chris Bannister <cbannister@slingshot.co.nz> - 2015-08-29 03:40 +0200
                            Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-29 03:50 +0200
                              Re: Adapter Names on Stretch Chris Bannister <cbannister@slingshot.co.nz> - 2015-08-29 04:00 +0200
                                Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-29 04:10 +0200
                                Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-29 04:20 +0200
                                Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-29 04:40 +0200
                                  Re: Adapter Names on Stretch Lisi Reisz <lisi.reisz@gmail.com> - 2015-08-29 12:20 +0200
                                    Re: Adapter Names on Stretch Renaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org> - 2015-08-29 12:40 +0200
                                    Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-29 15:40 +0200
                                      Re: Adapter Names on Stretch Lisi Reisz <lisi.reisz@gmail.com> - 2015-08-29 23:40 +0200
                                        Re: Adapter Names on Stretch Gene Heskett <gheskett@wdtv.com> - 2015-08-30 03:10 +0200
                                          Re: Adapter Names on Stretch [OT] David Wright <deblis@lionunicorn.co.uk> - 2015-08-30 06:10 +0200
                                            Re: Adapter Names on Stretch [OT] Gene Heskett <gheskett@wdtv.com> - 2015-08-30 07:30 +0200
                                              Re: Adapter Names on Stretch [OT] David Wright <deblis@lionunicorn.co.uk> - 2015-08-30 21:00 +0200
                                                Re: Adapter Names on Stretch [OT] Gene Heskett <gheskett@wdtv.com> - 2015-08-31 03:50 +0200
                                              Re: Adapter Names on Stretch [OT] Charles Kroeger <ckrogrr@frankensteinface.com> - 2015-09-07 09:00 +0200
                                          Re: Adapter Names on Stretch Lisi Reisz <lisi.reisz@gmail.com> - 2015-08-30 21:40 +0200
                                Re: Adapter Names on Stretch Ric Moore <wayward4now@gmail.com> - 2015-08-29 06:10 +0200
                      Re: Adapter Names on Stretch David Wright <deblis@lionunicorn.co.uk> - 2015-08-28 21:20 +0200
                      Re: Adapter Names on Stretch Lisi Reisz <lisi.reisz@gmail.com> - 2015-08-28 23:40 +0200
              Re: Adapter Names on Stretch Chris Bannister <cbannister@slingshot.co.nz> - 2015-08-29 00:10 +0200

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →


#156854

FromRenaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org>
Date2015-08-27 03:30 +0200
Message-ID<q1UaS-6ee-3@gated-at.bofh.it>
In reply to#156853
On Wed, 26 Aug 2015 21:14:00 -0400
Gene Heskett <gheskett@wdtv.com> wrote:

> Electricity is not magic, it has rules & regulations intended to tame it.
> Here, it works nice.

I live in a country where the only rule applying to electricity is:
"Pay the bill every month."
 
Cheers,
 
Ron.
-- 
                 The single biggest problem in communication
                   is the illusion that it has taken place.
                                      -- George Bernard Shaw 
                                    
                   -- http://www.olgiati-in-paraguay.org --
 

[toc] | [prev] | [next] | [standalone]


#156857

FromGene Heskett <gheskett@wdtv.com>
Date2015-08-27 04:20 +0200
Message-ID<q1UXf-7A4-9@gated-at.bofh.it>
In reply to#156854
On Wednesday 26 August 2015 21:22:04 Renaud  OLGIATI wrote:

> On Wed, 26 Aug 2015 21:14:00 -0400
>
> Gene Heskett <gheskett@wdtv.com> wrote:
> > Electricity is not magic, it has rules & regulations intended to
> > tame it. Here, it works nice.
>
> I live in a country where the only rule applying to electricity is:
> "Pay the bill every month."

Does Paraguay not have the equivalent of our National Electrical Code, 
commonly called the NEC?

Here  in the US, its considered the Bible on how to do electricity safely 
and legally in those government areas that require it.

Perhaps a bit of background on me.  Born in 1934, I have an 8th 
grade "official" education as I quit school in '49 to go fix televisions 
for a living. I have what was once a 1st phone license, and I am a 
Certified Electronics Technician & spent about 65% of my working life as 
a broadcast engineer, where because of the tall towers and their habit 
of being targets for lightning strikes, I got to understand the physics 
of it quite well.

The point being is that neither I nor my gear cares if a quarter million 
volt surge comes on the line, if the surge absorbers are working, then 
the line voltage seen by the equipment will never go above about 175 
volts from line to line.  The gear can tolerate that for a few 
millionths of a second. And additional layer of protection is a wireless 
mouse and keyboard.  The air gap may not be over 2", but even that is 
sufficient it seems to keep me from getting tapped.

> Cheers,
>
> Ron.


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]


#156872

FromRenaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org>
Date2015-08-27 12:00 +0200
Message-ID<q228r-RU-39@gated-at.bofh.it>
In reply to#156857
On Wed, 26 Aug 2015 22:09:52 -0400
Gene Heskett <gheskett@wdtv.com> wrote:

> Does Paraguay not have the equivalent of our National Electrical Code, 
> commonly called the NEC?
> 
> Here  in the US, its considered the Bible on how to do electricity safely 
> and legally in those government areas that require it.

No; no such thing is known here, nor planning/zoning regulations, vehicle 
technical inspection, or until very recently driving test or income tax..
 
Cheers,
 
Ron.
-- 
           A man will give up almost anything except his suffering.
                                                     -- John Cleese
                                    
                   -- http://www.olgiati-in-paraguay.org --
 

[toc] | [prev] | [next] | [standalone]


#156958

FromLisi Reisz <lisi.reisz@gmail.com>
Date2015-08-28 14:40 +0200
Message-ID<q2r6O-3lC-11@gated-at.bofh.it>
In reply to#156853
On Thursday 27 August 2015 02:14:00 Gene Heskett wrote:
> But I have had exactly zero
> equipment failures in the ensuing decade & change that I could attribute
> to that.

I have had no equipment failures _ever_ (<cross fingers, spit and throw salt 
over my left shoulder>) from lightning or thunderstorms.  Nor equipment 
damage from a hurricane.  I have no special precautions.

I also have no snake-trap anywhere, and have not been attacked by a snake.  
Though I did find a slow-worm on my kitchen floor. 

Gene, you of all people should know that the above is an illogical 
statement. ;-)

Renaud may just have been unlucky and you may just have been lucky.  Getting a 
new nic seems to me to be a lot less trouble than you went to!! 

Lisi

[toc] | [prev] | [next] | [standalone]


#156962

FromJohn Hasler <jhasler@newsguy.com>
Date2015-08-28 15:10 +0200
Message-ID<q2rzR-49f-33@gated-at.bofh.it>
In reply to#156958
Lisi writes:
> I have had no equipment failures _ever_ (<cross fingers, spit and
> throw salt over my left shoulder>) from lightning or thunderstorms.
> Nor equipment damage from a hurricane.  I have no special precautions.

For many years I had frequent lightning-induced equipment failures
despite having taken all the above measures and then some.  I had an
underground telephone line and overhead power.  Then NSP made some
distribution system changes that resulted in me getting underground
service.  End of problems.
-- 
John Hasler 
jhasler@newsguy.com
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]


#156965

FromRenaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org>
Date2015-08-28 15:50 +0200
Message-ID<q2scA-4SC-21@gated-at.bofh.it>
In reply to#156958
On Fri, 28 Aug 2015 13:37:41 +0100
Lisi Reisz <lisi.reisz@gmail.com> wrote:

> > But I have had exactly zero
> > equipment failures in the ensuing decade & change that I could attribute
> > to that.  

> I have had no equipment failures _ever_ (<cross fingers, spit and throw salt 
> over my left shoulder>) from lightning or thunderstorms.  Nor equipment 
> damage from a hurricane.  I have no special precautions.

> I also have no snake-trap anywhere, and have not been attacked by a snake.  
> Though I did find a slow-worm on my kitchen floor. 

> Gene, you of all people should know that the above is an illogical 
> statement. ;-)

> Renaud may just have been unlucky and you may just have been lucky.  Getting a 
> new nic seems to me to be a lot less trouble than you went to!! 

Also, balancing the costs and hassle of completely rewiring a house to Gene's 
standards, against those of buying a couple NICs every five or ten years...
 
Cheers,
 
Ron.
-- 
                            Les cons ça ose tout.
                     C'est même à çà qu'on les reconnaît.
                                        -- Michel Audiard
                                    
                   -- http://www.olgiati-in-paraguay.org --
 

[toc] | [prev] | [next] | [standalone]


#156969

FromGene Heskett <gheskett@wdtv.com>
Date2015-08-28 16:10 +0200
Message-ID<q2svV-5uI-29@gated-at.bofh.it>
In reply to#156958
On Friday 28 August 2015 08:37:41 Lisi Reisz wrote:

> On Thursday 27 August 2015 02:14:00 Gene Heskett wrote:
> > But I have had exactly zero
> > equipment failures in the ensuing decade & change that I could
> > attribute to that.
>
> I have had no equipment failures _ever_ (<cross fingers, spit and
> throw salt over my left shoulder>) from lightning or thunderstorms. 
> Nor equipment damage from a hurricane.  I have no special precautions.
>
> I also have no snake-trap anywhere, and have not been attacked by a
> snake. Though I did find a slow-worm on my kitchen floor.
>
> Gene, you of all people should know that the above is an illogical
> statement. ;-)
>
> Renaud may just have been unlucky and you may just have been lucky. 
> Getting a new nic seems to me to be a lot less trouble than you went
> to!!
>
> Lisi

And protecting that new nic, since I know how to do it, sure seems to 
have been worthwhile.  Wannabe J.O.A.T's are generally that way.

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]


#156906

FromChris Bannister <cbannister@slingshot.co.nz>
Date2015-08-27 20:10 +0200
Message-ID<q29MD-3F0-61@gated-at.bofh.it>
In reply to#156842
On Wed, Aug 26, 2015 at 11:58:03PM +0200, Nicolas George wrote:
> Le nonidi 9 fructidor, an CCXXIII, Renaud OLGIATI a écrit :
> > An added advantage is that on the day you replace your Ethernet NIC 
> > because it was fried by lightning, and put a new one in its stead, your 
> > network config will be buggered as the system will givethe new NICt 
> > a name different from the one assigned to the old one, since it will have 
> > a different MAC address.., 
> 
> Indeed, after two hours fiddling with firmwares hoping this is a software
> problem, then cables and hubs to find where the problem exactly is, then one
> hour and a half riding the subway to the other side of town where the shops
> that have discrete network cards nowadays are, and finally after you ruined
> six months uptime to shutdown and install the newly-bought card, editing a
> small config file is really the straw that broke the camel's back.

Honestly, I don't think it's that bad. 

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X

[toc] | [prev] | [next] | [standalone]


#156959

FromLisi Reisz <lisi.reisz@gmail.com>
Date2015-08-28 14:50 +0200
Message-ID<q2rgv-3xc-25@gated-at.bofh.it>
In reply to#156906
On Thursday 27 August 2015 19:01:32 Chris Bannister wrote:
> On Wed, Aug 26, 2015 at 11:58:03PM +0200, Nicolas George wrote:
> > Le nonidi 9 fructidor, an CCXXIII, Renaud OLGIATI a écrit :
> > > An added advantage is that on the day you replace your Ethernet NIC
> > > because it was fried by lightning, and put a new one in its stead, your
> > > network config will be buggered as the system will givethe new NICt
> > > a name different from the one assigned to the old one, since it will
> > > have a different MAC address..,
> >
> > Indeed, after two hours fiddling with firmwares hoping this is a software
> > problem, then cables and hubs to find where the problem exactly is, then
> > one hour and a half riding the subway to the other side of town where the
> > shops that have discrete network cards nowadays are, and finally after
> > you ruined six months uptime to shutdown and install the newly-bought
> > card, editing a small config file is really the straw that broke the
> > camel's back.
>
> Honestly, I don't think it's that bad.

Chris, what happened to your sense of humour? ;-)  This isn't like you!

Lisi

[toc] | [prev] | [next] | [standalone]


#156970

FromRic Moore <wayward4now@gmail.com>
Date2015-08-28 16:40 +0200
Message-ID<q2sYW-62C-23@gated-at.bofh.it>
In reply to#156959
On 08/28/2015 08:39 AM, Lisi Reisz wrote:
> On Thursday 27 August 2015 19:01:32 Chris Bannister wrote:
>> On Wed, Aug 26, 2015 at 11:58:03PM +0200, Nicolas George wrote:
>>> Le nonidi 9 fructidor, an CCXXIII, Renaud OLGIATI a écrit :
>>>> An added advantage is that on the day you replace your Ethernet NIC
>>>> because it was fried by lightning, and put a new one in its stead, your
>>>> network config will be buggered as the system will givethe new NICt
>>>> a name different from the one assigned to the old one, since it will
>>>> have a different MAC address..,
>>>
>>> Indeed, after two hours fiddling with firmwares hoping this is a software
>>> problem, then cables and hubs to find where the problem exactly is, then
>>> one hour and a half riding the subway to the other side of town where the
>>> shops that have discrete network cards nowadays are, and finally after
>>> you ruined six months uptime to shutdown and install the newly-bought
>>> card, editing a small config file is really the straw that broke the
>>> camel's back.
>>
>> Honestly, I don't think it's that bad.
>
> Chris, what happened to your sense of humour? ;-)  This isn't like you!

 From my own experience, if you replace a network card, udev will 
automagically name it /dev/eth +1 so eth0 becomes eth1. I'm using eth1 
right now. Bugs the hell out of me but the network works, :) Ric


-- 
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

[toc] | [prev] | [next] | [standalone]


#156979

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2015-08-28 17:30 +0200
Message-ID<q2tLl-7dc-17@gated-at.bofh.it>
In reply to#156970
Quoting Ric Moore (wayward4now@gmail.com):

> From my own experience, if you replace a network card, udev will
> automagically name it /dev/eth +1 so eth0 becomes eth1. I'm using
> eth1 right now. Bugs the hell out of me but the network works, :)

That's because you didn't clear the previous card's eth0 entry in
/etc/udev/rules.d/70-persistent-net.rules before you booted up
the new card.

If it bugs you, it's never too late. Just edit the name in that file
(you probably want to remove the stale entry too) and reboot.
(Removing all eth* entries and rebooting will achieve the same end.)
Of course, you'll have to change eth1 back to eth0 elsewhere.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#156984

FromRic Moore <wayward4now@gmail.com>
Date2015-08-28 17:50 +0200
Message-ID<q2u4H-7zO-31@gated-at.bofh.it>
In reply to#156979
On 08/28/2015 11:22 AM, David Wright wrote:
> Quoting Ric Moore (wayward4now@gmail.com):
>
>>  From my own experience, if you replace a network card, udev will
>> automagically name it /dev/eth +1 so eth0 becomes eth1. I'm using
>> eth1 right now. Bugs the hell out of me but the network works, :)
>
> That's because you didn't clear the previous card's eth0 entry in
> /etc/udev/rules.d/70-persistent-net.rules before you booted up
> the new card.
>
> If it bugs you, it's never too late. Just edit the name in that file
> (you probably want to remove the stale entry too) and reboot.
> (Removing all eth* entries and rebooting will achieve the same end.)
> Of course, you'll have to change eth1 back to eth0 elsewhere.


I tried that, it must be listed "elsewhere". Too much trouble, "Going 
with the flow" as everything works otherwise. :) Ric


-- 
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

[toc] | [prev] | [next] | [standalone]


#157004

FromChris Bannister <cbannister@slingshot.co.nz>
Date2015-08-29 00:10 +0200
Message-ID<q2A0q-7MI-23@gated-at.bofh.it>
In reply to#156979
On Fri, Aug 28, 2015 at 10:22:58AM -0500, David Wright wrote:
> Quoting Ric Moore (wayward4now@gmail.com):
> 
> > From my own experience, if you replace a network card, udev will
> > automagically name it /dev/eth +1 so eth0 becomes eth1. I'm using
> > eth1 right now. Bugs the hell out of me but the network works, :)
> 
> That's because you didn't clear the previous card's eth0 entry in
> /etc/udev/rules.d/70-persistent-net.rules before you booted up
> the new card.

I think you can delete the file and it will get regenerated on boot.
Well, it used to be that way, probably best to save a copy first in case
it doesn't work that way any more.

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X

[toc] | [prev] | [next] | [standalone]


#157023

FromTixy <tixy@yxit.co.uk>
Date2015-08-29 08:40 +0200
Message-ID<q2HXX-2g1-1@gated-at.bofh.it>
In reply to#157004
On Sat, 2015-08-29 at 10:06 +1200, Chris Bannister wrote:
> On Fri, Aug 28, 2015 at 10:22:58AM -0500, David Wright wrote:
> > Quoting Ric Moore (wayward4now@gmail.com):
> > 
> > > From my own experience, if you replace a network card, udev will
> > > automagically name it /dev/eth +1 so eth0 becomes eth1. I'm using
> > > eth1 right now. Bugs the hell out of me but the network works, :)
> > 
> > That's because you didn't clear the previous card's eth0 entry in
> > /etc/udev/rules.d/70-persistent-net.rules before you booted up
> > the new card.
> 
> I think you can delete the file and it will get regenerated on boot.
> Well, it used to be that way, probably best to save a copy first in case
> it doesn't work that way any more.

It does on Jessie. Just been bringing up several boards using the same
filesystem image and needed to do this myself. Which reminds me, I
should add a command to rc.local to delete all udev rules at boot. (Idea
is that I can swap out boards if they fail and keep the same disk image
- which is on SD card).

-- 
Tixy

[toc] | [prev] | [next] | [standalone]


#157027

FromMatt Ventura <mattventura@mattventura.net>
Date2015-08-29 09:30 +0200
Message-ID<q2IKl-3pw-1@gated-at.bofh.it>
In reply to#157023
On 8/28/2015 11:32 PM, Tixy wrote:
> On Sat, 2015-08-29 at 10:06 +1200, Chris Bannister wrote:
>> On Fri, Aug 28, 2015 at 10:22:58AM -0500, David Wright wrote:
>>> Quoting Ric Moore (wayward4now@gmail.com):
>>>
>>>>  From my own experience, if you replace a network card, udev will
>>>> automagically name it /dev/eth +1 so eth0 becomes eth1. I'm using
>>>> eth1 right now. Bugs the hell out of me but the network works, :)
>>> That's because you didn't clear the previous card's eth0 entry in
>>> /etc/udev/rules.d/70-persistent-net.rules before you booted up
>>> the new card.
>> I think you can delete the file and it will get regenerated on boot.
>> Well, it used to be that way, probably best to save a copy first in case
>> it doesn't work that way any more.
> It does on Jessie. Just been bringing up several boards using the same
> filesystem image and needed to do this myself. Which reminds me, I
> should add a command to rc.local to delete all udev rules at boot. (Idea
> is that I can swap out boards if they fail and keep the same disk image
> - which is on SD card).
>
You can also just delete the udev rule that generates the persistent
interface names to begin with.

Matt Ventura

[toc] | [prev] | [next] | [standalone]


#157031

FromTixy <tixy@yxit.co.uk>
Date2015-08-29 11:10 +0200
Message-ID<q2Kj8-5Iz-15@gated-at.bofh.it>
In reply to#157027
On Sat, 2015-08-29 at 00:24 -0700, Matt Ventura wrote:
> On 8/28/2015 11:32 PM, Tixy wrote:
> > On Sat, 2015-08-29 at 10:06 +1200, Chris Bannister wrote:
> >> On Fri, Aug 28, 2015 at 10:22:58AM -0500, David Wright wrote:
> >>> Quoting Ric Moore (wayward4now@gmail.com):
> >>>
> >>>>  From my own experience, if you replace a network card, udev will
> >>>> automagically name it /dev/eth +1 so eth0 becomes eth1. I'm using
> >>>> eth1 right now. Bugs the hell out of me but the network works, :)
> >>> That's because you didn't clear the previous card's eth0 entry in
> >>> /etc/udev/rules.d/70-persistent-net.rules before you booted up
> >>> the new card.
> >> I think you can delete the file and it will get regenerated on boot.
> >> Well, it used to be that way, probably best to save a copy first in case
> >> it doesn't work that way any more.
> > It does on Jessie. Just been bringing up several boards using the same
> > filesystem image and needed to do this myself. Which reminds me, I
> > should add a command to rc.local to delete all udev rules at boot. (Idea
> > is that I can swap out boards if they fail and keep the same disk image
> > - which is on SD card).
> >
> You can also just delete the udev rule that generates the persistent
> interface names to begin with.

My first thought was that the rule would re-appear if udev package gets
updated. But anyway, I grepped /usr for 70-persistent-net.rules and got
a hit in /usr/share/doc/libudev1/README.Debian which says:

        To disable persistent naming of network interfaces, create an
        empty
        /etc/udev/rules.d/75-persistent-net-generator.rules file to
        override
        the one in /lib/udev/rules.d/ and delete
        /etc/udev/rules.d/70-persistent-net.rules.
        
So,

  touch /etc/udev/rules.d/75-persistent-net-generator.rules

job done :-)

Thanks for the clue.

-- 
Tixy

[toc] | [prev] | [next] | [standalone]


#157052

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2015-08-29 17:50 +0200
Message-ID<q2Qye-68z-19@gated-at.bofh.it>
In reply to#157004
Quoting Chris Bannister (cbannister@slingshot.co.nz):
> On Fri, Aug 28, 2015 at 10:22:58AM -0500, David Wright wrote:
> > Quoting Ric Moore (wayward4now@gmail.com):
> > 
> > > From my own experience, if you replace a network card, udev will
> > > automagically name it /dev/eth +1 so eth0 becomes eth1. I'm using
> > > eth1 right now. Bugs the hell out of me but the network works, :)
> > 
> > That's because you didn't clear the previous card's eth0 entry in
> > /etc/udev/rules.d/70-persistent-net.rules before you booted up
> > the new card.
> 
> I think you can delete the file and it will get regenerated on boot.
> Well, it used to be that way, probably best to save a copy first in case
> it doesn't work that way any more.

I was being conservative. /etc/udev/rules.d/70-persistent-net.rules
may contain other information. I have an Acer laptop that for some
reason names the wifi interface as another eth unless I keep a line
in there.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#156985

FromGene Heskett <gheskett@wdtv.com>
Date2015-08-28 18:00 +0200
Message-ID<q2uem-7Lf-13@gated-at.bofh.it>
In reply to#156970
On Friday 28 August 2015 10:32:15 Ric Moore wrote:

> On 08/28/2015 08:39 AM, Lisi Reisz wrote:
> > On Thursday 27 August 2015 19:01:32 Chris Bannister wrote:
> >> On Wed, Aug 26, 2015 at 11:58:03PM +0200, Nicolas George wrote:
> >>> Le nonidi 9 fructidor, an CCXXIII, Renaud OLGIATI a écrit :
> >>>> An added advantage is that on the day you replace your Ethernet
> >>>> NIC because it was fried by lightning, and put a new one in its
> >>>> stead, your network config will be buggered as the system will
> >>>> givethe new NICt a name different from the one assigned to the
> >>>> old one, since it will have a different MAC address..,
> >>>
> >>> Indeed, after two hours fiddling with firmwares hoping this is a
> >>> software problem, then cables and hubs to find where the problem
> >>> exactly is, then one hour and a half riding the subway to the
> >>> other side of town where the shops that have discrete network
> >>> cards nowadays are, and finally after you ruined six months uptime
> >>> to shutdown and install the newly-bought card, editing a small
> >>> config file is really the straw that broke the camel's back.
> >>
> >> Honestly, I don't think it's that bad.
> >
> > Chris, what happened to your sense of humour? ;-)  This isn't like
> > you!
>
>  From my own experience, if you replace a network card, udev will
> automagically name it /dev/eth +1 so eth0 becomes eth1. I'm using eth1
> right now. Bugs the hell out of me but the network works, :) Ric

Thats nothing Ric, while looking for a machine to run my new mill, I 
moved the hard drive with the installed cnc running release to a 
different box several times, so it is now using eth5. I know how to fix 
it now, but have been lost in the search for my round tuit.  I have a 
machine broke down ATM, but should have it back running in another day 
or so.  Yes, its a certified PITA and needs fixed by debian or the 
maintainer.

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]


#156987

FromLisi Reisz <lisi.reisz@gmail.com>
Date2015-08-28 18:10 +0200
Message-ID<q2uo3-8ca-35@gated-at.bofh.it>
In reply to#156985
On Friday 28 August 2015 16:57:47 Gene Heskett wrote:
> Yes, its a certified PITA and needs fixed by debian or the
> maintainer.

It has become a Monty Python parrot - in other words a dead one.  See the 
beginning of this thread.  

Lisi

[toc] | [prev] | [next] | [standalone]


#156991

FromGene Heskett <gheskett@wdtv.com>
Date2015-08-28 19:00 +0200
Message-ID<q2vaq-FH-17@gated-at.bofh.it>
In reply to#156987
On Friday 28 August 2015 12:02:01 Lisi Reisz wrote:

> On Friday 28 August 2015 16:57:47 Gene Heskett wrote:
> > Yes, its a certified PITA and needs fixed by debian or the
> > maintainer.
>
> It has become a Monty Python parrot - in other words a dead one.  See
> the beginning of this thread.
>
> Lisi

I have assumed that dhcpd can probably deal with it if running 
network-mangler.  But I am staticly addressed, and N-M is the first 
thing I excise after a new install.

Maybe even wicd can but I haven't used it recently either as its not part 
of a default install.  My local network is 100% static.  So when udev 
screws me, I an not able to access anything or anybody to ask what 
hapoened.  And static cannot deal with its interfaces being renamed 
after the interface has been brought up.

I guess the udev way is the way it will be, but in that event, the bug, a 
huge one, needs a fixit script included with udev, and an entry in the 
udev man page under "see also' so anyone with the sense to run man 
network would see as a see also.

Neither exist that I am aware of, and I take the ignoring of folks who 
use static addressing into consideration in terms of having a working 
network rug jerked out from under them not at all well.  I will 
therefore bitch.  Fortunately it was recorded in the messages file, 
which told me what I had to do to make it work once again.  Would our 
mythical Joe and Judy Lunchbucket user have what it takes to fix it?  
Heck no.

But why should I be punished because I use static addresss defined in the 
hosts file?  Maybe a bit more trouble to setup initially, but that was 
17+ years ago when it was the only way to do it.  And its far simpler to 
maintain than all the moving targets udev and dhcp can be and are giving 
us, IMO just to harrass the long time users, which it does a fine job 
of.

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 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

Back to top | Article view | linux.debian.user


csiph-web