cvs commit: src/sys/netgraph/bluetooth/include ng_btsocket_rfcomm.h

Maksim Yevmenkin emax at
Mon Jan 10 17:39:54 PST 2005

emax        2005-01-11 01:39:53 UTC

  FreeBSD src repository

  Modified files:
    sys/netgraph/bluetooth/include ng_btsocket_rfcomm.h 
  Make default RFCOMM session MTU match default L2CAP MTU.
  This is just a workaround for a know problem with Motorola E1000
  phone. Something is wrong with the configuration of L2CAP/RFCOMM
  channel. Even though we set L2CAP MTU to 132 bytes (default RFCOMM
  MTU 127 + 5 bytes RFCOMM frame header) and the phone accepts it,
  the phone still sends oversized L2CAP packets. It appears that the
  phone wants to use bigger (667 bytes) RFCOMM frames, but it does
  not segment them according to the configured L2CAP MTU. The 667
  bytes RFCOMM frame size corresponds to the default L2CAP MTU of
  672 bytes (667 + 5 bytes RFCOMM frame header).
  This problem only appears if connection was initiated from the
  phone. I'm not sure who is at fault here, so for now just put
  workaround in place. Quick look at the spec did not reveal any
  Tested by:      Jes < jjess at freebsd dot polarhome dot com >
  MFC after:      3 days
  Revision  Changes    Path
  1.4       +3 -3      src/sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h

More information about the cvs-all mailing list