similar to: Ethernet puzzle

Hello, I have a problem with the latency of the packets passing a Linux router, and I thought perhaps you could put some light on it. It''s quite simple. I have one ADSL connection, and a LAN. The gateway is the Linux machine or a Windows XP machine. When the wXP is routing, for a host inside the LAN, the latency of, for example, the Counter Strike game to a given server is around 20 to 30

Hello, I''m running xen-3.0.2-3 and try to share the 4 ports of a adaptec 4port ethernet card between dom0 and domU by using pciback.hide. Therefor I had to modify the domU driver for the tulip cards due to the fact that there is only one eeprom on the board and all 4 ports of the card are using the same interrupt line. When starting the dom0 tulip driver (unmodified) I get two working

Hi, My machine just bombed when I did the following stupid command. :(){:|:};: Zsh chewed up everything on the machine... I ran it knowing I'd probably have to reboot. But, I hardly expected it to panic. Or, was that normal? Anyway, the following is some detail... Please mail me if there is more I'm ment to do. Thanks in advance :) ultraviolet@tulip:~ %> uname -a FreeBSD

Hey guys, I am planning to buy some components for a Linux router that will handle the Internet access of 200 computers (includes tc shaping) and some inter sub-network routing (at least 100MBps per eth - and there are 3 eth cards). I was thinking of a: Pentium 4 - 3GHz 256 or 512MB RAM Network Cards. Now - I wonder what is more important: the processor speed or the amount of RAM. And can you

Hi all, I found the web site for R and decided to install it on my freebsd system; however, I have run into 'permission problems' during execution. I do the standard .configure, make, make check, make install and install into the default location of /usr/local/... but when a normal user attempts to run 'R' I get the following: --- [tulip ~]% R R : Copyright 2001, The R

Hi all, I've recently upgraded a system from CentOS 4.4 to CentOS5, and now when the system boots, the r8169 ethernet card doesn't come up. After the boot sequence, if I type "ifup eth1 | ifup eth1.10 | ifup eth1.203" then the adapter starts up ok. It seems to be something with the boot sequence it loads the ethernet adapters a different way around (ie 4.4 eth0 is now

I want to setup a linux box with samba as a file and print server for a LAN of 20 NT 4.0 SP3 workstations. I want the home direcotories to be on the server the clients to have roaming profiles. For this, do I have to make the linux box a domain controller? I want to avoid it if I can, because the domain control code in not on the production releases. I don't want to setup an NT server either.

Hello ! I'm having serious problems with Samba's writing speed (both 2.0.5a from RH 6.1 and 2.0.6 compiled from sources) on a 100Mbit network. If I write a file with block size 65487 or less, then the writing speed is about 7-8 MB/s - a very nice value, my bow to the Samba team :) If I change the block size to 65488 or more, then the writing speed falls down to 3 MB/s, which is not what

Hi, Any body having idea to find the NIC Capacity / BW (10 / 100 Mbps) ? Whether the interface may be eth0/eth1/ppp0 or some other. Is there any related IOCTL avialable, if so just give the linux-2.4.18 file path. thanks, Srikanth. _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Hi, I am looking for dual or quad fast ethernet NICs that work with CentOS. There is no need for high performance so regular fast/pci is ok. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20101228/1f5e2944/attachment-0001.html>

Greetings, I have run into a kernel oops that I can generate at will, and that hangs my machine. The machine is running Gentoo Linux, 2.6.11 kernel and gcc 3.3.5. I can post more information if needed. The problem arises when I mount an SMB share from a 2000-series Snap server (network appliance); software version 3.4.804, hardware 2.0.3. The mount is fine, and can sit for a long time. However,

For those of you running SuSE 9.1, I do not recommend upgrading to 9.2 at this time. Refer to http://shorewall.net/myfiles.htm for information on my configuration: a) On Ursa: 1) After the upgrade, both of the NICs were recognized as "configured" in YAST yet neither of them would start; ifup claimed that no configuration could be found for either interface. Only got them running

This series add two important features. One of them changes the .ndo_tx_timeout to include an extra parameter to identify the stuck queue. Many drivers are using a nester loop to identify which queue is stooped/stucked. This is a redundant work since dev_watchdog is doing exactly the same thing. This is so interesting for other drivers to in terms of code optimization. The second part (second

This series add two important features. One of them changes the .ndo_tx_timeout to include an extra parameter to identify the stuck queue. Many drivers are using a nester loop to identify which queue is stooped/stucked. This is a redundant work since dev_watchdog is doing exactly the same thing. This is so interesting for other drivers to in terms of code optimization. The second part (second

At the risk of angering the crash Gods, my sustem has NOT crashed again since I downgraded the kernel from 2.6.18-1.2239.fc5 to 2.6.18-1.2200.fc5. Given that newfound stability, and my lack of time, I'm going to put on hold any further diagnostics, until the next kernel revision is released. I have submitted a report at bugzilla.redhat.com (bug 218128). (Ah, nuts; accidentally created a

A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only. Michael S. Tsirkin (3): netdev: pass the stuck queue to the timeout

Sorry about the churn, v10 was based on net - not on net-next by mistake. A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only.

Sorry about the churn, v10 was based on net - not on net-next by mistake. A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only.

Yet another forward declaration I missed. Hopfully the last one ... A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only.

A bunch of drivers want to know which tx queue triggered a timeout, and virtio wants to do the same. We actually have the info to hand, let's just pass it on to drivers. Note: tested with an experimental virtio patch by Julio. That patch itself isn't ready yet though, so not included. Other drivers compiled only. Michael S. Tsirkin (3): netdev: pass the stuck queue to the timeout