Skip to content

W
wr-switch-sw
Commit 638d3d32 authored by Adam Wujek's avatar Adam Wujek 💬
Browse files
Options

rootfs: support more ways to get dot-config's URL via DHCP 

Support assembling dot-config's URL from DHCP options:
--the filename
--the BOOTP next server option
In this case TFTP protocol is used. It is similar to the pxe booting.

Also update documentation.
Signed-off-by: Adam Wujek's avatarAdam Wujek <adam.wujek@cern.ch>
parent b417b5cd
Hide whitespace changes
Inline Side-by-side
Showing with 19 additions and 4 deletions
doc/wrs-user-manual.in
View file @ 638d3d32
......@@ -336,7 +336,7 @@ configuration file each time it is booted, and applies the choices
before starting any service. The name of the configuration file can
include the @sc{mac} or @sc{ip} address of the device, to allow
running several switches with different configurations in the same
network. The URL to the configuration file can also be retrieved from DHCP
network. The location of the configuration file can also be retrieved from DHCP
server.
@c ==========================================================================
......@@ -368,9 +368,14 @@ sources are implemented in current version:
Get a @t{dot-config} file from the URL provided in @t{CONFIG_DOTCONF_URL}.
@item CONFIG_DOTCONF_SOURCE_FORCE_DHCP
Get a URL to a @t{dot-config} file from a DHCP server.
The URL can be configured in the ``@t{filename}'' configuration field
of the DHCP server. The configured URL has to be in the same form as
Get a network location of a @t{dot-config} file from a DHCP server.
Server can be configured in a way to provide the entire URL to
the dot-config in the ``@t{filename}'' configuration field of the DHCP
server. As an alternative, ``@t{filename}'' can be configured only as a
path. It will be then interpreted as a path on a tftp server, which IP
address is taken from the configuration field
``@t{The BOOTP next server option}'' of a DHCP server.
In the case the URL is used it has to be in the same form as
@t{CONFIG_DOTCONF_URL}.
@item CONFIG_DOTCONF_SOURCE_TRY_DHCP
......
userspace/rootfs_override/wr/bin/dhcp_get_filename.sh
View file @ 638d3d32
......@@ -11,6 +11,16 @@
# needed. Then we replace the real file if different.
tmpdir="/tmp"
# check whether we got path to the dot-config file from DHCP server
if [ -n "$boot_file" ]; then
# check whether the path consists potocol type
proto=$(echo "$boot_file" | cut -d: -f 1)
if [ "$proto" != "tftp" ] && [ "$proto" != "ftp" ] && [ "$proto" != "http" ] && [ -n "$siaddr" ]; then
# There is no protocol type in the path. If $siaddr is not empty, assume
# config should come from $siaddr/$boot_file via tftp
boot_file=tftp://"$siaddr"/"$boot_file"
fi
# Path with protocol type (added above or originally included) that was
# received from the DHCP server.
echo $boot_file > "$tmpdir"/dot-config_source_url
fi
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment