Networking :: Ethernet Interfaces - Device Activated On Reboot
Dec 28, 2010
The ethernet configuration files are under
"/etc/sysconfig/network-scripts" such as "ifcfg-eth0:1" etc.
The file looks as follow:
I've set the ONBOOT=no. This means this device should not be activated at boot-time. But as I reboot the machine, this device is activated again. This means the option ONBOOT doesn't work. Seems this is a bug of RedHat LINUX?
I have installed Fedora 14 about 4 days ago. I have set all the networking parameters like dns path, hostname etc. I have also ensured that I select the check-box for "Enable automatically when system starts" for eth0 interface. But weirdly, whenever I boot my system(or restart), I see that the interface eth0 is disabled. I have to manually enter as root and enable it, each time I boot/reboot my system. Why is this happening? Could you please suggest a way so that I have eth0 interface enabled always when I boot up?Also, my domainname also is not boot-persistent. What steps should I take to ensure that the domainname set once persists across reboots?
Using ubuntu 10.10 (pinguy OS) i connected an ethernet cable from my girl's macbook pro to her lenovo ideapad s10-3t to transfer some DS9 episodes onto it. new enough to linux to have not been able to figure out how to access the files on the mac, so i disconnected the ethernet, and the wireless hasn't worked since. tried everything i know, and googling for a while (as well as searching again on this forum) to no avail.
Just before linking the 2 computers via ethernet, the wireless worked fine on the ideapad, always had; but not so after the ethernet connection that did nothing other than apparently kill the wireless. an "lshw -C network" command tells me i have a BCM4313 wireless card, and *-network UNCLAIMED. also, if i launch "install additional drivers", i see that the proprietary driver is not active.
How could merely plugging in an ethernet cable that happened to be conncected to a MBP running OSX.6 do that? and will that happen again? i thought linux was supposed to play real nice with other OS's, so why did a simple file transfer kill my wireless connectivity? i have no access to internet via ethernet cable, so i cannot just download the driver i need now. shouldn't it still be in the computer still? somewhere? is there a simple solution to this, or has the wireless driver been wiped out by plugging in the ethernet? is this a bug that should be reported?
Problem:I got a new Acer Aspire 8935G notebook, installed Ubuntu 9.10 on it and everything is fine, except the fact, that it wont detect any network interfaces (or how to call it So there are no ethernet or wlan connections available in the network-manager..
lspci gives me following lines: joe@IGNAZ ~ $ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev
DSL modem is a Speedstream 6520 router. All computers work fine via dhcp. I'm trying to setup a small server (print server, ssh & ftp servers). I understand enough of the software part of things to get it going, my problem is setting a static IP on the server box. Every time I set the IP in the /etc/network/interfaces file and reboot, I have no network connection. I can talk to the modem through the browser, but nothing beyond that, not even local computers.
/etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.254.202 network 192.168.254.0 netmask 255.255.255.0 gateway 192.168.254.254
ifconfig shows the .202 address, but box can't get to the outside world, and can't ssh into the box from a computer sitting next to it. If I let it dhcp, then I can ssh into it, and have access to the internet. In the modem, I have dmz set for that address. Wan address is static. I can ssh into it if I let it do dhcp, so I know it can work that far. But if I set static ip, I might as well pull the network cable. I've been beating my head on this for over a week, and I'm lost why I can't get it to work. I even changed the dhcp range on the modem, so the .202 is not in that range. There is no dhcp client installed that I can find. I'm using WattOS beta3, which is a light distro based on 9.04. The computer is an old Dell GX150, integrated nic. I have done ifdown and ifup eth0, still no happiness. Doesn't seem like it should be that hard, but I'm stumped. DMZ should let everything pass, so don't need to mess with port forwarding and such. I know it works using dhcp.
I use Linux Mint Debian XFCE and there was a large update (lots of programs) I have done prior to rebooting. After reboot, my computer can now no longer find the ethernet controller anymore in lspci, so my wired connection no longer works.
Is this a hardware issue? The green lights are all blinking fine though.
My computer wouldn't come out of sleep mode, so I had to shut it down improperly. Now there's no ethernet network connection. The NIC works as I can start the computer by wake-on-lan, but somehow Ubuntu no longer sets up a network connection on it.
The green light on the NIC is lit up and blinking. I have changed no settings. It used to get an IP address from the DHCP no problem, but ifconfig now only shows 127.0.0.1.
I updated to the latest available kernel for Kubuntu 10.04 today (2.6.32-24). When the system rebooted, it refused to connect to my wireless network. So far I have been unsuccessful in persuading it to connect. ifconfig shows the existence of the ethernet connection as eth0, and Network Manager also seems to accept the existence of the ethernet port - so why has it suddenly chosen now to stop connecting to the wired network?
I have a usb 4G dongle which has stated no linux support in australia from vividwireless.
The flip flop part does not exist for me in the sense I can not see the cd autorun files so I downloaded the files off the net and put them in my wine directory
I attempted to run the exe file thru wine but whether I try graphical or command line....it defaults to a graphical dialog box....I click on English...installer then shows the dialog box for the welcome screen ...then I click on next and the screen shows for a nanosecond the user agreement but exits with no log etc.
2) so in linux here is the info
Code: Bus 001 Device 020: ID 12d1:380b Huawei Technologies Co., Ltd. but when I press lsusb again....that info disappears....hmmm
Code: Oct 3 06:42:35 sid rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="1435" x-info="http://www.rsyslog.com"] rsyslogd was HUPed, type 'lightweight'. Oct 3 07:00:15 sid kernel: usb 1-8: new high speed USB device using ehci_hcd and address 3
I have two pci network adapters. I see them in pci device list (lspci). And I see them using ifconfig. How do I relate them - which pci device corresponds to ifconfig network adapter ? (I can't open my hardware and relate them using MAC stickers)
I have a device (not a pc) connected to my pc via ethernet, it dose not show up in networks, I was hoping there was a way of scanning to detect for it, is there a way of seeing content of it is basically what I'm asking?
I just upgraded to VMWare workstation 7. I was previously running v.6, and an older linux version, and everything was working fine. I moved over the same VM files to the new computer, and it doesn't find the ethernet connection. When I start up the virtual machine, I get an error message:
Could not connect Ethernet0 to virtual network "/dev/vmnet8". More information can be found in the vmware.log file.
There log file doesn't say much more:
Jan 07 17:31:36.928: vcpu-0| VNET: MACVNetPortOpenDevice: Ethernet0: can't open vmnet device (No such device or address) Jan 07 17:31:36.928: vcpu-0| VNET: MACVNetPort_Connect: Ethernet0: can't open data fd
Once xp has booted, I get the "new hardware" wizard, saying that it found an ethernet adapter. However, it can't find any driver for it. I think this dialog started appearing after I added a new virtual network entry using the "Virtual Network Editor". Originally I didn't even have a /dev/vmnet8 file. Now I do.
I have two HP servers which have a total of 10 Ethernet ports each, both running RHEL 5.7. I need to make sure that Ethernet ports are mapped to the same devices in Linux on both systems (see below) because these servers must be identical (the second box is a drop-in replacement in case the first system fails).The ethernet ports on the first system are mapped as follows:
Device Port eth0 Intel Dual Port Card, Port 1 (Rightmost Port) eth1 Dual, Port 2
We have a server and a target board. Most of the times I am able to mount the server through network file system. But sometimes it is observed that mounting hangs. When this happens, it was noted that both ethernet interfaces are up. Now when I make one down,mount works properly. The interface which I made down was having dummy(default) IP address, gateway etc.
I have a weird issue that I have not seen on any forum. My jaunty on DELL studio laptop seems connected to net, but I can not access any network service (ssh, firefox etc.). But when I connect a cable the cable lights blink as it should be and in wireless connection my wifi light blinks.
It was working 2 days ago without problem, and I have not done big changes recently.I removed and reinstalled network-manager and network-manager-gnome. Nothing changed. I see a message in each restart as follows (when Openafs is starting). I can reproduce it with "/etc/init.d/openafs-client restart"
ADVISEADDR:error in specifying interfaces: no existing ip interfaces found
Cost effective (the people want cheap) solution to increase server storage space with as little impact on throughput (what I want) as possible. I have a server that sends instructions to 20 clients to perform certain tasks. The clients send gigs of data back to the server for storage.
BACKGROUND INFORMATION Network: Gigabit Ethernet Clients: (20) HP, Solaris, Linux Linux Server: Dell R805 PowerEdge (QUAD Core Athlons 16 gigs of ram, 4 gigabit ports.
Selected directories are mounted (NFS) by clients. One directory to be mounted by the clients contains executable files. Mount commands are sent from the server (rsh) to the clients. Yes I know (ssh) but this is how the software was originally written so let's go with it.
The clients then receive commands to execute the binaries contained within the mounted directory. The binaries basically create an image of the clients filesystem including special applications. The client then sends the files and directories to the server which stores this �image�. This process can be reversed to restore a client to the initial baseline image.
In a nut shell, 20 clients are sending gigs of data to the server for storage. I need to attach a NAS (gigabit) to extend the storage capability of the server. The server would mount (NFS) to the hard drives on the NAS. The NAS, configured as a �direct attached storage� device (DAS), means the storage device is connected directly to the server and not the network (which makes it a DAS). This would provide direct storage expansion for the server. However, this configuration cannot be a bottleneck that significantly hinders performance.
I have an Ubuntu 9.10 machine with three ethernet interfaces, eth0, eth1 and eth2. eth2 is connected to a private network. eth0 and eth2 are connected to two different LANs. Either one will provide access to the internet. All three networks have DHCP servers. Using Ubuntu's the default settings (And Gnome), when I boot up all the interfaces are active and my system gets three IP addresses. However any attempt to access the internet results in connection timeouts and other weirdness.
I suspect that traffic is going out on one NIC (like eth0) and coming back in on another (like eth1). I'm not sure what's going on. The only way I can access the internet at the moment is to bring two of the devices down with ifdown. How can I configure eth0 as my primary interface so all trafic goes out by default on that interface, while keeping the other two active? Also, I want to make sure Avahi broadcasts properly on all three IPs so that the computers on the LAN of eth1 can still connect to myHostname.local...
Here's my routing table: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 172.16.151.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 172.16.30.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 10.1.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 0.0.0.0 172.16.30.2 0.0.0.0 UG 0 0 0 eth0 0.0.0.0 10.1.0.1 0.0.0.0 UG 0 0 0 eth1
I want the 172.16.30.2 network to be the primary one and the 10.1.0.0 network to be the secondary one. My nameservers are also incorrect. It seems like Ubuntu is bringing the networks up in order, eth0, then 1, then 2, and the DHCP information from eth1 is overriding eth0, and eth2 is overriding eth1. How can I reverse this so the DHCP information from eth0 is the "master"? This seems to be an issue with Gnome's NetworkManager.
Last night I created a fresh install of Ubuntu Server 10.10. I was working through a tutorial to set up a development server for home use, and everything worked perfectly. I was able to install OpenSSH, Apache, MySQL, and PHP (and Vim) with no problems. I was also able to use "ifconfig" to determine the network address of the server and I was able to view web pages on the server from another machine on my home network, using a browser. So, everything was "peachy". [By the way: The server is connected to the router using a CAT5 cable. This is a WIRED connection] I shut the Ubuntu server down at the end of the night and, now that I have rebooted this morning, I have apparently lost the network interface. I cannot ping anything from the server. If I run ifconfig, only the "lo" configuration is listed, with the 127.0.0.1 address.
I installed Ubuntu 10.04 for the first time and had a few issues to put my laptop's wireless device to work (see thread [URL]I am now able to use the wireless connectivity but I still have a problem. Every time I reboot Ubuntu, the system does not seem to recognize that a wireless device is present. To overcome this problem I remove the driver and once this is done I activate the driver.The system then finds the wireless device, enables it and connects to the default wireless connection.