similar to: Hard-set network via ifup scripts...

Greetings, I recently installed CentOS 5 on Dell PE 1750 server. I have noticed that the speed and duplex settings are 100 Half Duplex. I tried to change the duplex settings to full, but no success. I got the error message "Cannot get current device settings: Operation not supported". Does anyone else experience this issue?. Below is the error message and some more details about my box.

I have a server with dual nic's running centos 5.2 1 nic connects to the cable modem, which has 15m d and 2m up, but speed tests barely come back at 5mb down including road runner's internal speed test. I hook up my laptop to the same modem, same port, using the same cable and I get 17mb down. I have ruled out iptables, nics (because same result on both nics), cables, cable modem(with

I figured out how to force 10 megabit full duplex on my ethernet interface. The trick is i need it to stick in case of a reboot so i don't have to reforce it. I have not been able to figure that one out yet. I have not found it in the man's or google yet. If someone could point me in the right direction i would be much obliged. -- My "Foundation" verse: Isa 54:17 No

I and testing command line to up and down ethernet connection. if I perform following, client can not re-connect. ????? ifconfig eth0 down ????? ifconfig eth0 up if I use following, client can re-connect: ????? ifconfig eth0 down ????? ifup eth0 What difference between "ifconfig up" and "ifup"? thanks.

Hello, since updating to Centos 7.4 the ifup-post script in /etc/sysconfig/network-scripts does not behave as it did before the update. I use it to configure additional routes via? /sbin/ifup-local with the parameter of the interface being upped, but it seems to pass only 'lo' as interface name. Before it passed correctly 'eth0:0' of the virtual interface. Added a line in

All, This is a fresh, un-f#$ked-with OpenSUSE install after adding the Tumbleweed repository and doing a dup. I installed the Hypervisor with Tools for which it prompted me for Xen or QEMU and I chose Xen. No bridge was made. When I go to create a fully virtualised machine, it nao has the error: Error: Device 0 (vif) could not be connected. Could not find the bridge, and none was specified.

Hi all I have a SuSE 9.3 domU. It has a eth0 interface, corresponding to some vif interface in the dom0. Running ifup eth0 doesn''t seem to work. This means I don''t get any network. It seems that /sbin/ifup relies upon /sbin/getcfg but getcfg does not seem to find the right configuration for the eth0 device. A attached a patch below with a work around for this.

tags 671018 +patch thanks This issue has been fixed upstream for 4.2 by using the same hotplug scripts for tap devices as for vif devices rather than using a special qemu-ifup script. I don't think this is an appropriate thing to backport to 4.1 for wheezy so therefore I think the right fix is as Pierre suggests to set the MAC address in the qemu-ifup script. In terms of a patch to the

Hello, I have some domU accounts running CentOS 4.4 and whenever I try to bring up the network interface it fails with the following errors: [root@test5.liquidweb.com] ~ # ifup eth0 Usage: grep [OPTION]... PATTERN [FILE]... Try `grep --help'' for more information. Usage: grep [OPTION]... PATTERN [FILE]... Try `grep --help'' for more information. Usage: arping [-fqbDUAV] [-c

Hello all I am setting up a Centos 6 machine with one network card & one onboard network port. Both are recognized & work. Onboard Network port is unused yet, but is required for dedicated access to LTSP LAN, which would allow older PIII machines to boot from this system. I have installed LTSP but again Networking seems to be the problem area, as the clients won't boot from this

Package: xen-utils-common Version: 4.1.4-3 Severity: important Dear Maintainer, Executive summary: dist-upgrade - squeeze to wheezy. Rebooted machine; no default route on network interface eth0. Commented 'transfer_addrs' function in network-bridge produced a machine which worked after reboot. We're using network-bridge as our xen networking configuration. After rebooting the

Hi folks on debian stable I've a default samba file sharing config. Everything works perfectly (almost...) - samba version 3.6.6 >From linux and windows clients (wired and wifi too) when I (i.e. listen musics) often (one time every 4/5 minutes) networks suddenly collapse (for less one second) and immediately goes up. So I've an interrupt of broadcast (this happens also if I use rsync

Package: xen-utils-common Version: 4.0.0-1 Severity: important Tags: patch --- Please enter the report below this line. --- when you use "hardware" virtual machine (with qemu) with xen configured for bridging the network script treates a tap interface and then /etc/xen/scripts/qemu-ifup adds it to the bridge. That would be ok but tap interfaces have a random mac address and the bridge

Are any of you using the Intel 320 as ZIL? It''s MLC based, but I understand its wear and performance characteristics can be bumped up significantly by increasing the overprovisioning to 20% (dropping usable capacity to 80%). Anyone have experience with this? Ray

The short version. Copying over SFTP to our centos boxes maxes out at 2MB a sec. The Question: Is there some sort of speed limitation somewhere in the ssh/sftp daemon? Does anyone have any idea why this could be happening? The long version We have centos 4.6 installed on 2 different machines, different hardware, different nics. Even on 2 different subnets. I've tried different switches,

Dear All, I have an onboard Realtek RTL8111/8168B NIC. from lspci -vv : 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) It is detected, but why the speed is always 100Mbps, already change cable but still no luck. I use ethtool and from the output it seems that system know that this NIC support gigabit speed : ???????

So what does everyone out there use to generate web statistics these days? Are the tried and true awstats or webalizer still the best out there? Ray

We've just moved one a new server from our sever room, where I built it, to the datacenter. We want to force autoneg off, and tell it gigabit and full duplex. Using ethtool, I get no errors setting the speed or duplex. HOWEVER, autoneg on works... and autoneg off utterly refuses to work, and gives: ethtool -s eth0 autoneg off Cannot set new settings: Invalid argument not setting autoneg

Hi, In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, link on the interface becomes ready several seconds after 'ifup' is executed, which for some buggy images like cirros may slow down boot process for up to 1 minute [2]. If we switch from e1000 to virtio, the link is brought up and ready almost immediately. For the record, I am using the following versions: - L0

I have a series of static routes in route-eth0 Recently I had to made changes and could not find an effective way to get the old routes out and the new routes in. ifdown-route seems to apply the content of route-eth0 to take down the routes listed and ifup-route brings up routes based on route- So what ends up is that the old routes never go away, just new routes added. ifdown eth0; ifup