Technology Blog Dietmar Zlabinger

How to mount initrd?

dietmar — Mon, 04 Jan 2010 21:04:08 +0000

reading/writing initrd – the initial ram disk of a desktop Linux system:

mkdir tmp
cd tmp
gzip -dc /somepath/initrd.gz | cpio -id

# do the edits on the files

find . | cpio –quiet –dereference -o -H newc | gzip -9 > /somepath/new-initrd.gz

Parsing ASN1

dietmar — Tue, 12 May 2009 18:41:52 +0000

Abstract Syntax Notation 1 (ASN1) is probably one of the worst encodings the Internet community has seen. Unfortunately this encoding is a key component in Internet security. Peter Gutmann, professor at the University of Auckland, NZ has not just written “How Not to Design a Crypto Protocol/Standard“, but also an ASN1-dump C-program. I added a Java-script port written by Lapo Luchini to my homepage under http://www.zlabinger.at/asn1dump.

This version uses the top certificate of the TKK as an example.

Efficiency of xfs and ext3

dietmar — Tue, 12 May 2009 17:38:06 +0000

In a test-setup I put 561GByte of data onto a 1 TByte harddisk. The first disk is formated with ext3, the other with xfs.
Here are the results:
df -h /dev/sdc1 932G 561G 372G 61% /media/disk1_1T /dev/sdd1 917G 561G 311G 65% /media/disk2_1T mount /dev/sdc1 on /media/disk1_1T type xfs (rw) /dev/sdd1 on /media/disk2_1T type ext4 (rw)

Ok, by default ext reserves 5% for root-only usage, after removing that reservation ext4 ist still behind xfs:
tune2fs -m0 /dev/sdd1 Setting reserved blocks percentage to 0% (0 blocks)

df /dev/sdc1 932G 561G 372G 61% /media/hd51_1T /dev/sdd1 917G 561G 357G 62% /media/hd53_1T

Conclusion: ext3 reserves 15GByte more administrative space.
Of course, it’s not all about efficiency.

Asus EEE Box B202 & Linux

dietmar — Sun, 14 Dec 2008 20:46:43 +0000

You may call it a PC, you may call it a low-cost Mac-Mini, Microsoft calls it an ULCPC – an ultra low cost PC, I call it an ideal home server. If your Linksys NSLU2 is great but lacks RAM and performance but you do not like the noise and power consumption of a standard PC, then read on.

The B202 does not support X64 (64bit mode), but as the hardware design limits memory to max 2GB, the no point in running a 64bit-OS.
Debian (lenny) boots without any problems, just WLAN is not recoginised.
This is what /proc/cpuinfo says:
cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 28 model name : Intel(R) Atom(TM) CPU N270 @ 1.60GHz stepping : 2 cpu MHz : 1608.032 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni monitor ds_cpl est tm2 ssse3 xtpr lahf_lm bogomips : 3252.73 clflush size : 64 power management:

processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 28 model name : Intel(R) Atom(TM) CPU N270 @ 1.60GHz stepping : 2 cpu MHz : 1608.032 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 1 apicid : 1 initial apicid : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni monitor ds_cpl est tm2 ssse3 xtpr lahf_lm bogomips : 3215.95 clflush size : 64 power management:
And dmesg says the CPU is fast enougth for SAMBA & Co:
[ 0.252015] Total of 2 processors activated (6468.68 BogoMIPS).

lspci shows that WLAN comes from Ralink (2790)
lspci -v 00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03) Subsystem: Intel Corporation Mobile 945GME Express Memory Controller Hub Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information Kernel driver in use: agpgart-intel Kernel modules: intel-agp


00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])

        Subsystem: ASUSTeK Computer Inc. Device 1252

        Flags: bus master, fast devsel, latency 0, IRQ 5

        Memory at feb80000 (32-bit, non-prefetchable) [size=512K]

        I/O ports at ec80 [size=8]

        Memory at d0000000 (32-bit, prefetchable) [size=256M]

        Memory at feb40000 (32-bit, non-prefetchable) [size=256K]

        Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-

        Capabilities: [d0] Power Management version 2
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)

        Subsystem: ASUSTeK Computer Inc. Device 1252

        Flags: bus master, fast devsel, latency 0

        Memory at fea80000 (32-bit, non-prefetchable) [size=512K]

        Capabilities: [d0] Power Management version 2
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)

        Subsystem: ASUSTeK Computer Inc. Device 8331

        Flags: bus master, fast devsel, latency 0, IRQ 16

        Memory at feb38000 (64-bit, non-prefetchable) [size=16K]

        Capabilities: [50] Power Management version 2

        Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-

        Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00

        Kernel driver in use: HDA Intel

        Kernel modules: snd-hda-intel
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode])

        Flags: bus master, fast devsel, latency 0

        Bus: primary=00, secondary=04, subordinate=04, sec-latency=0

        I/O behind bridge: 0000d000-0000dfff

        Memory behind bridge: fe800000-fe8fffff

        Prefetchable memory behind bridge: 00000000bfe00000-00000000bfefffff

        Capabilities: [40] Express Root Port (Slot+), MSI 00

        Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+

        Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 1347

        Capabilities: [a0] Power Management version 2

        Kernel driver in use: pcieport-driver

        Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) (prog-if 00 [Normal decode])

        Flags: bus master, fast devsel, latency 0

        Bus: primary=00, secondary=03, subordinate=03, sec-latency=0

        Memory behind bridge: fe700000-fe7fffff

        Capabilities: [40] Express Root Port (Slot+), MSI 00

        Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+

        Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 1347

        Capabilities: [a0] Power Management version 2

        Kernel driver in use: pcieport-driver

        Kernel modules: shpchp
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) (prog-if 00 [Normal decode])

        Flags: bus master, fast devsel, latency 0

        Bus: primary=00, secondary=01, subordinate=02, sec-latency=0

        I/O behind bridge: 0000c000-0000cfff

        Memory behind bridge: fa700000-fe6fffff

        Prefetchable memory behind bridge: 00000000bbe00000-00000000bfdfffff

        Capabilities: [40] Express Root Port (Slot+), MSI 00

        Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+

        Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 1347

        Capabilities: [a0] Power Management version 2

        Kernel driver in use: pcieport-driver

        Kernel modules: shpchp
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) (prog-if 00 [UHCI])

        Subsystem: ASUSTeK Computer Inc. Device 1347

        Flags: bus master, medium devsel, latency 0, IRQ 23

        I/O ports at e480 [size=32]

        Kernel driver in use: uhci_hcd

        Kernel modules: uhci-hcd
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) (prog-if 00 [UHCI])

        Subsystem: ASUSTeK Computer Inc. Device 1347

        Flags: bus master, medium devsel, latency 0, IRQ 19

        I/O ports at e800 [size=32]

        Kernel driver in use: uhci_hcd

        Kernel modules: uhci-hcd
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) (prog-if 00 [UHCI])

        Subsystem: ASUSTeK Computer Inc. Device 1347

        Flags: bus master, medium devsel, latency 0, IRQ 18

        I/O ports at e880 [size=32]

        Kernel driver in use: uhci_hcd

        Kernel modules: uhci-hcd
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])

        Subsystem: ASUSTeK Computer Inc. Device 1347

        Flags: bus master, medium devsel, latency 0, IRQ 16

        I/O ports at ec00 [size=32]

        Kernel driver in use: uhci_hcd

        Kernel modules: uhci-hcd
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])

        Subsystem: ASUSTeK Computer Inc. Device 1347

        Flags: bus master, medium devsel, latency 0, IRQ 23

        Memory at feb3fc00 (32-bit, non-prefetchable) [size=1K]

        Capabilities: [50] Power Management version 2

        Capabilities: [58] Debug port: BAR=1 offset=00a0

        Kernel driver in use: ehci_hcd

        Kernel modules: ehci-hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) (prog-if 01 [Subtractive decode])

        Flags: bus master, fast devsel, latency 0

        Bus: primary=00, secondary=05, subordinate=05, sec-latency=32

        Capabilities: [50] Subsystem: ASUSTeK Computer Inc. Device 1347
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)

        Subsystem: ASUSTeK Computer Inc. Device 1347

        Flags: bus master, medium devsel, latency 0

        Capabilities: [e0] Vendor Specific Information

        Kernel modules: intel-rng, iTCO_wdt
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02) (prog-if 80 [Master])

        Subsystem: ASUSTeK Computer Inc. Device 1347

        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 19

        I/O ports at 01f0 [size=8]

        I/O ports at 03f4 [size=1]

        I/O ports at 0170 [size=8]

        I/O ports at 0374 [size=1]

        I/O ports at ffa0 [size=16]

        Capabilities: [70] Power Management version 2

        Kernel driver in use: ata_piix

        Kernel modules: ata_piix
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)

        Subsystem: ASUSTeK Computer Inc. Device 1347

        Flags: medium devsel, IRQ 19

        I/O ports at 0400 [size=32]

        Kernel driver in use: i801_smbus

        Kernel modules: i2c-i801
03:00.0 Network controller: RaLink Device 0781

        Subsystem: RaLink Device 2790

        Flags: bus master, fast devsel, latency 0, IRQ 17

        Memory at fe7f0000 (32-bit, non-prefetchable) [size=64K]

        Capabilities: [40] Power Management version 3

        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/5 Enable-

        Capabilities: [70] Express Endpoint, MSI 00

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Subsystem: ASUSTeK Computer Inc. Device 8168 Flags: bus master, fast devsel, latency 0, IRQ 220 I/O ports at dc00 [size=256] Memory at fe8ff000 (64-bit, non-prefetchable) [size=4K] Memory at bfef0000 (64-bit, prefetchable) [size=64K] Expansion ROM at fe8c0000 [disabled] [size=128K] Capabilities: [40] Power Management version 3 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Mask- TabSize=2 Capabilities: [d0] Vital Product Data Kernel driver in use: r8169 Kernel modules: r8169

Dual home with Red Hat (Centos)

dietmar — Fri, 21 Nov 2008 20:15:25 +0000

Most people have a number of computers and need at NAT device to connect them to the Internet, but in my case I had to solve the opposite problem – I had two internet connections, but just a single computer. With other words: I wanted the computer to be reachable from two different public addresses within two different subnets.

This is the solution:
/etc/iproute2/rt_tables
# # reserved values # 255 local 254 main 253 default 0 unspec # # local # #1 inr.ruhep # Provider DF 1 DF # Provider NX 2 NX 3 IN

Then I had to add some files in /etc/sysconfig/network-scripts
In my setup eth2 and eth2:0 are used for internet access:

ifcfg-eth2
DEVICE=eth2 ONBOOT=yes BOOTPROTO=none HWADDR=00:0c:29:3d:xx:xx IPADDR=81.162.157.165 NETMASK=81.162.157.0 # no default gateway TYPE=Ethernet

ifcfg-eth2:0
DEVICE=eth2:0 ONBOOT=yes BOOTPROTO=none HWADDR=00:0c:29:3d:xx:xx IPADDR=81.162.149.189 NETMASK=255.255.255.240 GATEWAY=81.162.149.177 TYPE=Ethernet
route-eth2
default via 81.162.157.1 table DF

route-eth2:0
default via 81.162.149.177 table NX

rule-eth2
from 81.162.157.165 lookup DF

rule-eth2:0
from 81.162.149.189 lookup NX

That’s it. Of course you have to replace the addresses 81.162.149.189/28 and 81.162.157.165/24 with yours. I used dummy addresses in the examples above. Good luck.

And do not forget to backup before:
cd /source/dir tar -cf - . | ( cd /destination/dir ; tar -xpvf - )

Option Icon 72 under Linux

dietmar — Sat, 08 Dec 2007 23:03:27 +0000

The Drei “Internet to go” mobile broadband prepaid-package comes with an Option Icon72 USB modem. The original driver supports MS Windows, but of course, running it under Linux is much more interesting.

The Option Icon72 (GTM378) is an UMTS-modem with an USB interface. It is very similar to the popular Huawei E220 modem. The difficult part is to switch this modem from mass-storage mode (Windows driver) to the USB-serial mode. There is a tool for the old Option 3,6 MBit-box called “icon_switch” written by Josua Dietze. Unfortunately the newer Icon72 uses different initialization commands. A newer and more flexible – tool “USB_modeswitch” written by the same author includes a configuration file for the Icon72 but that configuration did not work with my Icon72 (firmware version 2.2.0Hd, Date: Apr 13 2007, Time: 12:09:19).

By sniffing the USB communication under Windows using “SniffUSB” I found a number of commands sent to the device. Sending the same sequence allowed me use the device under Linux. The result of my work was a modified version of icon_switch, I named it icon_switch72 which supports switching the Option Icon72 into modem-mode.

Download: icon_switch72.c (static binary: icon_switch72static)

For the rest (how to compile and how to configure ppp) I basically refer to the page of Alrecht Gebhard, but:

use icon_switch72 instead of the original source file named icon_switch
modprobe usbserial vendor=0×0af0 product=0×6901
the modem requires a specific init sequence (again, result of sniffing – the original sequence was a bit longer)
to connect to Drei use the APN “drei.at“

The whole solution is by far not as mature as the original Windows driver, in the original setup, a number of parameters are checked before the connection is set up, and also during the connection a second (and third?) serial port are used to control the quality and/or to send and receive SMS (under Linux this would require a different concept for the ppp daemon).

Renaming DigiCam Photos

dietmar — Sun, 21 Oct 2007 12:52:22 +0000

Exif infos can be used to rename photosÂ For example, including the photos date and time into the filename helps to keep photos organized.

I use Irfanview to rename the files. My standard format is _-.jpg.

The Canon Powershot G2 and G6 cameras use the E306 (DateTime according to the Exif-specification) variable.

Note: “Replace text (2)” replaces space (not visible) with underline.
The Olympus uD500 cam does not support this variable, but in this case the same info can be found in E36867 (DateTimeOriginal).

If also this variable is missing (or there is no EXIF info at all), the date of the file ($T in Irfanview) can be used instead, but the output format is different.

Howto receive DVB-H in Vienna

dietmar — Mon, 02 Apr 2007 19:51:13 +0000

At the time of writing there was an ongoing DVB-H trial in Vienna on UHF channel 36 (center frequency 594 MHz).

DVB-H is just a variant of DVB-T, so my idea was to use a DVB-T USB stick to receive DVB-H on my Linux-PC.

(1)
The first thing to do is get a working DVB-T configuration. This is rather straight forward as long as a device driver for Linux available. The biggest problem is get a working firmware. In my case I needed dvb-usb-wt220u-zl0353-01.fw for a Wideview stick (bought as “dnt Eurostick”).

(2)

Tune to the correct frequency. This is channel 36 (equivalent to a center frequency of 594 MHz). You can find a frequency table at
http://www.zlabinger.at/tech/dvb/dvbchannels.html

dvbtune -f 594000
Using DVB card “WideView USB DVB-T”
tuning DVB-T (in United Kingdom) to 594000000 Hz
polling….
Getting frontend event
FE_STATUS:
polling….
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC
Bit error rate: 0
Signal strength: 13878
SNR: 58082
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC

(3)

Next is to scan for interesting PIDs:
# scan -c
using ‘/dev/dvb/adapter0/frontend0′ and ‘/dev/dvb/adapter0/demux0′
0×0000 0×2bbb: pmt_pid 0×00c8 OpenMux — Int Table (running)
0×0000 0×2b8e: pmt_pid 0×00b4 OpenMux IP Gateway — ORF1 (running)
0×0000 0×2b8f: pmt_pid 0×00b5 OpenMux IP Gateway — ORF2 (running)
0×0000 0×2b90: pmt_pid 0×00b6 OpenMux IP Gateway — ATV (running)
0×0000 0×2b91: pmt_pid 0×00b7 OpenMux IP Gateway — MTV-Mobilkom1 (running)
0×0000 0×2b95: pmt_pid 0×00bd OpenMux IP Gateway — OE3 (running)
0×0000 0×2b96: pmt_pid 0×00bf OpenMux IP Gateway — OE2W (running)
0×0000 0×2b93: pmt_pid 0×00b9 OpenMux IP Gateway — H3G1 (running)
0×0000 0×2b94: pmt_pid 0×00ba OpenMux IP Gateway — H3G2 (running)
0×0000 0×2bbc: pmt_pid 0×00c4 OpenMux IP Gateway — ESG ORS (running)
0×0000 0×2b97: pmt_pid 0×00c0 OpenMux IP Gateway — FM4 (running)
0×0000 0×2ba2: pmt_pid 0×00b8 OpenMux IP Gateway — ORF Mobil (running)
dumping lists (12 services)
Int Table (0×2bbb) 80:
ORF1 (0×2b8e) 0c:
ORF2 (0×2b8f) 0c:
ATV (0×2b90) 0c:
MTV-Mobilkom1 (0×2b91) 0c:
OE3 (0×2b95) 0c:
OE2W (0×2b96) 0c:
H3G1 (0×2b93) 0c:
H3G2 (0×2b94) 0c:
ESG ORS (0×2bbc) 0c:
FM4 (0×2b97) 0c:
ORF Mobil (0×2ba2) 0c:
Done.
#

(4)

The same can be achieved with “dvbsnoop”:

dvbsnoop -s pidscan
dvbsnoop V1.4.00 — http://dvbsnoop.sourceforge.net/

———————————————————
Transponder PID-Scan…
———————————————————
PID found: 0 (0×0000) [SECTION: Program Association Table (PAT)]
PID found: 16 (0×0010) [SECTION: Network Information Table (NIT) - actual network]
PID found: 17 (0×0011) [SECTION: Service Description Table (SDT) - actual transport stream]
PID found: 20 (0×0014) [SECTION: Time Date Table (TDT)]
PID found: 21 (0×0015) [SECTION: ITU-T Rec. H.222.0|ISO/IEC13818 reserved]
PID found: 181 (0×00b5) [SECTION: Program Map Table (PMT)]
PID found: 182 (0×00b6) [SECTION: Program Map Table (PMT)]
PID found: 183 (0×00b7) [SECTION: Program Map Table (PMT)]
PID found: 184 (0×00b8) [SECTION: Program Map Table (PMT)]
PID found: 185 (0×00b9) [SECTION: Program Map Table (PMT)]
PID found: 186 (0×00ba) [SECTION: Program Map Table (PMT)]
PID found: 196 (0×00c4) [SECTION: Program Map Table (PMT)]
PID found: 1200 (0×04b0) [SECTION: IP/MAC Notification Table (INT) [EN 301 192]]
PID found: 8191 (0×1fff)

(5)
By scanning an arbitrary service the Elementary PID (the one the actual IP traffic is on) can be found:

– dvbsnoop -spiderpid 183
dvbsnoop V1.4.00 — http://dvbsnoop.sourceforge.net/

————————————————————
SECT-Packet: 00000001 PID: 183 (0×00b7), Length: 28 (0×001c)
Time received: Fri 2007-03-30 00:14:18.451
————————————————————
0000: 02 b0 19 2b 91 c1 00 00 ff ff f0 00 90 e4 74 f0 …+……….t.
0010: 07 52 01 01 66 02 00 05 69 53 80 20 .R..f…iS.

PID: 183 (0×00b7)
Guess table from table id…
PMT-decoding….
Table_ID: 2 (0×02) [= Program Map Table (PMT)]
section_syntax_indicator: 1 (0×01)
(fixed ‘0′): 0 (0×00)
reserved_1: 3 (0×03)
Section_length: 25 (0×0019)
Program_number: 11153 (0×2b91)
reserved_2: 3 (0×03)
Version_number: 0 (0×00)
current_next_indicator: 1 (0×01) [= valid now]
Section_number: 0 (0×00)
Last_Section_number: 0 (0×00)
reserved_3: 7 (0×07)
PCR PID: 8191 (0×1fff)
reserved_4: 15 (0×0f)
Program_info_length: 0 (0×0000)

Stream_type loop:

Stream_type: 144 (0×90) [= User private]
reserved_1: 7 (0×07)
Elementary_PID: 1140 (0×0474)
reserved_2: 15 (0×0f)
ES_info_length: 7 (0×0007)

DVB-DescriptorTag: 82 (0×52) [= stream_identifier_descriptor]
Descriptor_length: 1 (0×01)
component_tag: 1 (0×01)

DVB-DescriptorTag: 102 (0×66) [= data_broadcast_id_descriptor]
Descriptor_length: 2 (0×02)
Data_broadcast_ID: 5 (0×0005) [= Multi protocol encapsulation]

CRC: 1767079968 (0×69538020)
==========================================================

(6)

Now let us perform a test to see if that PID is actually present:

dvbsnoop -spiderpid 1140
dvbsnoop V1.4.00 — http://dvbsnoop.sourceforge.net/

————————————————————
SECT-Packet: 00000001 PID: 1140 (0×0474), Length: 996 (0×03e4)
Time received: Fri 2007-03-30 00:15:34.630
————————————————————
0000: 3e b3 e1 0d e1 c1 00 00 0c 80 00 00 45 00 03 d4 >………..E…
0010: 68 70 00 00 07 11 d3 96 ac 16 05 0d e1 e1 e1 0d hp…………..
0020: c0 12 04 4c 03 c0 dd f5 80 e0 5a 1e fa b3 d3 8d …L……Z…..
(…) 03d0: 8e 91 da df 06 f9 42 54 2c 90 bf 5e 2a 7f f7 c0 ……BT,..^*…
03e0: 9c ee 8a fd ….

PID: 1140 (0×0474)
Guess table from table id…
DSM-CC DATAGRAM-decoding….
Table_ID: 62 (0×3e) [= DSM-CC - private data section // DVB datagram]
section_syntax_indicator: 1 (0×01)
private_indicator: 0 (0×00)
reserved_1: 3 (0×03)
Section_length: 993 (0×03e1)
MACaddrbyte/DevicdID 6: 13 (0×0d)
MACaddrbyte/DeviceID 5: 225 (0xe1)
reserved_2: 3 (0×03)
payload_scrambling_control: 0 (0×00) [= unscrambled]
address_scrambling_control: 0 (0×00) [= unscrambled]
LLC_SNAP_flag: 0 (0×00)
current_next_indicator: 1 (0×01) [= valid now]
Section_number: 0 (0×00)
Last_Section_number: 0 (0×00)
MACaddrbyte/DeviceID 4: 12 (0×0c)
MACaddrbyte/DeviceID 3: 128 (0×80)
MACaddrbyte/DeviceID 2: 0 (0×00)
MACaddrbyte/DeviceID 1: 0 (0×00) => MAC-Address/DeviceID: 00:00:80:0c:e1:0d
IP_datagram_bytes
0000: 45 00 03 d4 68 70 00 00 07 11 d3 96 ac 16 05 0d E…hp……….
0010: e1 e1 e1 0d c0 12 04 4c 03 c0 dd f5 80 e0 5a 1e …….L……Z.
(…)

(7)

Before we can create a network interface using this PID (to listen to FM4) we have get a description of the service, the so called SDP-file. This file can be found on PID 1200 [I forgot how I found this PID, possibly by guessing..]

dvbsnoop -b 1201 > pid1201.txt

In this file some XML structure can be found, somewhere in the middle there is the SDP for FM4:

v=0
o=- 1284305069 1139040522 IN IP4 192.168.250.2
s=realtimeaudio
c=IN IP4 226.226.0.2
a=control:*
a=range:npt=0.0-
a=ISMA-compliance:1,1.0,1
a=mpeg4-iod: “data:application/mpeg4-iod;base64,AoEHAA///w///wN+AAFAYGRhdGE6YXBwbGljYXRpb24vbXBlZzQtb2QtYXU7YmFzZTY0LEFTb0JLQUtmQXlRRDZBVUVEVUFWQUFZQUFBZ1RNQUFCdFlBR0VBQkVBQUNzUkFBQXJFUWdJQUFBQUFNPQQNAgUAAQAAAAAAAAAAAAYJAQAAAAAAAAAA”
m=audio 9030 RTP/AVP 101
b=AS:112
a=rtpmap:101 mpeg4-generic/44100/2
a=control:trackID=1000
a=fmtp:101 streamtype=5; profile-level-id=15; bitrate=112000; config=1210; sizelength=13; indexlength=3; indexdeltalength=3; profile=1; mode=AAC-hbr
a=mpeg4-esid:1000

(8)

So now it is time to create a network interface using this PID:

dvbnet -p 1175

(9)

Next is to configure the network interface to promiscous mode (the destionation MAC should be ff:ff:.. but is “abused” by the DVB-H standard to carry time-slicing information.
ifconfig dvb0_0 10.11.12.13 promisc up

The IP address is without any meaning (to me), but it is mandatory for the next command to succeed.

(10)

route add -net 224.0.0.0/4 dev dvb0_0

This sets the default route for multicast traffic.
(11)

vlc -vvv myservice.sdp

Not you should be able to listen. If not – maybe you need a different kernel. I succeded with Fedora core 6 and failed with Knoppix.

(12)

The default buffer value of 300ms in vlc is too short for the time slicing used in DVB-H. A value of 3000ms or more (10s) is suggested.

With Input/Codecs -> Access modules -> UDP/RTP -> Caching value set to 3000 ms, the errors you will notice otherwise will be gone.
(13)

Good luck!

Update March 2008: In February 2008 the DVB-H trial ended. Soon after new 10-year-licenses were issued to a consortium around Media Broadcast. It is intended to start commercial operation in June (in time for the euro-2008 soccer-championships). But the new programming will probably be encrypted.

Nokia E61 and VoIP with Asterisk

dietmar — Thu, 08 Mar 2007 23:28:32 +0000

You connecting flight is late. Ok, then let us kill time. First thing you need is a Nokia E61. The list of features sounds great, but when it gets to configure VoIP things become wearied.

First thing to do is to type *#0000#. If the result is 3 dot somethin you’re well off, else you can only hope not to get 1.0610.04.04 (19-04-06). This is version 1 and the voip client there is more than broken.

So let me start with the bugs first:

If there is no @ in the username, the phone will simply do nothing, no attempt to register at all. It just complains that it can’t get connected. If you need a realm anyway – or your provider ignores the realm – you’re well off, else: bad luck
The credentials have to be repeated in the “proxy” and “registry” section. But there the username is converted to lower case when being used for authentication – causing authentication to fail. So if your provider uses uppercase letters in the username – bad luck again.
There is no support for address translation, both ends of the voip call either need public IPs – or both need private IPs (for example when you connect to a local Asterisk box). If not – you guessed it: no luck again.

The best thing to do would be to upgrade the phone. But there is a small problem: Your provider needs to authorize the new version first, so if you have a SIM-locked phone, chances are high that the outdated firmware you have is still the latest version available. Some people say that there is a backdoor to upgrade anyway, I didn’t try.
Conclusion: You need a local Asterisk server and the username should only contain lower-case letters.

This is how to configure it:

Make sure WLAN is working (use the web-browser to surf some pages)
Install Asterisk and verify if it works (use Xlite for this)
Configure a user containing only LOWERCASE letters
Profile name: blabla
Service profile: IETF (means SIP)
Default acces point: your neighbour’s WLAN
Public username: sip:username@192.168.14.1 Don’t forget the realm. You really need it with version 1
Use Compression: No
Registration: “Always on” if you have two chargers – one at home and another one at your office …
Use security: No (Don’t know what this is, seems to be a Nokia-thing)

Proxy Server:

Proxy server address: sip:192.168.14.1 (do not use a domain name here, some people say that the DNS-client is broken too, it might be due to lack of support of SRV-records)
Realm: domain.tld
User name: username
Password: password
Allow loose routing: Yes (No idea what this would be good for)
Transport type: UDP (Asterisk does not support TCP)
Port: 5060 (default value)

Registrar server: same settings as for the proxy

In Asterisk the default settings should be fine:

[username]

type=friend

username=username (lower case only)
secret=password

qualify=yes

You missed your flight? Don’t blame me, blame N****

My photo-blogs

dietmar — Sat, 13 Jan 2007 22:04:42 +0000

You can find photos taken with my Nokia N70 camera-phone at http://www.flickr.com/photos/zlabinger/ and photos taken with my Sony-Ericsson K800 at http://zlabinger.blogspot.com/ (old photos) and http://zlabinger2.blogspot.com (newer photos).
Dietmar