Sorry for the late reply, a few things came up over the weekend that i
had to attend to.
Here are three tcp dump files from the internet node on bat0 and one
on eth1 (the internet port)
Really don't understand what is wrong here :-(
On Sat, Aug 14, 2010 at 5:46 PM, Marek Lindner <[email protected]> wrote:
>
> On Friday 13 August 2010 07:45:07 David Beaumont wrote:
> > Anything that looks obviously out of place here?
>
> I see nothing obviously wrong here.
> The best next step is using tcpdump / batctl / wireshark to find out where the
> packets get dropped. Feel free to share the result with us. :-)
>
>
> Regards,
> Marek
tcpdump -i bat0 (whilst ping http://www.google.com from mesh node)
14:25:23.578878 IP 192.168.1.119.37516 > 192.168.1.1.53: 41268+ AAAA? google.com
. (28)
14:25:23.580815 IP 192.168.1.1.53 > 192.168.1.119.37516: 41268 0/0/0 (28)
14:25:23.581578 IP 192.168.1.119.64720 > 192.168.1.1.53: 63944+ AAAA? google.com
. (28)
14:25:23.588693 IP 192.168.1.1.53 > 192.168.1.119.64720: 63944 0/0/0 (28)
14:25:23.593001 IP 192.168.1.119.37149 > 192.168.1.1.53: 18911+ AAAA? google.com
. (28)
14:25:23.598676 IP 192.168.1.1.53 > 192.168.1.119.37149: 18911 0/0/0 (28)
14:25:23.603824 IP 192.168.1.119 > fx-in-f104.1e100.net: ICMP echo request, id 1
6134, seq 0, length 64
14:25:23.730452 IP fx-in-f104.1e100.net > 192.168.1.119: ICMP echo reply, id 161
34, seq 0, length 64
14:25:24.612730 IP 192.168.1.119 > fx-in-f104.1e100.net: ICMP echo request, id 1
6134, seq 1, length 64
14:25:24.740792 IP fx-in-f104.1e100.net > 192.168.1.119: ICMP echo reply, id 161
34, seq 1, length 64
tcpdump -i bat0 (whilst wget http://www.google.com from mesh node)
4:25:57.259453 IP 192.168.1.119.37746 > 192.168.1.1.53: 37899+ AAAA? www.google
.com. (32)
14:25:57.304084 IP 192.168.1.1.53 > 192.168.1.119.37746: 37899 1/1/0 CNAME www.l
.google.com. (102)
14:25:57.314561 IP 192.168.1.119.12656 > 192.168.1.1.53: 51848+ A? www.google.co
m. (32)
14:25:57.321923 IP 192.168.1.1.53 > 192.168.1.119.12656: 51848 7/0/0 CNAME[|doma
in]
14:25:57.323845 IP 192.168.1.119.54396 > fx-in-f147.1e100.net.80: SWE 576811426:
576811426(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 4>
14:25:57.432719 IP fx-in-f147.1e100.net.80 > 192.168.1.119.54396: S 2862198252:2
862198252(0) ack 576811427 win 5720 <mss 1430,nop,nop,sackOK,nop,wscale 6>
14:25:57.433281 IP 192.168.1.119.54396 > fx-in-f147.1e100.net.80: . ack 1 win 36
5
14:25:57.433660 IP 192.168.1.119.54396 > fx-in-f147.1e100.net.80: P 1:78(77) ack
1 win 365
14:26:00.433415 IP 192.168.1.119.54396 > fx-in-f147.1e100.net.80: P 1:78(77) ack
1 win 365
tcpdump -i eth1 (whilst wget http://www.google.com from mesh node)
14:26:36.409857 IP 192.168.0.117.35199 > fx-in-f99.1e100.net.80: SWE 1188618495:
1188618495(0) win 5840 <mss 1460,nop,nop,sackOK,nop,wscale 4>
14:26:36.410482 IP 192.168.0.117.14600 > 192.168.0.1.53: 48720+ PTR? 99.39.125.7
4.in-addr.arpa. (43)
14:26:36.524517 IP 192.168.0.1.53 > 192.168.0.117.14600: 48720 1/4/4 (222)
14:26:36.529445 IP fx-in-f99.1e100.net.80 > 192.168.0.117.35199: S 3729599604:37
29599604(0) ack 1188618496 win 5720 <mss 1430,nop,nop,sackOK,nop,wscale 6>
14:26:36.534416 IP 192.168.0.117.35199 > fx-in-f99.1e100.net.80: . ack 1 win 365
14:26:36.539747 IP 192.168.0.117.35199 > fx-in-f99.1e100.net.80: P 1:78(77) ack
1 win 365
14:26:39.537084 IP 192.168.0.117.35199 > fx-in-f99.1e100.net.80: P 1:78(77) ack
1 win 365
