Herbert Xu wrote:
Marco Berizzi <[EMAIL PROTECTED]> wrote: > > Running 'tcpdump -p -n -v ip net 10.16.24.117' on mimosa > resolves the problem: sapgui clients can connect to sap > servers while tcpdump is running on mimosa. > Is this a bug?Very strange. Could you perhaps move the tcpdump to another machine so that we can observe what's going on without disturbing the bug?
Yes. It is very strange, but this morning I have done again the test: I confirm you this strange behaviour. One note: running 'tcpdump -p -n ip host 10.16.24.117' on mimosa did the trick. But running 'tcpdump -p -n ip host 172.16.0.138' (always on mimosa) doesn't "resolves" the problem. I'm attaching to this message a tar & bzipped file with three file inside: WITHOUTTCPDUMP-PLEIADI: this file is the tcpdump capture taken on eth2 (internal network NIC 172.16.0.0/23) on pleiadi. Sapgui client (172.16.0.138) connect to sapserver (10.16.24.117). Sapgui response is extremely slow (20'). After a while sapgui client connection goes down. This is the tcpdump command: tcpdump -p -n -i eth2 ip host 172.16.0.138 > WITHOUTTCPDUMP-PLEIADI WITHTCPDUMP-PLEIADI: this file is the tcpdump capture taken on eth2 (internal network NIC 172.16.0.0/23) on pleiadi when on mimosa is also running tcpdump. Sapgui client (172.16.0.138) connect to sapserver (10.16.24.117). Sapgui response is fast. This is the tcpdump command: tcpdump -p -n -i eth2 ip host 172.16.0.138 > WITHTCPDUMP-PLEIADI WITHTCPDUMP-MIMOSA: this file is the tcpdump capture taken on mimosa the same time as WITHTCPDUMP-PLEIADI This is the tcpdump command: tcpdump -p -n ip host 10.16.24.117 > WITHTCPDUMP-MIMOSA 172.16.0.138 is windows XPsp2 with sapgui 6.40 10.16.24.117 nmap tell me that it is HP-UX
dump.tar.bz2
Description: Binary data
