Raspberry – Jan Taczanowski's tech blog

Today I was trying to build ipt-netflow kernel module on my Raspberry Pi with Raspbian linux. For hours I was stuck with proper system setup to make it ready for compiling additional kernel modules. The problem was with make prepare modules_prepare command which gives me such error:

root@raspberrypi:/usr/src/linux-headers-4.9.59+# make prepare modules_prepare
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
make[1]: *** No rule to make target 'arch/arm/tools/gen-mach-types', needed by 'include/generated/mach-types.h'.  Stop.
arch/arm/Makefile:315: recipe for target 'archprepare' failed
make: *** [archprepare] Error 2

root@raspberrypi:/usr/src/linux-headers-4.9.59+# make prepare modules_prepare

CHK include/config/kernel.release

CHK include/generated/uapi/linux/version.h

CHK include/generated/utsrelease.h

make[1]: *** No rule to make target 'arch/arm/tools/gen-mach-types', needed by 'include/generated/mach-types.h'. Stop.

arch/arm/Makefile:315: recipe for target 'archprepare' failed

make: *** [archprepare] Error 2

Google was not very helpful with this problem. Finally, basing on various trops, I got it worked. Uff.. Here is the proper way to setup Raspberry Pi for compiling additional kernel modules:

Install kernel headers and other tools:

apt-get update
apt-get install raspberrypi-kernel-headers module-assistant pkg-config libncurses5-dev

1 2	apt-get update apt-get install raspberrypi-kernel-headers module-assistant pkg-config libncurses5-dev

Install rpi-source tool. This downloading full kernel sources, not only kernel headers.

wget https://raw.githubusercontent.com/notro/rpi-source/master/rpi-source -O /usr/bin/rpi-source
chmod +x /usr/bin/rpi-source
/usr/bin/rpi-source -q --tag-update

wget https://raw.githubusercontent.com/notro/rpi-source/master/rpi-source -O /usr/bin/rpi-source

chmod +x /usr/bin/rpi-source

/usr/bin/rpi-source -q --tag-update

Install kernel sources (Lack of this was the cause of problems).

rpi-source --skip-gcc

1	rpi-source --skip-gcc

You will see something like that:

root@raspberrypi:/home/pi# rpi-source --skip-gcc

 *** Using: /usr/share/doc/raspberrypi-bootloader/changelog.Debian.gz

 *** Latest firmware revision: 12e0bf86e08d6067372bc0a45d7e8a10d3113210

 *** Linux source commit: 36612d5d7a88672a3e7dd6cb458dbbbca0d75efe

 *** Kernel source already installed: /root/linux-36612d5d7a88672a3e7dd6cb458dbbbca0d75efe

root@raspberrypi:/home/pi# rpi-source --skip-gcc

*** Using: /usr/share/doc/raspberrypi-bootloader/changelog.Debian.gz

*** Latest firmware revision: 12e0bf86e08d6067372bc0a45d7e8a10d3113210

*** Linux source commit: 36612d5d7a88672a3e7dd6cb458dbbbca0d75efe

*** Kernel source already installed: /root/linux-36612d5d7a88672a3e7dd6cb458dbbbca0d75efe

I suggest you create a symlink to /usr/src/linux:

ln -s /root/linux-36612d5d7a88672a3e7dd6cb458dbbbca0d75efe /usr/src/linux

1	ln -s /root/linux-36612d5d7a88672a3e7dd6cb458dbbbca0d75efe /usr/src/linux

Copy current kernel config to downloaded kernel sources and make oldconfig:

modprobe configs
cd /usr/src/linux
zcat /proc/config.gz > .config
make oldconfig

modprobe configs

cd /usr/src/linux

zcat /proc/config.gz > .config

make oldconfig

Run module assistant:

m-a prepare

1	m-a prepare

Prepare kernel for modules compilation:

make prepare modules_prepare

1	make prepare modules_prepare

After this steps I was able to compile third party kernel modules. 🙂
At the end I would like to highly recommend ipt-netflow kernel module – it is very robust solution for sending netflows from linux machines.

Hi!

Some time ago I configured my Raspberry Pi as a home router. Below, in short brief is shown my configuration.
raspberry_cisco_switch

On the Cisco switch, I have created two vlans:
vlan10 – WAN (Internet connection)
vlan20 – LAN (Home network)

The first port of the Cisco switch is connected to the the Internet, and is configured as access port for vlan10. The second port is connected to the Raspberry Pi as trunk port – traffic from vlan10 and vlan20 is tagged on this port. Third port is in access mode and is connected to the home access point.

interface FastEthernet0/3
 switchport access vlan 20
!
interface FastEthernet0/2
 switchport mode trunk
!
interface FastEthernet0/1
 switchport access vlan 10
!
interface Vlan20
 ip address 192.168.50.2 255.255.255.0

interface FastEthernet0/3

switchport access vlan 20

interface FastEthernet0/2

switchport mode trunk

interface FastEthernet0/1

switchport access vlan 10

interface Vlan20

ip address 192.168.50.2 255.255.255.0

Switch#show vlan brief 

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Fa0/4
10   INTERNET                         active    Fa0/1
20   LAN                              active    Fa0/3

Switch#show vlan brief

VLAN Name Status Ports

---- -------------------------------- --------- -------------------------------

1 default active Fa0/4

10 INTERNET active Fa0/1

20 LAN active Fa0/3

Network configuration on Raspberry Pi looks as follows:

root@raspberrypi:/home/pi# cat /etc/network/interfaces 
auto lo

iface lo inet loopback
# Management
iface eth0 inet static
        address 192.168.100.1
        netmask 255.255.255.0
        post-up ifup vlan10
        post-up ifup vlan20

# Internet
auto vlan10
iface vlan10 inet dhcp
        hwaddress ether 00:12:2a:a7:f7:c0
        vlan-raw-device eth0
# Home network
auto vlan20
iface vlan20 inet static
        address 192.168.50.1
        netmask 255.255.255.0
        vlan-raw-device eth0

root@raspberrypi:/home/pi# cat /etc/network/interfaces

auto lo

iface lo inet loopback

# Management

iface eth0 inet static

address 192.168.100.1

netmask 255.255.255.0

post-up ifup vlan10

post-up ifup vlan20

# Internet

auto vlan10

iface vlan10 inet dhcp

hwaddress ether 00:12:2a:a7:f7:c0

vlan-raw-device eth0

# Home network

auto vlan20

iface vlan20 inet static

address 192.168.50.1

netmask 255.255.255.0

vlan-raw-device eth0

On eth0 interface I have set 192.168.100.1 address for management purpose in case of problems with access to the Raspberry Pi from vlan’s side. On vlan10 interface I have to set the custom mac address to obtain IP address from my internet provider. Vlan20 with addresses 192.168.50.1/24 is for my home network.
The rest of my configuration like NAT, dhcp, dns is pretty standard and will not be posted about it here. If you have questions, I will be happy to answer in the comments 🙂

How Raspberry Pi performs as a router on my 100/50 Mb/s internet connection? Quite nicely for a network card supported by USB – which has Raspberry.
4931071421

Jan Taczanowski's tech blog

Posts tagged Raspberry

Preparing Raspberry Pi for building additional kernel modules.

Raspberry Pi 2b as a home router with Cisco switch and VLANs