similar to: Failing Network card

Hi, one of our rented root-server has a problem with the network-adapter.The network is interrupted from time to time and i can not longer connect to our server. We can only reboote (remote) the server and restart the network. I think it was an network-driver-problem from an "Intel Corporation 82574L Gigabit Network" --- e1000e But now i have install a new kernel-driver and i have

My Trendnet 26 port managed switch gave up on me so I'm shopping for a new switch. I learned the hard way NOT to trust marketing material from anyone so now I'm asking the list: what am I looking for in a managed, VoIP switch? P.S: For those that don't understand WHY I can't trust marketing material, let me tell you something about the Trendnet switch that's fast becoming

Network stopped just out of the blue leaving this backtrace After this or during this my network switch just stopped working ang got stuck. Maybe the switch made the problem? Thanks, Eliezer Feb 1 04:07:15 localhost kernel: ------------[ cut here ]------------ Feb 1 04:07:15 localhost kernel: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x26d/0x280() (Not tainted) Feb 1 04:07:15

Just noticed that in the trace, it shows an old kernel, so I don't think grub was automatically selecting the latest kernel. Just wondering what process updates the default to be the latest kernel, and if a problem could be an update but grub selecting an older kernel, but other packages updated ? On Fri, Feb 19, 2016 at 10:56 AM, Ian B <ibrierley at gmail.com> wrote: > Hi all, >

Hi, anybody know how to fix this. May 20 12:16:15 wolfpac kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out May 20 12:16:15 wolfpac kernel: Modules linked in: pf_ring(U) af_key iptable_nat ipt_LOG iptable_filter ip_tables nf_conntrack_ipv6 nf_defrag_ipv6 xt_state ip6t_LOG xt_limit ip6table_filter ip6_tables bridge stp llc nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4

Hi all, I'm facing a serious problem with the e100e kernel module for Intel 82574L gigabit nics on Centos 6. The device eth0 suddenly stops working i.e. no more networking. When I do ifconfig from console I get eth0 Link encap:Ethernet HWaddr 00:xx:xx:xx:xx:EA inet6 addr: fe80::225:90ff:fe50:8fea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

Thanks Richard, We currently do all security updates at short notice (as opposed to everything), via a script. I've amended the grub config and rebooted to make sure it will reboot into the correct kernel now, and yes /etc/sysconfig/kernel was different to production servers. We may try all packages if it continues to be unstable now and maybe whatever as its on a dev server to test. Thanks

> Date: Friday, February 19, 2016 12:47:54 +0000 > From: Ian B <ibrierley at gmail.com> > > On Fri, Feb 19, 2016 at 12:33 PM, Richard wrote: > >> > Date: Friday, February 19, 2016 11:08:48 +0000 >> > From: Ian B <ibrierley at gmail.com> >> > >> > On Fri, Feb 19, 2016 at 10:56 AM, Ian B <ibrierley at gmail.com> >> >

We have a webserver that is connected to three different networks. Due to our cabling, we have to run two of those networks over the same physical network. When connecting from OS X and Windows we are occasionally blocked because the client is sending to the wrong interface. Linux clients seem to have no problem at all. I have read the docs and understand that the problems exists because of

Hi all, We have a development server we have just tried updating the kernel & glibc after recent recommendations. Its been stable previously for a few years with only scheduled reboots. Its running Centos 6.6(final) 2.6.32-573.18.1.el6.x86_64 GNU libc 2.12 Upgraded via YUM, rebooted, all fine for several hours, and then network seemed to hang. Not much happening as its a dev server we are

If your phones support PoE, I have had huge success with Zyxel: http://www.amazon.com/ZyXEL-ES1100-16P-16-Port-Ethernet-Unmanaged/dp/B00 5GRETMM/ref=sr_1_3?ie=UTF8&qid=1426296572&sr=8-3&keywords=zyxel+poe If you want to go even cheaper, I have successfully used these as well: http://www.amazon.com/TRENDnet-8-Port-100Mbps-Switch-TPE-S44/dp/B000QYEN

> Date: Friday, February 19, 2016 11:08:48 +0000 > From: Ian B <ibrierley at gmail.com> > > On Fri, Feb 19, 2016 at 10:56 AM, Ian B <ibrierley at gmail.com> > wrote: > >> Hi all, >> >> We have a development server we have just tried updating the >> kernel & glibc after recent recommendations. Its been stable >> previously for a few

I have a customer that has a Trendnet TEW-435BRM router which has the bad habit of rewriting all external connections so the Asterisk server only sees the IP address of the router itself. Up to today this has not been a problem since all extensions are on the local network but now they want to have a couple external IP phones (SIP). I opened up the ports on the router and my phone can register.

I am trying to transport a dd image between to hosts over a cross linked gigabit connection. Both hosts have an eth1 configured to a non routable ip addr on a shared network. No other devices exist on this link. When transferring via sftp I received a stall warning. Checking the logs I see this: dmesg | grep eth e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:1c:c0:f2:1f:bb

a previously rock solid reliable server of mine crashed last night, the server was still running but eth0, a Intel 82574L using the e1000e driver, went down. The server has a Supermicro X8DTE-F (dual Xeon X5650, yada yada). server is a drbd master, so that was the first thing to notice network issues. Just a couple days ago I ran yum update to the latest, I do this about once a month.

I need to get a wireless device for an upcoming trip (USB is preferable to PCMCIA for a long list of reasons) and I'm wondering if anyone has any experience with or recommendations for such items, particularly which ones work with Linux/CentOS. Right now I'm debating between a reasonably cheap Belkin 54G and a slightly more expensive Netgear 54G. Thanks. mhr

Currently, vhost-net is the only consumer of vhost infrastructure. So vhost infrastructure and vhost-net driver are in a single module. Separating this as a vhost.ko module and a vhost-net.ko module makes it is easier to share code with other vhost drivers, e.g. vhost-blk.ko, tcm-vhost.ko. Signed-off-by: Asias He <asias at redhat.com> --- drivers/vhost/Kconfig | 10 +++++++++-

Currently, vhost-net is the only consumer of vhost infrastructure. So vhost infrastructure and vhost-net driver are in a single module. Separating this as a vhost.ko module and a vhost-net.ko module makes it is easier to share code with other vhost drivers, e.g. vhost-blk.ko, tcm-vhost.ko. Signed-off-by: Asias He <asias at redhat.com> --- drivers/vhost/Kconfig | 10 +++++++++-

Hey all, i am fighting with a strange behavior here - i have two systems connected via a direct crosslink wire. After booting, the connection is up and both systems can reach the other one. After a small time window the interface is down. $ dmesg |grep eth4 igb 0000:41:00.2: added PHC on eth4 igb 0000:41:00.2: eth4: (PCIe:5.0Gb/s:Width x4) igb 0000:41:00.2: eth4: PBA No: G13158-000 8021q:

Hello, I have been using Xen on a Debian Lenny server for quite some time. I decided to build a new Dom0 using identical hardware, but newest version of Xen from repositories with Debian Squeeze. I attempting to create a new DomU on the new host which is similar to an existing DomU running on the older Lenny host. The DomU is a three NIC firewall. Two of the NICs are virtualized. One NIC is a