Strange TCP/IP problem?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I've been running 8-hour+ traffic runs on RTL-8139 10/100 ethernet cards connected
by a 10/100 etherswitch and linux-kernel 2.2.14 <-> 2.2.16.  I'm using three cards in each
machine, one for mgt, and two others for data generation/testing.
I use the ip command to set up source-based routing policies to
direct the ethernet traffic out over the correct port.

I'm running 4 Mbps of raw ethernet traffic, full duplex, 500Kbps
of UDP traffic, and two 56Kbps TCP/IP connections.  After about 6-8
hours, the IP connections stop transmitting traffic.  I'm not completely
sure whether the connection is actually broken or whether it just stops passing
traffic.... I'm still looking into that...
Sometimes the receive queue, as shown by netstat is very full, but the
TX isn't (My program should be select'ing and pulling off that incoming
data...)

I find it interesting that when the TCP/IP is locked up, UDP and raw
ethernet continue to flow just fine.  I also telnet'ed into the
LISTENing port, and it connected me just fine.

I was able to get traffic running again by bouncing the Ethernet ports
up/down with ifconfig and ip (to set up the source-based routing).


Anyone know of any significant kernel problems with 2.2.14 or 2.2.16
that might cause this?  Any other ideas??


When the system is in it's hosed up state, I see this on the side
that is trying to connect to the other:

[lanforge@card1 lanforge]$ netstat -an | grep 200
tcp        0      1 192.168.10.111:4730     192.168.10.211:20011    SYN_SENT    
tcp        0      1 192.168.10.111:4729     192.168.10.211:20010    SYN_SENT    
tcp        0      1 192.168.10.111:4725     192.168.10.211:20006    SYN_SENT    


Here is what the server (accept) side looks like:
[lanforge@candle lanforge]$ netstat -an | grep 200
tcp        0      0 192.168.10.211:20011    0.0.0.0:*               LISTEN      
tcp        0      0 192.168.10.211:20010    192.168.10.111:4729     SYN_RECV    
tcp        0      0 192.168.10.211:20010    0.0.0.0:*               LISTEN      
tcp        0      0 192.168.10.211:20006    0.0.0.0:*               LISTEN      
(I've seen where all three were in the SYN_RECV state, just didn't get a trace..)

Thanks in advance for any ideas!

Ben

-- 
Ben Greear (greearb@candelatech.com)  http://www.candelatech.com
Author of ScryMUD:  scry.wanfear.com 4444        (Released under GPL)
http://scry.wanfear.com               http://scry.wanfear.com/~greear
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux