World In The Net

[zz]Android装置的开发挑战：软硬体如何巧妙整合

2011-01-27T15:00:00.000-08:00

http://laoyaoba.com/ss6/?action-viewnews-itemid-166915

来源：集微网发布者：集微网
热度1票【共0条评论】【我要评论】时间：2011年1月26日 16:18
随着科技的快速演进，现代人对行动通讯、无线上网与多媒体娱乐的需求更甚以往，所谓的智慧型手机（Smart Phone）便成了炙手可热的个人消费电子产品之一，从Apple不断推出iPhone企图颠覆消费者对手机的想象、RIM推出主打商务功能的黑莓机、Google的Android系统让众家手机厂商争食大饼，到微软屡败屡战的从WinMo一路开发到WP7，智慧型手机的这块战场可说是打的如火如荼。然而在这些众家竞争者中，Android可说是目前行情看俏的一套作业系统，以国际市调研究机构Gartner最新出炉2010年第三季的调查为例，采用Android作业系统的智慧型手机在过去一年以来成长幅度最高，光是市占率便是前一年同期的七倍之多，销售量更是达到14倍的成长，同时也一举从市占率排名的第六名窜升到第二名。而在今年一月份甫落幕的国际消费性电子展（CES），也处处可见各式各样采用Android作业系统的产品。
Android在过去一直扮演后起之秀的角色，切入智慧型手机的速度似乎慢了苹果的iOS一步，但与Apple相同的是，它也成功的将其应用从手机移植到了平板电脑（Tablet PC）上。Android开放原始码（Open Source）的特性，能轻易地提高厂商对自家产品的接受度，更不用提背后Google的强力撑腰能带来多大的经济效益。目前可见包括手机厂商HTC、Motorola、SAMSUNG，以及电脑大厂HP与Dell等皆投向Android的怀抱，Android被广泛应用可说是势在必行。

尽管Android系统的普及看似指日可待，但在实际的产品应用上，也有其可能产生的问题风险。Android作为一个开放式的作业系统，是Google提供厂商的作业系统参考架构（reference design），厂商能有充足的发挥空间，以Android为基础向上开发设计自家产品，但也因为这样的开放性与自由性，让厂商在软硬体结合的这个环节必须下更大的功夫，像是如何挑选合适的硬体包括基频处理器、通讯晶片、触控感应晶片、天线与记忆体模组等，以及如何调整出最适当的软体设定等，更重要的是如何将软硬体整合，开发出差异化的产品。这中间所有的细节都会对产品最终样貌产生莫大的影响，像是其功能的完整度、使用介面的设计、效能表现（例如触控滑动画面、开启程式所需时间）、品质可靠度、甚至是后续的韧体升级动作等等。在此百佳泰便试图以专业中立的测试实验室角度，来点出厂商应用Android于手机、平板电脑或其他装置时应注意的开发重点，以希冀作为一个有效的参考资讯。

解构Android基本技术架构

首先我们先来看到Android的基本技术架构，Android是以Linux为核心，并采用软体堆迭（software stack）的架构延伸发展的一套软体平台与作业系统。根据下图可以看出，其基本架构分为五层：
Linux核心（Linux Kernel）：以Linux开发提供最底层的核心系统服务，包括安全性 (Security)、、记忆体管理(Memory Management)、进程管理(Process Management)、网路堆迭(Network Stack)与驱动程式模型（Driver Model）。
Android执行环境（Android Runtime）：透过Core Libraries(核心函式库)以及暂存器型态的Dalvik Virtual Machine(Dalvik虚拟机器)来执行程式。
系统函式库（Library）：使用C/C++函式库的系统元件以供呼叫使用，开发者可透过上层的应用程式框架来运用这些功能，这也是主要Android装置的效能关键。
应用程式框架（Application Framework）：被设计来简化元件的再运用，开发者能完整存取使用与核心应用程式（Core Application）相同的API，应用程式可以发布功能并为其它应用程式所使用（需受限于其安全性限制），开发者也可运用同样的机制来新增与置换元件。
应用程式（Application）：所有Android应用程式皆是以Java程式语言编写，原始就会包含像是Email、简讯、日历、地图、浏览器、联络人等其它应用程式，让使用者一开始就拥有这些基本功能，开发者也可在此客制其使用介面。

厂商越想要设计出与原始设定不同且增强效能的产品，便越需要对这五层架构进行修改。譬如像是多工处理能力（multi-tasking），便可能需要修改包括Linux核心与应用程式框架的设计；而应用程式的开发者更可能需要针对应用程式与框架进行调整。由此可见，对Android装置而言，任何一个功能的置入或是对硬体设定的细微更动，都需要对Android系统进行从下到上的调整以达到最优化的效能，而这正是最为困难与需要验证的一环。

Android装置软硬体整合的五大技术环节

如前所述，对众家开发厂商而言最大的挑战其实在于，如何将自己理想的产品诉求，与Android系统巧妙结合成一个功能完整并使用流畅顺手的产品，这其中牵涉了不同技术间的整合与运用。在此我们便根据其多年的测试与研究经验，归纳出五大Android相关装置在技术整合上的重要环节：

一、Linux驱动程式的导入

由于Android是根源于Linux所延伸出来的作业系统，因此各种关键功能的驱动程式也必须要能顺利的写入其中，举凡像是字元装置、记忆体的空间配置、中断处理、网路通讯、萤幕显示或是连接介面像是USB与PCI的驱动程式，这些可能是自行撰写、或是来自不同元件厂商的驱动程式，都必须要能被导入到Android系统，并维持良好稳定的效能表现。

二、系统单晶片的优化处理

对厂商而言，开发一款Android装置，不仅仅只是将所有零组件组合成为一个产品那么容易，最大的学问便在于将系统单晶片（System-on-a-chip，SoC）、各种新技术和Android系统进行整合，SoC涉及像是Dalvik Virtual Machine、OpenGL、V8、Webkit Engine等上层的演算，与Android间的结合便必须透过不断的尝试与验证，才能研发出既符合成本效益、又有良好效能的优化产品。目前市面上有些SoC厂商已针对Android系统的特性，提供整合过的SoC平台，将蓝牙、相机或上网等常用功能模组预先写入，减少终端成品厂商费力整合开发的时间，但对厂商而言，这样的预先整合是否适合自身产品，以及是否需要再作更细致的修改，则又是更困难的课题。

三、新技术的移植

随着技术的快速发展，更多新兴的技术规格也逐渐应用在手机等手持装置上，以手机为例，已经从过去以拨打电话为主要功能，转变为拥有各种多样化用途的产品。像是触控技术让消费者可以透过手指的滑动传送指令甚至是具备多点触控的支援、Wi-Fi模组提供随时无线上网的可能、通用图形处理器（General-purpose computing on graphics processing units，GPGPU）则能以并行方式透过图形处理器来执行通用计算任务、Android 2.3版所支持的NFC近场通讯技术，以及更高阶的相机模组等等，背后都有各自的驱动程式与软体技术，也必须要与Android系统相结合使用。

四、效能表现的稳定

尽管上述这些技术不断推陈出新，但也都不能因此而牺牲装置原本的效能表现，让处理速度因此变慢或造成使用上不顺畅的状况。除了采用更好的硬体设备外（例如现今处理器的时脉已迈向1GHz），更需要作业系统的支持，像是如何在多工运作的状况下维持程式执行速度以及系统满载的处理等等，都必须要透过软体面的奥援。也就是说，一台Android装置除了要能将各种功能与技术收纳起来、将软硬体整合外，更必须同时注重它在效能上能否维持应有的水准，以提供使用者在操作上流畅易上手的感受。

五、低电耗设计

Android的设计概念主要是应用于可携式装置上，目前市面上可见的像是平板电脑与智慧型手机等。对这类产品而言，电池续航力的好坏可说是影响消费者使用感受的关键之一，试想，若是一台智慧型手机的待机时间过短，而使用者在外时又无法随时充电使用，不能即时的连网查询资料或执行其他手机功能，这样的产品便失去了它作为可携式行动装置应有的便利性。追根究底，良好的待机时间除了需仰赖高容量的电池以提供充足电力之外，另一个重点就是装置本身在被使用执行时能否作到低电耗设计。Android装置让使用者能透过各种多样化的应用程式，来达到各种不同的使用目的，举凡像是单纯上网、观看新闻、邮件推播或是游戏等等，各种不同功能的程式都能透过自由下载使用，也由于其多工处理与让程式背景执行的能力，更让降低耗电量成为开发者不可轻忽的一项课题。

持续验证修正找出最佳Android整合方案

正如前面我们不断提到的，对Android装置而言，最困难的开发挑战便在于如何完美地”整合”软体与硬体，以开发出一项功能完整又同时注重使用者感受的产品。从对Android本身程式码的修改、相关硬体的选择，到驱动程式的结合运用以及能否维持稳定的效能表现等，在在都必须要透过仔细的研究与不断的尝试，才能找出问题的根源并解决、更进而找出最合适的整合方案。

附图我们归纳出一些在Android装置上经常出现的问题与其可能肇因，而这些也都是开发厂商必须重视却可能忽略的一环。像是Android原始码中对音源的重新取样（Re-sampling）设计，就会导致装置在读取48K音源时重新取样成44K，而造成谐波失真的现象影响音质，这便是厂商不会注意到而未去修改的问题；另外像是天线位置的设计，也可能直接的影响到收讯能力的好坏；而不良的电源管理设计，也极有可能影响到装置在持续使用状态中的耗电情形。百佳泰在此仅以专业测试验证实验室的角度，希冀以宏观的方式，针对Android装置的开发设计提供可用的参考，近期内我们也将会提供实际的相关测试数据报告，并进一步指陈这些可能的问题风险，以期让更多厂商与消费者都能注意到品质验证的重要性，是从产品设计的根源就要开始层层把关。

（本文由测试服务暨谘询顾问公司百佳泰Allion Test Labs, Inc提供）

YBox2 Kit - v1.1

2010-12-07T12:47:00.000-08:00

The YBox2 is a DIY networked set-top box. Connect it to your TV and you can design customized content to be delivered direct from the Internet.

This project is great for people who want a new platform to experiment with. The video and Internet cores are ready to go and easy to work with. We have some example widgets that demonstrate the YBox2's capability, and the whole project is open source so you can start hacking your own. If you've ever been curious about the Parallax Propeller chip, the YBox2 is a perky little platform with tons of accessories.

The kit comes with PCB and all necessary electronic parts, unassembled. Assembly is not difficult, but considering the number of components, it will take a couple hours to complete. Power supply, mint tin, TV, tools and cables not included.

Details:

Built using the new Parallax Propeller chip - 8 cores, 32KB of RAM running at 80MHz!
Works with any NTSC or PAL TV that has composite (RCA) input
Works with any network router that supports DHCP, just plug in an Ethernet cable and you're ready to go
Kit comes with an Internet-enabled bootloader already installed, so you can upload new programs directly from your computer, without a special cable or prop-plug (Propeller chip programmer)
IR receiver for using a TV remote control
Full color status LED
Piezo Buzzer for generating beeps, alarms, and tones
Pushbutton for input
Lots of examples widgets to try out
Fits in an altoids tin!

Theres tons of information at the YBox2 site so go check that out! YBox2 is a collaboration with Robert Quattlebaum and based off work by Uncommon Projects.

[zz]How to Dual Boot Windows 7 and Linux using BCDEdit

2010-03-20T14:47:00.001-07:00

http://www.iceflatline.com/2009/09/how-to-dual-boot-windows-7-and-linux-using-bcdedit/

Windows → How to Dual Boot Windows 7 and Linux using BCDEdit

14 Comments

September 16th, 2009 by iceflatline

This post will describe how to set up a system that can boot into Windows 7 or a Linux distribution. The Window 7 Boot Configuration Data Editor (BCDEdit) will be used to configure Windows 7 to display a menu at boot time that will allow the user to choose between Windows 7 and a Linux distribution of your choice.

To help explain the steps involved, we’ll use an 80 GB hard drive with Windows 7 already installed. We’ll then re-partition the drive using Gnome Partition Editor (GParted) in order to add Ubuntu or Fedora. We’ll then use BCDedit to add a boot menu option for our Linux distribution. All steps involved assume you have a functioning CD drive (or USB drive if you’d prefer) that the system can boot from. The versions for the software used in this post were as follows:

Fedora v11
GParted v0.4.6-1
Ubuntu v9.04
Windows 7 RC Build 7100

Oh… and while I’ve never encountered a situation where GParted destroyed existing disk data, make sure you backup any critical files before you proceed.

So, let’s get started.

Partitioning for Ubuntu

The first thing we’ll want to do is re-partition our 80GB drive. Download a copy of GParted Live and burn it to a CD (or place it on a bootable USB drive). Next, boot the system using the GParted disk. After accepting the default settings for keymap, language, and X-window configuration, you should arrive at the GParted desktop (See Figure 1).

Figure 1

You’ll notice that GParted is reporting ~74 GB of total disk space (1 Gigabyte = 1,073,741,824 Bytes) and that Windows 7 currently occupies all of that space using two primary partitions: one small boot partition at device /dev/hdd1 and the remaining operating system at device /dev/hdd2. Eventually, we will have five partitions in total: the two Windows 7 partitions just mentioned, as well as ones for the Ubuntu operating system and Linux swap. We’ll also create a FAT32 partition for sharing data between Windows 7 and Ubuntu. You’ll need to determine how much disk space you want to allocate to each of these partitions based on your disk size, but for our 80 GB example disk, we’ll use the following partition layout:

Windows 7: ~100MB (Windows 7 bootloader)
Windows 7: ~40 GB
Ubuntu: ~24 GB
Linux-Swap: ~1 GB
FAT32: ~9 GB

Let’s leave the Windows 7 boot partition at /dev/hdd1 alone and reduce the partition at /dev/hdd2 to ~40GB. Highlight /dev/hdd2 by left-clicking on it and then select “Resize/Move.” This will bring up a new window where the new size for the partition can be entered manually, or you can left-click and hold the graphical bar to resize the partition. Make sure the free space is following /dev/hdd2. Now hit “Resize/Move” to complete the resizing (See Figure 2).

Figure 2

Once the size of /dev/hdd2 is reduced, you’ll see that the remaining space is now labeled unallocated. Left-click this space to highlight it and then select “New” to create a new partition. Make this partition a primary partition and the file system ext3. Now, reduce the partition to ~29 GB – you can do this by typing in the value in the New Size field or by moving the slider to the left until you reach the desired size. When complete, select “Add” (See Figure 3).

Figure 3

The disk is limited to four primary partitions, so in the remaining unallocated space we’ll need to create a new extended partition instead of a primary partition. Once the new extended partition is created, left-click to highlight it and create two new logical partitions following the steps above. One should be linux-swap and sized to 1 GB; the other (in the remaining space) will be our FAT32 partition. When complete, you should have a partition layout that resembles Figure 4.

Figure 4

Review the newly created partition layout and make any necessary adjustments. You can back out of any changes you’ve made by selecting “Undo Last Operation” or “Clear All Operations” (under the Edit menu). Now select “Apply All Operations” and GParted will proceed with writing the changes to the disk. After a few minutes you should see the re-partitioned drive (See Figure 5).

Figure 5

You’ll notice that GParted retained the device designations /dev/hdd1 and /dev/hdd2 for Windows 7 but has now assigned the appropriate device designations to each of our newly minted partitions:

/dev/hdd1 – Windows 7 boot (Primary partition)
/dev/hdd2 – Windows 7 (Primary partition)
/dev/hdd3 – ext3 (Primary partition)
/dev/hdd4 – (Extended partition)
/dev/hdd5 – Linux-Swap (Logical partition)
/dev/hdd6 – FAT32 (Logical partition)

Make note of these partition designations because you will need to refer to them when we install Ubuntu. Now, let’s exit out of GParted and reboot the system. If all went well, you will arrive at the Windows 7 logon screen. Along the way, you may see Windows perform a disk check – don’t worry that’s normal. If you log into Windows 7 and access Explorer or Disk Manager you should see your FAT32 partition.

Partitioning for Fedora

The process for creating partitions for an Fedora 11 install is essentially the same as described for Ubuntu. What does differ, however, is the number and type of the partitions we’ll need. The Fedora 11 operating system utilizes the ext4 file system. Unfortunately, Fedora is incapable of placing its bootloader on the ext4 partition. Therefore, we’ll need to create a small primary partition that Fedora 11 can use to install the bootloader. For our 80 GB example disk, we’ll use the following partition layout. Note the addition of a small 100 MB partition that we will eventually format as ext3 and use for the Fedora bootloader:

Windows 7: ~100MB (Windows 7 bootloader)
Windows 7: ~40 GB
Fedora: ~100MB (Fedora bootloader)
Fedora: ~24 GB
Linux-Swap: ~1 GB
FAT32: ~9 GB

Now, using GParted and following similar steps described above for Ubuntu, create the following partitions (See Figure 6):

/dev/hdd1 – Windows 7 boot (Primary partition)
/dev/hdd2 – Windows 7 (Primary partition)
/dev/hdd3 – ext3 (Primary partition)
/dev/hdd4 – (Extended partition)
/dev.hdd5 – ext4 (Logical partition)
/dev/hdd6 – Linux-Swap (Logical partition)
/dev/hdd7 – FAT32 (Logical partition)

Figure 6

Installing Ubuntu

Now it’s time to install Ubuntu on to the partitions we created with Gparted. Download a copy of Ubuntu Desktop and burn it to a CD (or place it on a bootable USB drive). Boot the system using the Ubuntu disk. Double-click the install icon on the desktop to get started. Continue through the installation process until you arrive at “Prepare disk space” and select “Specify partitions manually (advanced)” to advance to the “Prepare partitions” screen (See Figure 7). This is where we’ll instruct Ubuntu which mount points and file systems to use on the partitions we created. You’ll notice that the Ubuntu installer references the partitions using the /dev/sda1, 2, 3…, etc. device labels typically used for SCSI, SATA, and USB drives. These correspond directly to the /dev/hdd1, 2, 3…, etc. device labels used by Gparted (e.g., device /dev/hdd3 = device /dev/sda3).

Figure 7

Left-click to highlight /dev/sda3 and then select “Edit partition.” On the pop-up screen make sure that the ext3 file system is selected and the check box instructing Ubuntu to format the partition is checked. Device /dev/sda3 will serve as the root partition for Ubuntu so we’ll set the mount point to / from the list of choices in the drop down menu. Now select “Okay” to accept the changes (See Figure 8).

Figure 8

Following similar steps, let’s move on to /dev/sda5 and set the mount point to linux-swap. There is no need to format this partition. Finally, device /dev/sda6 will serve as our FAT32 partition to share files between our Windows 7 and Linux systems so make sure the FAT32 file system is selected and set the mount point to /os-share (you can choose and alternative name if desired). There is also no need to format this partition. Do a final review and then select “Forward” to continue to the “Ready to install” screen (See Figure 9).

Figure 9

This next step is critical. We need to tell Ubuntu where to install its bootloader (GRUB). We DO NOT want to install GRUB on /dev/sda, as that would overwrite our disk’s Master Boot Record, nor do we want to install it on /dev/sda1, as that is being used for the Windows 7 boot configuration data. Instead, let’s have Ubuntu install GRUB on the partition that will contain the Ubuntu operating system – in our case /dev/sda3. To do this, left-click on the tab that says “Advanced.” This will bring up a pop-up screen where we can specify the location for the bootloader (See Figure 10).

Figure 10

First, make sure that the check box for installing the bootloader is checked. Next, we need to place GRUB on the same partition Ubuntu will be installed on. GRUB starts counting disk partitions from the beginning of the disk starting with 0 so let’s change (hd0) to (hd0,2). That will tell Ubuntu to install GRUB on the third partition of our disk (/dev/sda3). Now select “Okay” and continue with the Ubuntu installation. When the install completes you’ll be asked to reboot the system. If all went well, you will arrive once again arrive at the Windows 7 logon screen.

Installing Fedora

If you’re installing Fedora you’ll follow similar steps described in the Ubuntu install above.Download a copy of Fedora Desktop and burn it to a CD (or place it on a bootable USB drive). Boot the system using the Fedora disk and double-click on the install icon on the desktop to get started. Continue through the installation process until you arrive at Fedora’s disk partitioner, then select “Create custom layout” from the drop down menu list and select “Next.” (See Figure 11).

Figure 11

Scroll down the list of devices until you find /dev/sda3 (that’s the small primary partition we created using Gparted), left-click to highlight it and select “Edit.” In the pop-up screen chose /boot as the mount point and format the partition as ext3 (See Figure 12). When finished, select “Okay.” Next, highlight and edit /dev/sda5. This partition will contain the Fedora operating system so make sure to choose / for the mount point and format as ext4. Repeat these steps for the /dev/sda6 and /dev/sda7 – these will be used for our swap and FAT32 partitions respectively. Make sure to choose vfat (FAT32) for the /dev/sda7 partition and set the mount point to /os-share (you can choose and alternative name if desired).

Figure 12

When complete, select “Next” and do a final review of these partition changes in the pop-up screen, then select “Format.” Confirm the choices by selecting “Write changes to disk.” At this point you will be presented with some choices for where Fedora should install its bootloader (GRUB). This next step is critical. We DO NOT want to install the GRUB to /dev/sda as that will overwrite our disk’s Master Boot Record. Instead, let’s have Fedora install GRUB on the same partition as the Fedora boot partition – in our case /dev/sda3. To do this, left-click on the tab that says “Change device.” This will bring up a pop-up screen where we can specify location for the boot partition (See Figure 13).

Figure 13

When finished, select “Next” and Fedora will write the changes to disk and complete the install. After you reboot, if all went well, you will arrive at the Windows 7 logon screen.

Configuring for Dual Boot

Now that we have our disk partitioned and Fedora or Ubuntu installed, let’s set up our system to boot Windows 7 or the Linux distribution. This will involve copying the first 512 bytes of our Linux boot partition to Windows 7 and then use that file, and BCDEdit, to configure Windows 7 to display a menu at boot time that will give you a choice between Windows 7 and Linux.

Boot the system again using the Gparted disk and let’s make a mount point for the FAT32 share partition we created. Open up a terminal in Gparted and enter the following:

mkdir /mnt/os-share

Next, let’s mount the correct device to this directory. Recall from the Gparted partitioning steps above that the FAT32 partition is located at device /dev/hdd6 in the case of Ubuntu and device /dev/hdd7 in the case of Fedora. Assuming Ubuntu then for this example, enter the following:

mount /dev/hdd6 /mnt/os-share

Finally, let’s write the first 512 bytes from our Linux boot partition to a file and copy that file to our FAT32 partition. Note that the boot partition in the case of both Ubuntu and Fedora was the same – /dev/sda3:

dd if=/dev/hdd3 of=/mnt/os-share/linux.bin bs=512 count=1

Exit Gparted now and reboot to Windows 7. Open the FAT32 partition and you should see the linux.bin file. Copy that file to the root of the Windows boot (active) partition (e.g., C:\). Next, let’s use BCDEdit to modify Windows 7’s boot configuration data to add a boot menu option for our Linux distribution. Administrative privileges are required to use BCDEdit, so navigate to Start->All Programs->Accessories, Right-click on Command Prompt and select “Run as administrator.” Okay, now let’s start by creating an entry for our Linux distribution. Note here that you are free to choose another entry name if desired:

bcdedit /create /d “Linux” /application BOOTSECTOR

BCDEdit will return an alphanumeric identifier for this entry that I will refer to as {ID} in the remaining steps. You’ll need to replace {ID} by the actual returned identifier. An example of {ID} is {d7294d4e-9837-11de-99ac-f3f3a79e3e93}. Next, let’s specify which partition hosts a copy of the linux.bin file:

bcdedit /set {ID} device partition=c:

The path to our linux.bin file:

bcdedit /set {ID}  path \linux.bin

An entry to the displayed menu at boot time:

bcdedit /displayorder {ID} /addlast

and finally, let’s specify how long the menu choices will be displayed:

bcdedit /timeout 30

That’s it! Now reboot and you will be presented with menu where you can choose to boot to Windows 7 or Linux. When you choose Linux, you’ll be taken to the GRUB menu where you can choose to continue booting your Linux distribution or return to the previous menu.

Windows XP?

If you plan to dual boot using Windows XP then you will still partition and install Ubuntu or Fedora as described above (Note, however, that XP does not use a small primary partition for boot configuration data like Windows 7 does), but you won’t be needing BCDEdit. Instead, you can simply open the boot.ini file located at C:\ and add the following entry:

c:\linux.bin="Linux"

Conclusion

With a minimal amount time, the free and open source disk partitioning tool Gparted, and a little command line foo, you can easily set up a system that can dual boot Windows 7 and your choice of Linux distributions.

References

http://technet.microsoft.com/en-us/library/cc709667%28WS.10%29.aspx

Build OpenWrt howto

2009-07-16T17:30:00.000-07:00

* get code from svn repository
cd ~/openwrt/
svn co svn://svn.openwrt.org/openwrt/branches/8.09/ 8.09/
svn co svn://svn.openwrt.org/openwrt/packages 8.09/feeds/packages
cd 8.09/
./scripts/feeds update -a
* build
make package/symlinks
make menuconfig
make prereq
make world

[zz] USB Storage Howto

2009-07-15T19:31:00.000-07:00

USB storage howto

Contents

Intro

It's useful to extend the storage capacity of your USB enabled Wrt router f. e. making a central file server. This can easily be done with connecting USB storage devices (like a USB stick or a external USB harddisc) to the USB port on your router.

Requirements

Supported router by OpenWrt with USB (f. e. the Asus WL-500G or the Asus WL-500G deluxe)
a recent OpenWrt version installed (at least White Russian RC3)
some kind of a USB storage device (a USB stick or a external USB harddisc) supported by Linux
a USB hub (optional) to add more USB ports (it's probably a good idea to use an active USB hub with it's own PSU)

NOTE: Devices supporting USB v2.0

Installation

TIP: Some routers are USB 1.1 and 2.0 compatible. To use both devices with both versions install the modules for USB 1.1 and 2.0.

Modules for USB 1.1

For USB 1.1, try installing the UHCI drivers first:

ipkg install kmod-usb-uhci
insmod usbcore
insmod uhci

If you see the message:

insmod: init_module: uhci: No such device

then your hardware does not have a UHCI compliant device, so you might as well remove the package:

ipkg remove kmod-usb-uhci

TIP: Most USB chips have UHCI controllers. If you received a "No such device" error, then try installing the kmod-usb-ohci package instead. The BCM4710 and BCM4712 based routers require kmod-usb-ohci:

ipkg install kmod-usb-ohci
insmod usb-ohci

If you see the message:

insmod: init_module: usb-ohci: No such device

then your hardware does not have a OHCI compliant device, so you might as well remove the package:

ipkg remove kmod-usb-ohci

Modules for USB 2.0

This package includes the modules for USB 2.0.

NOTE: USB 2.0 support in White Russian is broken. There are some threads in the forum and some tickets as well if you like to read about what happens. (Im using WR 0.9 on an ASUS WL-500g Premium and USB 2.0 works just fine)

ipkg install kmod-usb2
insmod ehci-hcd

If you see messages like this:

insmod: unresolved symbol usb_calc_bus_time

try loading usbcore and then try ehci-hcd again:

insmod usbcore
insmod ehci-hcd

Note that you may want to have available the utility, lsusb. To enable it in Kamikaze, run "opkg install usbutils".

Modules for storage

To add storage support finally install

ipkg install kmod-usb-storage
insmod scsi_mod
insmod sd_mod
insmod usb-storage

Clean up

TIP: The max_scsi_luns=8 bit is needed for multi-card readers and should be added to the end of the scsi_mod line in the /etc/modules.d/60-usb-storage file.

OpenWrt uses /etc/modules.d directory to load the modules automatically on the next reboot. So reboot the router with

reboot

Now check if OpenWrt sees your USB device (of course inserting it into your Wrt router). If it's correct you should see similar messages as on the dmesg dump below.

dmesg

usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
uhci.c: USB Universal Host Controller Interface driver v1.1
PCI: Enabling device 01:02.0 (0000 -> 0001)
uhci.c: USB UHCI at I/O 0x100, IRQ 2
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Enabling device 01:02.1 (0000 -> 0001)
uhci.c: USB UHCI at I/O 0x120, IRQ 2
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
hub.c: new USB device 01:02.0-2, assigned address 2
usb.c: USB device 2 (vend/prod 0xd7d/0x100) is not claimed by any active driver.
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi0 : SCSI emulation for USB Mass Storage devices
  Vendor: Apacer    Model: Drive             Rev: 1.05
  Type:   Direct-Access                      ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
sda: Write Protect is off
Partition check:
 /dev/scsi/host0/bus0/target0/lun0: p1
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.

Configuration

Usage as a storage device to extend storage

First install the kernel file system modules, for example:

ipkg install kmod-vfat

Under Kamikaze 7.07 or later, use

ipkg install kmod-fs-vfat

TIP: After installing the modules, you should either reboot the device or load the installed modules manually:

insmod fat
insmod vfat

TIP: You can install support for more file systems by installing the appropriate packages.

File system	Package name	Comment
VFAT/MSDOS	kmod-vfat (kmod-fs-vfat)	File system generally used in USB devices and older Windows
EXT2	kmod-ext2 (kmod-fs-ext2)
EXT3	kmod-ext3 (kmod-fs-ext3)

Now install the fdisk package from the White Russian's backports repository. How to use the backports repository see OpenWrtDocs/Packages.

ipkg install fdisk

TIP: If you don't find fdisk in the rc6 backports repository, you can use the rc5 backports version:

ipkg install http://downloads.openwrt.org/backports/rc5/fdisk_2.12r-1_mipsel.ipk

Create the/mntdirectory for the mount point on the flash

mkdir /mnt

Check what partition you like to mount from your USB device

fdisk -l

Finally you can mount and use your USB device (with relevant modules for your file system in memory and created directory for mount):

mount /dev/scsi/host0/bus0/target0/lun0/part1 /mnt

Be happy and use your USB device like on every other GNU/Linux system or create a file server using Samba.

If you go with ext2 with journaling and install kmod-fs-ext2 , kmod-fs-ext3 and e2fsprogs you can use it like a normal unix type disk. Create the script /etc/init.d/usbdrive ( changing the mount point to match yours )

#!/bin/sh /etc/rc.common
START=99
STOP=40
start()
{
        echo -n "Testing USB Partition:  "
        e2fsck -p /dev/scsi/host0/bus0/target0/lun0/part1 &
        sleep 5
        echo -n "Mounting USB drive: "
        mount -t ext3 -o noatime /dev/scsi/host0/bus0/target0/lun0/part1 /usb
        echo "Done."
}
stop()
{
        echo -n "Umounting USB drive:  "
        sync
        sync
        umount /dev/scsi/host0/bus0/target0/lun0/part1
        echo "Done."
}
restart()
{
        stop
        start
}

then do a ./usbdrive enable

You may need language packages to support the filenames on various file systems:

kmod-nls-base - Kernel modules for basic native language support

kmod-nls-cp437 - Kernel module for codepage 437

kmod-nls-cp850 - Kernel module for codepage 850

kmod-nls-iso8859-1 - Kernel module for iso8859-1 charset support

kmod-nls-iso8859-15 - Kernel module for iso8859-15 charset support

kmod-nls-utf8 - Kernel module for utf8 support

How do I boot from the USB device (prep)

For this to work you need the same kernel modules for USB as described above. You also need the modules for the EXT3 file system:

NOTE: IMPORTANT: There are reports that this procedure bricks routers running Kamikaze with 2.6 kernel - proceed at your own risk! (It works for some, not for others)

ipkg install kmod-ext2 kmod-ext3

After installing the modules, you should either reboot the device or load the installed modules manually:

insmod ext2
insmod jbd
insmod ext3

The next step is to partition the USB device and create an EXT3 FS partition. This requires fdisk (install it as described above). You can do the partioning in OpenWrt it self or on a normal PC.

In OpenWrt do

fdisk /dev/sda
-OR-
fdisk /dev/scsi/host0/bus0/target0/lun0/disc

On a GNU/Linux desktop PC do

fdisk /dev/sda

IMPORTANT: Make sure you are modifying the right device. If you have any other USB drives, or a SCSI or SATA drive, your USB device might be at /dev/sdb or /dev/sdc (and so on) instead! Also, you do not want to use a partition such as /dev/sda1 (note the number at the end); you do want the base device name.

For more information about using fdisk, see http://www.tldp.org/HOWTO/Partition/fdisk_partitioning.html.

Next, "format" the newly created partition.

In OpenWrt do

For doing this in OpenWrt you first have to install the e2fsprogs package from the White Russian's backports repository. How to use the backports repository see OpenWrtDocs/Packages.

ipkg install e2fsprogs

Then "format" your partition with

mke2fs -j /dev/scsi/host0/bus0/target0/lun0/part1

mke2fs may fail on large disks (e.g. 300GB) if there is not enough memory, consider adding a swap partition, even if it is only used during mke2fs.

If you keep getting errors like:

Creating journal (4096 blocks): mke2fs: No such file or directory
        while trying to create journal

then run the following command:

ln -s /proc/mounts /etc/mtab

Now, we will copy everything from the flash to the USB device (make sure the EXT3 modules are loaded):

# mount it
mount -t ext3 /dev/scsi/host0/bus0/target0/lun0/part1 /mnt
# now, we need to mount the root contents somewhere so we can copy
# them without copying /mnt and /proc to the new usb device
mkdir /tmp/root
# if you're using squashfs, you want to copy the squashfs contents,
# not the jffs2 symlinks, so use the command:
mount -o bind /rom /tmp/root
# if you're using jffs2 then use the command /
mount -o bind / /tmp/root
# now /tmp/root contains the root filesystem with no extra directories mounted
# so we just copy this to the usb device
cp /tmp/root/* /mnt -a
# and now we unmount both the usb and our /tmp/root
umount /tmp/root
umount /mnt

Problems with booting from USB storage were reported with WhiteRussian RC4 or later, which is the version that introduced USB hotplug support. If you encounter problems as well, try disabling USB hotplug. (more info on this?)

As earlier stated on this page (to remove /etc/hotplug.d/usb/01-mount) is NOT a good idea, as this is where usbfs is mounted, so usb-storage might work fine but lsusb wohn't list your devices, and most software using USB won't be able to find devices since /proc/bus/usb will remain empty?

So either remove the file and mount usbfs somewhere else, or everything inside except the line which goes: [ -f /proc/bus/usb/devices ] || mount -t usbfs none /proc/bus/usb

Boot Configuration - (White Russian)

Next, remove /sbin/init from the JFFS2 partition (this is just a symlink to BusyBox anyway):

rm /sbin/init

And replace it with this script:

#!/bin/sh
# change this to your boot partition
boot_dev="/dev/scsi/host0/bus0/target0/lun0/part1"
# install needed modules for usb and the ext3 filesystem
# **NOTE** for usb2.0 replace "uhci" with "ehci-hcd"
# **NOTE** for ohci chipsets replace "uhci" with "usb-ohci"
for module in usbcore uhci scsi_mod sd_mod usb-storage jbd ext3; do {
        insmod $module
}; done
# this may need to be higher if your disk is slow to initialize
sleep 4s
# mount the usb stick
mount "$boot_dev" /mnt
# if everything looks ok, do the pivot root
[ -x /mnt/sbin/init ] && {
        mount -o move /proc /mnt/proc && \
        pivot_root /mnt /mnt/mnt && {
                mount -o move /mnt/dev /dev
                mount -o move /mnt/tmp /tmp
                mount -o move /mnt/jffs2 /jffs2 2>&-
                mount -o move /mnt/sys /sys 2>&-
        }
}
# finally, run the real init (from USB hopefully).
exec /bin/busybox init

Make sure your new /sbin/init is executable:

chmod a+x /sbin/init

Now just reboot, and if you did everything right it should boot from the USB device automatically.

If it could not boot from the USB device it will boot normally from the file system found on the flash as fallback.

Note that it is safest to leave the 'pivot_root' procedure as an ordinary script file, not part of the code automatically run on startup, at least until you are certain that it is operating as desired. This allows you to recover from any problems created by this script by simply rebooting the router without it.

Boot Configuration (Kamikaze)

First Create a script /etc/init.d/pivotroot

#!/bin/sh
# change this to your boot partition
boot_dev="/dev/sda1"
# install needed modules for usb and the ext3 filesystem
# **NOTE** for usb2.0 replace "uhci" with "ehci_hcd"
# **NOTE** for ohci chipsets replace "uhci" with "usb-ohci"
for module in usbcore uhci scsi_mod sd_mod usb-storage jbd kmod-fs-ext2 kmod-fs-ext3 ; do {
        insmod $module
}; done
# this may need to be higher if your disk is slow to initialize
sleep 4s
# mount the usb stick
mount "$boot_dev" /mnt
# if everything looks ok, do the pivot root
[ -x /mnt/sbin/init ] && {
        mount -o move /proc /mnt/proc && \
        pivot_root /mnt /mnt/mnt && {
                mount -o move /mnt/dev /dev
                mount -o move /mnt/tmp /tmp
                mount -o move /mnt/jffs2 /jffs2 2>&-
                mount -o move /mnt/sys /sys 2>&-
        }
}

Note: for Kamikaze 2.4 kernel that may not have hotplug2 then try using this instead. Tested with openwrt-brcm-2.4-squashfs.

#!/bin/sh
# change this to your boot partition
boot_dev="/dev/discs/disc0/part1"
# install needed modules for usb and the ext3 filesystem
# **NOTE** for usb2.0 replace "uhci" with "ehci-hcd"
# **NOTE** for ohci chipsets replace "uhci" with "usb-ohci"
for module in usbcore uhci scsi_mod sd_mod usb-storage jbd ext2 ext3 ; do {
        insmod $module
}; done
# this may need to be higher if your disk is slow to initialize
sleep 4s
# mount the usb stick
mount "$boot_dev" /mnt
# if everything looks ok, do the pivot root
[ -x /mnt/sbin/init ] && {
        mount -o move /proc /mnt/proc && \
        pivot_root /mnt /mnt/mnt && {
                mount -o move /mnt/dev /dev
                mount -o move /mnt/tmp /tmp
                mount -o move /mnt/jffs /jffs 2>&-
                mount -o move /mnt/sys /sys 2>&-
        }
}

Note: for Kazimate 2.6 kernel, add this before insmod loop.

/sbin/hotplug2 --override --persistent --max-children 1 --no-coldplug &

And kill it after the loop.

killall hotplug2

Make it executable:

chmod +x /etc/init.d/pivotroot

Then install the modules, for Kamikaze 7.07 or later (Kernel 2.6), use

ipkg install kmod-fs-ext2 kmod-fs-ext3

Test to see if pivotroot works:

/etc/init.d/pivotroot
df -h

You may safely ignore errors saying "insmod: cannot insert ..." If pivotroot worked, then df will show that your USB storage is mounted on "/" (root). Now reboot.

reboot

after that edit /etc/init.d/rcS

#!/bin/sh
# Copyright (C) 2006 OpenWrt.org
if test $2 == "boot" ; then
/etc/init.d/pivotroot
fi
{
        for i in /etc/rc.d/$1*; do
                $i $2 2>&1
        done
} | logger -s -p 6 -t '' &

now your System should Startup nicely either from USB or from internal Flash if the USB-disk is not available.

Installing and using OPKG packages in mount point other than root

The Optware packages already make use of a similar concept, by which ipkg-opt uses a config file (/opt/etc/opkg.conf) that points / to /opt in order to force the packages to install there. The settings to control where new packages are installed are defined by single-line entries in /etc/ipkg.conf with the original default being 'root / '. If you have external flash or hard drive, you may want to install packages there and add the corresponding directories to $PATH in /etc/profile.

NOTE: This is not tested. Please report if it's working for you.

-Works for me (MikkoKorkalo)

-Works for me (ElbenfreunD)

NOTE: PackagesOnExternalMediaHowTo, OpenWrtDocs/KamikazeConfiguration/PackagesOnExternalMediaHowTo and OpenWrtDocs/KamikazeConfiguration/BootFromExternalMediaHowTo contain additional important infos.

NOTE: Destination needs not to have trailing slash in order to make following script work (Nijel).

NOTE: Following script has been adjusted to reflect kamikaze using opkg instead of opkg

Configure opkg for a non-root destination

echo dest usb /mnt/usb >> /etc/opkg.conf

then install a package to a non-root destination

opkg -dest usb install kismet-server

Copy & paste this script into /bin/opkg-link (or somewhere in your $PATH).

#!/bin/sh
COMMAND=$1
PACKAGE=$2
setdest () {
        for i in `grep dest /etc/opkg.conf | cut -d ' ' -f 3`; do
                if [ -f $i/usr/lib/opkg/info/$PACKAGE.list ]; then
                        DEST=$i
                fi
        done
        if [ "x$DEST" = "x" ]; then
                echo "Can not locate $PACKAGE."
                echo "Check /etc/opkg.conf for correct dest listings";
                echo "Check name of requested package: $PACKAGE"
                exit 1
        fi
}
addlinks () {
        setdest;
        cat $DEST/usr/lib/opkg/info/$PACKAGE.list | while read LINE; do
                SRC=$LINE
                DST=`echo $SRC | sed "s|$DEST||"`
                DSTNAME=`basename $DST`
                DSTDIR=`echo $DST | sed "s|$DSTNAME\$||"`
                test -f "$SRC"
                if [ $? = 0 ]; then
                        test -e "$DST"
                        if [ $? = 1 ]; then
                                mkdir -p $DSTDIR
                                ln -sf $SRC $DST
                        else
                                echo "Not linking $SRC to $DST"
                                echo "$DST Already exists"
                        fi
                else
                        test -d "$SRC"
                        if [ $? = 0 ]; then
                                test -e $DST
                                if [ $? = 1 ]; then
                                        mkdir -p $DST
                                else
                                        echo "directory already exists"
                                fi
                        else
                                echo "Source directory $SRC does not exist"
                        fi
                fi
        done
}
removelinks () {
        setdest;
        cat $DEST/usr/lib/opkg/info/$PACKAGE.list | while read LINE; do
                SRC=$LINE
                DST=`echo $LINE | sed "s|$DEST||"`
                DSTNAME=`basename $DST`
                DSTDIR=`echo $DST | sed "s|$DSTNAME\$||"`
                test -f $DST
                if [ $? = 0 ]; then
                        rm -f $DST
                        test -d $DSTDIR && rmdir $DSTDIR 2>/dev/null
                else
                        test -d $DST
                        if [ $? = 0 ]; then
                                rmdir $DST
                        else
                                echo "$DST does not exist"
                        fi
                fi
        done
}
mountdest () {
        test -d $PACKAGE
        if [ $? = 1 ]; then
                echo "Mount point does not exist"
                exit 1
        fi
        for i in $PACKAGE/usr/lib/opkg/info/*.list; do
                $0 add `basename $i .list`
        done
}
umountdest () {
        test -d $PACKAGE
        if [ $? = 1 ]; then
                echo "Mount point does not exist"
                exit 1
        fi
        for i in $PACKAGE/usr/lib/opkg/info/*.list; do
                $0 remove `basename $i .list`
        done
}
case "$COMMAND" in
  add)
        addlinks
  ;;
  remove)
        removelinks
  ;;
  mount)
        mountdest
  ;;
  umount)
        umountdest
  ;;
  *)
        echo "Usage: $0  "
        echo "       Commands: add, remove, mount, umount"
        echo "       Targets: , "
        echo "Example:  $0 add kismet-server"
        echo "Example:  $0 remove kismet-server"
        echo "Example:  $0 mount /mnt/usb"
        echo "Example:  $0 umount /mnt/usb"
        exit 1
        ;;
esac
exit 0

Make sure the /bin/ipkg-link script is executable:

chmod a+x /bin/opkg-link

Examples howto use the script:

Link a single package to root:

opkg-link add kismet-server

Link all packages on a mount point to root:

opkg-link mount /mnt/usb

Remove symlinks:

opkg-link remove kismet-server

Remove all symlinks for all packages:

opkg-link umount /mnt/usb

[zz] USB on Kamikaze

2009-07-15T19:29:00.001-07:00

USB on Kamikaze

From Crashcourse Wiki

Jump to: navigation, search

This page will shortly have information on how to configure USB on your WL500GP for things like USB drives and so on. Until then, here are a number of links into the OpenWrt wiki (and elsewhere) that should be helpful.

[hide]

USB Devices on the WL500g Premium

Installation, configuration and testing done using Kamikaze devlopment version (bleeding edge, r10760).

All USB devices require the installation of the kmod-usb-core kernel module. For development versions of the operating firmware, packages are most easily accessed by copying the ~/openwrt/bin/packages directory from the git build tree to a USB key and mounting it on the router. Initial configuration can also be achieved by moving required packages to the router with scp. From a directory containing the relevant packages, the ipkg command can be used in direct mode:

root@OpenWrt:# ipkg install kmod-usb-core*

Version 1.1 USB controllers are one of two varieties, UHCI or OHCI. Installing both modules covers all V1.1 devices:

ipkg install kmod-usb-uhci*
ipkg install kmod-usb-ohci*

Version 2.0 USB devices require the usb2 kernel module:

ipkg install kmod-usb2*

USB Storage on the WL500g Premium HOWTO

[OpenWRT USB Storage HOWTO].

USB storage on the WL500gP in OpenWRT requires the usb-storage module. This module has a dependency of the scsi-core module which must be taken care of manually when using ipkg in direct mode:

ipkg install kmod-scsi-core*
ipkg install kmod-usb-storage*

Standard Linux filesystem capability (ext2/3):

ipkg install kmod-fs-ext2*
ipkg install kmod-fs-ext3*

Basic MS filesystem (msdos) and long filename capability (vfat) for default USB flash drive configurations:

ipkg install kmod-nls-base*
ipkg install kmod-fs-msdos*
ipkg install kmod-fs-vfat*

Further NLS modules may be required to mount filesystems containing filenames with non-English characters:

kmod-nls-cp1250 (Central and Eastern European MS Windows)

kmod-nls-cp437 (Extended ASCII DOS)

kmod-nls-cp850 (Western European DOS)

kmod-nls-iso8859-1 (Latin #1 ISO)

kmod-nls-iso8859-15 (Latin #9 ISO - includes Euro symbol)

kmod-nls-iso8859-2 (Latin #2 ISO)

kmod-nls-koi8r (Russian)

kmod-nls-utf8 (Unicode standard character set)

File Transfer Performance from USB Storage

So what is the transfer capability of a WL500gP router acting as a fileserver?

ftp network connection:

 USB2 drive->(hub*)->WL500gP->100mbit network->laptop
   *Same stats with/out the hub

laptop command line:

ftp> get ThomasVHS.mpg
local: ThomasVHS.mpg remote: ThomasVHS.mpg
200 PORT command successful. Consider using PASV.
150 Opening BINARY mode data connection for ThomasVHS.mpg (3026878464 bytes).
226 File send OK.
3026878464 bytes received in 1218.19 secs (2426.5 kB/s)

top on router during the transfer:

Mem: 28824K used, 1104K free, 0K shrd, 228K buff, 21188K cached
CPU:   0% usr  32% sys   0% nice   0% idle   0% io   3% irq  63% softirq
PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
4772     1 root     R     2076   7%  95% vsftpd
3592     2 root     RW<      0   0%   3% [usb-storage]

The router is waiting on the disk I/O (softirq and sys CPU usage) and is transferring as efficiently as possible.

The router can move files off an attached USB2 hard drive at 2.37 MiB/s. The same drive directly connected to the laptop shows a 20.6MiB/s transfer rate. Clearly the router is not saturating the 100Mb/s ethernet link (>10Mib/s) nor the USB port bandwidth. The transfer rate is bound by the router hardware, most notably the CPU. Note that reported transfer speeds for the stock firmware are around 1.8MiB/s, so the Kamikaze (bleeding edge, r10760) firmware shows a distinct performance improvement.

USB Audio on the WL500g Premium HOWTO

[OpenWRT USB Audio HOWTO].

ipkg install kmod-sound-core*
ipkg install kmod-usb-audio*
ipkg install alsa-lib*
ipkg install libncurses*
ipkg install libpthread*
ipkg install alsa-utils*
reboot

There are several options for USB soundcards. The Creative Audigy 2 NX USB sound card was used in this example.

By default, ALSA mutes sound devices. Use alsamixer to unmute and adjust volume of the sound card.

Madplayer can be used as a command-line client for playback of audio from local or web-based sources. Installation has several dependencies:

ipkg install zlib*
ipkg install libid3tag*
ipkg install libmad*
ipkg install madplay*

Testing:

# wget -O - http://www.mobiuseng.com/Kermit/Songs/Rainbow.mp3 | madplay -

Serving USB Printers on the WL500g Premium HOWTO

Printer sharing with OpenWRT is covered in: [[1]]. It uses the lightweight p910nd pass-through print server.

For the WL500g Premium, printer sharing requires the following packages to be installed:

ipkg install kmod-usb-printer*
ipkg install p910nd*

The configuration file for the print server is found in at /etc/config/p910nd. An example which works for a pair of Lexmark laser printers at ports 9100 and 9101 is:

config p910nd
 option device        "/dev/lp0"
 option port           0
 option bidirectional  1
    
config p910nd
 option device        "/dev/lp1"
 option port           1
 option bidirectional  1

Configuration of clients is straightforward:

From ubuntu, printer configuration uses a device URI of:

socket://192.168.254.111:9100

for a WL500gP at 192.168.254.111. Be sure to make a rule for forwarding port 9100 for print connections to the router from the WAN side.

Tips openWRT

2009-07-15T19:22:00.000-07:00

* setting openWRT to client mode
things might get missed during the procedure
- change /etc/resolv.conf
nameserver InternetGatewayIP
#nameserver 127.0.0.1 #default version
- missing wl520gu IP with DHCP enabled
after issuing /etc/init.d/network restart, Asus wl520gu IP changes, go to gateway router to see active connections and figure out new IP of wl520gu
* opkg package manager
- update /etc/opkg.conf to reflect package location
- opkg update
- use -force-downgrade when package is older than kernel

[zz] OpenWRT MP3 player with keyboard and display

2009-07-15T19:10:00.000-07:00

Enable an usbkeyboard for OpenWRT

Insert those modules:

insmod /lib/modules/2.4.30/input.o
insmod /lib/modules/2.4.30/evdev.o
insmod /lib/modules/2.4.30/hid.o

Download HERE

To compile those modules yourself, you need to enable the following kernel option:

Input core support  --->
 Input core support
   < >   Keyboard support
   < >   Mouse support
   < >   Joystick support
      Event interface support
   < >   User level driver support

USB support  --->
--- USB Human Interface Devices (HID)
          USB Human Interface Device (full HID) support
       [*]     HID input layer support
       [*]     /dev/hiddev raw HID device support

Info: I couldn't use the keyboard module (keybdev.o), when i inserted this module he complained about undefined references:

 unresolved symbol handle_scancode
unresolved symbol keyboard_tasklet
unresolved symbol kbd_ledfunc

I guess this is because the keyboard.o module doesn't exist.
Now create a new modules.d config file, /etc/modules.d/61-usb-hid with this content:
input
evdev
hid
Insert the modules manually or reboot your OpenWrt box.

Syslog when you connect the usb keyboard:
Jan 1 00:01:45 OpenFoensi kern.info kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik
Jan 1 00:01:45 OpenFoensi kern.info kernel: hid-core.c: USB HID support drivers
Jan 1 00:01:51 OpenFoensi kern.info kernel: hub.c: new USB device 01:03.0-2.3, assigned address 8
Jan 1 00:01:51 OpenFoensi kern.info kernel: input: USB HID v1.11 Keyboard [04d9:1203] on usb2:8.0
Jan 1 00:01:51 OpenFoensi kern.info kernel: input: USB HID v1.11 Device [04d9:1203] on usb2:8.1
Now there should be 2 input devices:
/dev/input/event0 /dev/input/event1

Now we need to handle these keyboard events, its time for cmdpad (http://cmdpad.sourceforge.net/). this app will listen to a /dev/input/eventX device (i our case a USB keyboard) and execute a program for each key pressed/released/keep pressing.
there seems to be a similar tool called mpc keyboard daemon, http://simon.arlott.org/sw/mpckbd/, but i didn't test it.

I compiled cmdpad for OpenWRT, but I didn't manage to create an ipkg package. You can get my poor ipkg attempt here or download just the binaries here.

install cmdpad to /usr/bin/
install cmdpad.conf to /etc/
install S70USBKbd to /etc/init.d/

the startscript looks like this:

/etc/init.d/S70USBKbd
#!/bin/sh
/usr/bin/cmdpad --quiet

SOUND

Install modules, source: http://sokrates.mimuw.edu.pl/%7Esebek/openwrt/ (http://sokrates.mimuw.edu.pl/%7Esebek/openwrt/packages/), extract them to /lib/modules/2.4.30/

Create /etc/modules.d/72-snd-usb-audio:

 soundcore
snd-page-alloc
snd
snd-rawmidi
snd-hwdep
snd-timer
snd-pcm
snd-mixer-oss
snd-pcm-oss
snd-usb-lib
snd-usb-audio

install alsa-lib ipkg
install alsa-utils ipkg
install mpd / mpc ipkg

Configure mpd:
I mount a usb stick to /mnt/stick1, where the _mp3 subdirectory contains all my mp3's.

My mpd configuration, /etc/mpd.conf:

##################### REQUIRED ###########################
music_directory         "/mnt/stick1/_mp3/"
playlist_directory      "/mnt/stick1/_mp3/playlist"
db_file                 "/mnt/stick1/_mp3/.mpd/mpd.db"
log_file                "/mnt/stick1/_mp3/.mpd/mpd.log"
error_file              "/mnt/stick1/_mp3/.mpd/mpd.error"
pid_file                "/mnt/stick1/_mp3/.mpd/mpd.pid"
##########################################################

#audio device
audio_output {
       type            "oss"
       name            "my OSS sound card"
       device          "/dev/dsp" # optional
       format          "44100:16:2" #optional
}

# OSS Mixer
mixer_type              "oss"
mixer_device            "/dev/mixer"
mixer_control           "PCM"

state_file              "/mnt/stick1/_mp3/.mpd/mpdstate"

buffer_before_play      "0%"

Don't forget to create those directories:
mkdir /mnt/stick1/_mp3/.mpd
mkdir /mnt/stick1/_mp3/playlist

Start mpd, this will create the db and searches for all mp3 files.

Now add all mp3 files to mpc:
# mpc listall | mpc add -

WARNING for asus wl500 users, DO NOT INSTALL the package "kmod-usb-ohci" or your usb subsystem will get messy, for example my usb 2.0 stick didn't work anymore, error: usb.c: USB device not responding, giving up (error=-145)

DISPLAY

First I wanted to use a "regular" LCD display, but compared to a palm device on ebay, they are way too expensive. I bought some palm devices on ebay and the best device I think is the palm 3c. Nice color display and a rechargeable battery. I modded a palm 3x device, so I don't need batteries anymore but take the power from the usb port. This has a big drawback, when the device loose power, all installed applications are gone. You could copy some apps to the internal ROM but there is just 50k free space.

PalmORB (http://palmorb.sourceforge.net/) is your friend, this application emulates an Matrix Orbital LK204-25 LCD. My palm use a serial connector, so I need an usb/serial convertor. I had trouble with an FTDI adapter, now I use an PL2303 adapter. It looks like you only can go up to 9600bps, else the connection gets fluffy, but this should be enough for our display.

On the Openwrt you need to install LCD4Linux, I've patched the mpc plugin, check this article for a how-to.

CONCLUSION

There is still much to do here's a small list...

Current Issues:
- My cheap USB sound card seems to buffer the sound, when i want to pause a song, the device keeps playing for about 4 seconds.
- I need to write some scripts for mount / dismount the USB stick, rescan the music source.
- Currently I'm working on a gps plugin for LCD4Linux.
- ...

Feel free to support me, contact me at michu at neophob dot com.

[zz] Building OpenWrt Kamikaze from source

2009-07-15T17:46:00.000-07:00

Assuming you are using Ubuntu 6.06.1 LTS (on a physical system or in the VMware Player)

1. install packages required by the OpenWrt Kamikaze buildsystem

aptitude install build-essential binutils flex bison autoconf gettext texinfo sharutils subversion libncurses5-dev ncurses-term zlib1g-dev

2. checkout and prepare Kamikaze and the packages

Code:

cd ~
svn co https://svn.openwrt.org/openwrt/trunk/
svn co https://svn.openwrt.org/openwrt/packages/ ~/trunk/feeds/packages/
cd ~/trunk/
make package/symlinks

2.1 Configure Kamikaze (select target system) and the packages (a full build with all packages selected requires about 9GB of free disk space)

make menuconfig

2.2 If you select extra packages it's a good idea to check if you have all prerequisites installed. Check with:

make prereq

TIP: To find the missing packages search at http://packages.ubuntu.com/

2.3 Finally build Kamikaze (to download all packages at once use 'make download world')

make world

3. After the build finished, ready to use images can be found in $(TOPDIR)/bin

Targets for 'make'

download
download all source tarballs (from the selected packages and it's dependencies) at once before starting the build

prereq
checks if you have all prerequisites installed on the host-system for building the selected packages

world
build everything

tools/install toolchain/install
only build the tools and the toolchain

clean
cleans the packages (NOT the tools and toolchain)

distclean
cleans up everything expect $(TOPDIR)/.config and $(TOPDIR)/dl/

package/-{clean,compile}
rebuild a single package

package/index
updates $(TOPDIR)/bin/packages/Packages

V=99
turns on debugging

make kernel_menuconfig
If you want, you can also modify the kernel config for the selected target system. Simply run "make kernel_menuconfig"
and the build system will unpack the kernel sources (if necessary), run menuconfig inside of the kernel tree, and then
copy the kernel config to target/linux//config so that it is preserved over "make clean" call.

Also look at the OpenWrt Kamikaze documentation at
- http://nbd.name/openwrt.html#x1-250002.1 or
- http://nbd.name/openwrt.pdf

Some more useful URLs:
- Free VMware Player (enough for most users, no need for the VMware Server)
- Download VMDK and VMX files for VMware Player
- Ubuntu (for the Ubuntu ISO image)
- Free VMware Server (also includes the VMware Tools)

Last edited by forum2006 (2007-05-06 18:24:28)

[zz] The OpenWrt build environment

2009-07-15T17:45:00.000-07:00

The OpenWrt build environment

One of the biggest challenges to getting started with embedded devices is that you just can't install a copy of Linux and expect to be able to compile a firmware. Even if you did remember to install a compiler and every development tool offered, you still wouldn't have the basic set of tools needed to produce a firmware image. The embedded device represents an entirely new hardware platform, which is incompatible with the hardware on your development machine, so in a process called cross compiling you need to produce a new compiler capable of generating code for your embedded platform, and then use it to compile a basic Linux distribution to run on your device.

The process of creating a cross compiler can be tricky, it's not something that's regularly attempted and so the there's a certain amount of mystery and black magic associated with it. In many cases when you're dealing with embedded devices you'll be provided with a binary copy of a compiler and basic libraries rather than instructions for creating your own -- it's a time saving step but at the same time often means you'll be using a rather dated set. Likewise, it's also common to be provided with a patched copy of the Linux kernel from the board or chip vendor, but this is also dated and it can be difficult to spot exactly what has been changed to make the kernel run on the embedded platform.

OpenWrt takes a different approach to building a firmware, downloading, patching and compiling everything from scratch, including the cross compiler. Or to put it in simpler terms, OpenWrt doesn't contain any executables or even sources, it's an automated system for downloading the sources, patching them to work with the given platform and compiling them correctly for the platform. What this means is that just by changing the template, you can change any step in the process.

As an example, if a new kernel is released, a simple change to one of the Makefiles will download the latest kernel, patch it to run on the embedded platform and produce a new firmware image -- there's no work to be done trying to track down an unmodified copy of the existing kernel to see what changes had been made, the patches are already provided and the process ends up almost completely transparent. This doesn't just apply to the kernel, but to anything included with OpenWrt -- It's this one simple understated concept which is what allows OpenWrt to stay on the bleeding edge with the latest compilers, latest kernels and latest applications.

So let's take a look at OpenWrt and see how this all works

download openwrt

This article refers to the "Kamikaze" branch of OpenWrt, which can be downloaded via subversion using the following command:

svn co https://svn.openwrt.org/openwrt/trunk

Additionally, there's a trac interface on http://dev.openwrt.org/ which can be used to monitor svn commits and browse the sources.

The directory structure

There are three key directories in the base:
- toolchain
- target
- package

Toolchain refers to the compiler, the c library, and common tools which will be used to build the firmware image. The result of this is two new directories, toolchain_build_ which is a temporary directory used for building the toolchain for a specific architecture, and staging_dir_ where the resulting toolchain is installed. You won't need to do anything with the toolchain directory unless you intend to add a new version of one of the components above.

Target refers to the embedded platform, this contains items which are specific to a specific embedded platform. Of particular interest here is the "target/linux" directory which is broken down by platform and contains the kernel config and patches to the kernel for a particular platform. There's also the "target/image" directory which describes how to package a firmware for a specific platform.

Package is for exactly that -- packages. In an OpenWrt firmware, almost everything is an ipk, a software package which can be added to the firmware to provide new features or removed to save space.

Both the target and package steps will use the directory "build_" as a temporary directory for compiling. Additionally, anything downloaded by the toolchain, target or package steps will be placed in the "dl" directory.

Building openwrt

While the OpenWrt build environment was intended mostly for developers, it also has to be simple enough that an inexperienced end user can easily build his or her own customized firmware.

Running the command "make menuconfig" will bring up OpenWrt's configuration menu screen, through this menu you can select which platform you're targeting, which versions of the toolchain you want to use to build and what packages you want to install into the firmware image. Similar to the linux kernel config,
almost every option has three choices, y/m/n which are represented as follows:

<*> (pressing y) This will be included in the firmware image
(pressing m) This will be compiled but not included (for later install)
(pressing n) This will not be compiled

After you've finished with the menu configuration, exit and when prompted, save your configuration changes. To begin compiling the firmware, type "make". By default OpenWrt will only display a high level overview of the compile process and not each individual command.

Code:

  make[2] toolchain/install
 make[3] -C toolchain install
 make[2] target/compile
 make[3] -C target compile
 make[4] -C target/utils prepare
 ...

This makes it easier to monitor which step it's actually compiling and reduces the amount of noise caused by the compile output. To see the full output, run the command "make V=99".

During the build process, buildroot will download all sources to the "dl" directory and will start patching and compiling them in the "build_" directory. When finished, the resulting firmware will be in the "bin" directory and packages will be in the "bin/packages" directory.

Creating your own packages

One of the things that we've attempted to do with OpenWrt's template system is make it incredibly easy to port software to OpenWrt. If you look at a typical package directory in OpenWrt you'll find two things:

- package//Makefile
- package//patches

The patches directory is optional and typically contains bug fixes or optimizations to reduce the size of the executable. The package makefile is the important item, provides the steps actually needed to download and compile the package.

Looking at one of the package makefiles, you'd hardly recognize it as a makefile. Through what can only be described as blatant disregard and abuse of the traditional make format, the makefile has been transformed into an object oriented template which simplifies the entire ordeal.

Here for example, is package/bridge/Makefile:

Code:

include $(TOPDIR)/rules.mk

PKG_NAME:=bridge
PKG_VERSION:=1.0.6
PKG_RELEASE:=1

PKG_BUILD_DIR:=$(BUILD_DIR)/bridge-utils-$(PKG_VERSION)
PKG_SOURCE:=bridge-utils-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=@SF/bridge
PKG_MD5SUM:=9b7dc52656f5cbec846a7ba3299f73bd
PKG_CAT:=zcat

include $(INCLUDE_DIR)/package.mk

define Package/bridge
 SECTION:=base
 CATEGORY:=Network
 DEFAULT:=y
 TITLE:=Ethernet bridging configuration utility
 DESCRIPTION:=Ethernet bridging configuration utility\\\
   Manage ethernet bridging; a way to connect networks together to\\\
   form a larger network.
 URL:=http://bridge.sourceforge.net/
endef

define Build/Configure
 $(call Build/Configure/Default,--with-linux-headers=$(LINUX_DIR))
endef

define Package/bridge/install
       install -m0755 -d $(1)/usr/sbin
       install -m0755 $(PKG_BUILD_DIR)/brctl/brctl $(1)/usr/sbin/
endef

$(eval $(call BuildPackage,bridge))

As you can see, there's not much work to be done; everything is hidden in other makefiles and abstracted to the point where you only need to specify a few variables.

PKG_NAME - The name of the package, as seen via menuconfig and ipkg
PKG_VERSION - The upstream version number that we're downloading
PKG_RELEASE - The version of this package Makefile
PKG_BUILD_DIR - Where to compile the package
PKG_SOURCE - The filename of the original sources
PKG_SOURCE_URL - Where to download the sources from
PKG_MD5SUM - A checksum to validate the download
PKG_CAT - How to decompress the sources (zcat, bzcat, unzip)

The PKG_* variables define where to download the package from; @SF is a special keyword for downloading packages from sourceforge. The md5sum is used to verify the package was downloaded correctly and PKG_BUILD_DIR defines where to find the package after the sources are uncompressed into $(BUILD_DIR).

At the bottom of the file is where the real magic happens, "BuildPackage" is a macro setup by the earlier include statements. BuildPackage only takes one argument directly -- the name of the package to be built, in this case "bridge". All other information is taken from the define blocks. This is a way of providing a level of verbosity, it's inherently clear what the DESCRIPTION variable in Package/bridge is, which wouldn't be the case if we passed this information directly as the Nth argument to BuildPackage.

BuildPackage uses the following defines:

Package/
matches the argument passed to buildroot, this describes the package
the menuconfig and ipkg entries. Within Package/ you can define the
following variables:

SECTION - The type of package (currently unused)
CATEGORY - Which menu it appears in menuconfig
TITLE - A short description of the package
DESCRIPTION - A long description of the package
URL - Where to find the original software
MAINTAINER - (optional) Who to contact concerning the package
DEPENDS - (optional) Which packages must be built/installed before this package

Package//conffiles (optional)
A list of config files installed by this package, one file per line.

Build/Prepare (optional)
A set of commands to unpack and patch the sources. You may safely leave this
undefined.

Build/Configure (optional)
You can leave this undefined if the source doesn't use configure or has a
normal config script, otherwise you can put your own commands here or use
"$(call Build/Configure/Default,)" as above to pass in additional
arguments for a standard configure script.

Build/Compile (optional)
How to compile the source; in most cases you should leave this undefined.

Package//install
A set of commands to copy files out of the compiled source and into the ipkg
which is represented by the $(1) directory.

The reason that some of the defines are prefixed by "Package/" and others are simply "Build" is because of the possibility of generating multiple packages from a single source. OpenWrt works under the assumption of one source per package makefile, but you can split that source into as many packages as
desired. Since you only need to compile the sources once, there's one global set of "Build" defines, but you can add as many "Package/" defines as you want by adding extra calls to BuildPackage -- see the dropbear package for an example.

After you've created your package//Makefile, the new package will automatically show in the menu the next time you run "make menuconfig" and if selected will be built automatically the next time "make" is run.

Troubleshooting

If you find your package doesn't show up in menuconfig, try the following command to see if you get the correct description:

TOPDIR=$PWD make -C package/ DUMP=1 V=99

If you're just having trouble getting your package to compile, there's a few shortcuts you can take. Instead of waiting for make to get to your package, you can run one of the following:

make package/-clean V=99
make package/-install V=99

Another nice trick is that if the source directory under build_ is newer than the package directory, it won't clobber it by unpacking the sources again. If you were working on a patch you could simply edit the sources under build_/ and run the install command above, when satisfied, copy the patched sources elsewhere and diff them with the unpatched sources. A warning though - if you go modify anything under package/ it will remove the old sources and unpack a fresh copy.

Final notes

I'm always interested to hear about people's experience with OpenWrt or answer questions about it so please don't hesitate to contact me.

[zz] Compiling software for OpenWrt (and creating packages)

2009-07-15T17:28:00.000-07:00

Compiling software for OpenWrt (and creating packages)

From my experience, compiling software is not especially hard, but most of the tutorials out there are somewhat dated (as this one will be in 6-7 months). But at least until then it can be useful, and hopefully I will find the time to update it later on. I’m using the trunk version of OpenWrt, which a little more up-to-date than 8.09, but most probably everything described here works with 8.09 (the latest release).

I’ve taken inspiration from the following sources:

The main ideas would be:

The easiest way to start is by copying an existing makefile and editing it to fit your needs
OpenWrt has an advanced build system which does all the following things:
- Download the application from its original source (and verify the integrity of the archive using md5sum)
- Apply some local patches to it
- Configure / build it
However, for local development you most likely won't need this. An alternative solution (which will be used in the tutorial later on) would be to copy the source to the build directory in the preparation faze.
Makefiles are very sensitive to tabs (so you have to have tabs and not 4 or 8 spaces in certain locations) and also, errors in them are very cryptic (for example "missing separator"). If your build fails, the first thing you should check is that you have your tabs in order. Also verify that your editor doesn’t have some kind of “transform tabs to spaces” option active. For example, if you are using mcedit with the default color-scheme, it will highlight correct tabs in red, as can be seen in the screenshot below.
Also, you might have observed that not all the sections use tabs, some are ok with spaces. However rules for which section should use what are not clear to me, so my recommendation is to stick with tabs everywhere. For a quick make tutorial, you can check out this site. A last word of warning on this matter: copy-pasting from this blogpost will almost certainly mess things up (convert tabs to spaces, etc), so please double check the source after copying it.

Our goal (taken from the first linke tutorial) is to get the following little C program to compile and run:


/****************
* Helloworld.c
* The most simplistic C program ever written.
* An epileptic monkey on crack could write this code.
*****************/
#include 

int main(void)
{
 printf("Hell! O' world, why won't my code compile?\n\n");
 return 0;
}

The first step is to create a Makefile for it:


# build helloworld executable when user executes "make"
helloworld: helloworld.o
 $(CC) $(LDFLAGS) helloworld.o -o helloworld
helloworld.o: helloworld.c
 $(CC) $(CFLAGS) -c helloworld.c

# remove object files and executable when user executes "make clean"
clean:
 rm *.o helloworld

Place the files in the packages/helloworld/src directory of either the checked-out OpenWrt source or the Openwrt SDK. Now change into this directory and make sure that everything builds on our local system (without the crosscompiling magic):


make
./helloworld <-- this should output the message make clean   <-- clean up after ourselves

Now to create the openwrt makefile. This will be located one level up (ie. packages/helloworld/Makefile):


#
# Copyright (C) 2008 OpenWrt.org
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#
# $Id$

include $(TOPDIR)/rules.mk

PKG_NAME:=helloworld
PKG_RELEASE:=1

include $(INCLUDE_DIR)/package.mk

define Package/helloworld
 SECTION:=utils
 CATEGORY:=Utilities
 TITLE:=Helloworld -- prints a snarky message
endef

define Build/Prepare
 mkdir -p $(PKG_BUILD_DIR)
 $(CP) ./src/* $(PKG_BUILD_DIR)/
endef

define Build/Configure
endef

define Build/Compile
 $(MAKE) -C $(PKG_BUILD_DIR) $(TARGET_CONFIGURE_OPTS)
endef

define Package/helloworld/install
 $(INSTALL_DIR) $(1)/bin
 $(INSTALL_BIN) $(PKG_BUILD_DIR)/helloworld $(1)/bin/
endef

$(eval $(call BuildPackage,helloworld))

The makefile should be pretty self-explanatory. A couple things I would like to highlight:

Build/Prepare is the step where we copy our source-code to the build directory. This is a hack to circumvent the need of downloading the tgz file, but it is a hack which works well (you might want to add the –r switch to cp if you have nested directories in src – this isn’t the case for this simple example)
In the Build/Compile step it is very important to include the $(TARGET_CONFIGURE_OPTS) part. Without it, the thing will build, but it will link with the standard libc, rather than the ulibc available on the Openwrt router. Tracking down this error is made harder by the unintuitive error messages. Specifically, you will see something like this on your router: “/bin/ash: The command /bin/helloworld can not be found”, even though you see that the file exists and it has execute permissions! To verify that your issues are caused by this problem, simply too a “less /bin/helloworld” on your router and check to see if you have strings indicating glibc (instead of ulibc).

Now you are ready to compile:

If you are using the SDK, simply go to its root directory and issue the make V=99 command
If you are building the complete tree, you have to first do “make menuconfig”, make sure that your package is checked for build (you should see the letter M near it) and then issue make V=99. Be aware that compiling the full tree can take a considerable time (more than a hour in some cases).

Your package should now be ready. Copy the package (you will find it in the bin/packages/target-... subfolder) to your router (or better yet, a Qemu VM running OpenWrt – for safety) and test that everything works:


scp helloworld.ipkg root@router:/root
[root@router]# opkg install helloworld.ipkg
[root@router]# helloworld <-- the message should be printed

This would be all :-). Because of simplicity, this tutorial doesn’t cover the the calling of configuration scripts. Also, as far as I’ve seen, there is no easy way to include parts of other projects. For example, if I wish to create a package for LuaFileSystem, I would need lua.h (and some other, related files). However, I haven’t found an easy way reference it from the lua package, and have opted for putting a local copy in the src/lua subdirectory.

Picture taken from cantrell.david's buddy icon with permission.

[zz] OpenWRT Howto

2009-07-15T17:24:00.000-07:00

Contents

Introduction

I went out and bought a WRT54G after playing with a work one that ended up being loaded with OpenWRT firmware and seeing first hand how neat these things really are if you get to tinker with them at a level beyond that of any simple webpage administration that Linksys ship by default.

The router I have is a WRT54G v3.1 and was pre-loaded with 4.00.7 firmware, which at first attempt wouldn't load OpenWRT firmware either by webpage or TFTP, as described on the OpenWRT website. My goal for the time being is fairly simple, I wanted a router I could take with me and plug into other peoples networks that wouldn't open the flood gates for the bad guys to get in, it also served as a testing and demonstration platform for customers that want a better then WEP security product for their network.

BIG FAT WARNING: Usual disclaimers about I'm not responsible for your actions, this information is provided for educational purposes only and if you turn your router into a brick it may be because you didn't research the topic enough before moving forward and doing anything.

Flashing your WRT54G

Preparing your WRT54G

This may or may not be optional, but I had to upgrade my WRT54G firmware to v4.20.7 before I could load the OpenWRT firmware via the webpage. You can grab this from the Linksys website.

Once loaded you will be able to telnet to your router, by default there is no web config that comes with OpenWRT, so you're stuck using vi for the most part, but then again you get the full power of the device at your disposal rather then a limited feature set.

Installing OpenWRT

Swatting up on the OpenWRT documentation wouldn't hurt before you do anything, it may take you a little time, but it could save you from turning your shiney new router into an expensive lump of plastic you are no longer able to use.

Firstly you will need to download a firmware image, the manual suggests using the squashfs version since this gives you a couple of more options if you screw up your install and will allow you to be able to fix it a lot easier then some of the other methods.

At the time of writting, the current stable image suitable for my WRT54G was WhiteRussian RC3 which seems to be pretty stable, at least I've not come across any problems that I didn't cause myself, all I did to get this working was download and then upload via the webpage, I waited about 30 seconds and was then able to telnet into the router.

Getting started with OpenWRT

First Time Use

I suggest for the first few steps you use a piece of cat5 connected to a computer to update the password on the router, otherwise if you come in over telnet via wireless it's possible someone else could of sniffed your packets while you add one. Enabling a password will then also enable SSH and disable telnet connections as well.

root@OpenWrt:~# passwd
Changing password for root
Enter the new password (minimum of 5, maximum of 8 characters)
Please use a combination of upper and lower case letters and numbers.
Enter new password:
Re-enter new password:

Cleaning things up a little

It's a VERY VERY good idea to set the clock on bootup, since every time you restart the router it will reset back to Jan 1st 2000, which can cause all sorts of issues with OpenVPN and time settings on certificates. The best solution is to install ntpclient and then run it to correct the system clock.

ipkg install ntpclient
/etc/init.d/S60ntpclient

It's also helpful to setup timezone information unless you prefer to view everything in GMT. For the east coast of Australia that has daylight savings time you'd do something along the lines of:

echo "EST-10EDT-11,M10.5.0/02:00:00,M3.5.0/03:00:00" > /etc/TZ

However due to the number of time zones and there are already articles written up in depth on other sites, so I won't duplicate their efforts, but instead point you to the other site: More TZ information here

You will also need a file to setup the SSID, default time (especially if you plan to run it in client mode), and transmit power level if you want to run lower then the default 255mW. vi /etc/init.d/S41defaults

SSID=$(nvram get wl0_ssid)
TXPWR1=$(nvram get wl0_txpwr1)

wl ssid $SSID
wl txpwr1 -m $TXPWR1
date -s '110401592005'

Since you won't be able to remotely access your router any longer with telnet you can do the following:

rm /etc/init.d/S50telnet
killall telnetd

Installing OpenVPN

Getting the packages

Next you will need to install OpenVPN, again due to all the effort put into OpenWRT there is a debian like packaging utility called ipkg, and just do the following:

ipkg update
ipkg upgrade
ipkg install openvpn wl

After installing if you run "df -h" you should have approximately 50% (1.1M) of free space left on your device.

Configuration

Once the packages have installed, this is where the fun begins, I've set my router up to trust the wired LAN ports, default firewall on the WAN port, and I've removed the wifi network from being bridged with my LAN ports, this way I can disable all traffic to and from the wifi network unless they've sucessfully connected via VPN.

I'd suggest wiping your nvram configuration and then rebooting:

mtd erase nvram
reboot

Once your router boots up you have a number of options, depending how locked down you want to make your router.

To disable SSID broadcasts:

nvram set wl0_closed=1

To allow G-Mode only (disables 802.11b clients from connecting and slowing your connection down):

nvram set wl0_gmode=2

You can set the channel (1-14 depending on your country) or set it to 0 for auto channel selection:

nvram set wl0_channel=0

To change the SSID:

nvram set wl0_ssid=My_AP

To allow you to recover from bad flash

nvram set boot_wait=on

To fix large file transfer problems

nvram set clkfreq=216

If you have a problem with your router rebooting unsetting the following may help

nvram unset watchdog

Next you need to remove the wifi network from the bridged network inside the router, and you simply do:

nvram set lan_proto=static
nvram set lan_ifname=br0
nvram set lan_ifnames=vlan0
nvram set lan_ipaddr=172.16.1.1
nvram set lan_netmask=255.255.255.0

Next you need to give your wifi network IP details

nvram set wifi_ifname=eth1
nvram set wifi_proto=static
nvram set wifi_ipaddr=172.16.2.1
nvram set wifi_netmask=255.255.255.0

If you are finished making changes do the following to make your changes go active:

nvram commit
reboot

Firewall Modifications

Next you'll need to modify your firewall slightly so people connecting via the wifi interface will only be able to request dhcp information and connect to the OpenVPN port.

cd /etc
rm firewall.user
cp -a /rom/etc/firewall.user .
vi firewall.user

When using vi, move the cursor down below the LAN= line and hit i (for insert), and then add the following line directly beneath it:

WLAN=$(nvram get wifi_ifname)

Now hit the escape key and move the cursor down below the warning section, and directly beneath this hit the i key again and insert the following lines:

if [ -n "$WLAN" ]
then
      iptables -A input_rule -i $WLAN -p udp --dport 67 -j ACCEPT
      iptables -A input_rule -i $WLAN -p udp --dport 1194 -j ACCEPT
      iptables -A input_rule -i $WLAN -j DROP
fi

Once you are sure everything is in place hit the escape key and type ":wq" (without the quotes) this will save and exit you out of the program.

DNSMASQ Configuration

Next you need to update dnsmasq so it has multiple subnet information, so do the following:

cd /etc
rm dnsmasq.conf
cp /rom/etc/dnsmasq.conf .
vi dnsmasq.conf

You'll need to scroll to the end of file, hit the "$" key then press "a" and paste the following lines into your config:

dhcp-range=lan,172.16.1.100,172.16.1.250,255.255.255.0,12h
dhcp-range=wlan,172.16.2.100,172.16.2.250,255.255.255.0,12h
dhcp-option=wlan,3
dhcp-option=6,172.16.1.1

Then hit the escape key and type ":wq", after which you'll need to restart dnsmasq:

killall dnsmasq
/etc/init.d/S50dnsmasq

OpenVPN Configuration

Next we can start with some of the more complicated configurations with OpenVPN itself. Due to the limited space on these devices you will also need a computer that has OpenSSL binaries installed as well.

mkdir /etc/openvpn
cd /etc/openvpn
vi openvpn.conf

Next hit the i key and paste the following:

mode server
tls-server
port 1194
proto udp
dev tap

local 172.16.2.1

up /etc/openvpn/server-tun.up
down /etc/openvpn/server-tun.down

cipher BF-CBC
auth SHA1

ifconfig-pool 172.16.1.50 172.16.1.99 255.255.255.0
ifconfig-pool-persist /tmp/ipp.txt
tls-verify /etc/openvpn/access-control.sh

ca /etc/openvpn/cacert.crt
dh /etc/openvpn/dh1024.pem
cert /etc/openvpn/server.crt
key /etc/openvpn/server.key

push "route-gateway 172.16.1.1"
push "redirect-gateway"
push "route 0.0.0.0 0.0.0.0"

client-to-client

keepalive 10 60
persist-key
persist-tun
ping-timer-rem

daemon

log /tmp/openvpn.log
verb 3

Then hit the escape key and type ":wq"

next "vi server-tun.up"

LAN=$(nvram get lan_ifname)

# bring up the tap interface
$DEBUG ifconfig $1 0.0.0.0 up
# and add that to the bridge
$DEBUG brctl addif $LAN $1

Then hit the escape key and type ":wq"

next "vi server-tun.down"

LAN=$(nvram get lan_ifname)

# and delete that from the bridge
$DEBUG brctl delif $LAN $1
# bring down the tap interface
$DEBUG ifconfig $1 0.0.0.0 down

Then hit the escape key and type ":wq", followed by "chmod +x server-tun.up server-tun.down"

next "vi access-control.sh"

if [ "$1" != "0" ]; then
      exit 0
fi

whologin=$(grep $2 /etc/openvpn/access-control.txt)
if [ -z ${whologin}]; then
  exit 1
else
  exit 0
fi

Then hit the escape key and type ":wq", followed by "chmod +x access-control.sh"

next "vi access-control.txt"

/emailAddress=user@isp.com

You will need to have at least one domain/hostname registered with CAcert, then you will need to generate a certificate and submit a signing request to CAcert.

openssl req -nodes -new -keyout server.key -out server.csr

Once you have a valid certificate simply "vi server.crt" and paste the contents in there. You will need to set the permissions on server.key so only root can read the file.

You will also need to put the contents of the CAcert root certificate in the directory as well.

wget http://www.cacert.org/cacert.crt
chmod 600 /etc/openvpn/server.key

Finally you will need to create a 1024bit dh file:

openssl dhparam -out dh1024.pem 1024

If you want OpenVPN to auto-start (which you should) you need to vi /etc/init.d/openvpn

/usr/sbin/openvpn --config /etc/openvpn/openvpn.conf

and

ln -sf /etc/init.d/openvpn /etc/init.d/S75openvpn

At this point you should restart your router to see if everything is working, once your router has rebooted you can run "ps auxww" to see if openvpn is listed.

Client Configuration

Under WRT54G

You can use a WRT54G as a ethernet bridge/router, and use the WAN port as another LAN port so you end up with a 5 port ethernet bridge/router which is useful for linking buildings togeather or even just floors/rooms in the same house without the hassle/expense of having cat5 cables run, or tripping over them in the middle of the night. The best bit is the price, in Australia the going price for a WRT54G is about AU$120 (inc GST) if you were to buy an ethernet bridge or gaming adapter they are at least $50 more and you only get 1 ethernet port not 5!

So once you have a second unit flashed (see above) and ready to be worked on run the following commands:

nvram set wl0_ssid=My_AP
nvram set lan_ifnames='vlan0 vlan1'
nvram set wan_ifname=tap0
nvram set wan_proto=dhcp
nvram set wifi_proto=dhcp
nvram set wl0_mode=sta
nvram unset wl0_channel
nvram set wl0_closed=1
nvram set wl0_gmode=2
nvram set boot_wait=on
nvram set clkfreq=216
nvram unset watchdog
nvram set boot_wait=on
nvram set lan_proto=static
nvram set lan_ifname=br0
nvram set lan_ipaddr=172.17.1.1
nvram set lan_netmask=255.255.255.0
nvram set wifi_ifname=eth1
nvram set wifi_ipaddr=172.17.2.1
nvram set wifi_netmask=255.255.255.0
nvram commit
mkdir /etc/openvpn-client
reboot

Next you'll need to create an vi /etc/openvpn-client/openvpn.conf file:

tls-client
remote 172.16.2.1
port 1194
proto udp
dev tap

pull

resolv-retry infinite
nobind

cipher BF-CBC
auth SHA1

ca /etc/openvpn-client/cacert.crt
cert /etc/openvpn-client/client.crt
key /etc/openvpn-client/client.key

daemon
user nobody
group nogroup

ping 5
ping-restart 15
resolv-retry 300
ping-timer-rem
persist-tun
persist-key

log /tmp/openvpn-client.log
verb 1

You will need to have a signed client/email certificate from the CAcert website, this is a simple step by step process on the website, once you have one you will need to export it from your brower, and most likely it will be in pkcs12 format so you will need to split this using openssl.

openssl pkcs12 -in .p12 -clcert

You'll need to split the output into a .key file and a .crt file, most likely openssl will force you to set a password on your private key you will also need to remove this if you plan to use OpenVPN in any sort of automate manner. You will need to mark the client private key as read/write by root only. You also need to grab a copy of the root certificate.

openssl rsa -in client.pem -out client.key
chmod 600 client.key
wget http://www.cacert.org/cacert.crt

One final thing you'll need to vi /etc/init.d/openvpn-client

/usr/sbin/openvpn --config /etc/openvpn-client/openvpn.conf

and

ln -sf /etc/init.d/openvpn-client /etc/init.d/S75openvpn

Under Ubuntu

OpenVPN has clients for a lot of platforms, at this point in time the only thing I need to connect via is my laptop running Ubuntu, hopefully others with experience on other platforms can add further information in this section.

firstly you will need to install OpenVPN and do some misc other things:

apt-get install openvpn
mkdir -p /etc/openvpn
cd /etc/openvpn
wget http://www.cacert.org/cacert.crt

Next you can start working on the openvpn.conf file:

tls-client
remote 172.16.2.1
port 1194
proto udp
dev tap

pull

resolv-retry infinite
nobind

cipher BF-CBC
auth SHA1

ca /etc/openvpn/cacert.crt
cert /etc/openvpn/client.crt
key /etc/openvpn/client.key

daemon
user nobody
group nogroup

ping 15
ping-restart 45
resolv-retry 300
ping-timer-rem
persist-tun
persist-key

log /var/log/openvpn/openvpn.log
verb 3

openssl pkcs12 -in .p12 -clcert

openssl rsa -in client.pem -out client.key
chmod 600 client.key

To simplify things for myself, when my wireless interface is brought up on my laptop, I also trigger the vpn tunnel as well in /etc/network/interfaces:

auto eth0
iface eth0 inet dhcp
      wireless-mode managed
      wireless-essid My_AP
      post-up openvpn --config /etc/openvpn/openvpn.conf
      pre-down killall -KILL openvpn

Gotchas

Out of Space

If you've used your OpenWRT and installed and removed packages or other things I found it doesn't release the space 100% of the time and I was forced to erase the jffs2 partition and reboot the device, upon reboot the squashfs partition will simply rebuild the jffs2 partition and you will be on your way again.

Another big fat warning, this will erase all changes you've made including any packages you've downloaded and installed, I'd suggest you backup anything you want to save !!!BEFORE!!! going any futher.

To backup the device you could do a dd and dump the entire file system, but this is difficult to extract one or 2 files from, instead I suggest you simple tarball files in any directory you've altered, for me I've only touched files in /etc and of course the nvram memory, so that's all I need to backup, although there is no harm in archiving too much, but it'll be too late once you erase it:

cd /tmp
nvram show > /tmp/nvram-backup
tar czvf backup.tgz /etc /tmp/nvram-backup

You will need to download a copy of the file, the easiest way is via scp from another linux box:

scp 172.16.1.1:/tmp/backup.tgz .

Once you have that out of the way you are then able to erase your device and start over again:

mtd erase nvram
mtd -r erase mtd4

If the device doesn't power cycle itself you will need to do it manually. Within a minute you should be back up and running.

More information

Notes

The WRT54G and WRT54GS aren't the only products capable of running the OpenWRT firmware, but they are some of the most widely available, check out the OpenWRT documentation for a list of compatible routers.

Simple web interface

Installing Lighttpd and PHP

You will need to edit your /etc/ipkg.conf:

rm /etc/ipkg.conf
cp /rom/etc/ipkg.conf .
echo "src nico http://openwrt.org/downloads/people/nico/testing/mipsel/packages" >> /etc/ipkg.conf
ipkg update
ipkg install php4-cgi lighttpd lighttpd-mod-cgi
echo -n > /etc/lighttpd.conf
vi /etc/lighttpd.conf

Press "i" and paste the following lines:

server.modules = (
      "mod_cgi",
)

server.document-root = "/www/"
server.errorlog = "/var/log/lighttpd/error.log"
index-file.names = ( "index.php" )

mimetype.assign = (
      ".pdf"   => "application/pdf",
      ".class" => "application/octet-stream",
      ".pac"   => "application/x-ns-proxy-autoconfig",
      ".swf"   => "application/x-shockwave-flash",
      ".wav"   => "audio/x-wav",
      ".gif"   => "image/gif",
      ".jpg"   => "image/jpeg",
      ".jpeg"  => "image/jpeg",
      ".png"   => "image/png",
      ".css"   => "text/css",
      ".html"  => "text/html",
      ".htm"   => "text/html",
      ".js"    => "text/javascript",
      ".txt"   => "text/plain",
      ".dtd"   => "text/xml",
      ".xml"   => "text/xml"
)

server.tag = "lighttpd"
static-file.exclude-extensions = ( ".php" )
server.pid-file = "/var/run/lighttpd.pid"
server.dir-listing = "disable"
cgi.assign = ( ".php" => "/usr/bin/php" )

Example Web Interface

Do to the size of this file, rather then posting the file to this page, it's available as a download instead. Simply wget it and save it as /www/index.php

wget http://wiki.cacert.org/wiki/OpenWRT?action=AttachFile&do=get&target=index.php

Screenshots:

Enabling PPPoE

You will need to install a couple of packages:

ipkg install kmod-ppp kmod-pppoe ppp ppp-mod-pppoe pppoe-client
echo "slhc
ppp_generic
ppp_async
pppox
pppoe" > /etc/modules.d/30-ppp

[zz] Wireless Home Network

2009-07-15T17:02:00.000-07:00

This article describes how I set up two wireless routers in my apartment, to provide a PSK2 encrypted wireless connection for all my household equipment. They are linked together using WDS (also PSK2). For software, I’m using OpenWRT. For hardware, I’m using two broadcom-based Asus WL-500G Premium boxes.

If you need a 3G connection as well, you may find my wireless router with 3G USB dongle or my summer house wireless+3g network writeup more relevant.

If you want to comment on this, please go to the blog entry.

Created by Simon Josefsson on 2008-05-08, updated for OpenWRT 8.09 on 2009-03-23 and for OpenWRT 8.09.1 on 2009-06-09.

Chosing OpenWRT Image

You may build your own OpenWRT image, or you may download one from openwrt.org.

For the ASUS WL-500gP device I chose the brcm-2.4 variant of OpenWRT for this device. The plain brcm variant will work, and uses the newer 2.6 kernel, but wireless will not work.

Downloading Image

To avoid building the image yourself, you may download it from openwrt.org.

$ wget --quiet http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/openwrt-brcm-2.4-squashfs.trx
$ md5sum openwrt-brcm-2.4-squashfs.trx
6ccb44d015a8477e2eb0fa81b9b83f1a  openwrt-brcm-2.4-squashfs.trx

Building OpenWRT

You may skip this section if you do not want to build your own image.

Building OpenWRT is quite easy these days. I’m using Debian x86 lenny, and you will need to install gcc and other development tools. Here are the commands I used:

svn co https://svn.openwrt.org/openwrt/trunk/
mv trunk openwrt
cd openwrt
make menuconfig
#  toggle 'select all packages by default'
#  quit and save config
make

That’s it! The complete build takes up about 2GB on my machine, and it will take quite some time to build (up to several hours).

The output files will be stored into the bin/ directory.

Installing OpenWRT

There are generic Installation instructions on the the OpenWRT Wiki.

You’ll have to use a ethernet cable at this point. Connect it to LAN1-LAN4, not WAN. Configure your local machine on the 192.168.1.x network, for example as 192.168.1.42. The router will use 192.168.1.1.

On many routers, including the Asus WL-500g Premium that I use, you flash an image by disconnecting power, press and hold down the reset button, and connect the power again. Wait a few seconds and the PWR led will start to blink. Release the reset button. The device will now have a tftp server running on 192.168.1.1.

$ tftp 192.168.1.1
tftp> trace
Packet tracing on.
tftp> binary
tftp> put openwrt-brcm-2.4-squashfs.trx
...

Wait a minute and restart the box by disconnecting and reconnecting power. Some documentations claim that the device should restart by itself but I have never seen this happen.

Configuring OpenWRT

When the router has restarted, it will have a telnet server running listening on 192.168.1.1.

$ telnet 192.168.1.1
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.
=== IMPORTANT ============================
 Use 'passwd' to set your login password
 this will disable telnet and enable SSH
------------------------------------------


BusyBox v1.11.2 (2009-05-28 19:38:17 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.1, r16278) ----------------------------
 * 10 oz Vodka       Shake well with ice and strain
 * 10 oz Triple sec  mixture into 10 shot glasses.
 * 10 oz lime juice  Salute!
---------------------------------------------------
root@OpenWrt:/#

Now you can configure OpenWRT. I’ll go through each step I made, but obviously you may deviate from this description.

Set hostname

My first step was to set a hostname on the machine, use vi to edit /etc/config/system to make it read:

config system
       option hostname caramel

If you prefer to cut’n'paste a command line invocation to do this, try:

root@OpenWrt:~# cat /etc/config/system | sed -e 's/OpenWrt/caramel/' > /etc/config/system

Setting a hostname will help when you have multiple OpenWRT boxes running, as the command prompt will show your hostname instead of OpenWRT (after you have restarted the router).

Set IP address

If you want the device to use another IP address than 192.168.1.1 you can modify /etc/config/network, in the LAN configuration section. A quick command to do this:

root@OpenWrt:~# cat /etc/config/network | sed -e 's/192.168.1.1/192.168.1.15/' > /etc/config/network

Replace telnet with SSH

As you do not want to use insecure telnet, you will need to set up ssh. You can type passwd to set a root password, and this will disable telnet. I dislike passwords, even if used over ssh, so I always set up public-key authentication instead. For reference, there is a dropbear public key authentication howto for OpenWRT wiki page.

The command to make your ssh key authorized to login as root on the router is:

root@OpenWrt:/# echo 'PUBLICKEY'  > /etc/dropbear/authorized_keys

Replace PUBLICKEY with the content of the ~/.ssh/id*.pub file on your own machine.

Disable password based login using:

root@OpenWrt:/# cat /etc/config/dropbear | sed -e "s/'on'/'off'/"  > /etc/config/dropbear

Alternatively, edit /etc/config/dropbear to look like:

config dropbear
       option PasswordAuth 'off'
       option Port         '22'

At this point, you can print the ssh host key fingerprint using:

root@OpenWrt:~# dropbearkey -y -f /etc/dropbear/dropbear_rsa_host_key
Public key portion is:
ssh-rsa AAAA... root@OpenWrt
Fingerprint: md5 b4:...

To use the web interface, you may want to set a root password.

root@OpenWrt:/# passwd
Changing password for root
New password:
Retype password:
Password for root changed by root
root@OpenWrt:/#

If you do not set a root password, you will need to manually disable the telnet server as follows.

root@OpenWrt:~# rm /etc/rc.d/S50telnet

After you have made your changes, try the new configuration by rebooting both devices.

root@OpenWrt:/etc/config# reboot

You should now be able to login as root using SSH. Try it from your machine. The SSH fingerprint should match what was printed by dropbearkey earlier.

jas@mocca:~$ ssh -l root 192.168.1.15
The authenticity of host '192.168.1.15 (192.168.1.15)' can't be established.
RSA key fingerprint is b4:...
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.1.15' (RSA) to the list of known hosts.


BusyBox v1.11.2 (2009-05-28 19:38:17 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.1, r16278) ----------------------------
 * 10 oz Vodka       Shake well with ice and strain
 * 10 oz Triple sec  mixture into 10 shot glasses.
 * 10 oz lime juice  Salute!
---------------------------------------------------
root@caramel:~#

Setup wireless

Wireless is disabled by default, and you will have to modify “/etc/config/wireless” to configure it.

A simple setup that use (insecure) WEP would be:

config wifi-device  wl0
       option type     broadcom
       option channel  5

config wifi-iface
       option device   wl0
       option network  lan
       option mode     ap
       option ssid     YourNetworkName
       option encryption wep
       option key      DEADBEEF

A better setup that use shared secrets but the more secure PSK2 would be:

config wifi-device  wl0
       option type     broadcom
       option channel  5

config wifi-iface
       option device   wl0
       option network  lan
       option mode     ap
       option ssid     YourNetworkName
       option encryption psk2
       option key      DEADBEEFDEADBEEFDEADBEEFDEADBEEF

Remember, your security is never better than your password.

As you may recall, the point of my exercise was to set up two routers with WDS and PSK2. For discussion, let’s say the MAC address of box 1 is 12:34:56:78:89:ab and the MAC address of box 2 is cd:ef:01:23:45:67. You can use ifconfig on each of the routers to find out the MAC address.

On the first box, my /etc/config/wireless file looks like:

# /etc/config/wireless configuration for device 12:34:56:78:89:ab
config wifi-device  wl0
       option type     broadcom
       option channel  5

config wifi-iface
       option device   wl0
       option network  lan
       option mode     ap
       option ssid     YourNetworkName
       option encryption psk2
       option key      UserNetworkPassword

config wifi-iface
       option device   wl0
       option network  lan
       option mode     wds
       option bssid    cd:ef:01:23:45:67
       option encryption psk2
       option ssid     WDSNetworkName
       option key      InternalWDSPassword

Replace YourNetworkName and WDSNetworkName with something more appropriate. You want to use a different SSID for the WDS than for the normal network.

On the second box, the /etc/config/wireless will look the same except that the BSSID will contain the MAC address of the first box. Here is the file:

# /etc/config/wireless configuration for device cd:ef:01:23:45:67
config wifi-device  wl0
       option type     broadcom
       option channel  5

config wifi-iface
       option device   wl0
       option network  lan
       option mode     ap
       option ssid     YourNetworkName
       option encryption psk2
       option key      UserNetworkPassword

config wifi-iface
       option device   wl0
       option network  lan
       option mode     wds
       option bssid    12:34:56:78:89:ab
       option encryption psk2
       option ssid     WDSNetworkName
       option key      InternalWDSPassword

Disable DHCP on one router

Both routers will by default run a DHCP server. You probably want to disable it on one of the boxes.

root@kladdkaka:~# /etc/init.d/dnsmasq disable
root@kladdkaka:~#

Restart router

After you have made your changes, try the new configuration by rebooting both devices.

root@kladdkaka:/etc/config# reboot

After 30 seconds or so, the devices should have connected via WDS and you should be able to ping the IP addresses of router A from router B and vice verse.

The default configuration is to bridge the wireless networks with the LAN ethernet sockets, so you can connect desktop machines etc and they should be able to reach all devices connected to the wireless network or the ethernet sockets on any of the two WDS connected routers.

Additional software

You can use opkg to install additional tools easily. First run opkg update to update the package list:

root@caramel:~# opkg update
Downloading http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/packages/Packages.gz
Connecting to downloads.openwrt.org (195.56.146.238:80)
Packages.gz          100% |*******************************|   130k 00:00:00 ETA
Inflating http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/snapshots
root@caramel:~#

Use opkg list to list all available packages.

Useful tools to install on a typical router includes avahi-daemon, miniupnpd, and openntpd.

Avahi allows DNS based service discovery. Install and enable as follows:

root@caramel:~# opkg install avahi-daemon
Installing avahi-daemon (0.6.23-2) to root...
Downloading http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/packages/avahi-daemon_0.6.23-2_mipsel.ipk
Connecting to downloads.openwrt.org (195.56.146.238:80)
avahi-daemon_0.6.23- 100% |*******************************| 19698  00:00:00 ETA
Installing libavahi (0.6.23-2) to root...
Downloading http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/packages/libavahi_0.6.23-2_mipsel.ipk
Connecting to downloads.openwrt.org (195.56.146.238:80)
libavahi_0.6.23-2_mi 100% |*******************************| 69773  00:00:00 ETA
Installing libdaemon (0.12-1) to root...
Downloading http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/packages/libdaemon_0.12-1_mipsel.ipk
Connecting to downloads.openwrt.org (195.56.146.238:80)
libdaemon_0.12-1_mip 100% |*******************************|  8352  --:--:-- ETA
Installing libpthread (0.9.29-14.1) to root...
Downloading http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/packages/libpthread_0.9.29-14.1_mipsel.ipk
Connecting to downloads.openwrt.org (195.56.146.238:80)
libpthread_0.9.29-14 100% |*******************************| 19278  00:00:00 ETA
Installing libexpat (1.95.8-1) to root...
Downloading http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/packages/libexpat_1.95.8-1_mipsel.ipk
Connecting to downloads.openwrt.org (195.56.146.238:80)
libexpat_1.95.8-1_mi 100% |*******************************| 47267  00:00:00 ETA
Configuring avahi-daemon
Configuring libavahi
Configuring libdaemon
Configuring libexpat
Configuring libpthread
root@caramel:~# /etc/init.d/avahi-daemon enable
root@caramel:~#

Bittorrent clients, for example, can use UPnP to open up ports in the firewall. For this to work, you need a UPnP server on your router:

root@caramel:~# opkg install miniupnpd luci-app-upnp
Installing miniupnpd (1.1-5) to root...
Downloading http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/packages/miniupnpd_1.1-5_mipsel.ipk
Connecting to downloads.openwrt.org (195.56.146.238:80)
miniupnpd_1.1-5_mips 100% |*******************************| 36923  00:00:00 ETA
Installing luci-app-upnp (0.8.7-1) to root...
Downloading http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/packages/luci-app-upnp_0.8.7-1_mipsel.ipk
Connecting to downloads.openwrt.org (195.56.146.238:80)
luci-app-upnp_0.8.7- 100% |*******************************|  2748  00:00:00 ETA
Configuring luci-app-upnp
Configuring miniupnpd
root@caramel:~# /etc/init.d/miniupnpd enable
root@caramel:~#

The clock will typically be way off unless you set it. Install a NTP client to automate this. (The package openntpd also works but takes more space.)

root@caramel:~# opkg install luci-app-ntpc
Installing luci-app-ntpc (0.8.7-1) to root...
Downloading http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/packages/luci-app-ntpc_0.8.7-1_mipsel.ipk
Connecting to downloads.openwrt.org (195.56.146.238:80)
luci-app-ntpc_0.8.7- 100% |*******************************|  2894  00:00:00 ETA
Installing ntpclient (2007_365-1) to root...
Downloading http://downloads.openwrt.org/kamikaze/8.09.1/brcm-2.4/packages/ntpclient_2007_365-1_mipsel.ipk
Connecting to downloads.openwrt.org (195.56.146.238:80)
ntpclient_2007_365-1 100% |*******************************| 12512  00:00:00 ETA
Configuring luci-app-ntpc
Configuring ntpclient
root@caramel:~#

[zz] Running Debian on ASUS WL-500W

2009-07-15T15:38:00.000-07:00

http://wpkg.org/Running_Debian_on_ASUS_WL-500W

From WPKG | Open Source Software Deployment and Distribution

This initial page is based on Running_Debian_on_ASUS_WL-500G_deluxe.
Please bear in mind this page is under construction and depends also on other enthousiasts who contribute to make this page in final stage
It would be nice to see detailed instructions to get the wireless to work properly and to include a good web frontend

[hide]

[edit] Installing Ubuntu linux

Install your favourite linux distro, but make sure you can compile and also Internet should be available; Below are instructions for ubuntu8.04 server

login with your username
sudo su
vi /etc/apt/sources.list and comment # all deb cdrom: entries and uncomment all deb http: ones
:wq! to save file en exit

run update/upgrade:

apt-get update
apt-get upgrade
apt-get install tftp subversion make unzip flex patch autoconf bison zlib1g-dev libncurses5-dev gawk g++
exit (to return from super user to user)

[edit] Flashing the kernel

The kernel image was built using OpenWRT buildroot (kamikaze, revision 6580 from 2007-Apr-03). It is 2.6.19.2, and has built-in SCSI, USB and ext3 support (to be able to boot from USB devices). To flash the image, use tftp. Start tftp program and point it to the IP of your ASUS device (192.168.1.1). Press the "restore" button and power on your device. Next step is to upload the image "openwrt-brcm-2.6-jffs2-128k.trx".

wget -P . http://www1.wpkg.org/debian-asus/openwrt-brcm47xx-2.6-jffs2-128k.trx

tftp 192.168.1.1
tftp> binary
tftp> trace
Packet tracing on.
tftp> put openwrt-brcm-2.6-jffs2-128k.trx
(...)

[edit] Writing Debian on your USB device

Download Debian base system and uncompress it to the /dev/sdb1, ext3-formatted partition, (so that you have /bin, /etc and all other directories at the top-dir of this partition). Make sure to use tune2fs on /dev/sda1 partition:

Plug in the USB stick

sudo su
fdisk -l
fdisk /dev/sdb
* d   delete a partition
* n   add a new partition
* p    primary partition (1-4)
* 1    Partition number (1-4): 1
* 1    First cylinder (1-1015, default 1):
* 1015 Last cylinder or +size or +sizeM or +sizeK (1-1015, default 1015):
* w   write table to disk and exit 
mkfs.ext3 /dev/sdb1

mkdir /media/usb-drive
mount -t ext3 /dev/sdb1 /media/usb-drive
df -h

cd $HOME
mkdir debian
cd debian
wget -P . http://www1.wpkg.org/debian-asus/debian-mipsel-2007-Apr-17.tar.bz2
tar xvfj debian-mipsel-2007-Apr-17.tar.bz2
cp -R mnt/debian-asus/* /media/usb-drive

Make sure the USB stick will not be checked by e2fsck - otherwise, the device might not boot at all!

tune2fs -c0 -i0 /dev/sdb1

WARNING!
When I said use tune2fs, I meant it:

Will now check root file system:fsck 1.40-WIP (14-Nov-2006)
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/sda1
/dev/sda1: Superblock last mount time is in the future.  FIXED.
/dev/sda1: Superblock last write time is in the future.  FIXED.
/dev/sda1 has gone 49710 days without being checked, check forced.
/dev/sda1: ***** REBOOT LINUX *****
/dev/sda1: 9030/56224 files (0.6% non-contiguous), 167947/224876 blocks
fsck died with exit status 3
failed!
* The file system check corrected errors on the root partition
but requested that the system be restarted.
* The system will be restarted in 5 seconds.

This means, your system will loop endlessly after checking the filesystem. This is because these devices don't have a battery-backed clock/rtc.

[edit] Configuring network

You will have to configure your network in the following files:

vi /media/usb-drive/etc/network/interfaces - to configure your network
- NOTE! By default, SSH listens on 192.168.10.55 and 192.168.11.178, so make sure to change the network settings appropriately.
vi /media/usb-drive/etc/resolv.conf - configure DNS (either 192.168.1.1 or DNS from ISP)
vi /media/usb-drive/etc/hostname - the hostname of your machine

[edit] Booting

When you completed previous steps you should be able to boot your ASUS to a fully-working Debian.
It doesn't matter which USB port you choose (unless you connect more devices).

You can log in via SSH, or consoles: USB or serial (check /etc/inittab to see console settings). If you didn't change the network settings, SSH listens on 192.168.10.55 and 192.168.11.178 (available via LAN or WAN interfaces, so check both before reporting problems).
The default password for the "root" user is "toor", and of course you are encouraged to change it.

You should see something like:

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

asus-debian:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 477M 164M 288M 37% /
tmpfs 15M 0 15M 0% /lib/init/rw
udev 10M 12K 10M 1% /dev
tmpfs 15M 4.0K 15M 1% /dev/shm
none 15M 0 15M 0% /tmp
asus-debian:~#

[edit] Building your own kernel

The author used revision 6850, however since it does not contain the WiFi for Asus 500W in this tutorial the latest revision from subversion will be extracted to build your own MIPS kernel. This should work in the end with Asus WL500-W BroadCom's 4704 Ethernet and BroadCom's 4321 WiFi on kernel 2.6.

1. Go to $HOME and download openwrt build environment

cd $HOME
svn checkout https://svn.openwrt.org/openwrt/trunk/

2. Go to trunk/ directory, and select all the required tools:

cd trunk
make menuconfig

From this step onward I am currently testing with the original doc, please feel free to update accordingly!

Make sure the first three options will look like:

"Target System (Broadcom BCM947xx/953xx [2.6])"
"Target Profile (Broadcom BCM43xx WiFi)" and
"Target Images" needs be set to "jffs2".

As we want to use Debian only we don't need any OpenWRT packages. This will make our .trx image build faster and it'll be smaller too; the next six options need to be deselected:

"Select all packages by default"
"Advanced configuration options"
"Buildsystem settings"
"Build the OpenWRT Image Builder"
"Build the OpenWRT SDK"
"Image Configuration"

Leave one package enabled as it will be needed to build the .trx firmware (otherwise, .trx image will be "empty", and won't build)

"Base system -> base-files"

Deselect all packages in:

"Network"
"Libraries"
"IPv6"
"Kernel modules"
"Boot Loaders"
"Utilities"
"Languages"

3. Now, Exit, build all the tools needed for cross-compilation, and a (not yet configured) kernel.
This steps takes quite a while so go and do something else:

make V=99

4. When all the tools are made, copy the .config file to trunk/build_dir/linux-brcm47xx/linux-2.6.x executing

cd $HOME/trunk/build_dir/linux-brcm47xx/linux-2.6.23.16
mv .config .config.backup
wget -P . http://www1.wpkg.org/debian-asus/.config

5. Configure the kernel according to your preference:

make ARCH=mips oldconfig
> 3. Support for BCM947xx based boards (BCM947XX)


Endianess selection
> 1. Little endian (CPU_LITTLE_ENDIAN)
choice[1]: 1
*
* CPU selection
*
CPU type
> 1. MIPS32 Release 1 (CPU_MIPS32_R1)
choice[1]: 1
*
* Kernel type
*
Kernel code model
> 1. 32-bit kernel (32BIT)
choice[1]: 1
Kernel page size
> 1. 4kB (PAGE_SIZE_4KB)
 2. 16kB (PAGE_SIZE_16KB)
 3. 64kB (PAGE_SIZE_64KB)
choice[1-3]: 1
MIPS MT options
> 1. Disable multithreading support. (MIPS_MT_DISABLED)
choice[1]: 1
Memory model
> 1. Flat Memory (FLATMEM_MANUAL)
choice[1]: 1
64 bit Memory and IO resources (EXPERIMENTAL) (RESOURCES_64BIT) [N/y/?] n
Timer frequency
 1. 100 HZ (HZ_100)
 2. 128 HZ (HZ_128)
> 3. 250 HZ (HZ_250)
 4. 256 HZ (HZ_256)
 5. 1000 HZ (HZ_1000)
 6. 1024 HZ (HZ_1024)
choice[1-6?]: 3
Preemption Model
> 1. No Forced Preemption (Server) (PREEMPT_NONE)
 2. Voluntary Kernel Preemption (Desktop) (PREEMPT_VOLUNTARY)
 3. Preemptible Kernel (Low-Latency Desktop) (PREEMPT)
choice[1-3]: 1
Kexec system call (EXPERIMENTAL) (KEXEC) [N/y/?] (NEW)

Answer "n" on "Kexec system call (EXPERIMENTAL) (KEXEC) [N/y/?] (NEW)"
Answer "y" on "Enable seccomp to safely compute untrusted bytecode (SECCOMP) [Y/n/?] (NEW)"

*
* General setup
*
Prompt for development and/or incomplete code/drivers (EXPERIMENTAL) [Y/n/?] y
Local version - append to kernel release (LOCALVERSION) []
Automatically append version information to the version string (LOCALVERSION_AUTO) [Y/n/?] y
Support for paging of anonymous memory (swap) (SWAP) [Y/n/?] y
System V IPC (SYSVIPC) [Y/n/?] y
POSIX Message Queues (POSIX_MQUEUE) [N/y/?] n
BSD Process Accounting (BSD_PROCESS_ACCT) [N/y/?] n
Export task/process statistics through netlink (EXPERIMENTAL) (TASKSTATS) [N/y/?] n
User Namespaces (EXPERIMENTAL) (USER_NS) [N/y/?] (NEW)

Answer "n" on "User Namespaces (EXPERIMENTAL) (USER_NS) [N/y/?] (NEW)"

Auditing support (AUDIT) [N/y/?] n
Kernel .config support (IKCONFIG) [Y/n/m/?] y
Enable access to .config through /proc/config.gz (IKCONFIG_PROC) [Y/n/?] y
Kernel log buffer size (16 => 64KB, 17 => 128KB) (LOG_BUF_SHIFT) [14] 14
Create deprecated sysfs files (SYSFS_DEPRECATED) [Y/n/?] (NEW)

Answer "y" on "Create deprecated sysfs files (SYSFS_DEPRECATED) [Y/n/?] (NEW)"

Kernel->user space relay support (formerly relayfs) (RELAY) [N/y/?] n
Initial RAM filesystem and RAM disk (initramfs/initrd) support (BLK_DEV_INITRD) [Y/n/?] y
 Initramfs source file(s) (INITRAMFS_SOURCE) []
Optimize for size (Look out for broken compilers!) (CC_OPTIMIZE_FOR_SIZE) [Y/n/?] y
*
* Configure standard kernel features (for small systems)
*
Configure standard kernel features (for small systems) (EMBEDDED) [Y/?] y
 Sysctl syscall support (SYSCTL_SYSCALL) [Y/n/?] y
 Load all symbols for debugging/ksymoops (KALLSYMS) [N/y/?] n
 Support for hot-pluggable devices (HOTPLUG) [Y/n/?] y
 Enable support for printk (PRINTK) [Y/n/?] y
 BUG() support (BUG) [Y/n/?] y
 Enable ELF core dumps (ELF_CORE) [N/y/?] n
 Enable full-sized data structures for core (BASE_FULL) [Y/n/?] y
 Enable futex support (FUTEX) [Y/n/?] y
Enable eventpoll support (EPOLL) [Y/n/?] y
Enable signalfd() system call (SIGNALFD) [Y/n/?] (NEW)

Answer "y" on "Enable signalfd() system call (SIGNALFD) [Y/n/?] (NEW)"
Answer "y" on "Enable eventfd() system call (EVENTFD) [Y/n/?] (NEW)"

Use full shmem filesystem (SHMEM) [Y/n/?] y
Enable VM event counters for /proc/vmstat (VM_EVENT_COUNTERS) [N/y/?] n
Choose SLAB allocator
> 1. SLAB (SLAB)
 2. SLUB (Unqueued Allocator) (SLUB) (NEW)
 3. SLOB (Simple Allocator) (SLOB)

Answer "1" to select "SLAB"

*
* Enable loadable module support
*
Enable loadable module support (MODULES) [Y/n/?] y
 Module unloading (MODULE_UNLOAD) [Y/n/?] y
   Forced module unloading (MODULE_FORCE_UNLOAD) [N/y/?] n
 Module versioning support (MODVERSIONS) [N/y/?] n
 Source checksum for all modules (MODULE_SRCVERSION_ALL) [N/y/?] n
 Automatic kernel module loading (KMOD) [Y/n/?] y
*
* Enable the block layer
*
Enable the block layer (BLOCK) [Y/n/?] y
 Support for Large Block Devices (LBD) [N/y/?] n
 Support for tracing block io actions (BLK_DEV_IO_TRACE) [N/y/?] n
 Support for Large Single Files (LSF) [N/y/?] n
 Block layer SG support v4 (EXPERIMENTAL) (BLK_DEV_BSG) [N/y/?] (NEW)

Answer "n" on "Block layer SG support v4 (EXPERIMENTAL) (BLK_DEV_BSG) [N/y/?] (NEW)"

*
* Support for PCI Hotplug (EXPERIMENTAL)
*
Support for PCI Hotplug (EXPERIMENTAL) (HOTPLUG_PCI) [N/m/y/?] n
*
* Executable file formats
*
Kernel support for ELF binaries (BINFMT_ELF) [Y/n/?] y
Kernel support for MISC binaries (BINFMT_MISC) [N/m/y/?] n
*
* Power management options
*
Power Management support (PM) [N/y/?] (NEW)

Answer "y" on "Power Management support (PM) [N/y/?] (NEW)"
Answer "y" on "Legacy Power Management API (DEPRECATED) (PM_LEGACY) [N/y/?] (NEW)"
Answer "n" on "Power Management Debug Support (PM_DEBUG) [N/y/?] (NEW)"
Answer "n" on "Suspend to RAM and standby (SUSPEND) [Y/n/?] (NEW)"

*
* Networking
*
Networking support (NET) [Y/n/?] y
 *
 * Networking options
 *
 Packet socket (PACKET) [Y/n/m/?] y
   Packet socket: mmapped IO (PACKET_MMAP) [Y/n/?] y
 Unix domain sockets (UNIX) [Y/n/m/?] y
 PF_KEY sockets (NET_KEY) [N/m/y/?] n
 TCP/IP networking (INET) [Y/n/?] y
   IP: multicasting (IP_MULTICAST) [N/y/?] n
   IP: advanced router (IP_ADVANCED_ROUTER) [N/y/?] n
   IP: kernel level autoconfiguration (IP_PNP) [N/y/?] n
   IP: tunneling (NET_IPIP) [N/m/y/?] n
   IP: GRE tunnels over IP (NET_IPGRE) [N/m/y/?] n
   IPSEC NAT-Traversal (KLIPS compatible) (IPSEC_NAT_TRAVERSAL) [N/y/?] n
   IP: ARP daemon support (EXPERIMENTAL) (ARPD) [N/y/?] n
   IP: TCP syncookie support (disabled per default) (SYN_COOKIES) [N/y/?] n
   IP: AH transformation (INET_AH) [N/m/y/?] n
   IP: ESP transformation (INET_ESP) [N/m/y/?] n
   IP: IPComp transformation (INET_IPCOMP) [N/m/y/?] n
   IP: IPsec transport mode (INET_XFRM_MODE_TRANSPORT) [N/m/y/?] n
   IP: IPsec tunnel mode (INET_XFRM_MODE_TUNNEL) [N/m/y/?] n
   IP: IPsec BEET mode (INET_XFRM_MODE_BEET) [N/m/y/?] n
   INET: socket monitoring interface (INET_DIAG) [M/n/y/?] m
   *
   * TCP: advanced congestion control
   *
   TCP: advanced congestion control (TCP_CONG_ADVANCED) [N/y/?] n
   TCP: MD5 Signature Option support (RFC2385) (EXPERIMENTAL) (TCP_MD5SIG) [N/y/?] (NEW)

Answer "n" on "TCP: MD5 Signature Option support (RFC2385) (EXPERIMENTAL) (TCP_MD5SIG) [N/y/?] (NEW)"

    *
   * IP virtual server support (EXPERIMENTAL)
   *
   IP virtual server support (EXPERIMENTAL) (IP_VS) [N/m/y/?] n
   The IPv6 protocol (IPV6) [N/m/y/?] n
 Security Marking (NETWORK_SECMARK) [N/y/?] n
 *
 * Network packet filtering framework (Netfilter)
 *
 Network packet filtering framework (Netfilter) (NETFILTER) [Y/n/?] y
   Network packet filtering debugging (NETFILTER_DEBUG) [N/y/?] n
   Bridged IP/ARP packets filtering (BRIDGE_NETFILTER) [N/y/?] n
   *
   * Core Netfilter Configuration
   *
   Netfilter netlink interface (NETFILTER_NETLINK) [N/m/y/?] n
   Netfilter connection tracking support (NF_CONNTRACK_ENABLED) [N/m/y/?] (NEW)

Answer "m" on "Netfilter connection tracking support (NF_CONNTRACK_ENABLED) [N/m/y/?] (NEW)"
Answer "n" on "Connection tracking flow accounting (NF_CT_ACCT) [N/y/?] (NEW)"
Answer "n" on "Connection tracking events (EXPERIMENTAL) (NF_CONNTRACK_EVENTS) [N/y/?] (NEW)"
Answer "n" on "SCTP protocol connection tracking support (EXPERIMENTAL) (NF_CT_PROTO_SCTP) [N/m/?] (NEW)"
Answer "n" on "UDP-Lite protocol connection tracking support (EXPERIMENTAL) (NF_CT_PROTO_UDPLITE) [N/m/?] (NEW)"
Answer "n" on "Amanda backup protocol support (NF_CONNTRACK_AMANDA) [N/m/?] (NEW)"
Answer "m" on "FTP protocol support (NF_CONNTRACK_FTP) [N/m/?] (NEW)"
Answer "m" on "H.323 protocol support (EXPERIMENTAL) (NF_CONNTRACK_H323) [N/m/?] (NEW)"
Answer "m" on "IRC protocol support (NF_CONNTRACK_IRC) [N/m/?] (NEW)"
Answer "n" on "NetBIOS name service protocol support (EXPERIMENTAL) (NF_CONNTRACK_NETBIOS_NS) [N/m/?] (NEW)"
Answer "m" on "PPtP protocol support (NF_CONNTRACK_PPTP) [N/m/?] (NEW)"
Answer "n" on "SANE protocol support (EXPERIMENTAL) (NF_CONNTRACK_SANE) [N/m/?] (NEW)"
Answer "m" on "SIP protocol support (EXPERIMENTAL) (NF_CONNTRACK_SIP) [N/m/?] (NEW)"
Answer "m" on "TFTP protocol support (NF_CONNTRACK_TFTP) [N/m/?] (NEW)"
Answer "n" on "RTSP protocol support (NF_CONNTRACK_RTSP) [N/m/?] (NEW)"
Answer "n" on "NFLOG" target support (NETFILTER_XT_TARGET_NFLOG) [N/m/y/?] (NEW)"
Answer "n" on "TRACE" target support (NETFILTER_XT_TARGET_TRACE) [N/m/?] (NEW)"
Answer "n" on "TARPIT" target support (NETFILTER_XT_TARGET_TARPIT) [N/m/y/?] (NEW)"
Answer "n" on "TCPMSS" target support (NETFILTER_XT_TARGET_TCPMSS) [N/m/y/?] (NEW)"
Answer "n" on "connlimit" match support" (NETFILTER_XT_MATCH_CONNLIMIT) [N/m/?] (NEW)"
Answer "n" on "u32" match support (NETFILTER_XT_MATCH_U32) [N/m/y/?] (NEW)"
Answer "n" on "hashlimit" match support (NETFILTER_XT_MATCH_HASHLIMIT) [N/m/y/?] (NEW)"
Answer "m" on "IPv4 connection tracking support (required for NAT) (NF_CONNTRACK_IPV4) [N/m/?] (NEW)"
Answer "y" on "proc/sysctl compatibility with old connection tracking (NF_CONNTRACK_PROC_COMPAT) [Y/n/?] (NEW)"
Answer "m" on "Full NAT (NF_NAT) [N/m/?] (NEW)"
Answer "n" on "Basic SNMP-ALG support (EXPERIMENTAL) (NF_NAT_SNMP_BASIC) [N/m/?] (NEW)"
Answer "n" on "ipporthash set support (IP_NF_SET_IPPORTHASH) [N/m/?] (NEW)"
Answer "n" on "iptreemap set support (IP_NF_SET_IPTREEMAP) [N/m/?] (NEW)"

set match support (IP_NF_MATCH_SET) [M/n/?] m
     SET target support (IP_NF_TARGET_SET) [M/n/?] m
   ROUTE target support (IP_NF_TARGET_ROUTE) [M/n/y/?] m
   *
   * Bridge: Netfilter Configuration
   *
   Ethernet Bridge tables (ebtables) support (BRIDGE_NF_EBTABLES) [M/n/y/?] m
     ebt: broute table support (BRIDGE_EBT_BROUTE) [M/n/?] m
     ebt: filter table support (BRIDGE_EBT_T_FILTER) [M/n/?] m
     ebt: nat table support (BRIDGE_EBT_T_NAT) [M/n/?] m
     ebt: 802.3 filter support (BRIDGE_EBT_802_3) [M/n/?] m
     ebt: among filter support (BRIDGE_EBT_AMONG) [M/n/?] m
     ebt: ARP filter support (BRIDGE_EBT_ARP) [M/n/?] m
     ebt: IP filter support (BRIDGE_EBT_IP) [M/n/?] m
     ebt: limit match support (BRIDGE_EBT_LIMIT) [M/n/?] m
     ebt: mark filter support (BRIDGE_EBT_MARK) [M/n/?] m
     ebt: packet type filter support (BRIDGE_EBT_PKTTYPE) [M/n/?] m
     ebt: STP filter support (BRIDGE_EBT_STP) [M/n/?] m
     ebt: 802.1Q VLAN filter support (BRIDGE_EBT_VLAN) [M/n/?] m
     ebt: arp reply target support (BRIDGE_EBT_ARPREPLY) [M/n/?] m
     ebt: dnat target support (BRIDGE_EBT_DNAT) [M/n/?] m
     ebt: mark target support (BRIDGE_EBT_MARK_T) [M/n/?] m
     ebt: redirect target support (BRIDGE_EBT_REDIRECT) [M/n/?] m
     ebt: snat target support (BRIDGE_EBT_SNAT) [M/n/?] m
     ebt: log support (BRIDGE_EBT_LOG) [M/n/?] m
     ebt: ulog support (OBSOLETE) (BRIDGE_EBT_ULOG) [M/n/?] m
 *
 * The DCCP Protocol (EXPERIMENTAL)
 *
 The DCCP Protocol (EXPERIMENTAL) (IP_DCCP) [N/m/y/?] n
 *
 * The SCTP Protocol (EXPERIMENTAL)
 *
 The SCTP Protocol (EXPERIMENTAL) (IP_SCTP) [N/m/y/?] n
 *
 * The TIPC Protocol (EXPERIMENTAL)
 *
 The TIPC Protocol (EXPERIMENTAL) (TIPC) [N/m/y/?] n
 Asynchronous Transfer Mode (ATM) (EXPERIMENTAL) (ATM) [M/n/y/?] m
   Classical IP over ATM (EXPERIMENTAL) (ATM_CLIP) [M/n/?] m
     Do NOT send ICMP if no neighbour (EXPERIMENTAL) (ATM_CLIP_NO_ICMP) [Y/n/?] y
   LAN Emulation (LANE) support (EXPERIMENTAL) (ATM_LANE) [M/n/?] m
     Multi-Protocol Over ATM (MPOA) support (EXPERIMENTAL) (ATM_MPOA) [M/n/?] m
   RFC1483/2684 Bridged protocols (ATM_BR2684) [M/n/?] m
     Per-VC IP filter kludge (ATM_BR2684_IPFILTER) [Y/n/?] y
 802.1d Ethernet Bridging (BRIDGE) [Y/n/m/?] y
 802.1Q VLAN Support (VLAN_8021Q) [Y/n/m/?] y
 DECnet Support (DECNET) [N/m/y/?] n
 ANSI/IEEE 802.2 LLC type 2 Support (LLC2) [N/m/y/?] n
 The IPX protocol (IPX) [N/m/y/?] n
 Appletalk protocol support (ATALK) [N/m/y/?] n
 CCITT X.25 Packet Layer (EXPERIMENTAL) (X25) [N/m/y/?] n
 LAPB Data Link Driver (EXPERIMENTAL) (LAPB) [N/m/y/?] n
 Acorn Econet/AUN protocols (EXPERIMENTAL) (ECONET) [N/m/y/?] n
 WAN router (WAN_ROUTER) [N/m/y/?] n
 *
 * QoS and/or fair queueing
 *
 QoS and/or fair queueing (NET_SCHED) [Y/n/?] y
 *
 * Queueing/Scheduling
 *
 Class Based Queueing (CBQ) (NET_SCH_CBQ) [M/n/y/?] m
 Hierarchical Token Bucket (HTB) (NET_SCH_HTB) [M/n/y/?] m
 Hierarchical Fair Service Curve (HFSC) (NET_SCH_HFSC) [M/n/y/?] m
 ATM Virtual Circuits (ATM) (NET_SCH_ATM) [M/n/?] m
 Multi Band Priority Queueing (PRIO) (NET_SCH_PRIO) [M/n/y/?] m
 Multi Band Round Robin Queuing (RR) (NET_SCH_RR) [N/m/y/?] (NEW)

Answer "m" on "Multi Band Round Robin Queuing (RR) (NET_SCH_RR) [N/m/y/?] (NEW)"
Answer "n" on "Connection Tracking Hash Types (NET_SCH_ESFQ_NFCT) [N/y/?] (NEW)"
Answer "n" on "Generic actions (NET_ACT_GACT) [N/m/y/?] (NEW)"
Answer "n" on "Redirecting and Mirroring (NET_ACT_MIRRED) [N/m/y/?] (NEW)"
Answer "n" on "IPtables targets (NET_ACT_IPT) [N/m/y/?] (NEW)"
Answer "n" on "Packet Editing (NET_ACT_PEDIT) [N/m/y/?] (NEW)"
Answer "n" on "Simple Example (Debug) (NET_ACT_SIMP) [N/m/y/?] (NEW)"

 *
* Classification
*
 Elementary classification (BASIC) (NET_CLS_BASIC) [M/n/y/?] m
 Traffic-Control Index (TCINDEX) (NET_CLS_TCINDEX) [M/n/y/?] m
 Routing decision (ROUTE) (NET_CLS_ROUTE4) [M/n/y/?] m
 Netfilter mark (FW) (NET_CLS_FW) [M/n/y/?] m
 Universal 32bit comparisons w/ hashing (U32) (NET_CLS_U32) [M/n/y/?] m
   Performance counters support (CLS_U32_PERF) [N/y/?] n
   Netfilter marks support (CLS_U32_MARK) [N/y/?] n
 IPv4 Resource Reservation Protocol (RSVP) (NET_CLS_RSVP) [M/n/y/?] m
 IPv6 Resource Reservation Protocol (RSVP6) (NET_CLS_RSVP6) [M/n/y/?] m
 Extended Matches (NET_EMATCH) [N/y/?] n
 Actions (NET_CLS_ACT) [Y/?] y
   Traffic Policing (NET_ACT_POLICE) [Y/?] (NEW) y
   Generic actions (NET_ACT_GACT) [N/m/y/?] (NEW) n
   Redirecting and Mirroring (NET_ACT_MIRRED) [N/m/y/?] (NEW) n
   IPtables targets (NET_ACT_IPT) [N/m/y/?] (NEW) n
   Packet Editing (NET_ACT_PEDIT) [N/m/y/?] (NEW) n
   Simple Example (Debug) (NET_ACT_SIMP) [N/m/y/?] (NEW) n
 Traffic Policing (obsolete) (NET_CLS_POLICE) [Y/n/?] y
 Incoming device classification (NET_CLS_IND) [N/y/?] n
*
* Network testing
*
 Packet Generator (USE WITH CAUTION) (NET_PKTGEN) [N/m/y/?] n
*
* Amateur Radio support
*
 Amateur Radio support (HAMRADIO) [Y/n/?] y
  *
  * Packet Radio protocols
  *
   Amateur Radio AX.25 Level 2 protocol (AX25) [M/n/y/?] m
     AX.25 DAMA Slave support (AX25_DAMA_SLAVE) [N/y/?] n
     Amateur Radio NET/ROM protocol (NETROM) [N/m/?] n
     Amateur Radio X.25 PLP (Rose) (ROSE) [N/m/?] n
     *
     * AX.25 network device drivers
     *
     Serial port KISS driver (MKISS) [M/n/?] m
     Serial port 6PACK driver (6PACK) [N/m/?] n
     BPQ Ethernet driver (BPQETHER) [N/m/?] n
     BAYCOM ser12 fullduplex driver for AX.25 (BAYCOM_SER_FDX) [N/m/?] n
     BAYCOM ser12 halfduplex driver for AX.25 (BAYCOM_SER_HDX) [N/m/?] n
     YAM driver for AX.25 (YAM) [N/m/?] n
 *
 * IrDA (infrared) subsystem support
 *
 IrDA (infrared) subsystem support (IRDA) [N/m/y/?] n
 *
 * Bluetooth subsystem support
 *
 Bluetooth subsystem support (BT) [M/n/y/?] m
   L2CAP protocol support (BT_L2CAP) [M/n/?] m
   SCO links support (BT_SCO) [M/n/?] m
   RFCOMM protocol support (BT_RFCOMM) [M/n/?] m
     RFCOMM TTY support (BT_RFCOMM_TTY) [Y/n/?] y
   BNEP protocol support (BT_BNEP) [M/n/?] m
     Multicast filter support (BT_BNEP_MC_FILTER) [Y/n/?] y
     Protocol filter support (BT_BNEP_PROTO_FILTER) [Y/n/?] y
   *
   * Bluetooth device drivers
   *
   HCI USB driver (BT_HCIUSB) [M/n/?] m
     SCO (voice) support (BT_HCIUSB_SCO) [Y/n/?] y
   HCI UART driver (BT_HCIUART) [M/n/?] m
     UART (H4) protocol support (BT_HCIUART_H4) [Y/n/?] y
     BCSP protocol support (BT_HCIUART_BCSP) [Y/n/?] y
   HCI BCM203x USB driver (BT_HCIBCM203X) [N/m/?] n
   HCI BPA10x USB driver (BT_HCIBPA10X) [N/m/?] n
   HCI BlueFRITZ! USB driver (BT_HCIBFUSB) [N/m/?] n
   HCI VHCI (Virtual HCI device) driver (BT_HCIVHCI) [N/m/?] n
 RxRPC session sockets (AF_RXRPC) [N/m/y/?] (NEW)

Answer "n" on "RxRPC session sockets (AF_RXRPC) [N/m/y/?] (NEW)"

 *
* Wireless
*
Improved wireless configuration API (CFG80211) [N/m/y] (NEW)

Answer "y" on "Improved wireless configuration API (CFG80211) [N/m/y] (NEW)"
Answer "n" on "Generic IEEE 802.11 Networking Stack (mac80211) (MAC80211) [N/m/y/?] (NEW)"

  Generic IEEE 802.11 Networking Stack (IEEE80211) [M/n/y/?] m
  Enable full debugging output (IEEE80211_DEBUG) [N/y/?] n
  IEEE 802.11 WEP encryption (802.1x) (IEEE80211_CRYPT_WEP) [M/?] m
  IEEE 802.11i CCMP support (IEEE80211_CRYPT_CCMP) [M/n/?] m
  IEEE 802.11i TKIP encryption (IEEE80211_CRYPT_TKIP) [M/n/?] m
  Software MAC add-on to the IEEE 802.11 networking stack (IEEE80211_SOFTMAC) [M/n/?] m
    Enable full debugging output (IEEE80211_SOFTMAC_DEBUG) [N/y] n
*
* RF switch subsystem support
*
RF switch subsystem support (RFKILL) [N/m/y/?] (NEW)

Answer "n" on "RF switch subsystem support (RFKILL) [N/m/y/?] (NEW)"
Answer "n" on "Plan 9 Resource Sharing Support (9P2000) (Experimental) (NET_9P) [N/m/y/?] (NEW)"

*
* Device Drivers
*
*
* Generic Driver Options
*
Select only drivers that don't need compile-time external firmware (STANDALONE) [Y/n/?] y
Prevent firmware from being built (PREVENT_FIRMWARE_BUILD) [Y/n/?] y
Userspace firmware loading support (FW_LOADER) [Y/m/?] y
*
* Connector - unified userspace <-> kernelspace linker
*
Connector - unified userspace <-> kernelspace linker (CONNECTOR) [M/n/y/?] m
*
* Memory Technology Device (MTD) support
*
Memory Technology Device (MTD) support (MTD) [Y/n/m/?] y
 Debugging (MTD_DEBUG) [N/y/?] n
 MTD concatenating support (MTD_CONCAT) [N/m/y/?] n
 MTD partitioning support (MTD_PARTITIONS) [Y/n/?] y
  Automatically set 'rootfs' partition to be root filesystem (MTD_ROOTFS_ROOT_DEV) [Y/n] (NEW)

Answer "y" on "Automatically set 'rootfs' partition to be root filesystem (MTD_ROOTFS_ROOT_DEV) [Y/n] (NEW)"
Answer "y" on "Automatically split 'rootfs' partition for squashfs (MTD_ROOTFS_SPLIT) [Y/n] (NEW)"

   RedBoot partition table parsing (MTD_REDBOOT_PARTS) [N/m/y/?] n
  Command line partition table parsing (MTD_CMDLINE_PARTS) [N/y/?] n
*
* User Modules And Translation Layers
*
Direct char device access to MTD devices (MTD_CHAR) [Y/n/m/?] y
Common interface to block layer for MTD 'translation layers' (MTD_BLKDEVS) [Y] (NEW) y
Caching block device access to MTD devices (MTD_BLOCK) [Y/n/m/?] y
FTL (Flash Translation Layer) support (FTL) [N/m/y/?] n
NFTL (NAND Flash Translation Layer) support (NFTL) [N/m/y/?] n
INFTL (Inverse NAND Flash Translation Layer) support (INFTL) [N/m/y/?] n
Resident Flash Disk (Flash Translation Layer) support (RFD_FTL) [N/m/y/?] n
NAND SSFDC (SmartMedia) read only translation layer (SSFDC) [N/m/y/?] n
*
* RAM/ROM/Flash chip drivers
*
Detect flash chips by Common Flash Interface (CFI) probe (MTD_CFI) [Y/n/m/?] y
Detect non-CFI AMD/JEDEC-compatible flash chips (MTD_JEDECPROBE) [N/m/y/?] n
Flash chip driver advanced configuration options (MTD_CFI_ADV_OPTIONS) [N/y/?] n
Support for Intel/Sharp flash chips (MTD_CFI_INTELEXT) [Y/n/m/?] y
Support for AMD/Fujitsu flash chips (MTD_CFI_AMDSTD) [Y/n/m/?] y
Support for ST (Advanced Architecture) flash chips (MTD_CFI_STAA) [N/m/y/?] n
Support for RAM chips in bus mapping (MTD_RAM) [N/m/y/?] n
Support for ROM chips in bus mapping (MTD_ROM) [N/m/y/?] n
Support for absent chips in bus mapping (MTD_ABSENT) [N/m/y/?] n
*
* Mapping drivers for chip access
*
Support non-linear mappings of flash chips (MTD_COMPLEX_MAPPINGS) [Y/n/?] y
CFI Flash device in physical memory map (MTD_PHYSMAP) [N/m/y/?] n
BCM47xx flash device (MTD_BCM47XX) [Y/n/m/?] y
PCI MTD driver (MTD_PCI) [N/m/y/?] n
Map driver for platform device RAM (mtd-ram) (MTD_PLATRAM) [N/m/y/?] n
*
* Self-contained MTD device drivers
*
Ramix PMC551 PCI Mezzanine RAM card support (MTD_PMC551) [N/m/y/?] n
Uncached system RAM (MTD_SLRAM) [N/m/y/?] n
Physical system RAM (MTD_PHRAM) [N/m/y/?] n
Test driver using RAM (MTD_MTDRAM) [N/m/y/?] n
MTD using block device (MTD_BLOCK2MTD) [N/m/y/?] n
*
* Disk-On-Chip Device Drivers
*
M-Systems Disk-On-Chip 2000 and Millennium (DEPRECATED) (MTD_DOC2000) [N/m/y/?] n
M-Systems Disk-On-Chip Millennium-only alternative driver (DEPRECATED) (MTD_DOC2001) [N/m/y/?] n
M-Systems Disk-On-Chip Millennium Plus (MTD_DOC2001PLUS) [N/m/y/?] n
*
* NAND Device Support
*
NAND Device Support (MTD_NAND) [N/m/y/?] n
*
* OneNAND Device Support
*
OneNAND Device Support (MTD_ONENAND) [N/m/y/?] n
*
* UBI - Unsorted block images
*
Enable UBI (MTD_UBI) [N/m/y/?] (NEW)

Answer "n" on "Enable UBI (MTD_UBI) [N/m/y/?] (NEW)"

*
* Parallel port support
*
Parallel port support (PARPORT) [N/m/y/?] n
*
* Block devices
*
Block devices (BLK_DEV) [Y/n/?] (NEW)

Answer "y" on "Block devices (BLK_DEV) [Y/n/?] (NEW)"

  Compaq SMART2 support (BLK_CPQ_DA) [N/m/y/?] n
 Compaq Smart Array 5xxx support (BLK_CPQ_CISS_DA) [N/m/y/?] n
 Mylex DAC960/DAC1100 PCI RAID Controller support (BLK_DEV_DAC960) [N/m/y/?] n
 Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL) (BLK_DEV_UMEM) [N/m/y/?] n
 Loopback device support (BLK_DEV_LOOP) [M/n/y/?] m
   Cryptoloop Support (BLK_DEV_CRYPTOLOOP) [M/n/?] m
 Network block device support (BLK_DEV_NBD) [M/n/y/?] m
 Promise SATA SX8 support (BLK_DEV_SX8) [N/m/y/?] n
 Low Performance USB Block driver (BLK_DEV_UB) [N/m/y/?] n
 RAM disk support (BLK_DEV_RAM) [N/m/y/?] n
 Packet writing on CD/DVD media (CDROM_PKTCDVD) [N/m/y/?] n
 ATA over Ethernet support (ATA_OVER_ETH) [N/m/y/?] n
*
* Misc devices
*
Misc devices (MISC_DEVICES) [Y/n/?] (NEW)

Answer "y" on "Misc devices (MISC_DEVICES) [Y/n/?] (NEW)"
Answer "n" on "Sensable PHANToM (PHANTOM) [N/m/y/?] (NEW)"
Answer "n" on "EEPROM 93CX6 support (EEPROM_93CX6) [N/m/y/?] (NEW)"

SGI IOC4 Base IO support (SGI_IOC4) [N/m/y/?] n
 TI Flash Media interface support (EXPERIMENTAL) (TIFM_CORE) [N/m/y/?] n
*
* ATA/ATAPI/MFM/RLL support
*
ATA/ATAPI/MFM/RLL support (IDE) [N/m/y/?] n
*
* SCSI device support
*
RAID Transport Class (RAID_ATTRS) [N/m/y/?] n
SCSI device support (SCSI) [Y/n/m/?] y
SCSI target support (SCSI_TGT) [N/m/y/?] (NEW)

Answer "m" on "SCSI target support (SCSI_TGT) [N/m/y/?] (NEW)"
Answer "n" on "Asynchronous SCSI scanning (SCSI_SCAN_ASYNC) [N/y/?] (NEW)"
Answer "y" on "SCSI low-level drivers (SCSI_LOWLEVEL) [Y/n] (NEW)"
Answer "n" on "SCSI RDMA Protocol helper library (SCSI_SRP) [N/m/y/?] (NEW)"

*
* Serial ATA (prod) and Parallel ATA (experimental) drivers
*
Serial ATA (prod) and Parallel ATA (experimental) drivers (ATA) [N/m/y/?] n
*
* Multiple devices driver support (RAID and LVM)
*
Multiple devices driver support (RAID and LVM) (MD) [N/y/?] n
*
* Fusion MPT device support
*
Fusion MPT ScsiHost drivers for SPI (FUSION_SPI) [N/m/y/?] n
Fusion MPT ScsiHost drivers for FC (FUSION_FC) [N/m/y/?] n
Fusion MPT ScsiHost drivers for SAS (FUSION_SAS) [N/m/y/?] n
*
* IEEE 1394 (FireWire) support
*
IEEE 1394 (FireWire) support - alternative stack, EXPERIMENTAL (FIREWIRE) [N/m/y/?] (NEW)

Answer "n" on "IEEE 1394 (FireWire) support - alternative stack, EXPERIMENTAL (FIREWIRE) [N/m/y/?] (NEW)"

*
* I2O device support
*
I2O device support (I2O) [N/m/y/?] n
*
* Network device support
*
Network device support (NETDEVICES) [Y/n/?] y
 Netdevice multiple hardware queue support (NETDEVICES_MULTIQUEUE) [N/y/?] (NEW)

Answer "n" on "Netdevice multiple hardware queue support (NETDEVICES_MULTIQUEUE) [N/y/?] (NEW)"
Answer "n" on "Intermediate Functional Block support (IFB) [N/m/y/?] (NEW)"
Answer "n" on "MAC-VLAN support (EXPERIMENTAL) (MACVLAN) [N/m/y/?] (NEW)"

EQL (serial line load balancing) support (EQUALIZER) [N/m/y/?] n
 IMQ (intermediate queueing device) support (IMQ) [M/n/y/?] m
   IMQ behavior (PRE/POSTROUTING)
     1. IMQ AA (IMQ_BEHAVIOR_AA)
     2. IMQ AB (IMQ_BEHAVIOR_AB)
   > 3. IMQ BA (IMQ_BEHAVIOR_BA)
     4. IMQ BB (IMQ_BEHAVIOR_BB)
   choice[1-4?]: 3
   Number of IMQ devices (IMQ_NUM_DEVS) [2] 2
 Universal TUN/TAP device driver support (TUN) [M/n/y/?] m
 *
 * ARCnet support
 *
 ARCnet support (ARCNET) [N/m/y/?] n
 *
 * PHY Device support and infrastructure
 *
 PHY Device support and infrastructure (PHYLIB) [N/m/y/?] n
 *
 * Ethernet (10 or 100Mbit)
 *
 Ethernet (10 or 100Mbit) (NET_ETHERNET) [Y/n/?] y
   Generic Media Independent Interface device support (MII) [Y/?] y
   ASIX AX88796 NE2000 clone support (AX88796) [N/m/y/?] (NEW)

Answer "n" on "ASIX AX88796 NE2000 clone support (AX88796) [N/m/y/?] (NEW)"
Answer "n" on "TOSHIBA TC35815 Ethernet support (TC35815) [N/m/y] (NEW)"
Answer "n" on "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL) (SC92031) [N/m/y/?] (NEW)"

*
* Ethernet (1000 Mbit)
*
Ethernet (1000 Mbit) (NETDEV_1000) [Y/n/?] (NEW)

Answer "n" on "Ethernet (1000 Mbit) (NETDEV_1000) [Y/n/?] (NEW)" Answer "n" on "Ethernet (10000 Mbit) (NETDEV_10000) [Y/n/?] (NEW)"

*
* Ethernet (10000 Mbit)
*
Ethernet (10000 Mbit) (NETDEV_10000) [Y/n/?] (NEW) n
*
* Token Ring driver support
*
Token Ring driver support (TR) [N/y/?] n
*
* Wireless LAN
*
Wireless LAN (pre-802.11) (WLAN_PRE80211) [N/y/?] (NEW)

Answer "y" on "Wireless LAN (pre-802.11) (WLAN_PRE80211) [N/y/?] (NEW)"
Answer "n" on "Wireless LAN (IEEE 802.11) (WLAN_80211) [N/y/?] (NEW)"

*
* USB Network Adapters
*
USB CATC NetMate-based Ethernet device support (EXPERIMENTAL) (USB_CATC) [N/m/y/?] n
USB KLSI KL5USB101-based ethernet device support (USB_KAWETH) [N/m/y/?] n
USB Pegasus/Pegasus-II based ethernet device support (USB_PEGASUS) [N/m/y/?] n
USB RTL8150 based ethernet device support (EXPERIMENTAL) (USB_RTL8150) [N/m/y/?] n
Multi-purpose USB Networking Framework (USB_USBNET) [N/m/y/?] n
*
* Wan interfaces support
*
Wan interfaces support (WAN) [N/y/?] n
*
* ATM drivers
*
ATM drivers (ATM_DRIVERS) [Y/n/?] (NEW)

Answer "n" on "ATM drivers (ATM_DRIVERS) [Y/n/?] (NEW)"
Answer "n" on "PPP over L2TP (EXPERIMENTAL) (PPPOL2TP) [N/m/?] (NEW)"

  SLIP (serial line) support (SLIP) [N/m/y/?] n
 Fibre Channel driver support (NET_FC) [N/y/?] n
 Traffic Shaper (OBSOLETE) (SHAPER) [N/m/y/?] n
 Network console logging support (EXPERIMENTAL) (NETCONSOLE) [N/m/y/?] n
*
* ISDN support
*
ISDN support (ISDN) [N/m/y/?] n
*
* Telephony support
*
Telephony support (PHONE) [N/m/y/?] n
*
* Input device support
*
Generic input layer (needed for keyboard, mouse, ...) (INPUT) [N/m/y/?] n
*
* Hardware I/O ports
*
Serial I/O support (SERIO) [N/m/y/?] n
Gameport support (GAMEPORT) [N/m/y/?] n
*
* Character devices
*
Virtual terminal (VT) [N/y/?] n
Non-standard serial port support (SERIAL_NONSTANDARD) [N/y/?] n
*
* Serial drivers
*
8250/16550 and compatible serial support (SERIAL_8250) [Y/n/m/?] y
 Console on 8250/16550 and compatible serial port (SERIAL_8250_CONSOLE) [Y/n/?] y
8250/16550 PCI device support (SERIAL_8250_PCI) [N/m/y/?] n
Maximum number of 8250/16550 serial ports (SERIAL_8250_NR_UARTS) [2] 2
Number of 8250/16550 serial ports to register at runtime (SERIAL_8250_RUNTIME_UARTS) [2] 2
Extended 8250/16550 serial driver options (SERIAL_8250_EXTENDED) [Y/n/?] y
 Support more than 4 legacy serial ports (SERIAL_8250_MANY_PORTS) [N/y/?] n
 Support for sharing serial interrupts (SERIAL_8250_SHARE_IRQ) [Y/n/?] y
 Autodetect IRQ on standard ports (unsafe) (SERIAL_8250_DETECT_IRQ) [N/y/?] n
 Support RSA serial ports (SERIAL_8250_RSA) [N/y/?] n
*
* Non-8250 serial port support
*
Digi International NEO PCI Support (SERIAL_JSM) [N/m/y/?] n
Unix98 PTY support (UNIX98_PTYS) [Y/n/?] y
Legacy (BSD) PTY support (LEGACY_PTYS) [N/y/?] n
*
* IPMI top-level message handler
*
IPMI top-level message handler (IPMI_HANDLER) [N/m/y/?] n
*
* Watchdog Timer Support
*
Watchdog Timer Support (WATCHDOG) [N/y/?] n
Hardware Random Number Generator Core support (HW_RANDOM) [Y/n/m/?] y
Enhanced Real Time Clock Support (RTC) [N/m/y/?] n
Siemens R3964 line discipline (R3964) [N/m/y/?] n
Applicom intelligent fieldbus card support (APPLICOM) [N/m/y/?] n
Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) (DRM) [N/m/y/?] n
RAW driver (/dev/raw/rawN) (RAW_DRIVER) [N/m/y/?] n
*
* TPM Hardware Support
*
TPM Hardware Support (TCG_TPM) [N/m/y/?] n
*
* I2C support
*
I2C support (I2C) [N/m/y/?] n
*
* SPI support
*
SPI support (SPI) [N/y/?] n
*
* PPS support
*
PPS support (PPS) [N/m/y/?] (NEW)

Answer "n" on "PPS support (PPS) [N/m/y/?] (NEW)"

*
* Dallas's 1-wire support
*
Dallas's 1-wire support (W1) [N/m/y/?] n
*
* Power supply class support
*
Power supply class support (POWER_SUPPLY) [N/m/y/?] (NEW)

Answer "n" on "Power supply class support (POWER_SUPPLY) [N/m/y/?] (NEW)"

*
* Hardware Monitoring support
*
Hardware Monitoring support (HWMON) [N/m/y/?] n
*
* Sonics Silicon Backplane
*
Sonics Silicon Backplane support (SSB) [Y/?] y
 Support for SSB on PCI-bus host (SSB_PCIHOST) [N/y/?] n
 No SSB kernel messages (SSB_SILENT) [N/y/?] n
 SSB debugging (SSB_DEBUG) [N/y/?] n
SSB Broadcom MIPS core driver (EXPERIMENTAL) (SSB_DRIVER_MIPS) [N/y/?] (NEW)

Answer "n" on "SSB Broadcom MIPS core driver (EXPERIMENTAL) (SSB_DRIVER_MIPS) [N/y/?] (NEW)"

*
* Multifunction device drivers
*
Support for Silicon Motion SM501 (MFD_SM501) [N/m/y/?] (NEW)

Answer "n" on "Support for Silicon Motion SM501 (MFD_SM501) [N/m/y/?] (NEW)"

*
* Multimedia devices
*
Video For Linux (VIDEO_DEV) [N/m/y/?] n
DVB for Linux (DVB_CORE) [N/m/y/?] (NEW)

Answer "n" on "DVB for Linux (DVB_CORE) [N/m/y/?] (NEW)"
Answer "n" on "DAB adapters (DAB) [Y/n/?] (NEW)"

*
* Graphics support
*
*
* Backlight & LCD device support
*
Backlight & LCD device support (BACKLIGHT_LCD_SUPPORT) [N/y/?] n
*
* Display device support
*
Display panel/monitor support (DISPLAY_SUPPORT) [N/m/y/?] (NEW)

Answer "n" on "Display panel/monitor support (DISPLAY_SUPPORT) [N/m/y/?] (NEW)"
Answer "n" on "Lowlevel video output switch controls (VIDEO_OUTPUT_CONTROL) [M/n/y/?] (NEW)"

Support for frame buffer devices (FB) [N/m/y/?] n
*
* Sound
*
Sound card support (SOUND) [N/m/y/?] n
*
* USB support
*
USB support (USB_SUPPORT) [Y/n/?] (NEW)

Answer "y" on "USB support (USB_SUPPORT) [Y/n/?] (NEW)"
Answer "y" on "USB device class-devices (DEPRECATED) (USB_DEVICE_CLASS) [Y/n/?] (NEW)"
Answer "n" on "USB selective suspend/resume and wakeup (EXPERIMENTAL) (USB_SUSPEND) [N/y/?] (NEW)"
Answer "n" on "USB device persistence during system suspend (DANGEROUS) (USB_PERSIST) [N/y/?] (NEW)"
Answer "n" on "OHCI support for Broadcom SSB OHCI core (USB_OHCI_HCD_SSB) [N/y/?] (NEW)"
Answer "n" on "R8A66597 HCD support (USB_R8A66597_HCD) [N/m/y/?] (NEW)"
Answer "m" on "USB Ours Technology Inc. OTi-6858 USB To RS232 Bridge Controller (EXPERIMENTAL) (USB_SERIAL_OTI6858) [N/m/?] (NEW)"
Answer "n" on "USB Debugging Device (USB_SERIAL_DEBUG) [N/m/?] (NEW)"
Answer "n" on "USB BlackBerry recharge support (USB_BERRY_CHARGE) [N/m/y/?] (NEW)"
Answer "n" on "IO Warrior driver support (USB_IOWARRIOR) [N/m/y/?] (NEW)"

USB testing driver (DEVELOPMENT) (USB_TEST) [N/m/y/?] n
*
* USB DSL modem support
*
USB DSL modem support (USB_ATM) [M/n/?] m
  Speedtouch USB support (USB_SPEEDTOUCH) [M/n/?] m
  Conexant AccessRunner USB support (USB_CXACRU) [M/n/?] m
  ADI 930 and eagle USB DSL modem (USB_UEAGLEATM) [M/n/?] m
  Other USB DSL modem support (USB_XUSBATM) [M/n/?] m
*
* USB Gadget Support
*
Support for USB Gadgets (USB_GADGET) [N/m/y/?] n
*
* MMC/SD card support
*
MMC/SD card support (MMC) [N/m/y/?] n
*
* LED Support
*
LED Support (NEW_LEDS) [N/y/?] n
*
* GPIO Support
*
GPIO Support (NEW_GPIO) [N/y/?] (NEW)

Answer "n" on "GPIO Support (NEW_GPIO) [N/y/?] (NEW)"

*
* InfiniBand support
*
InfiniBand support (INFINIBAND) [N/m/y/?] n
*
* Real Time Clock
*
Real Time Clock (RTC_CLASS) [N/m/y/?] n
*
* DMA Engine support
*
Support for DMA engines (DMA_ENGINE) [N/y/?] n
*
* DMA Clients
*
*
* DMA Devices
*
*
* Userspace I/O
*
Userspace I/O drivers (UIO) [N/m/y/?] (NEW)

Answer "n" on "Userspace I/O drivers (UIO) [N/m/y/?] (NEW)"

*
* File systems
*
Second extended fs support (EXT2_FS) [N/m/y/?] n
Ext3 journalling file system support (EXT3_FS) [Y/n/m/?] y
 Ext3 extended attributes (EXT3_FS_XATTR) [N/y/?] n
Ext4dev/ext4 extended fs support development (EXPERIMENTAL) (EXT4DEV_FS) [N/m/y/?] n
JBD (ext3) debugging support (JBD_DEBUG) [N/y/?] n
Reiserfs support (REISERFS_FS) [N/m/y/?] n
JFS filesystem support (JFS_FS) [N/m/y/?] n
XFS filesystem support (XFS_FS) [N/m/y/?] n
GFS2 file system support (GFS2_FS) [N/m/y/?] n
YAFFS2 file system support (YAFFS_FS) [N/m/y/?] n
OCFS2 file system support (OCFS2_FS) [N/m/y/?] n
Mini fanout overlay filesystem (MINI_FO) [N/m/y] n
Minix fs support (MINIX_FS) [N/m/y/?] n
ROM file system support (ROMFS_FS) [N/m/y/?] n
Inotify file change notification support (INOTIFY) [Y/n/?] y
 Inotify support for userspace (INOTIFY_USER) [Y/n/?] y
Quota support (QUOTA) [N/y/?] n
Dnotify support (DNOTIFY) [N/y/?] n
Kernel automounter support (AUTOFS_FS) [N/m/y/?] n
Kernel automounter version 4 support (also supports v3) (AUTOFS4_FS) [N/m/y/?] n
Filesystem in Userspace support (FUSE_FS) [N/m/y/?] n
*
* CD-ROM/DVD Filesystems
*
ISO 9660 CDROM file system support (ISO9660_FS) [N/m/y/?] n
UDF file system support (UDF_FS) [N/m/y/?] n
*
* DOS/FAT/NT Filesystems
*
MSDOS fs support (MSDOS_FS) [N/m/y/?] n
VFAT (Windows-95) fs support (VFAT_FS) [N/m/y/?] n
NTFS file system support (NTFS_FS) [N/m/y/?] n
*
* Pseudo filesystems
*
/proc file system support (PROC_FS) [Y/n/?] y
 /proc/kcore support (PROC_KCORE) [N/y] n
 Sysctl support (/proc/sys) (PROC_SYSCTL) [Y/n/?] y
sysfs file system support (SYSFS) [Y/n/?] y
Virtual memory file system support (former shm fs) (TMPFS) [Y/n/?] y
 Tmpfs POSIX Access Control Lists (TMPFS_POSIX_ACL) [N/y/?] n
Userspace-driven configuration filesystem (EXPERIMENTAL) (CONFIGFS_FS) [N/m/y/?] n
*
* Miscellaneous filesystems
*
ADFS file system support (EXPERIMENTAL) (ADFS_FS) [N/m/y/?] n
Amiga FFS file system support (EXPERIMENTAL) (AFFS_FS) [N/m/y/?] n
Apple Macintosh file system support (EXPERIMENTAL) (HFS_FS) [N/m/y/?] n
Apple Extended HFS file system support (HFSPLUS_FS) [N/m/y/?] n
BeOS file system (BeFS) support (read only) (EXPERIMENTAL) (BEFS_FS) [N/m/y/?] n
BFS file system support (EXPERIMENTAL) (BFS_FS) [N/m/y/?] n
EFS file system support (read only) (EXPERIMENTAL) (EFS_FS) [N/m/y/?] n
Journalling Flash File System v2 (JFFS2) support (JFFS2_FS) [Y/n/m/?] y
 JFFS2 debugging verbosity (0 = quiet, 2 = noisy) (JFFS2_FS_DEBUG) [0] 0
 JFFS2 write-buffering support (JFFS2_FS_WRITEBUFFER) [Y/n/?] y
 JFFS2 summary support (EXPERIMENTAL) (JFFS2_SUMMARY) [N/y/?] n
 JFFS2 XATTR support (EXPERIMENTAL) (JFFS2_FS_XATTR) [N/y/?] n
 Advanced compression options for JFFS2 (JFFS2_COMPRESSION_OPTIONS) [Y/n/?] y
   JFFS2 ZLIB compression support (JFFS2_ZLIB) [Y/n/?] y
   JFFS2 RTIME compression support (JFFS2_RTIME) [Y/n/?] y
   JFFS2 RUBIN compression support (JFFS2_RUBIN) [N/y/?] n
   JFFS2 default compression mode
     1. no compression (JFFS2_CMODE_NONE)
   > 2. priority (JFFS2_CMODE_PRIORITY)
     3. size (EXPERIMENTAL) (JFFS2_CMODE_SIZE)
   choice[1-3?]: 2
Compressed ROM file system support (cramfs) (CRAMFS) [N/m/y/?] n
SquashFS 3.0 - Squashed file system support (SQUASHFS) [N/m/y/?] n
FreeVxFS file system support (VERITAS VxFS(TM) compatible) (VXFS_FS) [N/m/y/?] n
OS/2 HPFS file system support (HPFS_FS) [N/m/y/?] n
QNX4 file system support (read only) (QNX4FS_FS) [N/m/y/?] n
System V/Xenix/V7/Coherent file system support (SYSV_FS) [N/m/y/?] n
UFS file system support (read only) (UFS_FS) [N/m/y/?] n
*
* Network File Systems
*
NFS file system support (NFS_FS) [N/m/y/?] n
NFS server support (NFSD) [N/m/y/?] n
SMB file system support (to mount Windows shares etc.) (SMB_FS) [N/m/y/?] n
CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers) (CIFS) [M/n/y/?] m
 CIFS statistics (CIFS_STATS) [N/y/?] n
 Support legacy servers which use weaker LANMAN security (CIFS_WEAK_PW_HASH) [N/y/?] n
 CIFS extended attributes (CIFS_XATTR) [N/y/?] n
 Enable additional CIFS debugging routines (CIFS_DEBUG2) [N/y/?] n
 CIFS Experimental Features (EXPERIMENTAL) (CIFS_EXPERIMENTAL) [N/y/?] n
NCP file system support (to mount NetWare volumes) (NCP_FS) [N/m/y/?] n
Coda file system support (advanced network fs) (CODA_FS) [N/m/y/?] n
Andrew File System support (AFS) (EXPERIMENTAL) (AFS_FS) [N/m/y/?] n
*
* Partition Types
*
Advanced partition selection (PARTITION_ADVANCED) [Y/n/?] y
 Acorn partition support (ACORN_PARTITION) [N/y/?] n
 Alpha OSF partition support (OSF_PARTITION) [N/y/?] n
 Amiga partition table support (AMIGA_PARTITION) [N/y/?] n
 Atari partition table support (ATARI_PARTITION) [N/y/?] n
 Macintosh partition map support (MAC_PARTITION) [N/y/?] n
 PC BIOS (MSDOS partition tables) support (MSDOS_PARTITION) [Y/n/?] y
   BSD disklabel (FreeBSD partition tables) support (BSD_DISKLABEL) [N/y/?] n
   Minix subpartition support (MINIX_SUBPARTITION) [N/y/?] n
   Solaris (x86) partition table support (SOLARIS_X86_PARTITION) [N/y/?] n
   Unixware slices support (UNIXWARE_DISKLABEL) [N/y/?] n
 Windows Logical Disk Manager (Dynamic Disk) support (LDM_PARTITION) [N/y/?] n
 SGI partition support (SGI_PARTITION) [N/y/?] n
 Ultrix partition table support (ULTRIX_PARTITION) [N/y/?] n
 Sun partition tables support (SUN_PARTITION) [N/y/?] n
 Karma Partition support (KARMA_PARTITION) [N/y/?] n
 EFI GUID Partition support (EFI_PARTITION) [N/y/?] n
 SYSV68 partition table support (SYSV68_PARTITION) [N/y/?] (NEW)

Answer "n" on "SYSV68 partition table support (SYSV68_PARTITION) [N/y/?] (NEW)"

*
* Native Language Support
*
Base native language support (NLS) [M/y/?] m
 Default NLS Option (NLS_DEFAULT) [iso8859-1] iso8859-1
 Codepage 437 (United States, Canada) (NLS_CODEPAGE_437) [N/m/?] n
 Codepage 737 (Greek) (NLS_CODEPAGE_737) [N/m/?] n
 Codepage 775 (Baltic Rim) (NLS_CODEPAGE_775) [N/m/?] n
 Codepage 850 (Europe) (NLS_CODEPAGE_850) [N/m/?] n
 Codepage 852 (Central/Eastern Europe) (NLS_CODEPAGE_852) [N/m/?] n
 Codepage 855 (Cyrillic) (NLS_CODEPAGE_855) [N/m/?] n
 Codepage 857 (Turkish) (NLS_CODEPAGE_857) [N/m/?] n
 Codepage 860 (Portuguese) (NLS_CODEPAGE_860) [N/m/?] n
 Codepage 861 (Icelandic) (NLS_CODEPAGE_861) [N/m/?] n
 Codepage 862 (Hebrew) (NLS_CODEPAGE_862) [N/m/?] n
 Codepage 863 (Canadian French) (NLS_CODEPAGE_863) [N/m/?] n
 Codepage 864 (Arabic) (NLS_CODEPAGE_864) [N/m/?] n
 Codepage 865 (Norwegian, Danish) (NLS_CODEPAGE_865) [N/m/?] n
 Codepage 866 (Cyrillic/Russian) (NLS_CODEPAGE_866) [N/m/?] n
 Codepage 869 (Greek) (NLS_CODEPAGE_869) [N/m/?] n
 Simplified Chinese charset (CP936, GB2312) (NLS_CODEPAGE_936) [N/m/?] n
 Traditional Chinese charset (Big5) (NLS_CODEPAGE_950) [N/m/?] n
 Japanese charsets (Shift-JIS, EUC-JP) (NLS_CODEPAGE_932) [N/m/?] n
 Korean charset (CP949, EUC-KR) (NLS_CODEPAGE_949) [N/m/?] n
 Thai charset (CP874, TIS-620) (NLS_CODEPAGE_874) [N/m/?] n
 Hebrew charsets (ISO-8859-8, CP1255) (NLS_ISO8859_8) [N/m/?] n
 Windows CP1250 (Slavic/Central European Languages) (NLS_CODEPAGE_1250) [N/m/?] n
 Windows CP1251 (Bulgarian, Belarusian) (NLS_CODEPAGE_1251) [N/m/?] n
 ASCII (United States) (NLS_ASCII) [N/m/?] n
 NLS ISO 8859-1  (Latin 1; Western European Languages) (NLS_ISO8859_1) [N/m/?] n
 NLS ISO 8859-2  (Latin 2; Slavic/Central European Languages) (NLS_ISO8859_2) [N/m/?] n
 NLS ISO 8859-3  (Latin 3; Esperanto, Galician, Maltese, Turkish) (NLS_ISO8859_3) [N/m/?] n
 NLS ISO 8859-4  (Latin 4; old Baltic charset) (NLS_ISO8859_4) [N/m/?] n
 NLS ISO 8859-5  (Cyrillic) (NLS_ISO8859_5) [N/m/?] n
 NLS ISO 8859-6  (Arabic) (NLS_ISO8859_6) [N/m/?] n
 NLS ISO 8859-7  (Modern Greek) (NLS_ISO8859_7) [N/m/?] n
 NLS ISO 8859-9  (Latin 5; Turkish) (NLS_ISO8859_9) [N/m/?] n
 NLS ISO 8859-13 (Latin 7; Baltic) (NLS_ISO8859_13) [N/m/?] n
 NLS ISO 8859-14 (Latin 8; Celtic) (NLS_ISO8859_14) [N/m/?] n
 NLS ISO 8859-15 (Latin 9; Western European Languages with Euro) (NLS_ISO8859_15) [N/m/?] n
 NLS KOI8-R (Russian) (NLS_KOI8_R) [N/m/?] n
 NLS KOI8-U/RU (Ukrainian, Belarusian) (NLS_KOI8_U) [N/m/?] n
 NLS UTF-8 (NLS_UTF8) [N/m/?] n
*
* Distributed Lock Manager
*
Distributed Lock Manager (DLM) (DLM) [N/m/y/?] (NEW)

Answer "n" on "Distributed Lock Manager (DLM) (DLM) [N/m/y/?] (NEW)"

*
* Profiling support
*
Profiling support (EXPERIMENTAL) (PROFILING) [N/y/?] n
*
* Kernel hacking
*
Show timing information on printks (PRINTK_TIME) [N/y/?] n
Enable __must_check logic (ENABLE_MUST_CHECK) [N/y/?] n
Magic SysRq key (MAGIC_SYSRQ) [N/y/?] n
Enable unused/obsolete exported symbols (UNUSED_SYMBOLS) [N/y/?] n
Debug Filesystem (DEBUG_FS) [N/y/?] n
Run 'make headers_check' when building vmlinux (HEADERS_CHECK) [N/y/?] n
Kernel debugging (DEBUG_KERNEL) [N/y/?] n
Are you using a crosscompiler (CROSSCOMPILE) [Y/n/?] y
Default kernel command string (CMDLINE) [root=/dev/sda1 rootdelay=10 console=ttyS0,115200] root=/dev/sda1 rootdelay=10 console=ttyS0,115200
*
* Security options
*
Enable access key retention support (KEYS) [N/y/?] n
Enable different security models (SECURITY) [N/y/?] n
*
* Cryptographic API
*
Cryptographic API (CRYPTO) [Y/?] y
 Cryptographic algorithm manager (CRYPTO_MANAGER) [M/y/?] m
 HMAC support (CRYPTO_HMAC) [N/m/y/?] n
 XCBC support (CRYPTO_XCBC) [N/m/y/?] (NEW)

Answer "n" on "XCBC support (CRYPTO_XCBC) [N/m/y/?] (NEW)"
Answer "n" on "GF(2^128) multiplication functions (EXPERIMENTAL) (CRYPTO_GF128MUL) [N/m/y/?] (NEW)"
Answer "m" on "PCBC support (CRYPTO_PCBC) [M/n/y/?] (NEW)"
Answer "n" on "LRW support (EXPERIMENTAL) (CRYPTO_LRW) [N/m/y/?] (NEW)"
Answer "n" on "Software async crypto daemon (CRYPTO_CRYPTD) [N/m/y/?] (NEW)"
Answer "n" on "FCrypt cipher algorithm (CRYPTO_FCRYPT) [N/m/y/?] (NEW)"
Answer "n" on "Camellia cipher algorithms (CRYPTO_CAMELLIA) [N/m/y/?] (NEW)"

Testing module (CRYPTO_TEST) [N/m/?] n
*
* Hardware crypto devices
*
Hardware crypto devices (CRYPTO_HW) [Y/n/?] (NEW)

Answer "n" on "Hardware crypto devices (CRYPTO_HW) [Y/n/?] (NEW)"
Answer "m" on "CRC ITU-T V.41 functions (CRC_ITU_T) [N/m/y/?]"
Answer "m" on "CRC7 functions (CRC7) [N/m/y/?] (NEW)"

6. Rerun menuconfig although nothing will be changed, this step is needed to update some stamp files. On exit save the changes

cd $HOME/trunk
make menuconfig

7. Make a new image; this step won't be so time consuming

make V=99

8. You will have new images in trunk/bin/

Now we have to build modules for our new kernel:

9. Remove .image and .modules in build_mipsel/linux/

cd $HOME/trunk/build_dir/linux-brcm47xx/linux-2.6.23.16
rm .image .modules

10. Go back to trunk/ directory and run make again (now it compiles also the modules we want)

cd ../../..
make

11. Put modules temporary somewhere (INSTALL_MOD_PATH is where we want to temporary put modules)

cd $HOME/trunk/build_dir/linux-brcm47xx/linux-2.6.23.16
INSTALL_MOD_PATH=/tmp/ make modules_install

12. Now we have in /tmp/lib/modules/$our_kernel_version our modules and these need to be copied on the router in /usr/lib/

# ls /tmp/lib/modules/$our_kernel_version/
kernel         modules.ccwmap  modules.ieee1394map  modules.isapnpmap  modules.pcimap    modules.symbols
modules.alias  modules.dep     modules.inputmap     modules.ofmap      modules.seriomap  modules.usbmap
# scp -r /tmp/lib/modules/$our_kernel_version/ router_IP:/lib/modules/

13. Log as root on the router and adjust permissions

# chown -R root:root /lib/modules/2.6.19.2/

14. Flash the image as explained before and that's it

Ubuntu/XP dual boot mini howto

2009-07-14T18:48:00.000-07:00

* prepare linux partitions inside Windows, using Acronis Disk Director Suite. No Partition Magic
- root
- swap
* install Ubuntu with CD-Rom
- keep grub boot loader at root partition
- leave XP loader at MBR untouched
- chain load linux, with bootpart

[zz] 泛仪器接口－－网络接口

2009-07-14T07:33:00.001-07:00

发信人: goofegg (混蛋), 信区: Linux
标题: 泛仪器接口－－网络接口
发信站: BBS 未名空间站 (Wed Jul 1 09:41:06 2009, 北京)

一看这题目外行人也许感觉莫名其妙，不过咱拉的通俗易懂，定会让您理解俺要说什么
，容咱慢慢道来。
内行人也许一搭眼就能大致猜到俺想说什么，咱属于只会空想不会做实事的半吊子，但
愿您能从后文中畅想出更细节深入的实现和以后应用的前景。
就不过多回顾过去了，电子技术的发展，仪器测控领域，开始一台台孤零零的仪器，后
来有了计算机，各种各样的外围总线接口，仪器接口随之出现，日常见到的串口，并口
，PCI，PCIe，USB，IDE，SATA，D-Sub，DVI，HDMI。。。等等都属于接口，仪器广泛
应用的接口也是五花八门：GPIB，VME，VXI，PXI。。。，有的属于机箱内的总线标准
，有的是外围的互联之间的标准，随着发展，有些机箱内的较快的总线又向外扩展，使
仪器之间或者和计算机之间可以更快的连接。所有这些连接都为了什么？通讯！说到通
讯，人们印象最深刻的估计就是网络了，那为什么这样的通讯接口不采用网络接口的标
准呢？
仪器之间的连接以及和计算机之间的连接，最底层实际上就归结为控制和数据采集。曾
有公司提出的虚拟仪器的思想也是根基于此，其开发的通用的AD板卡、多功能数字IO卡
等等再配合上层的软件，就可以自己定制出各种各样的应用，不再像从前需要很多仪器
的搭配，但是其最终还是需要计算机连接。现在市面上有了很多的直接有网络接口的仪
器，有些内嵌了通用的计算机，有些内嵌专用的DSP电路和网络接口芯片。相信这种带
有网络接口的仪器将会越来越普遍，既然各种各样的仪器接口需要各自的接口芯片和电
路，为什么就不用很通用的网络接口代替呢？同样是互联，现在的技术完全可以集成个
嵌入式CPU，用网络协议和通讯代替各种各样的仪器通讯标准。这样的仪器如果再留有
用户可自定制的软件接口，根本就不再需要再联个计算机。比如从一个万用表采个电压
上网，从前需要一个有仪器接口的万用表，还有台电脑通过专用接口电缆和仪器连接，
电脑通过接口和仪器通讯，再处理送向网络；内嵌网口的仪器插上网线就连上网了，需
要电压信号的客户端通过网络直接就能从仪器读到。
这样的硬件接口用通用的网络接口替代，优势就不说了；对于软件协议，也有现成的业
界广泛应用的－－EPICS。
EPICS－实验物理和工业控制系统，起源于欧美的一些大科学装置，后来广泛应用于工
业控制领域，并且是开源的。其核心是把所有控制和采集的东西当作一个PV－－过程变
量，都有一个变量名，不知以后浏览器是否会有这样的插件，就像通常的http协议一样
，可以通过这样的访问：epics://goofegg.com:goofegg:wife:name，就可以在页面上
显示出goofegg先生老婆的名字，当然，如果在局域网里完全可以把主机去掉，变成这
样：epics://:goofegg:wife:name。带网络接口的仪器，完全可以把能采集的各种变量
和需要被控的各种变量做成这样的EPICS通道，代替各种复杂的接口通讯。
当然，硬件做好，这样的软件接口完全可以根据情况定制并能很方便的升级以适应各种
各样的控制系统。

[zz] Use a PSP as an extended display

2009-07-13T20:45:00.000-07:00

posted Oct 6th 2008 1:49pm by Caleb Kraft
filed under: daily, handhelds hacks, playstation hacks, psp hacks

Follow along with this project and you could use your PSP as a display for your computer. The software, available for download on the site, gives you a 960×544 display. The data is compressed, sent to the PSP, then decompressed for display. Though that sounds clunky, the video after the break shows it working pretty smoothly with some Winamp visualization. Only 32 bit Windows XP or older is supported currently.

[thanks carlos]

[zz] Running Kamikaze On QEMU HowTo

2009-07-12T21:38:00.003-07:00

Running Kamikaze images under qemu

The Kamikaze x86 images run directly under qemu; all you need to do is to grow them to the full size that the partition table defines. This will be roughly 20MB, since the default configuration is 4MB for the boot partition and 16MB for the data partition, but will be a bit larger than this due to rounding up to whole numbers of cylinders.

Work out the exact number of sectors that the image should be by looking at the partition table, and multiplying the highest cylinder number by the sectors per cylinder:

$ fdisk openwrt-x86-2.6-jffs2-128k.image
You must set cylinders.
You can do this from the extra functions menu.

Command (m for help): p

Disk openwrt-x86-2.6-jffs2-128k.image: 0 MB, 0 bytes
16 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

                           Device Boot      Start         End      Blocks   Id System
openwrt-x86-2.6-jffs2-128k.image1   *           1           9        4504+  83 Linux
openwrt-x86-2.6-jffs2-128k.image2              10          42       16600+  83 Linux

Command (m for help): q

$ bc
bc 1.06
Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'.
42*1008
42336

$ dd if=/dev/null of=openwrt-x86-2.6-jffs2-128k.image seek=42336
0+0 records in
0+0 records out
0 bytes (0 B) copied, 2.5e-05 seconds, 0 B/s

$ ls -l openwrt-x86-2.6-jffs2-128k.image
-rw-r--r-- 1 yourname yourname 21676032 2007-10-23 11:20

Now you can boot this image directly:

$ sudo apt-get install qemu    # for Ubuntu
$ qemu openwrt-x86-2.6-jffs2-128k.image

Type 'qemu' by itself to get a list of options. Useful ones are '-snapshot' which keeps your image pristine (writes are made to temporary files); '-k en-gb' to set the keyboard layout; and '-m 64' to set the available memory to 64MB (defaults to 128MB)

Inside the VGA window, use Ctrl-Alt to release the mouse, and Ctrl-Alt-1/2/3 to switch between guest VGA, qemu monitor (where you can manage qemu itself), and serial port.

The '-nographic' option disables the VGA window display entirely and redirects the serial console to stdin/stdout. There are some special key sequences here for getting access to the monitor - type Ctrl-a h for help on these.

Networking

Network access to your image is provided by a virtual NE2000-type network card in the emulated guest environment. To access this you will need the kmod-ne2k-pci package, which is included by default in the x86 image.

User-mode networking

"User-mode" networking is enabled by default. Within the guest, if you edit /etc/config/network, set "option proto dhcp", then run "ifup lan", the br-lan interface will pick up an IP address from an internal private network, 10.0.2.x.

It then has outbound access to the Internet via your host machine, which appears to be a NAT firewall. You won't be able to send an ICMP ping (qemu would need to run as root to provide that), but you can open TCP connections and perform DNS lookups. For example, "ipkg update" works as expected.

No root privileges are needed to run qemu this way. However, if you wish to allow incoming connections then this has to be done via port forwarding (see the -redir option), just like on a real NAT firewall.

Bridged networking

A more powerful solution is to bridge your host adaptor's ethernet directly with the virtual ethernet NIC(s) of your QEMU guest(s). This gives them full access to your LAN as peers, and can pick up their own IP addresses using your LAN's existing DHCP server.

To do this involves setting up software bridging on the host, and adding the 'tap' device to this same bridge. The following instructions are for Ubuntu Linux.

Install the 'bridge-utils' package to get the brctl utility.

Now, you need to link your host PC's network port into a software bridge. Let's say your existing 'outside' Internet connection is via eth1, and you wish to bridge QEMU guests onto this. Firstly, unconfigure your network using ifdown eth1. Now edit /etc/network/interfaces and change

auto eth1
iface eth1 inet dhcp

auto br1
iface br1 inet dhcp
      bridge_ports eth1

Finally bring the interface back up using ifup br1. From now on, your outside connection is via br1, which is linked to eth1. Use brctl show to see this.

Next you need to edit /etc/qemu-ifup, which is the script run by qemu when it needs to access the interface, so that it can add itself into the bridge.

#!/bin/sh
sudo -p "Password for $0:" /sbin/ifconfig $1 0.0.0.0 promisc up
sudo /usr/sbin/brctl addif br1 $1

Finally, start qemu like this:

qemu -net tap -net nic -hda openwrt-x86-2.6-squashfs.image

What happens is that qemu creates a new 'tap' interface, e.g. tap0, connects this to the virtual NIC within the guest environment, and the qemu-ifup script connects this to the software bridge in the host environment.

If you get the following permission error:

warning: could not open /dev/net/tun: no virtual network emulation
Could not initialize device 'tap'

then you can chown /dev/net/tun to your own userid, or else run qemu as root.

If you are running multiple qemu instances simultaneously then each one will need to have a unique MAC address assigned to it: e.g.

qemu -net tap -net nic,macaddr=52:54:0:0:0:1 -hda openwrt-x86-2.6-squashfs.image1
qemu -net tap -net nic,macaddr=52:54:0:0:0:2 -hda openwrt-x86-2.6-squashfs.image2
...

Conversely, it's possible to connect a single qemu instance to multiple software bridges (and hence external NICs) on the host. This can be done by using a separate qemu-ifup script for each one, linking to a separate software bridge instance.

qemu -net nic,vlan=1 -net nic,vlan=2 \
     -net tap,vlan=1,script=/etc/qemu-ifup -net tap,vlan=2,script=/etc/qemu-ifup2 \
     -hda openwrt-x86-2.6-squashfs.image

Now within the guest, eth0 connects to one bridge and eth1 connects to another.

Other options

There are many other qemu networking possibilities, such as setting up IP-over-TCP encapsulation for point-to-point links between qemus, or IP-over-UDP multicast. Read the qemu manpage or google for other examples, e.g. http://www.gnome.org/~markmc/qemu-networking.html and http://www.h7.dion.ne.jp/~qemu-win/HowToNetwork-en.html