Re: Change eth0 to eno1

Paul M. Foster composed on 2021-10-26 18:06 (UTC-0400): > Along about Debian 10, the standard first ethernet card interface for a > desktop machine, referred to as "eth0", was changed to "eno1". Just out > of idle curiosity, does anyone know why this was done?

Re: Change eth0 to eno1

t; > Along about Debian 10, the standard first ethernet card interface for a > desktop machine, referred to as "eth0", was changed to "eno1". Just out > of idle curiosity, does anyone know why this was done? (It broke some > stuff on my machine.) > > Paul > > >

Re: Change eth0 to eno1

Hello, On Tue, Oct 26, 2021 at 06:06:18PM -0400, Paul M. Foster wrote: > Along about Debian 10, the standard first ethernet card interface for a > desktop machine, referred to as "eth0", was changed to "eno1". Just out of > idle curiosity, does anyone know why this w

Change eth0 to eno1

Folks: Along about Debian 10, the standard first ethernet card interface for a desktop machine, referred to as "eth0", was changed to "eno1". Just out of idle curiosity, does anyone know why this was done? (It broke some stuff on my machine.) Paul

Re: IP-CONFIG: no response | eth0 hardware address DHCP RARP

On 2021-02-07 9:40 p.m., Elias Pereira wrote: > hello, > > I have debian 10 in a xenserver 7.0 vm with static ip and keeps trying > dhcp. Already removed some packages that could be interfering, but must > still have something installed. > > the post messages >

IP-CONFIG: no response | eth0 hardware address DHCP RARP

hello, I have debian 10 in a xenserver 7.0 vm with static ip and keeps trying dhcp. Already removed some packages that could be interfering, but must still have something installed. the post messages https://i.stack.imgur.com/9ylgS.png

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

Jaikumar Sharma wrote: > For my tests on Cisco switch  at office (without any changes on > switch) and using bonding in  "active-backup" mode, I can ping the > active interface using bond0 IP after plugging out the network cable > of the cable of active interface. > Only catch was all interfaces

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

Hello, On Sun, Aug 23, 2020 at 09:16:48PM +0200, deloptes wrote: > Dan Ritter wrote: > > This really sounds like you're trying to test out a scenario in > > a situation where it can't possibly work. > > > > But this is exactly what he has to do - connect two wired network interfaces > to a

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

On Sat, Aug 22, 2020 at 9:36 PM Dan Ritter wrote: > This really sounds like you're trying to test out a scenario in > a situation where it can't possibly work. > > Don't do that. Test it in as close a simulation to reality as > possible. Thanks Dan for insights, it worked - I humbly appreciate

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

On Mon, Aug 24, 2020 at 12:47 AM deloptes wrote: > But this is exactly what he has to do - connect two wired network interfaces > to a managed switch. Then configure LAGG (LACP) on the switch for the two > ports and LAGG (LACP) on the PC/server. Right :) For my tests on Cisco switch at office

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

Dan Ritter wrote: >> Have to test it with two wired connections connected to Cisco managed >> switch. > > This really sounds like you're trying to test out a scenario in > a situation where it can't possibly work. > But this is exactly what he has to do - connect two wired network interfaces

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

Jaikumar Sharma wrote: > On Sat, Aug 22, 2020 at 5:10 PM Dan Ritter wrote: > > You still want bridging, not bonding. > Preferred is bonding, if it works :) > Have to test it with two wired connections connected to Cisco managed switch. This really sounds like you're trying to test out a

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

> hrmm... I just went back to the original post; I missed this bit the > first time around: > > In this setup i'm using a D-Link 8 port switch to connect eth0 using > > ethernet cable and eth1 is connected on wireless adapter of my laptop. > > eth0 and eth1 are probably o

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

On Sat, Aug 22, 2020 at 5:10 PM Dan Ritter wrote: > You still want bridging, not bonding. Preferred is bonding, if it works :) > WiFi doesn't have a cable, so it can't tell you when the > connection goes away, and it can't decide by itself to bring up > a connection. You need a management program

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

d connections will only work > on the NIC that's up. True. But it's better than manually switching things around. hrmm... I just went back to the original post; I missed this bit the first time around: > In this setup i'm using a D-Link 8 port switch to connect eth0 using > ethernet ca

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

Lee wrote: > > Or you can just configure the wired ethernet connection to have a > lower (better) routing metric than the wireless connection. That way > the machine always uses the wired connection if it's up and uses the > wireless connection when the wired connection is down. > > There's

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

On 8/22/20, Dan Ritter wrote: > Jaikumar Sharma wrote: >> On Fri, Aug 21, 2020 at 9:30 PM Dan Ritter wrote: >> > You don't want a bond, you want a bridge. >> > >> > Bonding takes two interfaces that talk to the same switch on the >> > other side, and makes them into one bond nic. You need

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

Jaikumar Sharma wrote: > On Fri, Aug 21, 2020 at 9:30 PM Dan Ritter wrote: > > You don't want a bond, you want a bridge. > > > > Bonding takes two interfaces that talk to the same switch on the > > other side, and makes them into one bond nic. You need support > > on the switch, too, which is

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

On Fri, Aug 21, 2020 at 9:30 PM Dan Ritter wrote: > You don't want a bond, you want a bridge. > > Bonding takes two interfaces that talk to the same switch on the > other side, and makes them into one bond nic. You need support > on the switch, too, which is unlikely in a D-Link 8-port unless >

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

Jaikumar Sharma wrote: > Thank you for pointers, this is a test switch at home but of course > we have bigger Cisco switches at office which have management interface. > It look like LACP needs to be checked/enabled on ports which needs to > be used in network bonding. Note that LACP is not

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

On Fri, Aug 21, 2020 at 9:30 PM Dan Ritter wrote: > > You don't want a bond, you want a bridge. > > Bonding takes two interfaces that talk to the same switch on the > other side, and makes them into one bond nic. You need support > on the switch, too, which is unlikely in a D-Link 8-port unless >

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

Dan Ritter wrote: > You don't want a bond, you want a bridge. > > Bonding takes two interfaces that talk to the same switch on the > other side, and makes them into one bond nic. You need support > on the switch, too, which is unlikely in a D-Link 8-port unless > it has a management interface --

Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

Jaikumar Sharma wrote: > Hi folks, > > I'm using Debian 10 (point release 5) and i've set up the bonding for > eth0 and eth1 in 'active-backup' mode, i'm using virtualbox VM for > testing it, if i disconnect cable (virtually from first ethernet - > eth0) ping to bond0

In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

Hi folks, I'm using Debian 10 (point release 5) and i've set up the bonding for eth0 and eth1 in 'active-backup' mode, i'm using virtualbox VM for testing it, if i disconnect cable (virtually from first ethernet - eth0) ping to bond0 IP stops and if i disconnect it from eth1 and reconnect on eth0

Re: All of my enoX interfaces are mapped to eth0

load/reload of the network driver resulted in a > correct mapping (eno1->eth0, eno2->eth1, etc.) and then I was able to set > up the bonded interface in active/passive failover mode just fine. So it's > all set now. That seems an odd solution to me, which might work in your particular

Re: All of my enoX interfaces are mapped to eth0

. The reason I was trying to figure out whether or not they were actually mapped to the same physical interface was that I needed to setup a bonded interface. A quick unload/reload of the network driver resulted in a correct mapping (eno1->eth0, eno2->eth1, etc.) and then I was able to

Re: All of my enoX interfaces are mapped to eth0

On Fri 30 Mar 2018 at 23:16:26 (-0400), David Parker wrote: > They are all on the same subnet, yes. But I haven't ever seen this > behavior before. Normally, when I have an interface which is unplugged, > its IP is unreachable. So we have two machines, one with eth0, eth1, eth2, eth

Re: All of my enoX interfaces are mapped to eth0

; from a different machine, even though the first interface is the only one > > which is physically connected to the network. The other three interfaces > > are unplugged. So that leads me to believe that all 4 eno interfaces are > > actually mapping to the first physical

Re: All of my enoX interfaces are mapped to eth0

em > from a different machine, even though the first interface is the only one > which is physically connected to the network. The other three interfaces > are unplugged. So that leads me to believe that all 4 eno interfaces are > actually mapping to the first physical interface (a.k.a

Re: All of my enoX interfaces are mapped to eth0

which is physically connected to the network. The other three interfaces are unplugged. So that leads me to believe that all 4 eno interfaces are actually mapping to the first physical interface (a.k.a. eth0). That's why I'm really confused. Thanks! On Fri, Mar 30, 2018 at 7:50 PM, David Wright

Re: All of my enoX interfaces are mapped to eth0

eed, it still uses > the ethX interface names). However, the one that was installed from > scratch is having an issue which I can't seem to figure out. There are 4 > network interfaces -- eno[1-4] -- but they are all getting mapped to eth0. > It looks like they were mapped correctly until I

All of my enoX interfaces are mapped to eth0

is having an issue which I can't seem to figure out. There are 4 network interfaces -- eno[1-4] -- but they are all getting mapped to eth0. It looks like they were mapped correctly until I reloaded the network driver a few days ago. Any idea how I can get them back into a 1:1 mapping with the actual

Re: How to rename my wired connection from 'eno1' to 'eth0'?

Dejan Jocic <jode...@gmail.com> writes: > On 13-06-17, Sharon Kimble wrote: >> >> Due to a hard-drive failure I've had to install Debian 9 and I've got a >> peculiar problem. >> >> My wired connection is showing as 'eno1' instead of the unexpected

Re: How to rename my wired connection from 'eno1' to 'eth0'?

Sharon Kimble wrote: ... > Due to a hard-drive failure I've had to install Debian 9 and I've got a > peculiar problem. > > My wired connection is showing as 'eno1' instead of the unexpected > 'eth0', which means that my 'vnstat' is failing to record my network > traffic. So h

Re: How to rename my wired connection from 'eno1' to 'eth0'?

On 13-06-17, Sharon Kimble wrote: > > Due to a hard-drive failure I've had to install Debian 9 and I've got a > peculiar problem. > > My wired connection is showing as 'eno1' instead of the unexpected > 'eth0', which means that my 'vnstat' is failing to record my network >

Re: How to rename my wired connection from 'eno1' to 'eth0'?

Sharon Kimble composed on 2017-06-13 11:00 (UTC+0100): . > Due to a hard-drive failure I've had to install Debian 9 and I've got a > peculiar problem. > My wired connection is showing as 'eno1' instead of the unexpected > 'eth0', which means that my 'vnstat' is failing to recor

How to rename my wired connection from 'eno1' to 'eth0'?

Due to a hard-drive failure I've had to install Debian 9 and I've got a peculiar problem. My wired connection is showing as 'eno1' instead of the unexpected 'eth0', which means that my 'vnstat' is failing to record my network traffic. So how do I change its name please? I've googled but haven't

Re: Problemes de conexió eth0

ctament igual que abans, amb 1 sol tram i directament > al router. > >> >> - Quin dispositiu de xarxa fas servir exactament? >> Ho pots mirar en una finestar de terminal executant: >> lspci | grep -ie net > > 00:19.0 Ethernet controller: Intel Corporation 82578DM Gig

Re: Problemes de conexió eth0

reboto a la llista, El 30/05/17 a les 11:10, Josep Lladonosa ha escrit: Que no sigui que abans anava bé a 100 (si l'Ethernet de l'encaminador era a 100) i ara intenti anar a 1000 (gigabit) i no pugui per temes de cablejat Podria passar que els parells (color, blanc amb banda del color) no

Re: Problemes de conexió eth0

El 30/05/17 a les 09:14, Santi Moreno ha escrit: > Speed: 100Mb/s > Duplex: Full > Port: Twisted Pair > PHYAD: 2 > Transceiver: internal > Auto-negotiation: on > MDI-X: off (auto) > Supports Wake-on: pumbg > Wake-on: g > Current message

Re: Problemes de conexió eth0

> > - També pots consultar altres coses sobre l'adaptador de xarxa que et > poden fer trobar problemes. Suposant que es diu «eth0»: > # Estat operatiu (em sembla que depèn de la IP): > /sys/class/net/eth0/operstate up > # Velocitat d'enllaç (sense IP): > cat /sys/class/n

Re: Problemes de conexió eth0

altres coses sobre l'adaptador de xarxa que et poden fer trobar problemes. Suposant que es diu «eth0»: # Estat operatiu (em sembla que depèn de la IP): /sys/class/net/eth0/operstate # Velocitat d'enllaç (sense IP): cat /sys/class/net/eth0/speed # Si la velocitat simètrica és simultània (sense IP): c

Re: Problemes de conexió eth0

El 29/05/17 a les 13:14, Santi Moreno ha escrit: >> - que el nou maquinari (encaminador que dóna el servei) té un port de més >> velocitat (gigabit) que l'anterior i aleshores ordinador i aparell no >> negocien igual. Algun cop, segons quin adaptador de xarxa he hagut de >> forçar l'Ethernet a una

Re: Problemes de conexió eth0

2017-05-29 11:09 GMT+02:00 Santi Moreno : > Hola gent, > a veure algú em podeu ajudar. Resulta que fins ara conectava per cable > sense problemes però ens varem passar a la fibra de Movistar i no se > perque ja no conecta per cable (sí per wifi). Inicialment va conectar

Problemes de conexió eth0

Hola gent, a veure algú em podeu ajudar. Resulta que fins ara conectava per cable sense problemes però ens varem passar a la fibra de Movistar i no se perque ja no conecta per cable (sí per wifi). Inicialment va conectar però després de reiniciar ja no ho he aconseguit. La resta de equips de la

Re: Why 2 dhclient processes running for eth0 (IPv4)?

b/dhcp/dhclient.eth1.leases eth1 > 447 dhclient -v -pf /run/dhclient.eth0.pid -lf > /var/lib/dhcp/dhclient.eth0.leases eth0 > 601 dhclient -v -pf /run/dhclient.eth0.pid -lf > /var/lib/dhcp/dhclient.eth0.leases eth0 > 664 dhclient -6 -pf /run/dhclient6.eth0.pid -lf > /var/l

Re: Why 2 dhclient processes running for eth0 (IPv4)?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Mar 10, 2017 at 08:31:10AM -0500, Greg Wooledge wrote: > On Fri, Mar 10, 2017 at 12:34:34PM +0100, to...@tuxteam.de wrote: > > Also, more "w" in the ps: > > > > ps auxf | less > > >From ps(1): > >w Wide output. Use this

Re: Why 2 dhclient processes running for eth0 (IPv4)?

On Fri, Mar 10, 2017 at 12:34:34PM +0100, to...@tuxteam.de wrote: > Also, more "w" in the ps: > > ps auxf | less >From ps(1): w Wide output. Use this option twice for unlimited width. You never need more than two.

Re: Why 2 dhclient processes running for eth0 (IPv4)?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Mar 10, 2017 at 01:23:36PM +, Jonathan Dowland wrote: > On Fri, Mar 10, 2017 at 06:58:30PM +0800, Clark Wang wrote: > > > There are 2 `dhclient` processes running for `eth0` (IPv4). Rebooting does > >

Re: Why 2 dhclient processes running for eth0 (IPv4)?

On Fri, Mar 10, 2017 at 06:58:30PM +0800, Clark Wang wrote: > > There are 2 `dhclient` processes running for `eth0` (IPv4). Rebooting does > > not help for me. > > > > Anyone else has the same problem? I think I have sometimes seen this, but I do not know what prov

Re: Why 2 dhclient processes running for eth0 (IPv4)?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Mar 10, 2017 at 06:58:30PM +0800, Clark Wang wrote: [...] > Anyone else has the same problem? No. At least not if I don't provoke it :-) You could gather some hints by looking into /var/log/daemon.log (dhclient's mumblings are there)

Re: Why 2 dhclient processes running for eth0 (IPv4)?

b/dhcp/dhclient.eth1.leases eth1 > 447 dhclient -v -pf /run/dhclient.eth0.pid -lf > /var/lib/dhcp/dhclient.eth0.leases eth0 > 601 dhclient -v -pf /run/dhclient.eth0.pid -lf > /var/lib/dhcp/dhclient.eth0.leases eth0 > 664 dhclient -6 -pf /run/dhclient6.eth0.pid -lf > /var/l

Why 2 dhclient processes running for eth0 (IPv4)?

/dhclient.eth0.leases eth0 601 dhclient -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 664 dhclient -6 -pf /run/dhclient6.eth0.pid -lf /var/lib/dhcp/dhclient6.eth0.leases eth0 root@debian:~# grep -n -C3 eth0 /etc/network/interfaces 7-auto lo 8-iface lo inet

Re: eth1 - eth0

El ds 24 de 09 de 2016 a les 23:21 +0200, en/na Simó Albert i Beltran va escriure: > Ho pots configurar a /etc/udev/rules.d/70-persistent-net.rules > Gracies, ja he fet el canvi i funciona. Salutacions Jordi.

Re: eth1 - eth0

Ho pots configurar a /etc/udev/rules.d/70-persistent-net.rules signature.asc Description: OpenPGP digital signature

eth1 - eth0

Bones, us voldria fer una pregunta sobre les interfícies de xarxa. Tenia un port ethernet connectat en un slot pci de la placa base --> eth0 I un altre que ja porta la placa base i que tenia desactivat --> eth1 La xarxa em funcionava amb eth0 però aquest maquinari s'ha espatllat i l'he

Re: Consulta router debian con wlan0 y eth0

Para no complicarte mucho para lo mejor opción que deberías hacer es crear una vlan 10 y 20 y una de ellas q Tenga servicio dhcp y para hacer tu puente o repetir esa red insatala router AP. Con eso tu problema está solucionado e más económico.

Re: Consulta router debian con wlan0 y eth0

El 25/07/16 a las 23:54, tomas gonzalez escribió: Hola amigos! quisera que me orienten ...en el trabajo existen dos oficinas: en una hay un router wifi y lo que quisiera hacer es en la otra oficina, instalar un server debian con dhcp con una placa inalambrica (wlan0) y otra ethernet (eth0

Re: Consulta router debian con wlan0 y eth0

t; escribió: > >> > Como estan amigos gracias por sus aportes, si es correcto seria algo > >> > asi: > >> > > >> > Oficina A > >> > Router con wifi > >> > > >> > Oficina B > >> > Servidor con 2 tarjetas de red (eth0 y wla

Re: Consulta router debian con wlan0 y eth0

> > asi: >> > >> > Oficina A >> > Router con wifi >> > >> > Oficina B >> > Servidor con 2 tarjetas de red (eth0 y wlan0) y DHCP >> > >> > Oficina A y Oficina B conectadas físicamente mediante wifi >> > >&

Re: Consulta router debian con wlan0 y eth0

<fernandojose.sa...@gmail.com> escribió: > El día 26 de julio de 2016, 19:01, tomas gonzalez > <bibliotecahue...@gmail.com> escribió: > > Como estan amigos gracias por sus aportes, si es correcto seria algo asi: > > > > Oficina A > > Router con wifi > > > &

Re: Consulta router debian con wlan0 y eth0

El día 26 de julio de 2016, 19:01, tomas gonzalez <bibliotecahue...@gmail.com> escribió: > Como estan amigos gracias por sus aportes, si es correcto seria algo asi: > > Oficina A > Router con wifi > > Oficina B > Servidor con 2 tarjetas de red (eth0 y wlan0) y DHC

Re: Consulta router debian con wlan0 y eth0

wifi > > Oficina B > Servidor con 2 tarjetas de red (eth0 y wlan0) y DHCP > > Oficina A y Oficina B conectadas físicamente mediante wifi > > Clientes de oficina B acceden mediante eth0 hacia un suiche. > > El 26 de julio de 2016, 10:57, Camaleón <noela...@gmail.com> escri

Re: Consulta router debian con wlan0 y eth0

Como estan amigos gracias por sus aportes, si es correcto seria algo asi: Oficina A Router con wifi Oficina B Servidor con 2 tarjetas de red (eth0 y wlan0) y DHCP Oficina A y Oficina B conectadas físicamente mediante wifi Clientes de oficina B acceden mediante eth0 hacia un suiche. El 26 de

Re: Consulta router debian con wlan0 y eth0

inalambrica (wlan0) y > otra ethernet (eth0); este server se conectara con wifi hacia el router > y realizara una puente hacia eth0 para compartir internet y ademas > brindar servicio de dhcp... muchas gracias por cualquier orientacion al > respecto - > muchas gracias Oficina A

Re: Consulta router debian con wlan0 y eth0

y lo que quisiera hacer es en la >>> otra oficina, instalar un server debian con dhcp con una placa >>> inalambrica (wlan0) y otra ethernet (eth0); este server se conectara >>> con wifi hacia el router y realizara una puente hacia eth0 para >>> compartir internet

Re: Consulta router debian con wlan0 y eth0

jo existen dos >>> oficinas: en una hay un router wifi y lo que quisiera hacer es en la >>> otra oficina, instalar un server debian con dhcp con una placa >>> inalambrica (wlan0) y otra ethernet (eth0); este server se conectara >>> con wifi hacia el router y realiza

Re: Consulta router debian con wlan0 y eth0

placa inalambrica (wlan0) y otra ethernet (eth0); este server se conectara con wifi hacia el router y realizara una puente hacia eth0 para compartir internet y ademas brindar servicio de dhcp... muchas gracias por cualquier orientacion al respecto - muchas gracias Hola, para mandar lo de wlan a eth

Re: Consulta router debian con wlan0 y eth0

tra ethernet (eth0); este server se conectara > con wifi hacia el router y realizara una puente hacia eth0 para > compartir internet y ademas brindar servicio de dhcp... muchas gracias > por cualquier orientacion al respecto - muchas gracias Hola, para mandar lo de wlan a eth tenes que hacer

Re: Consulta router debian con wlan0 y eth0

El 25/07/16 a las 23:54, tomas gonzalez escribió: Hola amigos! quisera que me orienten ...en el trabajo existen dos oficinas: en una hay un router wifi y lo que quisiera hacer es en la otra oficina, instalar un server debian con dhcp con una placa inalambrica (wlan0) y otra ethernet (eth0

Consulta router debian con wlan0 y eth0

Hola amigos! quisera que me orienten ...en el trabajo existen dos oficinas: en una hay un router wifi y lo que quisiera hacer es en la otra oficina, instalar un server debian con dhcp con una placa inalambrica (wlan0) y otra ethernet (eth0); este server se conectara con wifi hacia el router y

Re: ifdown: interface eth0 not configured

Em 21-06-2016 14:46, S escreveu: Aproveitando o assunto, estou com problemas para manter a resolução de nomes na minha máquina (debian testing). O network manager deleta sempre o arquivo /etc/resolv.conf e cria um link para /var/run/NetworkManager/resolv.conf, mas o arquivo está sempre vazio e

Re: ifdown: interface eth0 not configured

Luis, isso ocorre pois quem está gerenciando a rede é o network manager, que não se embasa neste arquivo. Outra opção para "derrubar" a interface seria com Ifconfig eth0 down E Ifconfig eth0 up (Como root, claro) Diego Rabatone Oliveira Em 21 de jun de 2016 9:22 AM, "Luis A

Re: ifdown: interface eth0 not configured

bom dia amigos, obrigado pelas repostas, não estou com problemas, o que percebi é que meu arquivo /etc/network/interfaces, não aparece a linha iface eth0 inet dhcp, mas a interface está recebendo ip normalmente. att. Luis Teixeira *.ºvº*. | Linux, porque eu amo a liberdade! */(L)\* | Linux

Re: ifdown: interface eth0 not configured

comando: ifdown etho, apareceu o seguinte resultado: ifdown: interface eth0 not configured fui até o aquivo /etc/network/interfaces e pra minha surpresa não aparece a linha que informa que o sistema deve receber ip por dhcp, segue abaixo com o está o arquivo: # This file describes the network interfac

Re: ifdown: interface eth0 not configured

quando tenho problemas com a interface de rede, por exemplo, de não pegar IP, eu rodo o seguinte comando como root: # dhclient eth0 man dhclient tem várias informações úteis como verbose e etc. Faça o teste. Em 20 de junho de 2016 20:52, Luis Augusto Teixeira < luisteixeir...@gmail.

ifdown: interface eth0 not configured

boa noite amigos, Fui pego de surpresa com a seguinte situação no meu desktop debian Tenho em casa para testes um servidor, fiz uma alteração no servidor dhcp e no meu desktop usei seguinte comando: ifdown etho, apareceu o seguinte resultado: ifdown: interface eth0 not configured fui até o aquivo

Re: need to make an eth0:1 net interface

l email. > > > > So what was the ":1" about? And did it play any part in your > > > solution? It was, after all, a feature of your of your original > > > message. > > > > > > Glad you got it working in some unknown way. > > > > That

Re: need to make an eth0:1 net interface

> It was, after all, a feature of your of your original message. > > > > Glad you got it working in some unknown way. > > That was an attempt to make use of the eth0 interface by adding the :1 > that responded to the usual 192.168.1.X block of addresses. Okay, s

Re: need to make an eth0:1 net interface

ter all, a feature of your of your original message. > > Glad you got it working in some unknown way. That was an attempt to make use of the eth0 interface by adding the :1 that responded to the usual 192.168.1.X block of addresses. That of course did NOT work. So, I wound up with this in /etc/

Re: need to make an eth0:1 net interface

On Mon 16 May 2016 at 14:45:12 -0400, Gene Heskett wrote: > On Monday 16 May 2016 00:48:11 Andy Smith wrote: > > > More details first, I think. > > > > Cheers, > > Andy > > Thanks for the interest Andy, but I got it working and its been > re-installed in place of the router that wasn't

Re: need to make an eth0:1 net interface

On Monday 16 May 2016 00:48:11 Andy Smith wrote: > Hi Gene, > > On Sun, May 15, 2016 at 07:38:46PM -0400, Gene Heskett wrote: > > Do we have a utility that makes it easy to add a :1 to an existing > > eth0 interface? > > It depends what exactly you are trying to ac

Re: need to make an eth0:1 net interface

Hi Gene, On Sun, May 15, 2016 at 07:38:46PM -0400, Gene Heskett wrote: > Do we have a utility that makes it easy to add a :1 to an existing eth0 > interface? It depends what exactly you are trying to achieve. If you just want to add an additional IP address to an interface then you

need to make an eth0:1 net interface

Greetings all; Do we have a utility that makes it easy to add a :1 to an existing eth0 interface? I need to reconfigure a router from scratch. I've manually added it, but I'm pinging myself when I ping it, as in no effect on the ping when the newer router is unplugged. Either cat5 or power

Re: Question: eth0 vs enp1s0 (second try)

nstallations and for > new hardware. Here the hardware was already there; there was just > no firmware. The ethernet interface is the only one mentioned in the .rules file because there was no wlan0 interface due to a lack of firmware on Jessie. eth0 is not renamed on upgrade to unstable because there is

Re: Question: eth0 vs enp1s0 (second try)

On 2016-01-07 18:47:48 +, Brian wrote: > Many WiFi devices require firmware. Some of those devices will not have > an interface registered (they are not initialised) if the firmware is > not present to be loaded into the device. Other devices get an interface > whether the firmware is present

Re: Question: eth0 vs enp1s0 (second try)

On Thu 07 Jan 2016 at 13:12:59 +, Brian wrote: > Pass. 70-persistent-net.rules was generated on Jessie and carried over > to testing. You would need a Jessie install on the same machine to > investigate. Perhaps not; one theory could be tested on Stretch. Many WiFi devices require firmware.

Re: Question: eth0 vs enp1s0 (second try)

link' give without this addition? > > > > > > > > I get: > > > > > > > > ls /sys/class/net/ > > > > > > > > enp1s0 Io wlan0 > > > > > > Interesting. One interface is renamed; one is not (wlan0). > > > &g

Re: Question: eth0 vs enp1s0 (second try)

> Repeat with 70-persistent-net.rules returned to /etc/udev/rules.d. Any > > changes in 'ls /sys/class/net/'? > > Well, I want to keep eth0 on my laptop because I have things > that depend on it. But what I was wondering is why I have > wlp61s0 instead of wlan0, i.e. why a

Re: Question: eth0 vs enp1s0 (second try)

; > > > > > followed by > > > > > > modprobe -v > > > > > > Repeat with 70-persistent-net.rules returned to /etc/udev/rules.d. Any > > > changes in 'ls /sys/class/net/'? > > > > Well, I want to keep eth0 on my laptop becaus

Re: Question: eth0 vs enp1s0

On Thu 31 Dec 2015 at 22:14:49 +0100, Michael Biebl wrote: > udev is already run in the initramfs. > So for any changes that are made to 70-persistent-net.rules, you need to > rebuild your initramfs. > > Maybe your initramfs contains an outdated udev rules file. > If you update the initramfs via

Re: Question: eth0 vs enp1s0 (second try)

get: > > > > > > ls /sys/class/net/ > > > > > > enp1s0 Io wlan0 > > > > Interesting. One interface is renamed; one is not (wlan0). > > On my laptop (installed from Jessie, then upgraded to unstable), > this is the opposite: > > eth0 lo

Re: Question: eth0 vs enp1s0 (second try)

On Thu 31 Dec 2015 at 19:08:18 +0100, Hans wrote: > What do 'ls /sys/class/net' and 'ip link' give without this addition? > > I get: > > ls /sys/class/net/ > > enp1s0 Io wlan0 Interesting. One interface is renamed; one is not (wlan0). [Snip] > I believe, the different outrputs are just

Re: Question: eth0 vs enp1s0 (second try)

t; > Interesting. One interface is renamed; one is not (wlan0). On my laptop (installed from Jessie, then upgraded to unstable), this is the opposite: eth0 lo wlp61s0 Quite strange... -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validate

Re: Question: eth0 vs enp1s0 (second try)

Hi Brian, > Is there no sign of any discovered interfaces for the Aspire in the > output of dmesg? > I get this: dmesg | grep eth0 [2.201866] forcedeth :00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 1c:75:08:2c:84:f8 [ 36.198523] forcedeth :00:0a.0 eth0: MS

Re: Question: eth0 vs enp1s0 (second try)

et control methods supported: 0xe301713 > [ 64.534486] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready dmesg or journalctl have no indication that eth0 on the EEEPC is renamed? [...] > Hope this helps a little bit. My solution at the moment is the well known > addition "

MAC address and security (was: Question: eth0 vs enp1s0 (second try))

On 2015-12-30 16:11:39 +0100, Hans wrote: > I changed the MAC cause of security purposes in this mail. FYI: http://security.stackexchange.com/questions/67893/is-it-dangerous-to-post-my-mac-address-publicly -- Vincent Lefèvre - Web: 100% accessible

Re: Question: eth0 vs enp1s0

y EEEPC > 1005HGO) , the other one the old eth0 scheme (my Aspire 7520G). > > Both got 70-persistent-net-rules configured. udev is already run in the initramfs. So for any changes that are made to 70-persistent-net.rules, you need to rebuild your initramfs. Maybe your initramfs contains

Re: Question: eth0 vs enp1s0

Am Donnerstag, 31. Dezember 2015, 22:14:49 schrieb Michael Biebl: > Am 29.12.2015 um 19:34 schrieb Hans: Hi Michael, > Maybe your initramfs contains an outdated udev rules file. > If you update the initramfs via update-initramfs -u, does that change > anything? No, I already tried this, but it

Re: Question: eth0 vs enp1s0

Did you take a look at dmesg on both systems? Something like grep -E '(enp|eth)' /var/log/dmesg Could you show the content of both 70-persistent-net-rules files? Regards, jvp.

  1   2   3   4   5   6   7   8   9   10   >