[Touch-packages] [Bug 1674137] Re: ifdown unknown interface net-tools is broken

2017-03-19 Thread Roger Lawhorn
UPDATE: 
Rewrote my scripts to set enp3s0 AFTER the bridge creation and deletion.
Issue with that part over.

ifdown still broken.
Unknown if script issue is related, but those scripts worked fine before the 
updates.
Perhaps more than one update changed how things work.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1674137

Title:
  ifdown unknown interface net-tools is broken

Status in Linux Mint:
  New
Status in net-tools package in Ubuntu:
  New

Bug description:
  System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena
  Network:   Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller
     driver: alx port: d000 bus-ID: 03:00.0
     IF: enp3s0 state: up speed: 1000 Mbps duplex: full
     Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: 
ath9k bus-ID: 04:00.0
     IF: wlp4s0 state: up

  After mint 18.1 upgrade had various issues.
  After quite a few updates I started having issues with ifdown command.

  I use a script with qemu to setup a bridge (br0) with tap0 and the default 
wired connection enp3s0. The script began giving off unknown interface errors.
  Testing showed that the ifdown command changed behavior after the updates and 
now does this.
  The behavior is not limited to scripting.
  I changed the code from using ifdown to ifconfig enp3s0 down.
  This fails also within the script but with no error.
  It, however, works from a terminal just fine.
  I switched to using the ip command i.e. ip link set enp3s0 down.
  Same result, the interface does not go down, but no error.
  After the script is run and windows 7 boots in qemu I have to open a terminal 
and run the commands manually:
  >ifconfig enp3s0 down
  >ifconfig enp3s0 0.0.0.0 promisc up

  Then all is well.
  These commands will not run from within a script.
  The script is run as such:
  >sudo ./up.sh tap0

  It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge.

  The fact that ifdown no longer recognizes any interfaces seems to
  point to a change in net-tools that has broken something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1674137/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1674137] Re: ifdown unknown interface net-tools is broken

2017-03-19 Thread Roger Lawhorn
UPDATE:
To reverify, ifdown command fails always. net-tools is broken after the update.

I have done extensive testing on my scripts adding Y/N questions to verify that 
each command succeeded. They do. 
Therefore, the ip and ifconfig commands do succeed inside of scripts (but not 
ifdown). I was incorrect about that.

What really happens:
At the point where the bridge is made and tap0 and enp3s0 are added to it the 
ipaddr of enp3s0 goes from 0.0.0.0 back to 192.168.1.130 thus breaking the 
bridge.
Both tap0 and enp3s0 must be 0.0.0.0. promiscuous mode, and up inside the 
bridge br0 to work properly.

I am digging deeper on why this happens.
As a temp fix I reset enp3s0 to the correct settings a 2nd time after the 
bridge is made.

Also, after the bridge is removed enp3s0 never performs dhcp to regain its 
original ipaddr.
That is also an issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1674137

Title:
  ifdown unknown interface net-tools is broken

Status in Linux Mint:
  New
Status in net-tools package in Ubuntu:
  New

Bug description:
  System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena
  Network:   Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller
     driver: alx port: d000 bus-ID: 03:00.0
     IF: enp3s0 state: up speed: 1000 Mbps duplex: full
     Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: 
ath9k bus-ID: 04:00.0
     IF: wlp4s0 state: up

  After mint 18.1 upgrade had various issues.
  After quite a few updates I started having issues with ifdown command.

  I use a script with qemu to setup a bridge (br0) with tap0 and the default 
wired connection enp3s0. The script began giving off unknown interface errors.
  Testing showed that the ifdown command changed behavior after the updates and 
now does this.
  The behavior is not limited to scripting.
  I changed the code from using ifdown to ifconfig enp3s0 down.
  This fails also within the script but with no error.
  It, however, works from a terminal just fine.
  I switched to using the ip command i.e. ip link set enp3s0 down.
  Same result, the interface does not go down, but no error.
  After the script is run and windows 7 boots in qemu I have to open a terminal 
and run the commands manually:
  >ifconfig enp3s0 down
  >ifconfig enp3s0 0.0.0.0 promisc up

  Then all is well.
  These commands will not run from within a script.
  The script is run as such:
  >sudo ./up.sh tap0

  It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge.

  The fact that ifdown no longer recognizes any interfaces seems to
  point to a change in net-tools that has broken something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1674137/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1674137] Re: ifdown unknown interface net-tools is broken

2017-03-19 Thread Roger Lawhorn
** Also affects: net-tools (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1674137

Title:
  ifdown unknown interface net-tools is broken

Status in Linux Mint:
  New
Status in net-tools package in Ubuntu:
  New

Bug description:
  System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena
  Network:   Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller
     driver: alx port: d000 bus-ID: 03:00.0
     IF: enp3s0 state: up speed: 1000 Mbps duplex: full
     Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: 
ath9k bus-ID: 04:00.0
     IF: wlp4s0 state: up

  After mint 18.1 upgrade had various issues.
  After quite a few updates I started having issues with ifdown command.

  I use a script with qemu to setup a bridge (br0) with tap0 and the default 
wired connection enp3s0. The script began giving off unknown interface errors.
  Testing showed that the ifdown command changed behavior after the updates and 
now does this.
  The behavior is not limited to scripting.
  I changed the code from using ifdown to ifconfig enp3s0 down.
  This fails also within the script but with no error.
  It, however, works from a terminal just fine.
  I switched to using the ip command i.e. ip link set enp3s0 down.
  Same result, the interface does not go down, but no error.
  After the script is run and windows 7 boots in qemu I have to open a terminal 
and run the commands manually:
  >ifconfig enp3s0 down
  >ifconfig enp3s0 0.0.0.0 promisc up

  Then all is well.
  These commands will not run from within a script.
  The script is run as such:
  >sudo ./up.sh tap0

  It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge.

  The fact that ifdown no longer recognizes any interfaces seems to
  point to a change in net-tools that has broken something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1674137/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes

2017-03-17 Thread Roger Lawhorn
UPDATE:

I created my own bluez 5.43 unsigned packages and installed them.
The issue is still present.

Here are the steps I took:

It was suggested that bluez 5.4 fixes the issue. However, that package
is not available for ubuntu 16.04. I was able to build my own unsigned
and upgradable package using the following steps and I have bluez 5.43.
Still does not connect though.

sudo  apt-get install debhelper devscripts dh-autoreconf flex bison
libdbus-glib-1-dev libglib2.0-dev  libcap-ng-dev libudev-dev
libreadline-dev libical-dev check dh-systemd libebook1.2-dev

wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez_5.43.orig.tar.xz
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez_5.43-0ubuntu1.debian.tar.xz
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez_5.43-0ubuntu1.dsc

tar xf bluez_5.43.orig.tar.xz
cd bluez-5.43
tar xf ../bluez_5.43-0ubuntu1.debian.tar.xz
debchange --local=~lorenzen 'Backport to Xenial'
debuild -b -j4 -us -uc
cd ..
sudo dpkg -i *.deb

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490347

Title:
  [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy
  LMP Link Management Protocol) PIN codes

Status in Bluez Utilities:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes

2017-03-17 Thread Roger Lawhorn
Same here.

Linux Mint 18.1 64bit Cinnamon Desktop (ubuntu 16.04), Bluetoothctl
v5.37.

After I wrote the below forum post I also implemented this udev change
which helped somewhat as I have an onboard bluetooth that I wanted to
disable after buying a "csr 4.0" usb dongle off of ebay. The GUI worked
better, but still no pair:

>sudo gedit /etc/udev/rules.d/81-bluetooth-hci.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0cf3", ATTRS{idProduct}=="3004", 
ATTR{authorized}="0"

Here is the article I posted in a facebook forum with all the gory
details:

Been unable to use bluetooth for many years and many laptops. Bought a CSR v4.0 
dongle off of ebay.
>lsusb Bus 003 Device 011: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
>Dongle (HCI mode)

Even worse results.

In bluetoothctl (skipping the GUI):
[bluetooth]# list
Controller 00:1A:7D:DA:71:13 GT70-2PE #1 [default]
Controller 48:5A:B6:19:7F:30 GT70-2PE

#1 is the usb dongle I bought.
The other is the built-in Atheros in the laptop.

[bluetooth]# power on
Changing power on succeeded

[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1A:7D:DA:71:13 Discovering: yes
[CHG] Device 48:5A:B6:19:7F:30 RSSI: -64
[CHG] Device 00:07:62:18:3D:C5 RSSI: -51

[bluetooth]# info 00:07:62:18:3D:C5
Device 00:07:62:18:3D:C5
Name: iMT525
Alias: iMT525
Class: 0x240404
Icon: audio-card
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: yes
RSSI: -51

I am trying to connect to the iMT525 speaker phone by Altec Lansing.

[bluetooth]# pair 00:07:62:18:3D:C5
Attempting to pair with 00:07:62:18:3D:C5
[CHG] Device 00:07:62:18:3D:C5 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationRejected
[CHG] Device 00:07:62:18:3D:C5 Connected: no

Cannot pair though the default pair code is  for a sound device.

Any ideas?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490347

Title:
  [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy
  LMP Link Management Protocol) PIN codes

Status in Bluez Utilities:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp