Date: Thu, 14 May 2009 19:20:46 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Iain Hibbert <plunky@rya-online.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: btpand example Message-ID: <200905141920.47717.doconnor@gsoft.com.au> In-Reply-To: <1242289912.789883.948.nullmailer@galant.ukfsn.org> References: <200905141438.17380.doconnor@gsoft.com.au> <1242289912.789883.948.nullmailer@galant.ukfsn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart2851386.WXdrXRW9Ae Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 14 May 2009, Iain Hibbert wrote: > On Thu, 14 May 2009, Daniel O'Connor wrote: > > Also, I found the MTU by trial and error, 600 works for me, 650 > > does not. I am guessing this is a bluetooth thing but I'm not > > sure.. If it is would it be possible for btpand to set the MTU? > > Why did you think to change the MTU and what was the failure? I found that pinging worked and I could connect to an SSH port but they=20 SSH key exchange stalled so I guessed MTU and got lucky. > btpand itself doesn't actually care about the interface MTU and I > talk to a WinMo 6.0 system fine (from NetBSD) with default ethernet > MTU of 1500. OK. I later tried l2ping -s 1500 -a pda and it worked so I'm not sure what's=20 going on. > On the bluetooth side, the BNEP minimum MTU is 1691 but we won't send > anything bigger than as we don't create any extension headers in > client mode. Packets will be what came from the tap. OK.. I wonder where the problem is :( I have done the same operation on the same hardware in Linux and it=20 worked without MTU tweaks, however I haven't looked to see what MTU it=20 used or anything. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2851386.WXdrXRW9Ae Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iD8DBQBKC+l35ZPcIHs/zowRAqo2AJ0aHc9Wnzt55nuFAjDYge40Jm5hWQCfVxE+ AOk6lRb67XPNZY609+TGZtw= =A8/U -----END PGP SIGNATURE----- --nextPart2851386.WXdrXRW9Ae--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905141920.47717.doconnor>