[PATCH v2] Documentation: some extra steps requires for DHCP network configuration for sandbox on the host OS

Oleksij Rempel linux at rempel-privat.de
Thu Apr 22 05:36:54 BST 2021


Hi,

thank you for your patch!

Am 21.04.21 um 20:08 schrieb Neeraj Pal:
> Signed-off-by: Neeraj Pal <neerajpal09 at gmail.com>
> ---
>  Documentation/boards/sandbox.rst | 66 ++++++++++++++++++++++++++++++++
>  1 file changed, 66 insertions(+)
>
> diff --git a/Documentation/boards/sandbox.rst b/Documentation/boards/sandbox.rst
> index e9e518365..925dfc808 100644
> --- a/Documentation/boards/sandbox.rst
> +++ b/Documentation/boards/sandbox.rst
> @@ -74,3 +74,69 @@ Available sandbox invocation options include:
>
>  To terminate barebox and return to the calling shell, the poweroff command is
>  suitable.
> +
> +Network configuration
> +---------------------
> +
> +While running the sandbox, the following steps are required
> +
> +* On host
> +
> +  * virbr0: virtual bridge interface created by Qemu (easy method)
> +
> +  * if Qemu virtual bridge (virbr0) is not available then manually create and configure one bridge like "br0"
> +
> +    .. code-block:: console
> +
> +        $ ip link show
> +        4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
> +            link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
> +        6: barebox: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
> +            link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
> +
> +    .. code-block:: console
> +
> +        $ sudo apt install bridge-utils
> +        $ sudo ifconfig barebox up
> +        $ sudo brctl addif virbr0 barebox
> +        $ sudo ip link set barebox master virbr0
> +        $ sudo dhclient -v virbr0

bridge-utils and ifconfig are deprecated tools. Please use ip utils instead. Usual bridge
configuration with ip utils looks like:

# create bridge interface with name br0
ip l a name br0 type bridge
# bring up bridge interface

ip l s dev br0 up
# link existing eth0 interface to the bridge br0
ip l s eth0 master br0
ip l s dev eth0 up
ip l s eth1 master br0
ip l s dev eth1 up



In case you wont to assign static address to the bridge interface:
ip a a 172.17.1.1/24 dev br0


> +
> +* On Sandbox
> +
> +    .. code-block:: console
> +
> +        barebox at Sandbox:/ devinfo eth0
> +        Parent: tap0
> +        Parameters:
> +          ethaddr: 00:00:00:00:00:00 (type: MAC)
> +          gateway: 0.0.0.0 (type: ipv4)
> +          ipaddr: 0.0.0.0 (type: ipv4)
> +          linux.bootargs:  (type: string)
> +          linux.devname:  (type: string)
> +          mode: dhcp (type: enum) (values: "dhcp", "static", "disabled")
> +          netmask: 0.0.0.0 (type: ipv4)
> +          serverip:  (type: string)
> +
> +    .. code-block:: console
> +
> +        barebox at Sandbox:/ dhcp eth0
> +        WARNING: eth0: No MAC address set. Using random address c2:2c:a1:17:b8:47
> +        T eth0: DHCP client bound to address 192.168.122.21
> +        barebox at Sandbox:/ ping google.com
> +        PING google.com (172.217.167.46)
> +        host google.com is alive
> +
> +    .. code-block:: console
> +
> +        barebox at Sandbox:/ devinfo eth0
> +        Parent: tap0
> +        Parameters:
> +          ethaddr: c2:2c:a1:17:b8:47 (type: MAC)
> +          gateway: 192.168.122.1 (type: ipv4)
> +          ipaddr: 192.168.122.21 (type: ipv4)
> +          linux.bootargs:  (type: string)
> +          linux.devname:  (type: string)
> +          mode: dhcp (type: enum) (values: "dhcp", "static", "disabled")
> +          netmask: 255.255.255.0 (type: ipv4)
> +          serverip: 192.168.122.1 (type: string)
>


--
Regards,
Oleksij



More information about the barebox mailing list