udev rule for kindle paperwhite 2 with usbnet doesnt work

[la_tristesse]

I'm running Ubunut 15.04 on a 64-bit System with a Kindle Paperwhite 2. Here's my usbnet config:

$ cat /mnt/base-us/usbnet/etc/config
#!/bin/sh
#
# $Id: config 9688 2013-08-10 00:30:05Z NiLuJe $
#

# WARNING: Take note that we're essentially a shell script, se we absolutely *MUST* use UNIX line endings!
# WARNING: To avoid leaving your system in an undefined state,
#          do *NOT* modify this file while usb over ethernet is enabled!
#          (That means when the the auto enable feature is in use, too!)

# Tweak this to your liking (IPv4 only, no hostname aliases)
KINDLE_IP=192.168.15.244

# Allow SSH over WiFi
# NOTE: If you set this to true, the SSHD *WILL* check your passwords!
# Make sure you know your root password, or auth via shared keys!
USE_WIFI="true"

# Don't switch to Ethernet over USB, and only launch SSHD
# NOTE: Make sure you're able to properly login over SSH before enabling this...
# It's obviously only useful with WiFi devices, so leave to false on non-WiFi devices
USE_WIFI_SSHD_ONLY="false"

# Use OpenSSH instead of dropbear (somewhat faster login)
# NOTE: OpenSSH *WILL* check your passwords!
# Make sure you know your root password, or auth via shared keys!
USE_OPENSSH="true"

# Don't let dropbear print the banner at each login
QUIET_DROPBEAR="false"

# Use a custom NIC field for the MAC adresses.
# Will mostly be of use to people needing to plug multiple Kindles on the same computer/network.
TWEAK_MAC_ADDRESS="false"

I followed the instructions at https://wiki.mobileread.com/wiki/Kindle_Touch_Hacking about about "Preventing networkmanager to connect to device".

Here are the steps I performed:

$ sudo nano /etc/udev/rules.d/90-local.rules
ACTION=="add", KERNEL=="usb0", ATTRS{manufacturer}==""Linux 3.0.35-lab126 with fsl-usb2-udc", RUN+="/etc/udev/scripts/kindle"
$ sudo mkdir -p  /etc/udev/scripts/
$ sudo nano /etc/udev/scripts/kindle
#!/bin/bash
ifconfig usb0 down
ifconfig usb0 hw ether 48:b3:35:3e:96:9b
ifconfig usb0 192.168.15.201
ifconfig usb0 up
$ sudo chmod  +x /etc/udev/scripts/kindle
$ sudo udevadm control --reload 
$ sudo nano /etc/NetworkManager/NetworkManager.conf
[keyfile]
unmanaged-devices=mac:48:b3:35:3e:96:9b

Because i wasnt able to connect to ssh after I plugged the pw2 back into the usb-port I begann monitoring udev with:

$ udevadm monitor --kernel
KERNEL[15829.836665] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6/1-4.6:1.0/net/usb0/queues/rx-0 (queues)
KERNEL[15829.836712] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6/1-4.6:1.0/net/usb0/queues/tx-0 (queues)
KERNEL[15829.836738] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6/1-4.6:1.0/net/usb0 (net)
KERNEL[15829.868418] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6/1-4.6:1.0 (usb)
KERNEL[15829.868465] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6/1-4.6:1.1 (usb)
KERNEL[15829.872928] remove   /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6 (usb)
KERNEL[15840.111293] add      /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6 (usb)
KERNEL[15840.113088] add      /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6/1-4.6:1.0 (usb)
KERNEL[15840.116244] add      /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6/1-4.6:1.0/net/usb0 (net)
KERNEL[15840.116278] add      /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6/1-4.6:1.0/net/usb0/queues/rx-0 (queues)
KERNEL[15840.116304] add      /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6/1-4.6:1.0/net/usb0/queues/tx-0 (queues)
KERNEL[15840.117149] add      /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6/1-4.6:1.1 (usb)

I then altered the udev-rule to the following:

$ sudo nano /etc/udev/rules.d/90-local.rules
KERNEL=="usb[0-9]*", DEVPATH=="/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.6/1-4.6:1.0/net/usb0", ACTION=="add", RUN+="/etc/udev/scripts/kindle"

Both rules didnt succeed. I cant connect to ssh. So I'm left wondering what I did wrong. Any suggestions?

[knc1]

First suspect is timing.

I.E: udev runs when the device is detected, which is very likely to be before the device itself is ready.

Note: A common problem with udev and USB devices.