similar to: Routing issue?

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.

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

Two problems I hope to solve: 1. The switch being used has autoneg off and has port set to 100 full duplex. 2. Many times NIC fails to come up properly during PXE boot: r8169: eth0: link down ADDRCONF(NETDEV_UP): eth0: link is not ready I can't use ethtool to disable autoneg because the nic driver is built into a bzImage. The root fs is currently being mounted via nfs during pxeboot at

Hi, What's the correct way to disble TSO (TCP Segmentation Offload) in RHEL5? I have tried adding those options in ifcfg-ethX configuration file: # grep ETHTOOL /etc/sysconfig/network-scripts/ifcfg-eth0 ETHTOOL_OPTS="tso off" And also with: ETHTOOL_OPTS="-K eth0 tso off" But when restating the server TSO is enabled: # ethtool -k eth0 tcp segmentation offload: on As

I am having an extremely strange issue with a BL460c1 (G1) blade on a c7000 enclosure. I could not for the life of me get the machine to ping the gateway or any other blade on the same enclosure (yes, the subnet mask was correct & quadruple-checked); although pinging to the local IP works. I was almost convinced that it was a network or hardware issue; until I asked someone to try

Anyone know off the top of their head the "right" way to hard set a link automatically to 100Mbps Full Duplex, etc using the ifup or ifcfg files? Don't see options in the scripts that might cover this, but maybe there's a more elegant way to do it than to do something in rc.local or hack up the ifup files myself... Ray

I come across some problem when using xen-4.1.1-rc1-pre from xen-4.1-testing tree and 2.6.32.36xen linux kernel from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git. when I use ''xend restart'' , it hangs when kernel dmesg printing ''Bridge firewalling registered'' and the console show below messages: localhost# xend restart Nothing to flush. Cannot

I have no output in the logs, but /etc/init.d/network restart fixes the issue. I am rsync/scp (10GB) data from one 100MB Full duplex host to an ASUS M3A78-EM (RTL8111B/C). It locks up around the 1.5GB Tx mark. If I ethtool -s eth0 autoneg off speed 100 duplex full it does not happen again. Ideas? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -

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

> Hi, > > Recently I'm noticing an interesting issue. > My CentOS servers are trying to send logs to a logging server via 514/udp, > however I'm not receiving anything. > > I did the following on CentOS > *tcpdump -vvv -nn udp -i esn160 port 514* > > In another session on the same server: > *nc syslog-server -u 514* > > tcpdump started to show me

Am 07.01.2016 um 11:58 schrieb Sébastien Le Ray: > Hi list (and happy new year), > > I'm experiencing some troubles using Samba (4.1.17 debian version) over > VPN. Basically we've following setup : > > PC === LAN ===> VPN (WAN) ==== LAN ===> Samba file Server > > Copying big (say > 1MiB) files from PC to Samba file server almost > always ends up with a

Le 07/01/2016 12:22, Reindl Harald a écrit : > > /usr/sbin/ifconfig eth0 txqueuelen 100 > ______________________________________________ > > ifcfg-eth0: > > ETHTOOL_OPTS="-K ${DEVICE} tso on lro off; -G ${DEVICE} rx 128 tx 128" > ______________________________________________ > > sysctl.conf: > > net.core.rmem_max = 65536 > net.core.wmem_max = 65536

Hi I installed xen by following this link: http://www.howtoforge.com/virtualization-with-xen-on-debian-lenny-amd64 Dom0(debian) has two IP :174.x.x.79 , 67.x.x.32 gateway is 174.x.x.65 DomU(win2003) IP is :67.x.x.38 The problem is : 1.weird network issue in win2003(can not access the internet in win2003): A:weird ping time for 127.0.0.1 B:weird ping time for its own ip 67.x.x.38 C:timeout

I can't explain why 700 msecs aren't enough to avoid timeouts in 100 Mbps networks, but my tests verify it, so I'm writing to the list to request that you increase the default timeo to at least 30, or to 600 which is the default for `mount -t nfs`. How to reproduce: 1) Cabling: server <=> 100 Mbps switch <=> client Alternatively, one can use a 1000 Mbps switch and

Greetings. When I "pull" data from server A to server B, with nfs, server B reports a high load when viewed via uptime. The load is upwards of 6.x. Server A's load remains light. When I "push" the data, server A's and B's loads are relatively light. When I change the mount point from nfs to cifs, I don't see this problem. I also don't have this

based on what your saying.. im not thinking this is samba related. I guess check your switches and find the "fault" autosense for your nics.. You can use thisone to disable autosence ethtool -s ethX autoneg off en set correct nic speed. ethtool -s ethX speed XXXX BUT ! check your switches first. greetz, Louis >-----Oorspronkelijk bericht----- >Van: sambait3 at

I think I got it. Both nfsmount and `mount -t nfs` now default to rsize/wsize = 1 MB. By lowering this to 32K, all issues are gone, even with the default timeo=7. And nfsroot=xxx client responsiveness is a whole lot better. I think when nfsmount was initially written, the default rsize/wsize were much lower, which matched the timeo=7. Now they cause the lags/timeouts that I reported. So

Win2K box and the file server are on the same switch. They are both configured as 100FD, AutoNeg=Off. I have not met anyone so far with that much performance difference, though some reported 1:2 speed ratio. Attached is our config file for your information. I've searched through this mail lists' archives. I couldn't find a solution, though I've seen people reporting similar

In case anyone's interested, I followed up in the linux-nfs mailing list: https://marc.info/?l=linux-nfs&m=156887818618861&w=2 Thanks, Alkis On 9/15/19 10:51 AM, Alkis Georgopoulos wrote: > I think I got it. > > Both nfsmount and `mount -t nfs` now default to rsize/wsize = 1 MB. > By lowering this to 32K, all issues are gone, even with the default > timeo=7. And

Hi all, I''m installing the latest version of puppet (opensource) for Windows on Windows 2008 Server (At Amazon EC2). For some reason, Puppet''s scheduled task is configured to run every 20 hours instead of the desired 30 minutes (as shown in - http://docs.puppetlabs.com/windows/running.html) Is it a bug in Puppet? Is it something that I misconfigured? Screenshot of the