On Mon, Jun 22, 2009 at 2:46 PM, Sven Eckelmannsven.eckelmann@gmx.de wrote:
On Monday 22 June 2009 22:31:57 Outback Dingo wrote:
when you say dont go thru, what exactly are they not passing through, which interface or meaning thru the DSL / internet link, we need to try to detmine also the bottleneck of the issue, so what interface is data not passing through, and icmp tests wount decipher much in regards to MTU.... tcpdump however might tell us where the traffic is getting stopped at
I would guess that the data gets stopped at the bat0 interface. Lets say that the workstation sends a big sized ethernet frame (aka 1500 bytes) with ip data. Then it comes to the workstation over the eth0 interface which accepts frames till the size of 1500 bytes (everything happy until now). The bridge now sends it to the bat0 interface.... and oh noes, this fails because the bat0 only accepts ethernet frames of the size of 1476 bytes (see the mtu of the ath0 - 24 bytes for bat-adv stuff). The bridge should now send information (icmp packet) back the path that it cannot send the ethernet frame through this chokepoint[1]. This doesn't seem to happen here or isn't recognized by the client.
Regards, Sven
[1] ftp://ftp.rfc-editor.org/in-notes/rfc1191.txt
OK, what if I set the MTU of ath0 higher? Lemme see.