From kanwaldeepsingh@hotmail.com Fri, 02 Mar 2001 03:36:20 Date: Fri, 02 Mar 2001 03:36:20 From: kanwaldeep singh kanwaldeepsingh@hotmail.com Subject: [vortex-bug] Linux eth0 and eth1 problem

I have five linux servers used as RAS servers having two ethernet cards.

I two cards has ip address:

eth0 172.18.1.11

eth1 172.16.1.191

i can ping to both the networks on one server , but on other servers it doesn't even ping to eth1 network ( saying destination unreachable).

My route table is ok, all the servers has same network configuration.

Did anybody faced this type of problem before.

Kanwaldeep

Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

From sedat.sengul@vestel-usa.com Thu, 08 Mar 2001 16:52:29 -0800 Date: Thu, 08 Mar 2001 16:52:29 -0800 From: Sedat Sengul sedat.sengul@vestel-usa.com Subject: [vortex-bug] About pci-scan.o module for 3c905-TX ethernet card Hi; I have 3c905-TX ethernet card. 2.2.14-5.0 version kernel with Red Hat dist. 6.2 I compiled 3c59x.c and pci-scan.c files with my kernel and obtained object modules. I know where to put 3c59x.o module to make my kernel capable of linking after boot my ethernet driver, but it depends on pci-scan.o Where should I put pci-scan.o module to make automatic module insertion after booting? I need help, Thanks Sedat Sengul From fleury@cs.auc.dk Tue, 27 Mar 2001 11:50:28 +0200 Date: Tue, 27 Mar 2001 11:50:28 +0200 From: Emmanuel Fleury fleury@cs.auc.dk Subject: [vortex-bug] 3c59x new bug ? Hi, A friend and me are testing the 2.4 kernel under high bandwith. We want to perform some experiments on the netfilter statefull firewall. But our first test was only with the 2.4 kernel to calibrate our experiment. Then we notice a bottleneck in the network (actually we add a pentium 75 box as a router in an fake network designed for such experiments, so we knew what was the behavior of the network without the 2.4 box). We take a look at the connections (using tcpdump) and we noticed a big amount of packets loss. Actually, hte high bandwith has nothing to do with it. The loss of packet remain the same whatever the bandwith is used. We were thinking about a broken hardware (network cable, NIC, ...) but it happens again and again except when we add a new network card (EtherExpress 10/100) in place of one of the two 3C905B-TX. In this case the bottleneck only appear on one way. Then we start to look at some log message and we get this one (several times) from the kernel (in /var/log/kern.log). Mar 25 10:32:03 cerium kernel: eth0: Transmit error, Tx status register 82. Mar 25 10:32:03 cerium kernel: Flags; bus-master 1, full 0; dirty 394461(13) current 394461(13). Mar 25 10:32:03 cerium kernel: Transmit list 00000000 vs. c3b412d0. Mar 25 10:32:03 cerium kernel: 0: @c3b41200 length 8000004a status 0001004a Mar 25 10:32:03 cerium kernel: 1: @c3b41210 length 8000004a status 0001004a Mar 25 10:32:03 cerium kernel: 2: @c3b41220 length 80000052 status 00010052 Mar 25 10:32:03 cerium kernel: 3: @c3b41230 length 80000147 status 00010147 Mar 25 10:32:03 cerium kernel: 4: @c3b41240 length 8000004a status 0001004a Mar 25 10:32:03 cerium kernel: 5: @c3b41250 length 80000052 status 00010052 Mar 25 10:32:03 cerium kernel: 6: @c3b41260 length 8000004a status 0001004a Mar 25 10:32:03 cerium kernel: 7: @c3b41270 length 80000123 status 00010123 Mar 25 10:32:03 cerium kernel: 8: @c3b41280 length 80000052 status 00010052 Mar 25 10:32:03 cerium kernel: 9: @c3b41290 length 8000012b status 0001012b Mar 25 10:32:03 cerium kernel: 10: @c3b412a0 length 8000004a status 0001004a Mar 25 10:32:03 cerium kernel: 11: @c3b412b0 length 80000052 status 00010052 Mar 25 10:32:03 cerium kernel: 12: @c3b412c0 length 800004a3 status 800104a3 Mar 25 10:32:03 cerium kernel: 13: @c3b412d0 length 8000004a status 0001004a Mar 25 10:32:03 cerium kernel: 14: @c3b412e0 length 80000052 status 00010052 Mar 25 10:32:03 cerium kernel: 15: @c3b412f0 length 8000004a status 0001004a When you look at the tcpdump logs, this problem looks very similar to http://www.cs.unc.edu/~jeffay/dirt/FAQ/fxp_drain.html I think that the 3C59x keep several packets and at one point (don't know which one !) send them very quickly. So the receiver is overloaded and the emiter has to resend the data. My question is: Is this bug a new one ? And if not, is there a patch for that ? I really look after this patch but I didn't find one. Thanks -- Emmanuel I'm killing time while I wait for life to shower me with meaning and happiness. -- Calvin & Hobbes From bogdan.costescu@iwr.uni-heidelberg.de Tue, 27 Mar 2001 14:17:00 +0200 (CEST) Date: Tue, 27 Mar 2001 14:17:00 +0200 (CEST) From: Bogdan Costescu bogdan.costescu@iwr.uni-heidelberg.de Subject: [vortex-bug] 3c59x new bug ? On Tue, 27 Mar 2001, Emmanuel Fleury wrote: > Mar 25 10:32:03 cerium kernel: eth0: Transmit error, Tx status register > 82. Please read http://www.scyld.com/network/vortex.html for a possible explanation for this problem. Also try searching the archives of this list (and also vortex@scyld.com) for occurences of the same problem. Sincerely, Bogdan Costescu IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868 E-mail: Bogdan.Costescu@IWR.Uni-Heidelberg.De From terokoi@nic.fi Thu, 29 Mar 2001 11:00:42 -0000 Date: Thu, 29 Mar 2001 11:00:42 -0000 From: terokoi@nic.fi terokoi@nic.fi Subject: [vortex-bug] Bug with Darwin Streaming Server Hello all! I'm new at the list and I don't know has this issue been here before: It seems that 3Com's 3C9xxx ethernet-card family is partly uncompatible with Linux distribution (RedHat 7.0) of Darwin (=Quicktime) Streaming Server! Problem occurs when the server is doing http-streaming over port 80. It sends nothing to the receiver with that method for bypassing the firewalls! Here's what Apple's tutorials tells about that method: "HTTP tunneling. When all else fails, use HTTP tunneling to "wrap" your RTP packets inside ordinary HTTP packets. This usually allows the stream to pass through any firewall or NAT router. To enable HTTP tunneling, each viewer must configure her QuickTime Settings control panel by checking Use HTTP and setting the port to 80 (or the port used for HTTP transfers by your streaming server), and the server must be set up to support HTTP tunneling." And I'm not the only one that has faced this problem according QT mailing list. I know I should be far more accurate, but I'm not the system operator and I don't know about the driver version (3C905C card) of the box I'm running my DSS. But I have root-access, so I can dig up all information what's needed if you specify where it's at. Here's quote that I had from Apple's Quicktime specialist on their mailing list: --->Quote start If you are STILL having problems streaming over HTTP, and if you are certain that Apache is not running, then find out what your Ethernet card and driver you are using. We once ran into an issue where I was helping someone with a similar problem, and they were using a 3COM 3C9xxx network interface card. They ended up replacing the card with a cheap Linksys Ethernet card with a Digital Chip using the "tulip" driver. <---End quote Do you know is this a driver issue or some hardware bug?!? - Tero Koivula, Finland. terokoi@nic.fi ________________________________________________________________ Ilmainen Internet @ http://www.nic.fi/ From bogdan.costescu@iwr.uni-heidelberg.de Thu, 29 Mar 2001 13:20:49 +0200 (CEST) Date: Thu, 29 Mar 2001 13:20:49 +0200 (CEST) From: Bogdan Costescu bogdan.costescu@iwr.uni-heidelberg.de Subject: [vortex-bug] Bug with Darwin Streaming Server On Thu, 29 Mar 2001 terokoi@nic.fi wrote: > Problem occurs when the server is doing http-streaming over port 80. It sends > nothing to the receiver with that method for bypassing the firewalls! Before claiming anything else, please try to get a glimpse at the traffic using tcpdump or some other packet capturing tool. By doing it both on the server (which means before the packets actually hit the driver/NIC) and client (to see what is received) you can narrow down the possible causes; it's even better if you try with 2 different clients or try to sniff the packets as they go out of the server NIC (on a non-switching hub) to eliminate client-related problems. Have you also tried to connect a client using HTTP without a firewall ? Maybe the firewall is eating some packets... Sincerely, Bogdan Costescu IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868 E-mail: Bogdan.Costescu@IWR.Uni-Heidelberg.De From terokoi@nic.fi Thu, 29 Mar 2001 11:35:40 -0000 Date: Thu, 29 Mar 2001 11:35:40 -0000 From: terokoi@nic.fi terokoi@nic.fi Subject: [vortex-bug] Bug with Darwin Streaming Server Thanks for quick reply, Bogdan! >> Problem occurs when the server is doing http-streaming over port 80. It sends >> nothing to the receiver with that method for bypassing the firewalls! > > Before claiming anything else, please try to get a glimpse at the traffic > using tcpdump or some other packet capturing tool. Ok, the problem is not that black and white as I first sayed, because the streams get trough with mac Quicktime client, but not every time. About every fifth time. And PC clients aren't getting anything. And I did some network monitoring from the client side: Log about streams going via http port 80: http://gamma.nic.fi/~terokoi/logfile.pdf (20 kt) That log file is from the QuickTime 4.1.2 Mac (OS 9.0.4) client succesfully receiving a port 80 stream from my DSS streaming server. I have pointed out the position where it gets idle if it's not going to receive a stream at all. Hope that logfile helps. > Have you also tried to connect a client using HTTP without a firewall ? > Maybe the firewall is eating some packets... I don't have firewall at my office and my server provider tried to connect right from the serverroom (with pc client) without success. - Tero, Finland. ________________________________________________________________ Ilmainen Internet @ http://www.nic.fi/ From barry@penrallt.clara.co.uk Thu, 29 Mar 2001 13:00:32 +0100 Date: Thu, 29 Mar 2001 13:00:32 +0100 From: Barry Hill barry@penrallt.clara.co.uk Subject: [vortex-bug] setting 3c509 media type ?? Hi, First of all, sorry if this isn't the most suitable list, but I guess that there are a number of people who would know the answer :-) How do I set the media type on a 3c509 card? It defaults to BNC and doesn't seem to autodetect the TP hub :-( Best regards, Barry mailto:barry@penrallt.clara.co.uk From vlado_potisk@tempest.sk Sat, 31 Mar 2001 16:30:55 +0200 Date: Sat, 31 Mar 2001 16:30:55 +0200 From: Vlado Potisk vlado_potisk@tempest.sk Subject: [vortex-bug] 3com card initialization problem I'd like to report a bug I encountered, but I am not sure if it is vortex specific... The equipment: - PC hardware - 3com PCI card 3c905C - 3com ISA card 3c509B - Linux kernel 2.2.17 or 2.2.19 with both drivers compiled in If there is only one card physically installed (either ISA or PCI), everything is fine, but if I install both cards, only one card gets recognized and initialized on startup (no eth1) I found a workaround: when I compile both drivers as modules, the problem disappears and everything works as expected. That's why I assume this is not a hardware problem. Thanks, Vlado