Hello, I have a problem that TCP stalls after a short while on a TAP (bridged adapter) device. I have enabled traffic shaping (wondershaper) on the br0 device. When I start a ftp session it stops after a while. When I then start a ping and use tcpdump to monitor I see the ping is outgoing but no replies. I just can get traffic working again after a boot Anybody got experience with this? Peter Lindeman
Peter Lindeman wrote:> I have a problem that TCP stalls after a short while on a TAP (bridged > adapter) device. I have enabled traffic shaping (wondershaper) on the > br0 device. When I start a ftp session it stops after a while. When I > then start a ping and use tcpdump to monitor I see the ping is outgoing > but no replies. I just can get traffic working again after a boot > > Anybody got experience with this? >It this a 2.6 kernel? -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net
Tom Eastep wrote:> Peter Lindeman wrote: > >> I have a problem that TCP stalls after a short while on a TAP (bridged >> adapter) device. I have enabled traffic shaping (wondershaper) on the >> br0 device. When I start a ftp session it stops after a while. When I >> then start a ping and use tcpdump to monitor I see the ping is >> outgoing but no replies. I just can get traffic working again after a >> boot >> >> Anybody got experience with this? >> > > It this a 2.6 kernel?Groan -- I of course meant "*Is* this a 2.6 kernel?". The reason that I ask is that I had miserable results with bridging when I tried in on 2.6.2. Others on the list seem to have had success with later 2.6 versions though. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net
Tom Eastep wrote:>>> I have a problem that TCP stalls after a short while on a TAP >>> (bridged adapter) device. I have enabled traffic shaping >>> (wondershaper) on the br0 device. When I start a ftp session it stops >>> after a while. When I then start a ping and use tcpdump to monitor I >>> see the ping is outgoing but no replies. I just can get traffic >>> working again after a boot >>> >>> Anybody got experience with this? >>> >> >> It this a 2.6 kernel? > > > Groan -- I of course meant "*Is* this a 2.6 kernel?". The reason that I > ask is that I had miserable results with bridging when I tried in on > 2.6.2. Others on the list seem to have had success with later 2.6 > versions though.This was indeed a 2.6 kernel (in Mandrake 10 Official) but I also tried the exact same thing in a 2.4.25 kernel and the problem is the same. What is the best way to investigate this? -- Groeten, Peter Computer possessed? Try DEVICE=C:\EXOR.SYS - - Heb je een Dreambox 7000S ? - Kijk eens op http://www.dreamvcr.com - Kijk ook op http://www.lindeman.org - ICQ 22383596 - Uptime lindeman.org - 78 days, 18 hours and 46 minutes, 0 users logged in.
Peter Lindeman wrote:>> >> >> Groan -- I of course meant "*Is* this a 2.6 kernel?". The reason that >> I ask is that I had miserable results with bridging when I tried in on >> 2.6.2. Others on the list seem to have had success with later 2.6 >> versions though. > > > This was indeed a 2.6 kernel (in Mandrake 10 Official) but I also tried > the exact same thing in a 2.4.25 kernel and the problem is the same. > What is the best way to investigate this? >I would use tcpdump on the bridge port that is giving you problems. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net
Tom Eastep wrote:>> This was indeed a 2.6 kernel (in Mandrake 10 Official) but I also >> tried the exact same thing in a 2.4.25 kernel and the problem is the >> same. What is the best way to investigate this? >> > > I would use tcpdump on the bridge port that is giving you problems.Well I did that this morning while pinging a system on the local subnet. I see the outgoing ping in tcpdump but there is no reply. -- Groeten, Peter Als je nooit de eerste keer slaagt, moet je niet gaan parachutespringen. - - Heb je een Dreambox 7000S ? - Kijk eens op http://www.dreamvcr.com - Kijk ook op http://www.lindeman.org - ICQ 22383596 - Uptime lindeman.org - 78 days, 18 hours and 55 minutes, 0 users logged in.
Peter Lindeman wrote:> Tom Eastep wrote: > >>> This was indeed a 2.6 kernel (in Mandrake 10 Official) but I also >>> tried the exact same thing in a 2.4.25 kernel and the problem is the >>> same. What is the best way to investigate this? >>> >> >> I would use tcpdump on the bridge port that is giving you problems. > > > Well I did that this morning while pinging a system on the local subnet. > I see the outgoing ping in tcpdump but there is no reply. >Then you need to find out what is happening at the other end. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net
Tom Eastep wrote:>> Well I did that this morning while pinging a system on the local >> subnet. I see the outgoing ping in tcpdump but there is no reply. >> > > Then you need to find out what is happening at the other end.It is not logical to me that the other side is a problem. After a reboot of this linux machine it is working. I''m going to investigate it further. Thanks -- Groeten, Peter Error: Keyboard not attached. Press F1 to continue. - - Heb je een Dreambox 7000S ? - Kijk eens op http://www.dreamvcr.com - Kijk ook op http://www.lindeman.org - ICQ 22383596 - Uptime lindeman.org - 78 days, 22 hours and 40 minutes, 0 users logged in.
Peter Lindeman wrote:> Tom Eastep wrote: > >>> Well I did that this morning while pinging a system on the local >>> subnet. I see the outgoing ping in tcpdump but there is no reply. >>> >> >> Then you need to find out what is happening at the other end. > > > It is not logical to me that the other side is a problem. After a reboot > of this linux machine it is working. I''m going to investigate it > further. Thanks >I didn''t say that the other end is the problem -- right now, you don''t know if you have a tranmit problem or a receive problem. If you learn that the ''ping'' reqests are reaching the other end and are being replied to but you aren''t seeing them on your end, then you will know that the problem is on the local receive side. Basic network troubleshooting.... -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net