Dell Inspiron 1545 upgrade – Enable virtualization in BIOS and change CPU

27 02 2017

The Dell laptop Inspiron 1545 doesn’t have any menu in the BIOS for enable virtualization, but using a tool from Dell allow us to enable it from the operating system.

The tool was called Dell Client Configuration Toolkit – CCTK and was available here:

http://en.community.dell.com/techcenter/systems-management/w/wiki/1952.dell-client-configuration-toolkit-cctk
But they change the name, and now it is called Dell Client Command Suite, and then, Dell Command | Configure. Download it from the following links (maybe they don’t change it again, who knows…):

The latest version of CCTK is now Dell Command | Configure and is a part of the Dell Client Command Suite.
http://en.community.dell.com/techcenter/enterprise-client/w/wiki/7431.dell-client-command-suite
http://en.community.dell.com/techcenter/enterprise-client/w/wiki/7532.dell-command-configure

It is possible to do it from linux, in my case a .deb package is available. Download and install it. After, execute the following (search for the binary before):
# cctk --virtualization
virtualization=disable
# cctk --virtualization=enable
virtualization=enable

In my case, the CPU is an old Pentium Dual Core T4300 2.10GHz, 800MHz FSB, 1MB cache and I need to change the processor too, this doesn’t have the vmx instruction support. The requirements are:

1. The CPU should be a socket P CPU with 478 pins (P-series processors were more energy efficient than T-series)
2. More or equal than 1MB cache
3. More or equal than 800Mhz FSB, maybe close to 1066Mhz.
4. Core 2 duo preferred, if not, any Celeron ,Celeron Dual-Core or Pentium Dual-Core

For the upgrade, I choose a the Intel Core 2 Duo P9500 SLB4E 2.53Ghz 6M 1066Mhz. It works perfect, the fan is running less time, the temperature is lower and the perfomance is better. Change it if you have the opportunity.

Replacing it was very easy, unlock the bottom cover, unlock 5 screws from the heat pipe and unlock the screw of the CPU (half turn only), remove, mount the new one with some thermal paste and attach the heat pipe and the cover.

More info:

http://www.benshardwareblog.com/laptop-hardware/upgrading-a-dell-inspiron-1545-cpu
http://en.community.dell.com/support-forums/laptop/f/3518/t/19525777





Install VMware Horizon Client in Debian 8 Jessie

24 02 2017

Download the linux client from the VMware website:

https://my.vmware.com/en/web/vmware/info/slug/desktop_end_user_computing/vmware_horizon_clients/4_0

The downloaded file is a bash script, execute it from a privileged user:

# bash VMware-Horizon-Client-4.3.0-4710754.x64.bundle

Install dependencies:

# apt-get install libudev-dev libffi-dev libglibmm-2.4-dev

Before finish the install, click into the “Scan” button. If libffi.so.5 is missing and you have libffi.so.6 only (usually in a modern Debian), create a symlink for bypass:

cd /usr/lib/x86_64-linux-gnu && ln -s libffi.so.6 libffi.so.5

Probably, if you execute now the client, it doesn’t start because the following:

$ vmware-view
/usr/lib/vmware/view/bin/vmware-view: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

Solve that creating a simlink:

# cd /lib/x86_64-linux-gnu && ln -s libudev.so.1 libudev.so.0

And run!:

$ vmware-view





Multiple network interfaces with multiple public IPs in an EC2 instance with different outbound source using network namespaces

14 02 2017

In this scenario we will have an ec2 instance with:

* 3 network interfaces
* 3 public IPs (one for each interface)
* 3 different process with different public outbound address running in separate network namespaces

As starting point, we have a simple ec2 instance with one interface and a public IP assigned to it. The steps are:

– Allocate two new elastic IPs

– Create two new network interfaces in the same subnet in which resides the instance.

– Associate the new elastic IPs to these new network interfaces.

– Associate the new network interfaces to the instance. Now, it have the default eth0 and two more, eth1 and eth2.

– Create a pair of network namespaces for the new interfaces:

ip netns add blue
ip link set eth1 netns blue
ip netns add green
ip link set eth2 netns green

– Request the IPs for the interfaces:

ip netns exec blue dhclient eth1ip netns exec green dhclient eth2

– And test it:

curl ipinfo.io/ip
ip netns exec blue curl ipinfo.io/ip
ip netns exec green curl ipinfo.io/ip

Take into account that:

– You need to launch the proces with the “ip netns exec xxxx” due that systemd don’t support the network namespace assignement.
https://github.com/systemd/systemd/issues/2741

– Look the limits of AWS, by default, only 5 EIPs are allowed and each type of instance have a network limit.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html





Ssh error Too many authentication failures for root

8 02 2017

ssh -o PubkeyAuthentication=no root@host





Allow caching when the request have cookies – nginx

16 01 2017

Simply, ignore them. If Nginx sees it, it disables caching:

proxy_ignore_headers "Set-Cookie";
proxy_hide_header "Set-Cookie";





Docker: Remove all images and containers

15 01 2017

List all images:
docker images -a

List all containers:
docker ps -a

Delete all containers
docker rm $(docker ps -a -q)

Delete all images
docker rmi $(docker images -q)

Delete intermediate images ” <none":
docker rmi $(docker images --filter "dangling=true" -q --no-trunc)





Testing hhtp2 with curl

9 01 2017

Testing a domain resolving different IP in http2:
# curl --http2 -I --resolve http://www.domain.com:443:192.168.1.1 https://www.domain.com