K3 Wireless breaks kindlets

[knc1]

Here is one that I don't think I published before.

This uses "Source Based" routing rather than modify iptable rules.

In this example, all of the local wireless devices are assigned an IP address from within the 169.254.0.225/27 address block.
Change that entry as required to match your assignment practices.

# Put a full block on Chatty Kathy's attempts to call home:
/bin/ip rule add from 169.254.0.225/27 to 207.171.160.0/19 prohibit
/bin/ip rule add from 169.254.0.225/27 to 107.20.0.0/14 prohibit
/bin/ip rule add from 169.254.0.225/27 to 184.72.0.0/15 prohibit
/bin/ip rule add from 169.254.0.225/27 to 204.246.160.0/19 prohibit
/bin/ip rule add from 169.254.0.225/27 to 205.251.192.0/18 prohibit
/bin/ip rule add from 169.254.0.225/27 to 72.21.192.0/19 prohibit
/bin/ip rule add from 169.254.0.225/27 to 50.16.0.0/14 prohibit
/bin/ip rule add from 169.254.0.225/27 to 23.0.0.0/12 prohibit

The above is an old example, refer to my 'Exploring the Kpw' thread for the currently known address ranges to block.

The above routing rules are added to my gateway machine, I have not tried adding them to a Kindle - so am not sure if Source Based routing is supported by the Amazon Kindle kernel build.

[fonzie4msg]

done, thx

[twobob]

You don't state that this is via ssh or via telnet.

If it's telnet then that will be the problem.

[fonzie4msg]

Originally Posted by twobob

You don't state that this is via ssh or via telnet.

If it's telnet then that will be the problem.

ssh

sorry

(
fonzie@fonzie-desktop:~$ sudo ip link set up dev usb0
fonzie@fonzie-desktop:~$ sudo ip address add 192.168.15.201 peer 192.168.15.244 dev usb0
fonzie@fonzie-desktop:~$ ssh -l root 192.168.15.244
)

[twobob]

It's a SYSTEM lib...

/lib/libe2p.so.2

so... type

echo $LD_LIBRARY_PATH

if /lib is in that list then it is something in the way you are giving the instruction... or something even weirder

[knc1]

Originally Posted by twobob

It's a SYSTEM lib...

/lib/libe2p.so.2

so... type

echo $LD_LIBRARY_PATH

if /lib is in that list then it is something in the way you are giving the instruction... or something even weirder

hmm...
well, almost

/lib should be in the default path of the dynamic loader already, as should /usr/lib;
plus the paths listed in: /etc/ld.so.conf
plus the paths in the concatenated contents of the files of /etc/ld.so.conf.d (if used by the Kindle libc implementation).

Whatever the situation happens to be on your device ;
Using the ldd command (a script) on the executable will list the libraries and the paths to them after giving consideration to all of the libc configuration stuff (including LD_LIBRARY_PATH - which in a normal run-time is empty, but which may not be when using the KUAL.system extensions).

[twobob]

I fixed it for him. He's happy now