Ethernet¶

There are two possible scenarios:

1. Connect the DE10-Standard to a router via network cable
2. Connect the DE10-Standard to your PC via a NIC (included with the kit)

Scenario 1 - router¶

Connect the board to the router and the PC to the router via wifi or cable.

Follow the steps below:

1. Connect the DE10-Standard via network cable to the router
2. Connect to the board via the USB-Serial port (screen)
3. Turn on the board (with the SDCARD)
4. Configure the target

Configuring target¶

With an ethernet cable connected to the RJ45, we need to configure Linux to use this "port". On the target, check if Linux detects the network card, with the command: ifconfig eth0 up, and then ifconfig all.

Requesting IP (DHCP)¶

Now we need to get an IP from the DHCP server (which is on your router), for this we will use the udhcpc program, with the following command:

$ udhcpc eth0

To see the IP

$ ifconfig

Testing¶

To test:21985

1. Ping Host → Target / Target → Host / Target → internet.
2. Check the IP with the ifconfig command and try to ping some site ping google.com.

Scenario 2 - NIC¶

Connect the board to the computer via the NIC adapter:

1. Connect the DE10-Standard to the NIC
2. Connect the NIC to your PC's USB
3. Connect to the board via the USB-Serial port (screen)
4. Turn on the board (with the SDCARD)
5. Configure your PC
6. Configure the target

Configuring PC¶

We will have to configure a fixed IP on the ethernet port that the NIC creates on your PC's Linux.

Configuring Target¶

Now on the target we will configure the network port to have a fixed IP:

$ ifconfig eth0 up
$ ifconfig eth0 169.254.0.13 netmask 255.255.0.0 up

Testing¶

To test, let's ping Host → Target and Target → Host.

Automating at boot¶

These settings are not persistent, if you restart the embedded Linux you will have to do everything again. To make our life easier, we will execute this at boot.

RC¶

Have you noticed the /etc/rc* folders in your operating system? That's where most of the scripts that are executed at boot/reboot/halt reside. Each distribution uses the scripts differently, for example, Debian uses them in the following way:

• https://wiki.debian.org/BootProcess

Inside each rc.x folder, the scripts have names that dictate the sequence in which the scripts in the folder will be called.

Adding script to boot - systemd¶

Create a script named S60MAC.sh in the /etc/init.d folder and add the following code (depends on which scenario you will use):

#!/bin/sh

case "$1" in
start)
        start
        ifconfig eth0 up
        ifconfig eth0 169.254.0.13 netmask 255.255.0.0 up
        ;;
stop)
        stop
        ifconfig eth0 down
        ;;
restart|reload)
        restart
        ;;
*)
        echo "Usage: $0 {start|stop|restart}"
        exit 1
esac

#!/bin/bash

case "$1" in
start)
    printf "Setting ip: "
    /sbin/ifconfig eth0 169.254.0.13 netmask 255.255.0.0 up
    [ $? = 0 ] && echo "OK" || echo "FAIL"
    ;; 
*)
    exit 1
    ;;
esac

Make the script is executable: chmod +x S60MAC.sh. Once the script is created, it will need to be added to the system startup, for this we must call (when the iso uses systemd, which is the case of Amstrong, but not buildroot):

$ systemctl enable S60MAC.sh

• ref: https://forums.kali.org/showthread.php?21985-How-to-make-mac-address-random-at-each-boot-up

Changing the MAC¶

It may necessary to change the MAC address to connect to the lab's network, it will be necessary to edit the board's MAC, otherwise it will not be able to connect. To do this, execute the following commands:

$ ifconfig eth0 down
$ ifconfig eth0 hw ether 02:01:02:03:04:08
$ ifconfig eth0 up