Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have been installing fc 64 on a few servers. I noticed that the transfer rate between the servers, on the same network is extremely slow. Maybe 100 kbs if lucky. Wget is a joke....
I get 10 mbs between the other servers and 1 mbs from server to another server on another network..
Originally posted by joey52 Emailed it to you. I also paid for membership but i can't send pm's as of yet. Can you make a note on that one also.
Thanks
Cool, will certainly update Jeremy (the admin), thank's for the donation!
As for the email...
Wow! 10 NIC's in one box!
The "Gigabyte Card" is a bit too generic, if you can post:
/sbin/lspci
We can see what kind of card you actually have (or rather the chipset on the card).
You'll also want to see which modules are loading:
/sbin/lsmod
And your current kernel:
uname -r
You might also want to look at your log files, there could be a reason that traffic is creeping, maybe your firewall is extremely restrictive to the point of delaying traffic to 'sniff'.
I'll also move this to the networking forum, they'll certainly be able to troubleshoot this a lot better over there than in Newbie.
cat /sbin/lspci Yields this mess. By the looks of things, either I deleted some important stuff, ot I need to install something?
Quote:
Àt¥íÃIÄÛëLâ¹ÞL÷AÿÕ1Ò Status: D%d PME-Enable%c DSel=%d DScale=%d PME%c[]A\ÃfffffffffHìH
À Status: RQ=%d Iso%c ArqSz=%d Cal=%d SBA%c ITACoh%c GART64%c HTrans%c 64bit%c FW%c AGP3%c Rate=%s
zCommand: RQ=%d ArqSz=%d Cal=%d SBA%c AGP%c GART64%c 64bit%c FW%c Rate=%s
Command: DPERE%c ERO%c RBC=%d OST=%d
Status: Bus=%u Dev=%u Func=%u 64bit%c 133MHz%c SCD%c USC%c, DC=%s, DMMRBC=%u, DMOST=%u, DMCRS=%u, RSCEM%c
Secondary Status: 64bit%c, 133MHz%c, SCD%c, USC%c, SCO%c, SRD%c Freq=%d
Status: Bus=%u Dev=%u Func=%u 64bit%c 133MHz%c SCD%c USC%c, SCO%c, SRD%c
: Upstream: Capacity=%u, Commitment Limit=%u
: Downstream: Capacity=%u, Commitment Limit=%u
Message Signalled Interrupts: 64bit%c Queue=%d/%d Enable%c
Slot ID: %d slots, First%c, chassis %02x
Bus: primary=%02x, secondary=%02x, subordinate=%02x, sec-latency=%d
!!! Unknown I/O range types %x/%x
!!! Unknown memory range types %x/%x
!!! Unknown prefetchable memory range types %x/%x
BridgeCtl: Parity%c SERR%c NoISA%c VGA%c MAbort%c >Reset%c FastB2B%c
Prefetchable memory behind bridge: %08x-%08x
Prefetchable memory behind bridge: %08x%08x-%08x%08x
Memory behind bridge: %08x-%08x
I/O behind bridge: %08x-%08x
Memory window %d: %08x-%08x%s%s
BridgeCtl: Parity%c SERR%c ISA%c VGA%c MAbort%c >Reset%c 16bInt%c PostWrite%c
16-bit legacy interface ports at %04x
!!! Unknown header type %02x
!!! Invalid class %04x for header type %02x
Control: I/O%c Mem%c BusMaster%c SpecCycle%c MemWINV%c VGASnoop%c ParErr%c Stepping%c SERR%c FastB2B%c
Status: Cap%c 66Mhz%c UDF%c FastB2B%c ParErr%c DEVSEL=%s >TAbort%c <TAbort%c <MAbort%c >SERR%c <PERR%c
Interrupt: pin %c routed to IRQ %d
## %02x.%02x:%d is a bridge from %02x to %02x-%02x
!!! Bridge points to invalid primary bus.!!! Bridge points to invalid bus range.Discovered device %02x:%02x.%d
WARNING: Bus mapping can be reliable only with direct hardware access enabled.
%02x:%02x.%d%04x: (prog-if %02x [%s] (rev %02x) [size=%dM%dK Region %d: I/O ports at <ignored> [disabled]<unassigned>Memory at non-32-bit64-bitlow-1Mtype 3 (%s, %sprefetchable)<invalid-64bit-slot>%08x%08x[virtual] Power Management version %d
Bridge: PM%c B3%c
AGP version %x.%x
PCI-X non-bridge device.bridgesimplePCI-X bridge device. Expansion ROM at Address: %08x Data: %04x
Capabilities: <available only to root>[%02x] Vital Product Data#%02x [%04x]
<chain broken> Secondary status: SERR (prefetchable) I/O window %d: %08x-%08x%s
Subsystem: %s
slowmediumfast?? BIST is running BIST result: %02x
Latency: %d (, Cache Line Size %02x%dns max%dns min Flags: %s devsel, IRQ %d, latency %duser-definable features, 66Mhz, fast Back2Back, stepping, VGA palette snoop, bus master, %02xevice: Class: %s
SVendor: %s
SDevice: %s
ProgIf: %02x
Rev: %02x
Summary of buses:
%02x.%d Bridge to %02x-%02x <crossing bug> <overlap bug>%02x: Entered via %02x:%02x.%d
Primary host busSecondary host bus (?)Only root can map the bus.-d: %s-s: %s--versionlspci version 2.1.99-test35$@ã#@$@$@$@&$@5$@H$@Ô@@wA@wA@wA@wA@wA@wA@wA@wA@wA@wA@wA@wA@wA@wA@wA@wA@wA@wA@wA@wA@Ü@@wA@ö@@wA @wA@wA@wA@@wA@wA@wA@2A@Ä@@wA@wA@wA@wA@=A@aA@wA@lA@wA@¾A@lspci: Unable to allocate %d bytes of memory/usr/share/hwdata/pci.idspcilib: Decided to use %s
Trying method %d......No.
...OK
Out of memory (allocation of %d bytes failed)This access method is not supported.Cannot find any working access method.Unaligned write: pos=%02x,len=%dUnaligned read: pos=%02x, len=%d%x: dump: Malformed line%x:%x:%x.%d%x:%x.%d dump: Cannot open %s: %sdump: File name not given.dumpdump: line too long or unterminatedWriting to dump files is not supported.%s: %s: %s
%s, line %d: duplicate entry%s, line %d: parse error%x%xreadstat<too-large>%s %s%s: Unknown device %04xUnknown device %04x:%04x%s [%04x]Class %04xSecO SecP Master PriO PriP %s%s%s%s%s<pci_lookup_name: invalid request>êÕÿÿÿÿÓÿÿEÓÿÿÔÿÿêÕÿÿêÕÿÿêÕÿÿêÕÿÿÔÿÿ»Ôÿÿ+ÕÿÿêÕÿÿêÕÿÿêÕÿÿêÕÿÿöÕÿÿInvalid domain numberInvalid bus numberInvalid slot numberInvalid function number':' expectedInvalid vendor IDInvalid device ID/sys/bus/pci...cannot open %s...using %sFile name too longValue in %s too longError reading %s: %sresource%llx %llxSyntax error in %s%s/devicesirqCannot open %sDirectory name too longconfigsysfs_read: read failed: %ssysfs_write: write failed: %sLinux-sysfs%s/devices/%04x:%02x:%02x.%d/%sResource %d in %s has a 64-bit address, ignoringsysfs_scan: Couldn't parse entry name %ssysfs_read: tried to read %d bytes at %d, but got only %dsysfs_write: tried to write %d bytes at %d, but got only %d/proc/bus/pci%s/%02x/%02x.%dproc_read: read failed: %sproc_write: write failed: %sLinux-proc%x %x %x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08x %08xproc: parse error (read only %d items)proc_read: tried to read %d bytes at %d, but got only %dproc_write: tried to write %d bytes at %d, but got only %dScanning bus %02x for devices...
Bus %02x seen twice (firmware bug). Ignored.Device %04x:%02x:%02x.%d has unknown header type %02x.
%04x:%02x:%02x.%d: Invalid 64-bit address seen.%04x:%02x:%02x.%d 64-bit device address ignored.ÈxÿÿäÿÿTÿÿ4
ÿÿTÿÿ|$ÿÿTÿÿ¬ÔÿÿÄtÿÿì´ÿÿ
4ÿÿ<¤ÿÿ\$ÿÿ¤ÿÿÌÿÿäÿÿtÿÿD4ÿÿlTÿÿ
You don't actually have to "cat" the /sbin/lspci, it will do that itself. If you are having problems grabbing the output to post up here and that's why you are catting it, execute:
/sbin/lspci | less
And scroll using the up/down arrow keys, same with:
/sbin/lsmod | less
You've got a kernel that isn't quite up to date, but should certainly suffice to have the modules that a newer one would, so I wouldn't really worry about that being part of your issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.