I wanted to use a 3G dongle with a twin SIM card as my Internet connection when I’m traveling. I have earlier decribed howto share the Internet connection and make it more flexible by using an OpenWRT router with USB interface as a bridge between Wlan and 3G/GPRS provided internet.
Unfortunatly Tele2s support personel cannot keep track of the unlogical rules among their different subscriptions so they fouled my to buy a twincard to my regular subscription and use that for data. After a couple of more calls to Tele2, including that they listened to a recording of when I ordered the twincard I have to give up that track because it was not possible. The twincard only works for phone calls, not data connections and especially not when I had a flatrate subscription on my master SIM card.
After some investigation I came to the conclusion that I have to use my Regular phone, a HTC Desire with Android as my connection to internet.
Unfortunatly the work done with getting the USB 3G dongle was a waste of time.
An OpenWRT router with a working USB interface and a rndis enabled modem, I use a HTC Desire.
root@WRT160NL:~# opkg install kmod-usb-net-rndis
I also installed some USB packages, probably not all of them are necessery:
root@WRT160NL:~#opkg install kmod-ar9170 kmod-usb-acm kmod-usb-core kmod-usb-ohci kmod-usb-serial comgt kmod-usb-serial-option kmod-usb-storage kmod-usb-uhci kmod-usb2 usb-switch
Add the following to /etc/config/network
config 'interface' 'usb0'
option 'name' 'usb0'
option 'proto' 'dhcp'
option 'ifname' 'usb0'
option 'defaultroute' '0'
option 'peerdns' '0'
Use the same firewall rules with your 3G connection as your normal WLAN, add the yellow marked line to /etc/config/firewall:
config 'zone'
option 'name' 'wan'
option 'input' 'REJECT'
option 'output' 'ACCEPT'
option 'forward' 'REJECT'
option 'masq' '1'
option 'mtu_fix' '1'
option 'network' 'wan usb0 ppp0'
Do a reboot
To use your new connection, run ifup
root@WRT160NL:~# ifup usb0 udhcpc (v1.15.3) started root@OpenWrt:~# Sending discover... Sending select for 192.168.100.100... Lease of 192.168.100.100 obtained, lease time 864000 udhcpc: ifconfig usb0 192.168.100.100 netmask 255.255.255.0 broadcast + udhcpc: setting default routers: 192.168.100.254 udhcpc: setting dns servers: 192.168.100.254 root@WRT160NL:~# ping www.google.com PING www.google.com (74.125.39.104): 56 data bytes 64 bytes from 74.125.39.104: seq=0 ttl=51 time=371.025 ms 64 bytes from 74.125.39.104: seq=1 ttl=51 time=388.617 ms 64 bytes from 74.125.39.104: seq=2 ttl=51 time=316.767 ms ^C --- www.google.com ping statistics --- 4 packets transmitted, 3 packets received, 25% packet loss round-trip min/avg/max = 316.767/358.803/388.617 ms
Shutdown the connection with ifdown
root@WRT160NL:~# ifdown usb0
]]>
op5 is the leading provider of monitoring software in Europe. op5 uses Open Source and their monitoring services are now available in the Cloud via City Cloud, a cloud computing service from City Network. By introducing monitoring in a new business model, customers are now able to get professional monitoring in the Cloud which is both more cost-efficient and flexible.
By providing monitoring in the cloud op5 are able to give their existing customers an external solution to monitor their web based services, regardless if they are inside or outside the cloud. This gives the customer the ability to measure and control the user experience in a specific service. City Network also benefits from the introduction of op5 Cloud Monitor. The 500 customers using City Cloud can now create servers with the sole purpose of monitoring their virtual machines directly through the service provided by op5.
- The fact that op5 introduces their external monitoring services in the cloud using City Cloud is a great acknowledgment, not only for City Cloud but also for cloud computing in general. It´s the beginning of a new era where both small and enterprise companies can benefit from the cloud and services within the cloud says Johan Christenson, Chairman at City Cloud.
- Being the leading provider in any field means that you always need to be innovative both with your products and your business models. Providing our monitoring service in City Cloud is a natural step for us and creates great advantages for our customers. More flexible, installed and ready within 15 minutes and cost efficient are the key ingredients that we think makes this solution suitable for everyone in need of professional monitoring says Jan Josephson, CEO at op5.
About City Network
With more than 10 000 customers in Scandinavia City Network is one of the leading hosting providers in northern Europe. City Network is the only Scandinavian hosting provider to offer a full service menu of hosting related services such as shared hosting to dedicated servers to cloud computing. In addition City Network is a registrar of many top level domains and offer a full suite of domain services. Box Hosting, onlinebackup.se is brands owned by City Network. Visit us at www.citycloud.eu for more information on City Cloud and www.citynetwork.eu for corporate information or www.citycloud.se for Scandinavian version of City Cloud.
About op5
op5 is a market leading developer of Open Source Management solutions develops and delivers open source based software for monitoring and administration of IT systems and networks. The solutions are built on open source code that op5 extends and markets and supports as complete systems. The main products are op5 Monitor, op5 Statistics and op5 LogServer. op5 has customers such as Aftonbladet, Volvo, SAAB, Max Matthiessen, Swedish Wetherservice (SMHI), CrossKey Banking, SAAB Industries, Bring City Mail, Channel 5 and Swedish Television (SVT), Swedish Customs and many other State authorities, local authorities and municipalities. op5 was established in 2003, has offices in Stockholm and Gothenburg and partners in several countries. op5 is owned by its founders and employees, Pod Venture Partners and KTH Chalmers Capital.
More information about op5 can be found at http://www.op5.com
For more information please contact:
Jan Josephson, CEO at op5 – jan.josephson@op5.com
Johan Christenson, Chairman at City Network Hosting AB – johan@citynetwork.se
After waiting for the Hummingbird release for the LaFonera 2.0G a long time and discussed with the Fon support team when 3G dongles will work, I gave up and installed OpenWRT on my LaFonera 2.0G router.
I’m sorry FON, you have a cool idea and nice routers but your unlogical approach to the users and communtity, finally got me to install plain OpenWRT instead.
After alot of googling and testing and downloading, reading and so on, I finally run into a guide that worked for me.
Most of the descriptions and howto assumes that the RedBoot will accept to download a new firmware via TFTP, this is true with the early releases of 2.0G , but the one sold now do not have this feature.
The trick is to install a firmware that allows changing the RedBoot partition of the memory, change the RedBoot parttion and install OpenWRT via TFTP.
The guide is unfortunatly in French, but google translate helped me to translate it to English.
The pitfalls I run into is to reboot the device several timesafter installing the hacked version of FON firmware: FON2202_2.2.5.0_Flipper_RedBootC_VoteGOP.image
The only difference is that I used a later version of OpenWRT. I used Backfire 10.03 instead of Kamikaze 8.9.1
]]>After succesfully installed my new Linksys WRT160NL with OpenWrt, the next step is to configure it. As the summer is approaching and my need for Internet access in our summer cottage will arrise. The summer cottage is in the middle of nowhere so it would be handy to put a USB dongle and the Wlan router in the spot with best 3G field strength and use the WiFi to connect several computers to the router and Internet.
The 3G USB modem is a Huawei modem I bought for 20 EUR and unlocked using this guide.
I found an excellent guide describing excactly what I wanted todo but it did not work 100% in my environment so I will describe what I did to get it running. Read the guide to get background and deeper explanation of how things are done. This guide assumes that you have read the guide, basic knowledge of OpenWRT, howto edit files in a Linux environment and so on.
The USB hardware and the modem need some extra packages to be installed. I installed the following:
root@WRT160NL:~#opkg install kmod-ar9170 kmod-usb-acm kmod-usb-core kmod-usb-ohci kmod-usb-serial comgt kmod-usb-serial-option kmod-usb-storage kmod-usb-uhci kmod-usb2 usb-switch
Probably not all of them are necessery but during my tests and fiddeling these are the ones I installed.
Create /etc/modules.d/60-usb-serial:
usbserial vendor=0x12d1 product=0x1446
The vendor and product parameters can be found by attaching the 3G modem and run:
root@WRT160NL:~# cat /proc/bus/usb/devices
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 2.06
S: Manufacturer=Linux 2.6.32.10 ehci_hcd
S: Product=Atheros AR91xx built-in EHCI controller
S: SerialNumber=ar71xx-ehci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=1446 Rev= 0.00
S: Manufacturer=HUAWEI Technology
S: Product=HUAWEI Mobile
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usbserial_generic
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usbserial_generic
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
The parameters are marked in yellow above.
The next step is to configure usb switch. Create /etc/usb-modeswitch.conf
######################################################## # Huawei E270+ (HSPA+ modem) DefaultVendor= 0x12d1 DefaultProduct=0x1446 TargetVendor= 0x12d1 TargetProductList="1001,1406,140c,14ac" CheckSuccess=20 MessageContent="55534243123456780000000000000011060000000000000000000000000000"
I have no clue of the syntax but I copied it from my Ubuntu machine /etc/usb_modeswitch.d/12d1:1446 and it works:-)
Add the following to /etc/config/network
config 'interface' 'ppp0'
option 'ifname' 'ppp0'
option 'proto' '3g'
option 'device' '/dev/ttyUSB0'
option 'apn' 'internet.tele2.se'
option 'pincode' '1234'
The pincode is obvious, the apn is local and given by your local operator. It is handy to configure it to work in Ubuntu and then look at the configuration Ubuntu creates.
The firewall rules need to be updated and I added ppp0 to the wan section in /etc/config/firewall
config 'zone'
option 'name' 'wan'
option 'input' 'REJECT'
option 'output' 'ACCEPT'
option 'forward' 'REJECT'
option 'masq' '1'
option 'mtu_fix' '1'
option 'network' 'wan ppp0'
To make the change to take effect run:
root@WRT160NL:~# /etc/init.d/firewall restart
Attach the modem and run:
root@WRT160NL:~# usb_modeswitch
Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
Found default devices (1)
Accessing device 002 on bus 001 ...
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usbserial_generic")
OK, driver "usbserial_generic" detached
SCSI inquiry data (for identification)
-------------------------
Vendor String: HUAWEI
Model String: Mass Storage
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI Technology
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x01 ...
OK, message successfully sent
Device is gone, skipping any further commands
Checking for mode switch (max. 20 times, once per second) ...
Original device is gone already, not checking
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Found correct target device
Mode switch succeeded. Bye.
logread should now give something similiar to:
Jun 12 17:29:11 WRT160NL user.info kernel: generic ttyUSB0: generic converter now disconnected from ttyUSB0 Jun 12 17:29:11 WRT160NL user.info kernel: usbserial_generic 1-1:1.0: device disconnected Jun 12 17:29:11 WRT160NL user.warn kernel: usb 1-1: usbfs: process 1345 (usb_modeswitch) did not claim interface 0 before use Jun 12 17:29:11 WRT160NL user.info kernel: usb 1-1: USB disconnect, address 2 Jun 12 17:29:11 WRT160NL user.info kernel: generic ttyUSB1: generic converter now disconnected from ttyUSB1 Jun 12 17:29:11 WRT160NL user.info kernel: usbserial_generic 1-1:1.1: device disconnected Jun 12 17:29:16 WRT160NL user.info kernel: usb 1-1: new high speed USB device using ar71xx-ehci and address 3 Jun 12 17:29:16 WRT160NL user.info kernel: usb 1-1: configuration #1 chosen from 1 choice Jun 12 17:29:16 WRT160NL user.info kernel: option 1-1:1.0: GSM modem (1-port) converter detected Jun 12 17:29:16 WRT160NL user.info kernel: usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0 Jun 12 17:29:16 WRT160NL user.info kernel: option 1-1:1.1: GSM modem (1-port) converter detected Jun 12 17:29:16 WRT160NL user.info kernel: usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1 Jun 12 17:29:16 WRT160NL user.info kernel: option 1-1:1.2: GSM modem (1-port) converter detected Jun 12 17:29:16 WRT160NL user.info kernel: usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2 Jun 12 17:29:16 WRT160NL user.info kernel: scsi3 : SCSI emulation for USB Mass Storage devices Jun 12 17:29:16 WRT160NL user.debug kernel: usb-storage: device found at 3 Jun 12 17:29:16 WRT160NL user.debug kernel: usb-storage: waiting for device to settle before scanning Jun 12 17:29:16 WRT160NL user.info kernel: scsi4 : SCSI emulation for USB Mass Storage devices Jun 12 17:29:16 WRT160NL user.debug kernel: usb-storage: device found at 3 Jun 12 17:29:16 WRT160NL user.debug kernel: usb-storage: waiting for device to settle before scanning Jun 12 17:29:21 WRT160NL user.notice kernel: scsi 3:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 Jun 12 17:29:21 WRT160NL user.debug kernel: usb-storage: device scan complete Jun 12 17:29:21 WRT160NL user.notice kernel: scsi 4:0:0:0: Direct-Access HUAWEI SD Storage 2.31 PQ: 0 ANSI: 2 Jun 12 17:29:21 WRT160NL user.notice kernel: sd 4:0:0:0: [sda] Attached SCSI removable disk Jun 12 17:29:21 WRT160NL user.debug kernel: usb-storage: device scan complete
To start using your new configuration:
root@WRT160NL:~# ifup ppp0 SIM ready PIN set successfully
And now ping a host on Internet
root@WRT160NL:~# ping ftp.sunet.se PING ftp.sunet.se (194.71.11.69): 56 data bytes 64 bytes from 194.71.11.69: seq=0 ttl=55 time=119.351 ms 64 bytes from 194.71.11.69: seq=1 ttl=55 time=88.978 ms 64 bytes from 194.71.11.69: seq=2 ttl=55 time=88.751 ms 64 bytes from 194.71.11.69: seq=3 ttl=55 time=88.484 ms 64 bytes from 194.71.11.69: seq=4 ttl=55 time=128.257 ms ^C --- ftp.sunet.se ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 88.484/102.764/128.257 ms
Stop your connection:
root@WRT160NL:~# ifdown ppp0
]]>
After getting fedup with the bad fon support I decided to give a new wireless router a try. After browsing internet and openwrt forums I thought that a Linksys WRT160NL would fulfill my requirements:
The requrements are:
The installation from Linksys is crap, a CD comes with the product and if you want to configure it you need to install software from the CD. The only supported operating systems are windows or Mac, I run linux.
I skipped the CD and connected my Linux box with a ethernet cable to the router. I tried to connect to http://192.168.1.1 and got a login screen.
After some googling I found that the default login was blank and the password admin.
I managed to configure my new router after logging in. I do not now the purpose of the CD, real stupid.
I read the instructions to get OpenWRT on my Linksys WRT160NL and tried the "OEM easy installation". According to the instruction openwrt-ar71xx-wrt160nl-squashfs.bin is the image to install. Unfortunatly I get an errormessage " Firmware Upgrade Failed!"
I upgraded the firmware to the latest Linksys firmware and after that tried the OpenWRT firmware with the same error message.
After some bad language and alot of googling I found a bug reported that the version I tried to install always gives that message when installed from the Linksys webgui.
So I tried the Beta version instead and finally I success message.
I telneted to 192.168.1.1 and run passwd to change my password.
ssh to 192.168.1.
run:
root@OpenWrt:~# opkg update root@OpenWrt:~# opkg install kmod-ath9k root@OpenWrt:~# opkg install hostapd
And start configure.
It was a annoying feeling to run beta when a stable version existed.
I used the luci webgui to update the firmware to the stable version and it looked alright. I managed to log in both with ssh and webgui.
But when I tried to install a new package it gave me an error message that there was no free disk, sigh!
I installed the BETA version and it worked, tried RC3 and the same problem with no free disk.
After some bad language and a lot of fiddeling I updated to the stable with the checkbox "Keep configuration files" unchecked and this time it works flawless.
Follow the guidlines above to change root password, update the software package list, install wlansupport, WAP support and start configure.
A succefull login below:
peter@peter-laptop:~$ ssh -l root 192.168.1.1
root@192.168.1.1's password:
BusyBox v1.15.3 (2010-04-06 03:14:11 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
Backfire (10.03, r20728) --------------------------
* 1/3 shot Kahlua In a shot glass, layer Kahlua
* 1/3 shot Bailey's on the bottom, then Bailey's,
* 1/3 shot Vodka then Vodka.
---------------------------------------------------
root@WRT160NL:~# uname -a Linux WRT160NL 2.6.32.10 #20 Tue Apr 6 15:01:26 CEST 2010 mips GNU/Linux
]]>
- OpenBSD 4.7 RELEASED -------------------------------------------------
May 19, 2010.
We are pleased to announce the official release of OpenBSD 4.7.
This is our 27th release on CD-ROM (and 28th via FTP). We remain
proud of OpenBSD's record of more than ten years with only two remote
holes in the default install.
As in our previous releases, 4.7 provides significant improvements,
including new features, in nearly all areas of the system:
- New/extended platforms:
o OpenBSD/alpha
o Added support for the DS15/DS25/ES45.
o OpenBSD/loongson
New platform for systems based on the Loongson 2E and 2F MIPS-compatible
processors. Supported machines include:
o Lemote Fuloong 2F mini-PC
o Lemote Lynloong all-in-one-PC
o Lemote Yeeloong netbook (8.9" and 10.1" models)
o EMTEC Gdium Liberty 1000 netbook
o OpenBSD/sgi
o Added support for multi-node SGI Origin systems, in M mode.
o Added support for the SGI Origin 350, Onyx 350, Onyx 4 and
Tezro systems.
o Added SMP support on the SGI Octane.
o Support for many more onboard devices on Octane and Origin systems.
o OpenBSD/socppc
o Added support for the RouterBOARD RB600A.
o OpenBSD/sparc64
o Preliminary support for running OpenBSD in a guest domain on top of
an OpenBSD control domain on sun4v machines.
- Improved hardware support, including:
o Revamped SCSI midlayer and improved driver support.
o UDF 2.5 and 2.6 (HDDVD and Blu-ray) disks support.
o Added mpath(4), a driver that steals paths to scsi devices if they could
be available via multiple paths and then made available via mpath(4).
o New aibs(4) driver for ASUSTeK AI Booster hardware monitoring.
o New uthum(4) driver for the TEMPerHUM USB temperature and humidity
sensors.
o New utrh(4) driver for USBRH temperature and humidity sensors.
o New uyurex(4) driver for the Maywa-denki & KAYAC YUREX twitch/jiggle of
knee sensor.
o New urndis(4) driver for remote NDIS Ethernet over USB devices (phones).
o New xf86-video-wsudl(4) Xorg driver for USB DisplayLink devices
supported by udl(4).
o New mpii(4) driver for LSI Logic Fusion MPT Message Passing Interface II
based SAS 2 controllers.
o New athn(4) driver for Atheros IEEE 802.11a/g/n wireless network devices.
o New alc(4) driver for Atheros AR8131/AR8132 10/100/Gigabit Ethernet
devices.
o New lisa(4) driver for STMicroelectronics LIS331DL MEMS motion sensors.
o New gcu(4) driver for Intel EP80579 Global Configuration Unit.
o New lom(4) driver for LOMLite and LOMLite2 as found on many of Sun's
UltraSPARC-IIi servers.
o New vsw(4) driver for virtual switches on sun4v machines.
o New vds(4) driver for virtual disk servers on sun4v machines.
o Support for EP80579 integrated Ethernet and ICH9 M V has been added
to em(4).
o Support for 82599 and SFP+ 82598 devices has been added to ix(4).
o Support for the Sun GigabitEthernet SBus Adapter 1.0/1.1 has been
added to ti(4).
o Support for SBus variants of the QLogic Fibre Channel host adapters
has been added to isp(4).
o Support for SBus variants of the Sun Gigabit Ethernet has been added
to gem(4).
o Support for Intel WiFi Link 1000 and Intel Centrino
Advanced-N 6200/Ultimate-N 6300 has been added to iwn(4).
o Support for Ralink RT3572 based 802.11n devices has been added to run(4).
o VIA Tremor 5.1, M-Audio Revolution 5.1 cards has been added to envy(4).
o New uhts(4) driver for USB HID touchscreens.
o Improved touchscreen support in the xf86-input-ws(4) Xorg driver and
improved calibration using the new device properties from Xinput.
o Support for ON CAT6095 and ON CAT34TS02 temperature sensors added
to sdtemp(4).
o Several improvements and bug fixes to existing Ethernet drivers,
including em(4), re(4), ti(4) and vge(4).
o Support for the PIC PCI-X controller added to the SGI xbridge(4) driver.
o Support for the onboard Fast Ethernet interface found on SGI Octane
and many SGI Origin family systems, iec(4).
o Support for more SGI input and video devices on Octane and Origin
systems, with iockbc(4), impact(4), and odyssey(4).
o Improved PCI resource allocation; more hardware left unconfigured by
the machine's firmware (including hotplugged hardware) should work now.
o Support for recording/full-duplex added to mavb(4).
o Improved support for USB audio devices in uaudio(4).
o Improved support for bwi(4) devices on strict-alignment architectures
like armish.
o Eliminate usage of SCSI tagged queueing mechanisms other than simple
queuing, thus avoiding incorrect implementations on various disk devices.
o Eliminate spurious dhclient(8) error messages when the specified
interface does not exist.
o Eliminate spurious softraid(4) error messages for removable devices
without media.
- New tools:
o newfs_ext2fs(8) for creating ext2 filesystems.
o mkuboot(8) for creating U-Boot boot loader images.
o midicat(1) MIDI server allowing MIDI programs to communicate
o POSIX-compliant fuser(1) to identify process IDs holding a file open
- Filesystem midlayer improvements:
o Dynamic Buffer Cache now supported to a max size set with sysctl
kern.bufcachepercent
o Dynamic VFS name cache rewrite, now uses Red/Black trees instead of
linked lists.
o Numerous NFS client stability fixes.
o Fix FAT32 mounting.
o Fix cd9660 directory handling to eliminate looping and random
truncation of directory entries.
o Fix various internal locking problems with cd9660, udf, msdosfs
and ffs file systems.
- pf(4) improvements:
o nat-to, rdr-to, binat-to options replace the nat, rdr and binat
translation rules.
changes for more info.
o The route-to, reply-to, dup-to and fastroute options in pf.conf
move to filteropts.
o pf(4) can now translate packets between different routing domains.
o Added -S and -L options to pfctl(8) to store and load pf state table
from a file.
o Added support for IPV4 and IPv6 divert sockets.
- OpenBGPD, OpenOSPFD and other routing daemon improvements:
o Update capability code in bgpd(8) to follow RFC 5492.
o BGP MPLS VPN (RFC 4364) support added to the bgpd RIB.
o In bgpd(8), implement the RFC4486 BGP Cease Notification
Message subcodes.
o It is now possible to enable/disable specific BGP capabilities.
o Update bgpctl(8) irrfilter to support IPv6 and 4-byte AS numbers.
o Minimal router-dead-time of 1 second and sub-second hello intervals
added to ospfd(8). Additionally it is now possible to specify
sub-second SPF timers for faster route fail-over.
o ospf6d(8) is now installed by default. The RIB can be synced with
the kernel routing table now. Support for AS-ext LSA has been added.
This is still work-in-progress but testing is highly appreciated.
o ldpd -- the MPLS label distribution protocol daemon -- is now
installed by default. A custom kernel with option MPLS is needed
to use it.
- Generic network stack improvements:
o brconfig is now integrated into ifconfig(8)
o Added vether(4), a virtual Ethernet device.
o Two bugs in IPsec/HMAC-SHA2 were fixed, resulting in an incompatibility
with the HMAC-SHA-256/384/512 hash algorithms with previous versions
of OpenBSD and other IPsec implementations sharing the bugs.
o In dhcpd(8), echo back the Relay Agent Information option if present,
and add support for the ipsec-tunnel hardware type.
o Make dhcrelay(8) pick up the routing domain from the specified interface
and use that rdomain for relaying the packets to the server.
o Added support in dhcrelay(8) for RFC3046 "DHCP-over-ipsec".
o Make the tcpdump(8) BGP OPEN capability parser RFC 5492 compliant.
o Added an exec command to route(8) to run a process and its children
in a specified routing domain.
o ifconfig(8) now deals with more than 64 alias addresses.
o Various fixes to mbuf defragmenting and mbuf chain copying
improve reliability.
- Assorted improvements:
o malloc(3) now has an S flag to turn on the options that help debugging
and improve security.
o Updated terminfo(3) database and ncurses(3) library.
o Added support for lazy binding in ld.so(1) on hppa.
o Added POSIX silent check option (-C) to sort(1).
o Added POSIX extended regular expression support to sed(1) (-E option).
o Added GNU-compatible macro prefix option (-P) to m4(1).
o Make it possible to specify a port in resolv.conf(5).
o Improved FILE locking support in stdio(3).
o Added SO_SNDTIMEO and SO_RCVTIMEO support in pthreads(3).
o cdio(1) no longer prints bogus information if no TOC is found on
the disk.
o New -v flag causes cdio(1) to print profile and feature information.
o whois(1) no longer attempts to keep the memory of 6Bone alive.
o Added per-application MIDI-controlled volume knob to aucat(1)
o Added MMC and MTC support to aucat(1) making possible MIDI-to-audio
synchronization.
o Added mio_open(3) interface to access hardware and software MIDI ports
o Many memory leaks found by parfait and eliminated.
o Make handling of floppy disk disklabels more reliable by properly
initializing starting label.
- Install/Upgrade process changes:
o Take more care to ensure all filesystems are umount'ed when restarting
an install or upgrade.
o If no possible root disk is found, keep checking until one appears.
o The default ftp directory for -stable is now the release directory
instead of the snapshot directory.
o Selection of TZ during installs is no longer confused by
trailing slashes.
o If /etc/X11 is found during upgrades, add the X sets to the list
of default sets to install.
- OpenSSH 5.5:
o New features:
o SSH protocol 1 is disabled by default.
o Remove the libsectok/OpenSC-based smartcard code and add support
for PKCS#11 tokens.
o Add support for certificate authentication of users and hosts
using a new, minimal OpenSSH certificate format (not X.509).
o Added a 'netcat mode' to ssh(1).
o Add the ability to revoke keys in sshd(8) and ssh(1).
o Rewrite the ssh(1) multiplexing support to support non-blocking
operation of the mux master.
o Add a 'read-only' mode to sftp-server(8) that disables open in
write mode and all other fs-modifying protocol methods. (bz#430)
o Allow setting an explicit umask on the sftp-server(8) commandline
to override whatever default the user has. (bz#1229)
o Many improvements to the sftp(1) client.
o New RSA keys will be generated with a public exponent of 65537
instead of the previous value 35.
o Passphrase-protected SSH protocol 2 private keys are now protected
with AES-128 instead of 3DES.
o The following significant bugs have been fixed in this release:
o Fixed a minor information leak of environment variables specified in
authorized_keys if an attacker happens to know the public key in use.
o When using ChrootDirectory, make sure we test for the existence of
the user's shell inside the chroot and not outside. (bz#1679)
o Cache user and group name lookups in sftp-server using
user_from_[ug]id(3) to improve performance on hosts where these
operations are slow. (bz#1495)
o Fix problem that prevented passphrase reading from being interrupted
in some circumstances. (bz#1590)
o Ignore and log any Protocol 1 keys where the claimed size is not
equal to the actual size.
o Make HostBased authentication work with a ProxyCommand. (bz#1569)
o Avoid run-time failures when specifying hostkeys via a relative path
by prepending the current working directory in these cases. (bz#1290)
o Do not prompt for a passphrase if we fail to open a keyfile, and log
the reason why the open failed to debug. (bz#1693)
o Document that the PubkeyAuthentication directive is allowed in a
sshd_config(5) Match block. (bz#1577)
o When converting keys, truncate key comments at 72 chars as per
RFC4716. (bz#1630)
o Do not allow logins if /etc/nologin exists but is not readable by
the user logging in.
o Output a debug log if sshd(8) can't open an existing
authorized_keys. (bz#1694)
o Quell tc[gs]etattr(3) warnings when forcing a tty (ssh -tt), since
we usually don't actually have a tty to read/set. (bz#1686)
o Prevent sftp(1) from crashing when given a "-" without a command;
also, allow whitespace to follow a "-". (bz#1691)
o After sshd(8) receives a SIGHUP, ignore subsequent HUPs while
sshd(8) re-execs itself; prevents two HUPs in quick succession
from resulting in sshd(8) dying. (bz#1692)
o Clarify in sshd_config(5) that StrictModes does not apply to
ChrootDirectory; permissions and ownership are always checked
when chrooting. (bz#1532)
o Set close-on-exec on various descriptors so they don't get leaked
to child processes. (bz#1643)
o Fix very rare race condition in x11/agent channel allocation
o Fix incorrect exit status when multiplexing and channel ID 0 is
recycled. (bz#1570)
o Fail with an error when an attempt is made to connect to a server
with ForceCommand=internal-sftp with a shell session. (bz#1606)
o Warn but do not fail if stat(2)ing the subsystem binary
fails. (bz#1599)
o Change "Connecting to host..." message to "Connected to host." and
delay it until after the sftp protocol connection has been
established. (bz#1588)
o Use the HostKeyAlias rather than the hostname specified on the
commandline when prompting for passwords. (bz#1039)
o Correct off-by-one in percent_expand(). (bz#1607)
o Fix passing of empty options from scp(1) and sftp(1) to the
underlying ssh(1); also add support for the stop option "--".
o Fix an incorrect magic number and typo in PROTOCOL. (bz#1688)
o Don't escape backslashes when displaying the SSH2 banner. (bz#1533)
o Don't unnecessarily dup() the in and out fds for
sftp-server(8). (bz#1566)
o Force use of the correct hash function for random-art signature
display. (bz#1611)
o Do not fall back to adding keys without constraints when the agent
refuses the constrained add request. (bz#1612)
o Fix a race condition in ssh-agent(1) that could result in a wedged
or spinning agent. (bz#1633)
o Flush stdio before exec() to ensure that everything has made it out
before the streams go away. (bz#1596)
o Set FD_CLOEXEC on in/out sockets in sshd(8). (bz#1706)
- Over 5,800 ports, major robustness and speed improvements in package tools.
- Many pre-built packages for each architecture:
o i386: 5951
o sparc64: 5745
o alpha: 5641
o sh: 768
o amd64: 5879
o powerpc: 5785
o sparc: 4053
o arm: 3711
o hppa: 5500
o vax: 1785
o mips64: 3690
o mips64el: 4316
- Some highlights:
o Gnome 2.28.2.
o KDE 3.5.10.
o Xfce 4.6.1.
o MySQL 5.1.42.
o PostgreSQL 8.4.2.
o Postfix 2.6.5.
o OpenLDAP 2.3.43.
o Mozilla Firefox 3.0.18 and 3.5.8.
o Mozilla Thunderbird 2.0.0.23.
o OpenOffice.org 3.1.1.
o Emacs 21.4 and 22.3
o Vim 7.2.267.
o PHP 5.2.12.
o Python 2.4.6, 2.5.4 and 2.6.3.
o Ruby 1.8.6.369.
- As usual, steady improvements in manual pages and other documentation.
- The system includes the following major components from outside suppliers:
o Xenocara (based on X.Org 7.4 with xserver 1.6.5 + patches,
freetype 2.3.9, fontconfig 2.6.0, Mesa 7.4.2, xterm 250 and more)
o Gcc 2.95.3 (+ patches) and 3.3.5 (+ patches)
o Perl 5.10.1 (+ patches)
o Our improved and secured version of Apache 1.3, with SSL/TLS
and DSO support
o OpenSSL 0.9.8k (+ patches)
o Groff 1.15
o Sendmail 8.14.3, with libmilter
o Bind 9.4.2-P2 (+ patches)
o Lynx 2.8.6rel.5 with HTTPS and IPv6 support (+ patches)
o Sudo 1.7.2
o Ncurses 5.7
o Latest KAME IPv6
o Heimdal 0.7.2 (+ patches)
o Arla 0.35.7
o Binutils 2.15 (+ patches)
o Gdb 6.3 (+ patches)
If you'd like to see a list of what has changed between OpenBSD 4.6
and 4.7, look at
http://www.OpenBSD.org/plus47.html
Even though the list is a summary of the most important changes
made to OpenBSD, it still is a very very long list.
------------------------------------------------------------------------
- SECURITY AND ERRATA --------------------------------------------------
We provide patches for known security threats and other important
issues discovered after each CD release. As usual, between the
creation of the OpenBSD 4.7 FTP/CD-ROM binaries and the actual 4.7
release date, our team found and fixed some new reliability problems
(note: most are minor and in subsystems that are not enabled by
default). Our continued research into security means we will find
new security problems -- and we always provide patches as soon as
possible. Therefore, we advise regular visits to
http://www.OpenBSD.org/security.html
and
http://www.OpenBSD.org/errata.html
Security patch announcements are sent to the security-announce@OpenBSD.org
mailing list. For information on OpenBSD mailing lists, please see:
http://www.OpenBSD.org/mail.html
------------------------------------------------------------------------
- CD-ROM SALES ---------------------------------------------------------
OpenBSD 4.7 is also available on CD-ROM. The 3-CD set costs $50 CDN and
is available via mail order and from a number of contacts around the
world. The set includes a colourful booklet which carefully explains the
installation of OpenBSD. A new set of cute little stickers is also
included (sorry, but our FTP mirror sites do not support STP, the Sticker
Transfer Protocol). As an added bonus, the second CD contains an audio
track, a song entitled "I'm still here". MP3 and OGG versions of
the audio track can be found on the first CD.
Lyrics (and an explanation) for the songs may be found at:
http://www.OpenBSD.org/lyrics.html#47
Profits from CD sales are the primary income source for the OpenBSD
project -- in essence selling these CD-ROM units ensures that OpenBSD
will continue to make another release six months from now.
The OpenBSD 4.7 CD-ROMs are bootable on the following four platforms:
o i386
o amd64
o macppc
o sparc64
(Other platforms must boot from floppy, network, or other method).
For more information on ordering CD-ROMs, see:
http://www.OpenBSD.org/orders.html
The above web page lists a number of places where OpenBSD CD-ROMs
can be purchased from. For our default mail order, go directly to:
https://https.OpenBSD.org/cgi-bin/order
All of our developers strongly urge you to buy a CD-ROM and support
our future efforts. Additionally, donations to the project are
highly appreciated, as described in more detail at:
http://www.OpenBSD.org/goals.html#funding
------------------------------------------------------------------------
- OPENBSD FOUNDATION ---------------------------------------------------
For those unable to make their contributions as straightforward gifts,
the OpenBSD Foundation (http://www.openbsdfoundation.org) is a Canadian
not-for-profit corporation that can accept larger contributions and
issue receipts. In some situations, their receipt may qualify as a
business expense writeoff, so this is certainly a consideration for
some organizations or businesses. There may also be exposure benefits
since the Foundation may be interested in participating in press releases.
In turn, the Foundation then uses these contributions to assist OpenBSD's
infrastructure needs. Contact the foundation directors at
directors@openbsdfoundation.org for more information.
------------------------------------------------------------------------
- T-SHIRT SALES --------------------------------------------------------
The OpenBSD distribution companies also sell tshirts and polo shirts.
And our users like them too. We have a variety of shirts available,
with the new and old designs, from our web ordering system at, as
described above.
The OpenBSD 4.7 t-shirts are available now. We also sell our older
shirts, as well as a selection of OpenSSH t-shirts.
------------------------------------------------------------------------
- FTP INSTALLS ---------------------------------------------------------
If you choose not to buy an OpenBSD CD-ROM, OpenBSD can be easily
installed via FTP. Typically you need a single small piece of boot
media (e.g., a boot floppy) and then the rest of the files can be
installed from a number of locations, including directly off the
Internet. Follow this simple set of instructions to ensure that
you find all of the documentation you will need while performing
an install via FTP. With the CD-ROMs, the necessary documentation
is easier to find.
1) Read either of the following two files for a list of ftp
mirrors which provide OpenBSD, then choose one near you:
http://www.OpenBSD.org/ftp.html
ftp://ftp.OpenBSD.org/pub/OpenBSD/4.7/ftplist
As of May 19, 2010, the following ftp mirror sites have the 4.7 release:
ftp://ftp.eu.openbsd.org/pub/OpenBSD/4.7/ Stockholm, Sweden
ftp://ftp.bytemine.net/pub/OpenBSD/4.7/ Oldenburg, Germany
ftp://mirror.aarnet.edu.au/pub/OpenBSD/4.7/ Brisbane, Australia
ftp://ftp.wu-wien.ac.at/pub/OpenBSD/4.7/ Vienna, Austria
ftp://ftp.usa.openbsd.org/pub/OpenBSD/4.7/ CO, USA
ftp://ftp5.usa.openbsd.org/pub/OpenBSD/4.7/ CA, USA
ftp://obsd.cec.mtu.edu/pub/OpenBSD/4.7/ Michigan, USA
The release is also available at the master site:
ftp://ftp.openbsd.org/pub/OpenBSD/4.7/ Alberta, Canada
However it is strongly suggested you use a mirror.
Other mirror sites may take a day or two to update.
2) Connect to that ftp mirror site and go into the directory
pub/OpenBSD/4.7/ which contains these files and directories.
This is a list of what you will see:
ANNOUNCEMENT armish/ mvme68k/ sparc64/
Changelogs/ ftplist mvme88k/ src.tar.gz
HARDWARE hp300/ packages/ sys.tar.gz
PACKAGES hppa/ ports.tar.gz tools/
PORTS i386/ root.mail vax/
README landisk/ sgi/ xenocara.tar.gz
alpha/ mac68k/ socppc/ zaurus/
amd64/ macppc/ sparc/
It is quite likely that you will want at LEAST the following
files which apply to all the architectures OpenBSD supports.
README - generic README
HARDWARE - list of hardware we support
PORTS - description of our "ports" tree
PACKAGES - description of pre-compiled packages
root.mail - a copy of root's mail at initial login.
(This is really worthwhile reading).
3) Read the README file. It is short, and a quick read will make
sure you understand what else you need to fetch.
4) Next, go into the directory that applies to your architecture,
for example, i386. This is a list of what you will see:
INSTALL.i386 cd47.iso floppyB47.fs pxeboot*
INSTALL.linux cdboot* floppyC47.fs xbase47.tgz
MD5 cdbr* game47.tgz xetc47.tgz
base47.tgz cdemu47.iso index.txt xfont47.tgz
bsd* comp47.tgz install47.iso xserv47.tgz
bsd.mp* etc47.tgz man47.tgz xshare47.tgz
bsd.rd* floppy47.fs misc47.tgz
If you are new to OpenBSD, fetch _at least_ the file INSTALL.i386
and the appropriate floppy*.fs or install47.iso files. Consult the
INSTALL.i386 file if you don't know which of the floppy images
you need (or simply fetch all of them).
If you use the install47.iso file (roughly 200MB in size), then you
do not need the various *.tgz files since they are contained on that
one-step ISO-format install CD.
5) If you are an expert, follow the instructions in the file called
README; otherwise, use the more complete instructions in the
file called INSTALL.i386. INSTALL.i386 may tell you that you
need to fetch other files.
6) Just in case, take a peek at:
http://www.OpenBSD.org/errata.html
This is the page where we talk about the mistakes we made while
creating the 4.7 release, or the significant bugs we fixed
post-release which we think our users should have fixes for.
Patches and workarounds are clearly described there.
Note: If you end up needing to write a raw floppy using Windows,
you can use "fdimage.exe" located in the pub/OpenBSD/4.7/tools
directory to do so.
------------------------------------------------------------------------
- X.ORG FOR MOST ARCHITECTURES -----------------------------------------
X.Org has been integrated more closely into the system. This release
contains X.Org 7.4. Most of our architectures ship with X.Org, including
amd64, sparc, sparc64 and macppc. During installation, you can install
X.Org quite easily. Be sure to try out xdm(1) and see how we have
customized it for OpenBSD.
------------------------------------------------------------------------
- PORTS TREE -----------------------------------------------------------
The OpenBSD ports tree contains automated instructions for building
third party software. The software has been verified to build and
run on the various OpenBSD architectures. The 4.7 ports collection,
including many of the distribution files, is included on the 3-CD
set. Please see the PORTS file for more information.
Note: some of the most popular ports, e.g., the Apache web server
and several X applications, come standard with OpenBSD. Also, many
popular ports have been pre-compiled for those who do not desire
to build their own binaries (see BINARY PACKAGES, below).
------------------------------------------------------------------------
- BINARY PACKAGES WE PROVIDE -------------------------------------------
A large number of binary packages are provided. Please see the PACKAGES
file (ftp://ftp.OpenBSD.org/pub/OpenBSD/4.7/PACKAGES) for more details.
------------------------------------------------------------------------
- SYSTEM SOURCE CODE ---------------------------------------------------
The CD-ROMs contain source code for all the subsystems explained
above, and the README (ftp://ftp.OpenBSD.org/pub/OpenBSD/4.7/README)
file explains how to deal with these source files. For those who
are doing an FTP install, the source code for all four subsystems
can be found in the pub/OpenBSD/4.7/ directory:
xenocara.tar.gz ports.tar.gz src.tar.gz sys.tar.gz
------------------------------------------------------------------------
- THANKS ---------------------------------------------------------------
Ports tree and package building by Jasper Lievisse Adriaanse, Michael Erdely,
Simon Bertrang, Stuart Henderson, Antoine Jacoutot, Robert Nagy,
Nikolay Sturm, and Christian Weisgerber. System builds by Theo de Raadt,
Mark Kettenis, and Miod Vallat. X11 builds by Todd Fries and Miod Vallat.
ISO-9660 filesystem layout by Theo de Raadt.
We would like to thank all of the people who sent in bug reports, bug
fixes, donation cheques, and hardware that we use. We would also like
to thank those who pre-ordered the 4.7 CD-ROM or bought our previous
CD-ROMs. Those who did not support us financially have still helped
us with our goal of improving the quality of the software.
Our developers are:
Alexander Bluhm, Alexander Hall, Alexander von Gernler,
Alexander Yurchenko, Alexandre Ratchov, Alexey Vatchenko,
Anders Magnusson, Andreas Gunnarsson, Anil Madhavapeddy,
Antoine Jacoutot, Ariane van der Steldt, Artur Grabowski,
Austin Hook, Benoit Lecocq, Bernd Ahlers, Bob Beck, Bret Lambert,
Can Erkin Acar, Chad Loder, Charles Longeau, Chris Kuethe,
Christian Weisgerber, Claudio Jeker, Dale Rahn, Damien Bergamini,
Damien Miller, Dariusz Swiderski, Darren Tucker,
David Gwynne, David Hill, David Krause, Edd Barrett, Eric Faurot,
Esben Norby, Fabien Romano, Federico G. Schwindt, Felix Kronlage,
Gilles Chehade, Giovanni Bechis, Gordon Willem Klok,
Henning Brauer, Ian Darwin, Igor Sobrado, Ingo Schwarze,
Jacek Masiulaniec, Jacob Meuser, Jakob Schlyter, Janne Johansson,
Jared Yanovich, Jason Dixon, Jason George, Jason McIntyre,
Jason Meltzer, Jasper Lievisse Adriaanse, Jim Razmus II, Joel Sing,
Joerg Goltermann, Johan Mson Lindman, Jolan Luff, Jonathan Armani,
Jonathan Gray, Jordan Hargrave, Joshua Stein, Kenneth R Westerback,
Kevin Lo, Kevin Steves, Kjell Wooding, Kurt Miller, Landry Breuil,
Laurent Fanis, Marc Espie, Marco Peereboom, Marco Pfatschbacher,
Marco S Hyman, Marcus Glocker, Marek Vasut, Mark Kettenis,
Mark Uemura, Markus Friedl, Martin Reindl, Martynas Venckus,
Mathieu Sauve-Frankel, Mats O Jansson, Matthias Kilian,
Matthieu Herrb, Michael Erdely, Michael Knudsen, Michele Marchetto,
Mike Larkin, Miod Vallat, Moritz Grimm, Moritz Jodeit,
Nicholas Marriott, Nick Holland, Nikolay Sturm, Okan Demirmen,
Oleg Safiullin, Otto Moerbeek, Owain Ainsworth, Paul de Weerd,
Paul Irofti, Peter Hessler, Peter Stromberg, Peter Valchev,
Philip Guenther, Pierre-Emmanuel Andre, Pierre-Yves Ritschard,
Rainer Giedat, Reyk Floeter, Robert Nagy, Rui Reis,
Ryan Thomas McBride, Simon Bertrang, Simon Perreault, Stefan Kempf,
Stefan Sperling, Stephan A. Rickauer, Steven Mestdagh,
Stuart Henderson, Takuya Asada, Ted Unangst, Theo de Raadt,
Thordur I Bjornsson, Tobias Stoeckmann, Tobias Weingartner,
Todd C. Miller, Todd Fries, Will Maier, William Yodlowsky,
Xavier Santolaria, Yasuoka Masahiko, Yojiro Uo
]]>I have registred me to attend the open Splunk event in Stockholm. Within 24 hours I got an email telling that they do not want competitors at the event and would like to discuss the purpose of me attending.
I called the Splunk representative and told him that op5 thinks Splunk is a competitor in some cases and in some cases we have products that run in parallel at customer sites. We want to integrate op5 Monitor with Splunk because we have got the question a couple of times from customers and potential customers. My intention of attending the meeting is to get a better understanding of Splunk so op5 can integrate our products, so our customers get the products that suits them best. If Splunk wants to be part of the integration, the better.
The Splunk representative still do not want me to attend. At Splunk they will discuss this matter internally but so far, this is their view.
I would really like to make a parallel with another op5 competitor, Würth, at their event they invited op5 as key speaker and I really recommend Splunk to reconsider their decision.
]]>| VOIP Today magazine releases its 8th the postscript to www.voiptoday.org VOIP Today magazine is a freely available and independent online publication presenting up-to-date VoIP news and information covering all aspects of the VoIP technology, internet telephony solutions, networks, phones, security, internet telephony marketplace, mobile communications, VoIP forums and call center solutions. It has strong relationships with members of the VoIP community and is rapidly building a unique, high-quality community of VoIP users and vendors. VoIP Today magazine is building tomorrow’s VoIP community. Share in building tomorrow‘s community by joining VOIP Today community |
|
]]>
I’m the happay owner of a Huawei E1750 modem and it is real easy to get it running in Ubuntu. This guide will probably work with many other 3G USB modems.
Just type from the command line:
sudo apt-get install usb-modeswitch
Plug in the modem
Go to the Network manager and enter your Mobile Broadband credentials and now it works!
]]>I found a new favorite app to my Android, mythmote.
By using it you can turn your Android into a remote control for MythTV. On the mythfrontend telnet control must be enbled and it is found under Setup-Setup-General and check "Enable Network Remote Control Interface".
The Android uses wifi to connect to the telnet server at the mythfront.
]]>
I wanted to unlock my operator locked Huawei e1750 modem. After googling I found this page in swedish.
The unlock code can be calculated by using the IMEI number, the unlock code is sent by using AT commands.
I have succesfully tested this on e1750 and e1550.
I also tried it on e220 and it did not work.
Normally this is printed on the device put the geek way of getting it is by asking the device:
peter@peter-laptop:~/huawei$ cat /dev/ttyUSB0 & [1] 9378 peter@peter-laptop:~/huawei$ echo -e "ATI\r" > /dev/ttyUSB0 peter@peter-laptop:~/huawei$ ATI Manufacturer: huawei Model: E1750 Revision: 11.126.07.04.00 IMEI: 123456789012347 +GCAP: +CGSM,+DS,+ES OK
So the IMEI number is: 123456789012347
The following python script will calculate the unlock code:
import hashlib
def getCode(imei, salt):
digest = hashlib.md5((imei+salt).lower()).digest()
code = 0
for i in range(0,4):
code += (ord(digest[i])^ord(digest[4+i])^ord(digest[8+i])^ord(digest[12+i])) << (3-i)*8
code &= 0x1ffffff
code |= 0x2000000
return code
# Your IMEI goes here:
imei = "123456789012347"
print "Unlock code: %s" % getCode(imei, "5e8dd316726b0335")
print "Flash code: %s" % getCode(imei, "97b7bc6be525ab44")
When run:
peter@peter-laptop:~/huawei$ python unlock_code.py Unlock code: 36963763 Flash code: 53969249
peter@peter-laptop:~/huawei$ echo -e 'AT^CARDLOCK="36963763"\r' > /dev/ttyUSB0 OK
Congratulations, now your modem is unlocked
]]>With my new and fancy HTC Desire I wanted to look at my Nagios or op5 Monitor status. I have found two apps Nagroid and NagMonDroid.
NagMonDroid did I not get working, probably because op5 Monitor only uses https as protocol.
Nagroid works like a charm:
The configuration is rather straightforward:
]]>I wanted to use the Android SDK on my Ubuntu machine, mainly to grab screenshoots but also to play around with it.
I followed the guidelines at this guide, but it did not work. DDM just show garbage as the device and when trying to get a screenshoot it complained with:
54:42 W/ddms: Unable to get frame buffer: device (????????????) request rejected: insufficient permissions for device
After some googling i figured out that I had to hack my udev rules.
I added to /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c87", MODE="0666"
and run reload udev
The idVendor and idProduct was found by running lsusb:
# lsusb Bus 002 Device 011: ID 0bb4:0c87 High Tech Computer Corp.
Now when starting DDM:
And I can take screenshoots:
]]>
For the first time I felt that this is more than a phone, for the first time calender integration works, for the first time I can use the builtin GPS, for the first time accessing the web with a phone works, for the first time downloaded software really works.
My favorite apps so far is:
Of cource the device is not perfect, I miss:
I really hope that Google and/or HTC understand and use the power of the community to make the Android even more succesfull by open it even more.
]]>
I have not updated my blog lately because of heavy traveling. In Tuesday, after visiting GoOpen 2010, I took this picture at Gardemoen, Oslo. I was very lucky because my flight was DY3774
It seams like I was in luck and used an ash hole to get home:-)
]]>
op5 will release op5 Monitor 5.0 April the 13:th including:
You are welcome to a release party together with op5, customers and partners.
Welcome!!
]]>
I bought a Fonera 2.0g WLAN router and I wanted to extend the functionality to have the possibility to add packages from OpenWRT. I also wanted the possibility to manage my new router with ssh.
The way to achive this is by installing developer firmware.
I followed the instructions at Fons beta/developer wiki.
The image I used can be found here.
I try to connect by using ssh
peter@peter-laptop:~$ ssh -l root 192.168.10.1
root@192.168.10.1's password:
BusyBox v1.11.1 (2009-04-17 12:45:57 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
__
_.-~ )
_..--~~~~,' ,-/ _
.-'. . . .' ,-',' ,' )
,'. . . _ ,--~,-'__..-' ,'
,'. . . (@)' ---~~~~ ,'
/. . . . '~~ ,-'
/. . . . . ,-'
; . . . . - . ,'
: . . . . _ /
. . . . . `-.:
. . . ./ - . )
. . . | _____..---.._/ ____ Seal _
~---~~~~----~~~~ ~~
Flipper
-------- Fonera 2.0 Firmware (v2.2.5.0) -----------
* Based on OpenWrt - http://openwrt.org
* Powered by FON - http://www.fon.com
----------------------------------------------------
When using a cool router software like OpenWRT it is a good idea to monitor the network usage. This article describe howto get SNMP on your OpenWRT based router.
The easiest way is to use the webgui, http://<your router ip>
Log in to the La Fonera using ssh:
peter@peter-laptop:~$ ssh -l root 192.168.0.159
root@192.168.0.159's password:
BusyBox v1.11.2 (2009-12-02 11:25:47 UTC) built-in shell (ash)
Enter 'help' for a list of built-in commands.
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
KAMIKAZE (8.09.2, r18961) -------------------------
* 10 oz Vodka Shake well with ice and strain
* 10 oz Triple sec mixture into 10 shot glasses.
* 10 oz lime juice Salute!
---------------------------------------------------
root@fon:~#
Start snmpd
root@fon:~# /etc/init.d/snmpd start
Make it start when rebooted:
root@fon:~# /etc/init.d/snmpd enable
If you want to change your SNMP configuration the configuration is located in:
/etc/config/snmpd
Now you can get the SNMP data and use your favorite Monitor tool, i.e. Nagios or op5 Monitor.
Below a screenshoot from op5 Monitor:
I got an unused La Fonera router by a collegue. They can be bought from http://www.fon.com for approximately 40 Euro including freight. The purpose of the Fon community is to build a community of hotspots around the world so every owner of a La Fonera could use any other La Fonera router in the world.
I am curios about the legal aspect if someone in the Fon community uses my internet connection to do something bad, like download copyrighted software, hack CIA or whatever.
The La Fonera router is real cool because:
I followed this guide, the only exception was that I used the latest OpenWRT in "Phase C":
# ./ap51-flash-1.0-42 eth0 openwrt-atheros-root.squashfs openwrt-atheros-vmlinux.lzma
The files can be downloaded from OpenWRTs download section for atheros platform.
]]>
It is always a good idea to monitor the server hardware, in many cases the root cause of the probblem is hardware related like: a fan stops and the temperature gets to high, dust in the machine makes it to hot, disks that fails, memory corruption and so on. This article will describe howto enable hardware monitoring on a HP Proliant running CentOS Linux and then howto collect the data with Nagios or op5 Monitor. The procedure is the same with RedHat Enterprise Linux and similiar with Suse Enterprise server.
The HP manuals and information is bloated with irrelevant information and I had to struggle several hours, ask collegues to get it running. I hope this blog article will help others to get monitoring of HP Proliant using HP Insight Manager easier to setup.
You need two packages from HP and can be downloaded from hp.com under "Support & Drivers". Search your hardware plattform and correct operating system:
Install kernel source code and rpm tools:
# yum install kernel-devel rpm-build rpm-devel
Proliant Support Package is not supported on CentOS so you have to let the installer think it is a RedHat system. If you have a RHEL system skip the next steps.
# cp /etc/redhat-release /etc/redhat-release.backup # echo "Red Hat Enterprise Linux Server release 5.4 (Tikanga)">/etc/redhat-release
Untar the Proliant Support Package
# tar xzvf psp-8.25.rhel5.i686.en.tar.gz
Install the Proliant Support Package
# cd compaq/csp/linux/ # ./install825.sh
alot of text appears and some questions, answer them.
Install HP System Health Application and Insight Management Agents, and for some stupid reason it is in conflict with some other packages just installed. I solved it in a dirty way:
# rpm -i --force --replacefiles --nodeps hpasm-8.0.0-173.rhel5.i386.rpm
Configure by running:
# hpa/etc/init.d/hpasm configure
and answer the questions.
Do not forget to restore /etc/redhat-release
# cp /etc/redhat-release.backup /etc/redhat-release
I did modify my /etc/snmp/snmp.conf to:
dlmod cmaX /usr/lib/libcmaX.so rocommunity public trapsink 10.1.1.20 syscontact peter@it-slav.net syslocation PDC, Peters DataCenter
To test that you have installation and configuration work, run a snmpwalk from your Nagios or op5 Monitor host:
# snmpwalk -c public -v1 <ip-adress of your proliant box> 1.3.6.1.4.1.232 SNMPv2-SMI::enterprises.232.1.1.1.0 = INTEGER: 1 SNMPv2-SMI::enterprises.232.1.1.2.0 = INTEGER: 23 SNMPv2-SMI::enterprises.232.1.1.3.0 = INTEGER: 2 SNMPv2-SMI::enterprises.232.1.2.1.4.1.0 = INTEGER: 30 SNMPv2-SMI::enterprises.232.1.2.1.4.2.1.1.1 = INTEGER: 1 SNMPv2-SMI::enterprises.232.1.2.1.4.2.1.2.1 = STRING: "Compaq Standard Equipment Agent for Linux" SNMPv2-SMI::enterprises.232.1.2.1.4.2.1.3.1 = "" SNMPv2-SMI::enterprises.232.1.2.1.4.2.1.4.1 = Hex-STRING: 00 00 00 00 00 00 00 SNMPv2-SMI::enterprises.232.1.2.1.4.2.1.5.1 = STRING: "To gather Standard Equipment data for Linux." ...
The check_hpasm can be downloaded from Console Labs.
Unpack the tarball
# tar xzvf check_hpasm-4.1.2.tar.gz
Configure and compile # ./configure --prefix=/opt/plugins/custom/hp-insight --with-nagios-user=monitor --with-nagios-group=users --enable-perfdata ... # make ... # make install
Test
# /opt/plugins/custom/hp-insight/libexec/check_hpasm -H -C public OK - System: 'proliant dl360 g3', S/N: '7J31LMW6N01D', ROM: 'P31 01/28/2004', hardware working fine, da: 1 logical drives, 1 physical drives | fan_1=50% fan_2=50% temp_1_cpu=16;50;50 temp_2_cpu=15;65;65 temp_3_ioBoard=21;56;56 temp_4_cpu=20;65;65
Congratulations your plugin and hw monitoring works!
checkcommands.cfg
# command 'check_hpasm'
define command{
command_name check_hpasm
command_line $USER1$/custom/libexec/check_hpasm -H $HOSTADDRESS$ -C $ARG1$
}
services.cfg
# service 'Insight Manager'
define service{
use default-service
host_name humpa
service_description Insight Manager
check_command check_hpasm!public
contact_groups call_it-slav,it-slav_jabber,it-slav_mail
}
Screenshoot, using ninja
]]>
The op5 Monitor Beta use Ninja as GUI and Merlin as a databasebackend.
]]>I got a hint from a friend that I should try RockBox, so I download it and used the very simple installer on linux and it works perfectly well. All the drawbacks mentioned above are solved and as a bonus the gui is much better.
Now I can:
If you are lucky and owns a Rockbox supported media player, update it. You will not regret it.
]]>
I have read the book Asterisk now by Nir Simionovich, published in March 2008. The book was a big disappointment, the reason is that the book do not cover the software used in AsteriskNOW today. The book cover the Asterisk GUI but AsteriskNOW is using FreePBX instead which is totally different. One main reason to use AsteriskNow is to avoid the sometimes cumbersome task to install Linux or a similair operating system, download, compile and configure Asterisk using cryptic text files. So an accurate description of the GUI used is essential for a book like this and unfortunatly the book is to old. I do not intend to install an old version of AsteriskNOW just for a bookreview so I cannot tell how accurate the book is. So my recommendation is to wait for an updated version of AsteriskNow book.
–cut–
Hi All, The op5 devel team has been kind of quiet on the list lately. The–cut–
I was with my geekfriends at a ski resort and I managed to get an Internet connection using a cellphone. Of course I wanted to share it with my friends. As geeks we brought a switch and a couple of ethernetcables.
Using this script on a Ubuntu 9.10 I managed to share my connection:
sudo ifconfig eth0 10.8.16.1 sudo sysctl -w net.ipv4.ip_forward=1 sudo sysctl -w net.ipv4.conf.default.forwarding=1 sudo sysctl -w net.ipv4.conf.all.forwarding=1 sudo iptables -P FORWARD ACCEPT sudo iptables --table nat -A POSTROUTING -o ppp0 -j MASQUERADE
Conmnect everymachine with the switch and the clients just needed to use a 10.0.0.0/8 network adress and add 10.8.16.1 as default gateway and it works!
]]>