DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
hi ,i am running debian linux in vmware 2.0.4. when i try to up eth0 using ifconfig eth0 command it says eth0:device not found but if i type ifconfig alone configurations of eth3 is displayed?what is this meant to be?pls confirm soon
hi ,i am running debian linux in vmware 2.0.4. when i try to up eth0 using ifconfig eth0 command it says eth0:device not found but if i type ifconfig alone configurations of eth3 is displayed?what is this meant to be?pls confirm soon
This can be caused by moving a vm image from one machine or another. Or sometimes weird things happen like that. If you could please post the following to help us out.
1. /etc/modules
2. /etc/network/interfaces
3. /etc/udev/rules.d/<file that has persistent-net.rules
that will give us a good start. Here we should be able to modifiy things to get you back to using eth0
This can be caused by moving a vm image from one machine or another. Or sometimes weird things happen like that. If you could please post the following to help us out.
1. /etc/modules
2. /etc/network/interfaces
3. /etc/udev/rules.d/<file that has persistent-net.rules
that will give us a good start. Here we should be able to modifiy things to get you back to using eth0
When I opened the first /etc/modules, I got the following information in the terminal /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
I found there is nothing usefull with this information
i tried the next file /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
#allow-hotplug eth0
auto eth0
iface eth0-work inet dhcp
iface eth1 inet dhcp
finally, I opened /etc/udev/rules.d/
I found a file z25_persistent-net.rules
This was the result I got!
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:88:c2:aa", NAME="eth3"
their can be certain changes that has to be made in this file so as to convert eth3 to eth0
pls assist me in this regard
Well you can change the eth0 and eth3 in the udev file then save and do the same for the interfaces file then reboot and that should switch around everything.
Well you can change the eth0 and eth3 in the udev file then save and do the same for the interfaces file then reboot and that should switch around everything.
i tried the same. as follows
in the /etc/network/interfaces
i changed eth3 to eth0 as follows
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:75:4b:1e", NAME="eth0"
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:26:87:82", NAME="eth1"
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:30:6b:f1", NAME="eth2"
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:88:c2:aa", NAME="eth3"
finally ,when i reboot the system in vmware,os says it is not able to read /etc/network/interfaces
but if i give ifconfig
it shows eth0 information alone
i am afraid ,whether i am aliasing eth3 as eth0.
kindly conclude
i tried the same. as follows
in the /etc/network/interfaces
i changed eth3 to eth0 as follows
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:75:4b:1e", NAME="eth0"
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:26:87:82", NAME="eth1"
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:30:6b:f1", NAME="eth2"
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0c:29:88:c2:aa", NAME="eth3"
finally ,when i reboot the system in vmware,os says it is not able to read /etc/network/interfaces
but if i give ifconfig
it shows eth0 information alone
i am afraid ,whether i am aliasing eth3 as eth0.
kindly conclude
~
~
~
In your earlier post you had eth3 setup with a Static IP. But it looks like you deleted the entry for the eth3 in your interfaces file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.