Hi,
I have solved my problem.
It is related to the TCP checksum offload function: I am using as embedded
platform PCEngines Alix 3d2, that do not support this function (and also
qemu virtual machines do not support it).
This patch disable the tx checksum offload and everything now works
Hi,
I have solved my problem.
It is related to the TCP checksum offload function: I am using as embedded
platform PCEngines Alix 3d2, that do not support this function (and also
qemu virtual machines do not support it).
This patch disable the tx checksum offload and everything now works
Dear all,
I have solved my problem.
It is related to the TCP checksum offload function: I am using as embedded
platform PCEngines Alix 3d2, that do not support this function (and also
qemu virtual machines do not support it).
This patch disable the tx checksum offload and everything now works
It is correct. I'm using openwrt and, at the moment, without -M option.
1500byte packets work, with fragmentation.
However, my TCP packets are small (about 60bytes). I have verified TCPDump
file and packets arrive. It seems that the Linux IP stack does not forward
them to the application.
Dear Sven, Marek
you can find as attachment the dump on eth2 of GW (tcpdump -ni eth2 -s 0 -w
gw.cap);
the output of batctl td -p 4 eth1 is:
10:29:15.51 BAT 52:54:00:00:20:01 52:54:00:00:30:01: UCAST, ttl 50, IP
192.168.100.2.9001 192.168.20.4.45417: TCP, flags [...PA.], length 6
On Tue, Oct 06, 2009 at 12:33:55PM +0200, a wrote:
Dear Sven, Marek
you can find as attachment the dump on eth2 of GW (tcpdump -ni eth2 -s 0 -w
gw.cap);
the output of batctl td -p 4 eth1 is:
10:29:15.51 BAT 52:54:00:00:20:01 52:54:00:00:30:01: UCAST, ttl 50, IP
192.168.100.2.9001
Hi,
you can find as attachment the dump on eth2 of GW (tcpdump -ni eth2 -s 0 -w
gw.cap);
the output of batctl td -p 4 eth1 is:
I could not find anything revealing in the logs you provided. Could you please
follow Sven's suggestion to log both ends as well ?
Just to not forget the obvious:
Dear Marek,
On Tue, Oct 6, 2009 at 2:55 PM, Marek Lindner lindner_ma...@yahoo.dewrote:
Hi,
you can find as attachment the dump on eth2 of GW (tcpdump -ni eth2 -s 0
-w
gw.cap);
the output of batctl td -p 4 eth1 is:
I could not find anything revealing in the logs you provided. Could
Hi,
The IP connectivity is ok and I can ping from B1 to EX and vice versa.
I have installed a tcp echo server on the three nodes and it works between
B1-GW and GW-EX, but I have problem with B1-EX test.
B1 correctly receives data from EX, but EX application doesn’t receive data
from B1. I
No,
it is not a MTU problem. TCP packet are small (I'm sending only few
characters) and big packet size (1400 byte) ping works
2009/10/5 Marek Lindner lindner_ma...@yahoo.de
Hi,
The IP connectivity is ok and I can ping from B1 to EX and vice versa.
I have installed a tcp echo server on
On Monday 05 October 2009 20:12:20 a wrote:
No,
it is not a MTU problem. TCP packet are small (I'm sending only few
characters) and big packet size (1400 byte) ping works
The limit on ethernet is 1500 bytes - please try that.
If that still works you should log the traffic on the GW with
Dear Marek,
The ping with 1500 byte packets works.
The three nodes are connected in this way:
B1 --- batman --- GW1 --- EX1
eth1 on B1 and GW1 is managed by batman. eth2 on gw1 not.
The IP configuration is:
B1:
# ip a
eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state
a wrote:
The ping with 1500 byte packets works.
How can you send 1500 bytes packets with an mtu of 1476?
Do the test with `ping -M do -s 1472 IP` (this should create an 1500 bytes
packet and disables fragmentation).
The three nodes are connected in this way:
B1 --- batman --- GW1 --- EX1
13 matches
Mail list logo
