similar to: [Bluez-devel] Re: [Bridge] bridging bluetooth bnep deviceswith kernel 2.6.6-*

Fixes message_age field update in config BPDUs. Also checks whether the BPDU message age has exceeded bridge max age before transmitting config BPDUs. Signed-off-by: Kishore A K <KishoreAK@myw.ltindia.com> Index: linux-2.6.7/net/bridge/br_stp.c ============================================================= --- linux-2.6.7/net/bridge/br_stp.c.orig 2004-06-17 20:17:27.000000000 +0530 +++

This is a revised version of Kishore's patch to set message age appropriately in STP configuration packets. Signed-off-by: Kishore A K <KishoreAK@myw.ltindia.com> Signed-off-by: Stephen Hemminger <shemminger@osdl.org> diff -Nru a/net/bridge/br_stp.c b/net/bridge/br_stp.c --- a/net/bridge/br_stp.c 2004-06-29 14:45:50 -07:00 +++ b/net/bridge/br_stp.c 2004-06-29 14:45:50 -07:00 @@

CentOS Errata and Security Advisory 2008:0581 https://rhn.redhat.com/errata/RHSA-2008-0581.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/bluez-libs-2.10-3.ia64.rpm updates/ia64/RPMS/bluez-libs-devel-2.10-3.ia64.rpm updates/ia64/RPMS/bluez-utils-2.10-2.4.ia64.rpm updates/ia64/RPMS/bluez-utils-cups-2.10-2.4.ia64.rpm --

CentOS Errata and Security Advisory 2017:2685 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:2685 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f55b99ac9aeb545e217b69fa3f9bf1570ec4c59f5c6d121c22c2af788345ae7d bluez-4.66-2.el6_9.i686.rpm

CentOS Errata and Security Advisory 2008:0581 Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0581.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: bluez-libs-3.7-1.1.i386.rpm bluez-libs-3.7-1.1.x86_64.rpm bluez-libs-devel-3.7-1.1.i386.rpm bluez-libs-devel-3.7-1.1.x86_64.rpm bluez-utils-3.7-2.2.el5.centos.x86_64.rpm

CentOS Errata and Security Advisory 2008:0581 Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0581.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: bluez-libs-2.10-3.x86_64.rpm bluez-libs-2.10-3.x86_64.rpm bluez-libs-devel-2.10-3.x86_64.rpm bluez-utils-2.10-2.4.x86_64.rpm bluez-utils-cups-2.10-2.4.x86_64.rpm src:

CentOS Errata and Security Advisory 2017:2685 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2017:2685 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 8cd4e393e1259f57b2c4d422b6bcedcb19a4e5c361fec469b4df95d16576f337 bluez-5.44-4.el7_4.x86_64.rpm

Centos continues to fall behind in with the state of bluetooth development. Nothing new from 5.1 to 5.2. Has anyone got a more recent version working and have compile and rpm build instructions? Here are the rpms that I have: bluez-gnome-0.5-5.fc6.i386.rpm bluez-hcidump-1.32-1.i386.rpm bluez-libs-3.7-1.i386.rpm bluez-utils-3.7-2.el5.centos.i386.rpm bluez-utils-cups-3.7-2.el5.centos.i386.rpm

CentOS Errata and Security Advisory 2008:0581 Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0581.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: bluez-libs-3.7-1.1.i386.rpm bluez-libs-devel-3.7-1.1.i386.rpm bluez-utils-3.7-2.2.el5.centos.i386.rpm bluez-utils-cups-3.7-2.2.el5.centos.i386.rpm src: bluez-libs-3.7-1.1.src.rpm

CentOS Errata and Security Advisory 2008:0581 Upstream details at : https://rhn.redhat.com/errata/RHSA-2008-0581.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: bluez-libs-2.10-3.i386.rpm bluez-libs-devel-2.10-3.i386.rpm bluez-utils-2.10-2.4.i386.rpm bluez-utils-cups-2.10-2.4.i386.rpm src: bluez-libs-2.10-3.src.rpm

CentOS Errata and Security Advisory 2007:0065 https://rhn.redhat.com/errata/RHSA-2007-0065.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/bluez-utils-2.10-2.2.ia64.rpm updates/ia64/RPMS/bluez-utils-cups-2.10-2.2.ia64.rpm -- Pasi Pirhonen - upi at iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

Hello all. Does anyone know how to get bluetooth working on CentOS 5? I can't pair any device. Things work perfectly on CentOS 4. Here is what happens: root at miho ~]# /etc/rc.d/init.d/bluetooth start Starting Bluetooth services: [ OK ] [root at miho ~]# hcitool scan Scanning ... 00:12:EE:XX:XX:XX K750i [root at miho ~]# hcitool cc

I installed: gnome-bluetooth.i386 0.7.0-10.2.el5 from the base repo It also installed (at least): gnome-bluetooth-libs.i386 0.7.0-10.2.el5 These show up in /var/log/yum.log interestingly they do not show up in /var/log/rpmpkgs My bluetooth mouse is now working. It was not before. But I do not see any bluetooth management stuff in gnome (http://live.gnome.org/BluetoothManager) What

Merge the ioctl stub calls that just end up calling the sub-function to do the actual ioctl. Move br_get_XXX_ifindices into the ioctl file as well where they can be static. diff -Nru a/net/bridge/br_device.c b/net/bridge/br_device.c --- a/net/bridge/br_device.c 2004-05-20 10:51:05 -07:00 +++ b/net/bridge/br_device.c 2004-05-20 10:51:05 -07:00 @@ -19,21 +19,6 @@ #include <asm/uaccess.h>

Has anyone here managed to send files from a mobile phone to a CentOS system via Bluetooth? I'm trying with a Samsung E1310, using the GNOME tools, but can't get it to work. I can send files from the Linux box to this phone using the Nautilus bluetooth plugin (nautilus-sendto-bluetooth), and have also managed to "pull" some data I've been trying to send, via

28th February I am working with Asterisk 1.2.15. I have configured sip.conf for two soft phones (I am using Xlite).I have installed the Bluez stack and so far, i manage to make a phone call from a soft phone to a GSM network. However, i have an audio problem. The soft phone can be heart by the GSM costumer but the voice in Xlite is not transmitted to the GSM. In asterisk all i got is the

Hi All; This is my first post to the OPUS group but I would like to find out if anyone is using OPUS over Bluetooth? If so, I have some follow-up questions on the implementation strategies that have been used. Is anyone using OPUS over A2DP? Is it possible for off-the-shelf OPUS bluetooth devices manufactured by different companies to be compatible with each other? If so, which A2DP Audio

Hi Stefan, > At the moment I'm into the Bleuz mailing list for getting the SCO > feature to work, starting with my laptops BT and my dads Nokia. > > I have now a basic understanding from the RFCOMM layer which delivers > the AT commands, AT works. If I get the basic SCO functions > working with > the test tools, to get the headsetfunction itself into the > pc.

Robert Bean wrote: > This is my first post to the OPUS group but I would like to find out if > anyone is using OPUS over Bluetooth? If so, I have some follow-up > questions on the implementation strategies that have been used. I know some people have looked at it (see, e.g.,

Anyone familiar with: http://usefulinc.com/software/gnome-bluetooth/ And will it work with Centos' version of Gnome?