kernel
/
dracut
mirror of https://git.kernel.org/pub/scm/boot/dracut/dracut.git/
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
725 Commits
1 Branch
68 Tags
6.7 MiB
Tree: 13beb248bc
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '13beb248bc'
${ noResults }
dracut/modules.d/40network/parse-ip-opts.sh

146 lines
4.4 KiB
Raw Normal View History Unescape

netroot: Add ip= cmdline checker As with other netroot boot arguments ip= lines should be parsed and checked. Having this has the advantage that other cmdline scripts can tell the ip= parser if dhcp or ip=:srv:... is needed, like parse-root.sh (renamed dhcp-fallback) or parse-nfsroot do. The nfs test-suite has one check which uses static ip lines, but the autoconf param is wrong. Fixed this as well.
16 years ago
#!/bin/sh
#
# Format:
# ip=[dhcp|on|any]
#
# ip=<interface>:[dhcp|on|any]
#
# ip=<client-IP-number>:<server-id>:<gateway-IP-number>:<netmask>:<client-hostname>:<interface>:[dhcp|on|any|none|off]
#
multinic support: Add bootdev cmdline argument This introduces a new cmdline argument bootdev, to support the case where multiple nics need to be up before the netroot handler is called. Cases involved might be bonding, iscsi multipathing, bonding, ... This argument is required to decide which interface is the primary to use for dhcp root-path, default gw, etc. When multiple ip= items are present on the cmdline, the ip= parser now enforces the presence of <dev> further demands that the new argument bootdev contains the name of the primary interface. Configurtion if of course still delegated to netroot but in is enhance to ensure that netroot "waits" for all required interfaces to be up. Example: root=dhcp ip=eth0:dhcp ip=client-ip:::netmask::eth1:off bootdev=eth0 First, the ip= cmdline parser ensures that all ip items contain a <dev> then checks the ip items and checks as well that an ip= item for the given bootdev was found. When the first netroot starts, probably for eth1, it checks wheter interface configuration for all interfaces is available. If not it exits. The second start of netroot (eth0, which was a bit delayed because of dhcp) sees that all interfaces are present, configures them and continues.
16 years ago
# When supplying more than only ip= line, <interface> is mandatory and
# bootdev= must contain the name of the primary interface to use for
# routing,dns,dhcp-options,etc.
#
netroot: Add ip= cmdline checker As with other netroot boot arguments ip= lines should be parsed and checked. Having this has the advantage that other cmdline scripts can tell the ip= parser if dhcp or ip=:srv:... is needed, like parse-root.sh (renamed dhcp-fallback) or parse-nfsroot do. The nfs test-suite has one check which uses static ip lines, but the autoconf param is wrong. Fixed this as well.
16 years ago
# Sadly there's no easy way to split ':' separated lines into variables
ip_to_var() {
local v=${1}:
set --
while [ -n "$v" ]; do
set -- "$@" "${v%%:*}"
v=${v#*:}
done
unset ip srv gw mask hostname dev autoconf
case $# in
0) autoconf="error" ;;
1) autoconf=$1 ;;
2) dev=$1; autoconf=$2 ;;
*) ip=$1; srv=$2; gw=$3; mask=$4; hostname=$5; dev=$6; autoconf=$7 ;;
esac
}
netroot: Only start interface configuration if really needed Currently network configuration is launched by udev as soon as it discovers a driver. This isn't such a good idea since we don't know if network configuration is actually required. Change this by writing the udev rules on the fly if required.
16 years ago
# Check if ip= lines should be used
if getarg ip= >/dev/null ; then
if [ -z "$netroot" ] ; then
echo "Warning: No netboot configured, ignoring ip= lines"
return;
fi
fi
netroot: Add pxelinux BOOTIF support Having BOOTIF as an argument is a clear pointer which interface should be used for netroot. This changes network rule generation accordingly.
16 years ago
# Don't mix BOOTIF=macaddr from pxelinux and ip= lines
getarg ip= >/dev/null && getarg BOOTIF= >/dev/null && \
die "Mixing BOOTIF and ip= lines is dangerous"
# No more parsing stuff, BOOTIF says everything
[ -n "$(getarg BOOTIF)" ] && return
netroot: Add ip= cmdline checker As with other netroot boot arguments ip= lines should be parsed and checked. Having this has the advantage that other cmdline scripts can tell the ip= parser if dhcp or ip=:srv:... is needed, like parse-root.sh (renamed dhcp-fallback) or parse-nfsroot do. The nfs test-suite has one check which uses static ip lines, but the autoconf param is wrong. Fixed this as well.
16 years ago
if [ -n "$netroot" ] && [ -z "$(getarg ip=)" ] ; then
removed warning "No ip= argument(s) for netroot provided..."
16 years ago
# No ip= argument(s) for netroot provided, defaulting to DHCP
netroot: Add ip= cmdline checker As with other netroot boot arguments ip= lines should be parsed and checked. Having this has the advantage that other cmdline scripts can tell the ip= parser if dhcp or ip=:srv:... is needed, like parse-root.sh (renamed dhcp-fallback) or parse-nfsroot do. The nfs test-suite has one check which uses static ip lines, but the autoconf param is wrong. Fixed this as well.
16 years ago
return;
fi
multinic support: Add bootdev cmdline argument This introduces a new cmdline argument bootdev, to support the case where multiple nics need to be up before the netroot handler is called. Cases involved might be bonding, iscsi multipathing, bonding, ... This argument is required to decide which interface is the primary to use for dhcp root-path, default gw, etc. When multiple ip= items are present on the cmdline, the ip= parser now enforces the presence of <dev> further demands that the new argument bootdev contains the name of the primary interface. Configurtion if of course still delegated to netroot but in is enhance to ensure that netroot "waits" for all required interfaces to be up. Example: root=dhcp ip=eth0:dhcp ip=client-ip:::netmask::eth1:off bootdev=eth0 First, the ip= cmdline parser ensures that all ip items contain a <dev> then checks the ip items and checks as well that an ip= item for the given bootdev was found. When the first netroot starts, probably for eth1, it checks wheter interface configuration for all interfaces is available. If not it exits. The second start of netroot (eth0, which was a bit delayed because of dhcp) sees that all interfaces are present, configures them and continues.
16 years ago
# Count ip= lines to decide whether we need bootdev= or not
if [ -z "$NEEDBOOTDEV" ] ; then
[ "$CMDLINE" ] || read CMDLINE < /proc/cmdline
local count=0
for p in $CMDLINE; do
[ "${p%%=*}" = "ip" ] && count=$(( $count + 1 ))
done
[ $count -gt 1 ] && NEEDBOOTDEV=1
fi
# If needed, check if bootdev= contains anything usable
if [ -n "$NEEDBOOTDEV" ] ; then
BOOTDEV=$(getarg bootdev=) || die "Please supply bootdev argument for multiple ip= lines"
[ -z "$BOOTDEV" ] && die "Bootdev argument is empty"
fi
netroot: Add ip= cmdline checker As with other netroot boot arguments ip= lines should be parsed and checked. Having this has the advantage that other cmdline scripts can tell the ip= parser if dhcp or ip=:srv:... is needed, like parse-root.sh (renamed dhcp-fallback) or parse-nfsroot do. The nfs test-suite has one check which uses static ip lines, but the autoconf param is wrong. Fixed this as well.
16 years ago
# Check ip= lines
# XXX Would be nice if we could errorcheck ip addresses here as well
[ "$CMDLINE" ] || read CMDLINE < /proc/cmdline
for p in $CMDLINE; do
[ -n "${p%ip=*}" ] && continue
ip_to_var ${p#ip=}
multinic support: Add bootdev cmdline argument This introduces a new cmdline argument bootdev, to support the case where multiple nics need to be up before the netroot handler is called. Cases involved might be bonding, iscsi multipathing, bonding, ... This argument is required to decide which interface is the primary to use for dhcp root-path, default gw, etc. When multiple ip= items are present on the cmdline, the ip= parser now enforces the presence of <dev> further demands that the new argument bootdev contains the name of the primary interface. Configurtion if of course still delegated to netroot but in is enhance to ensure that netroot "waits" for all required interfaces to be up. Example: root=dhcp ip=eth0:dhcp ip=client-ip:::netmask::eth1:off bootdev=eth0 First, the ip= cmdline parser ensures that all ip items contain a <dev> then checks the ip items and checks as well that an ip= item for the given bootdev was found. When the first netroot starts, probably for eth1, it checks wheter interface configuration for all interfaces is available. If not it exits. The second start of netroot (eth0, which was a bit delayed because of dhcp) sees that all interfaces are present, configures them and continues.
16 years ago
# We need to have an ip= line for the specified bootdev
[ -n "$NEEDBOOTDEV" ] && [ "$dev" = "$BOOTDEV" ] && BOOTDEVOK=1
netroot: Add ip= cmdline checker As with other netroot boot arguments ip= lines should be parsed and checked. Having this has the advantage that other cmdline scripts can tell the ip= parser if dhcp or ip=:srv:... is needed, like parse-root.sh (renamed dhcp-fallback) or parse-nfsroot do. The nfs test-suite has one check which uses static ip lines, but the autoconf param is wrong. Fixed this as well.
16 years ago
# Empty autoconf defaults to 'dhcp'
if [ -z "$autoconf" ] ; then
warn "Empty autoconf values default to dhcp"
autoconf="dhcp"
fi
# Error checking for autoconf in combination with other values
case $autoconf in
error) die "Error parsing option '$p'";;
bootp|rarp|both) die "Sorry, ip=$autoconf is currenty unsupported";;
none|off) \
[ -z "$ip" ] && \
die "For argument '$p'\nValue '$autoconf' without static configuration does not make sense"
[ -z "$mask" ] && \
die "Sorry, automatic calculation of netmask is not yet supported"
;;
dhcp|on|any) \
multinic support: Add bootdev cmdline argument This introduces a new cmdline argument bootdev, to support the case where multiple nics need to be up before the netroot handler is called. Cases involved might be bonding, iscsi multipathing, bonding, ... This argument is required to decide which interface is the primary to use for dhcp root-path, default gw, etc. When multiple ip= items are present on the cmdline, the ip= parser now enforces the presence of <dev> further demands that the new argument bootdev contains the name of the primary interface. Configurtion if of course still delegated to netroot but in is enhance to ensure that netroot "waits" for all required interfaces to be up. Example: root=dhcp ip=eth0:dhcp ip=client-ip:::netmask::eth1:off bootdev=eth0 First, the ip= cmdline parser ensures that all ip items contain a <dev> then checks the ip items and checks as well that an ip= item for the given bootdev was found. When the first netroot starts, probably for eth1, it checks wheter interface configuration for all interfaces is available. If not it exits. The second start of netroot (eth0, which was a bit delayed because of dhcp) sees that all interfaces are present, configures them and continues.
16 years ago
[ -n "$NEEDBOOTDEV" ] && [ -z "$dev" ] && \
die "Sorry, '$p' does not make sense for multiple interface configurations"
netroot: Add ip= cmdline checker As with other netroot boot arguments ip= lines should be parsed and checked. Having this has the advantage that other cmdline scripts can tell the ip= parser if dhcp or ip=:srv:... is needed, like parse-root.sh (renamed dhcp-fallback) or parse-nfsroot do. The nfs test-suite has one check which uses static ip lines, but the autoconf param is wrong. Fixed this as well.
16 years ago
[ -n "$ip" ] && \
die "For argument '$p'\nSorry, setting client-ip does not make sense for '$autoconf'"
;;
*) die "For argument '$p'\nSorry, unknown value '$autoconf'";;
esac
if [ -n "$dev" ] ; then
multinic support: Add bootdev cmdline argument This introduces a new cmdline argument bootdev, to support the case where multiple nics need to be up before the netroot handler is called. Cases involved might be bonding, iscsi multipathing, bonding, ... This argument is required to decide which interface is the primary to use for dhcp root-path, default gw, etc. When multiple ip= items are present on the cmdline, the ip= parser now enforces the presence of <dev> further demands that the new argument bootdev contains the name of the primary interface. Configurtion if of course still delegated to netroot but in is enhance to ensure that netroot "waits" for all required interfaces to be up. Example: root=dhcp ip=eth0:dhcp ip=client-ip:::netmask::eth1:off bootdev=eth0 First, the ip= cmdline parser ensures that all ip items contain a <dev> then checks the ip items and checks as well that an ip= item for the given bootdev was found. When the first netroot starts, probably for eth1, it checks wheter interface configuration for all interfaces is available. If not it exits. The second start of netroot (eth0, which was a bit delayed because of dhcp) sees that all interfaces are present, configures them and continues.
16 years ago
# We don't like duplicate device configs
netroot: Add ip= cmdline checker As with other netroot boot arguments ip= lines should be parsed and checked. Having this has the advantage that other cmdline scripts can tell the ip= parser if dhcp or ip=:srv:... is needed, like parse-root.sh (renamed dhcp-fallback) or parse-nfsroot do. The nfs test-suite has one check which uses static ip lines, but the autoconf param is wrong. Fixed this as well.
16 years ago
if [ -n "$IFACES" ] ; then
for i in $IFACES ; do
[ "$dev" = "$i" ] && die "For argument '$p'\nDuplication configurations for '$dev'"
done
fi
multinic support: Add bootdev cmdline argument This introduces a new cmdline argument bootdev, to support the case where multiple nics need to be up before the netroot handler is called. Cases involved might be bonding, iscsi multipathing, bonding, ... This argument is required to decide which interface is the primary to use for dhcp root-path, default gw, etc. When multiple ip= items are present on the cmdline, the ip= parser now enforces the presence of <dev> further demands that the new argument bootdev contains the name of the primary interface. Configurtion if of course still delegated to netroot but in is enhance to ensure that netroot "waits" for all required interfaces to be up. Example: root=dhcp ip=eth0:dhcp ip=client-ip:::netmask::eth1:off bootdev=eth0 First, the ip= cmdline parser ensures that all ip items contain a <dev> then checks the ip items and checks as well that an ip= item for the given bootdev was found. When the first netroot starts, probably for eth1, it checks wheter interface configuration for all interfaces is available. If not it exits. The second start of netroot (eth0, which was a bit delayed because of dhcp) sees that all interfaces are present, configures them and continues.
16 years ago
# IFACES list for later use
netroot: Add ip= cmdline checker As with other netroot boot arguments ip= lines should be parsed and checked. Having this has the advantage that other cmdline scripts can tell the ip= parser if dhcp or ip=:srv:... is needed, like parse-root.sh (renamed dhcp-fallback) or parse-nfsroot do. The nfs test-suite has one check which uses static ip lines, but the autoconf param is wrong. Fixed this as well.
16 years ago
IFACES="$IFACES $dev"
fi
multinic support: Add bootdev cmdline argument This introduces a new cmdline argument bootdev, to support the case where multiple nics need to be up before the netroot handler is called. Cases involved might be bonding, iscsi multipathing, bonding, ... This argument is required to decide which interface is the primary to use for dhcp root-path, default gw, etc. When multiple ip= items are present on the cmdline, the ip= parser now enforces the presence of <dev> further demands that the new argument bootdev contains the name of the primary interface. Configurtion if of course still delegated to netroot but in is enhance to ensure that netroot "waits" for all required interfaces to be up. Example: root=dhcp ip=eth0:dhcp ip=client-ip:::netmask::eth1:off bootdev=eth0 First, the ip= cmdline parser ensures that all ip items contain a <dev> then checks the ip items and checks as well that an ip= item for the given bootdev was found. When the first netroot starts, probably for eth1, it checks wheter interface configuration for all interfaces is available. If not it exits. The second start of netroot (eth0, which was a bit delayed because of dhcp) sees that all interfaces are present, configures them and continues.
16 years ago
# Small optimization for udev rules
[ -z "$NEEDBOOTDEV" ] && [ -n "$dev" ] && BOOTDEV=$dev
# Do we need to check for specific options?
if [ -n "$NEEDDHCP" ] || [ -n "$DHCPORSERVER" ] ; then
# Correct device? (Empty is ok as well)
[ "$dev" = "$BOOTDEV" ] || continue
# Server-ip is there?
[ -n "$DHCPORSERVER" ] && [ -n "$srv" ] && continue
# dhcp? (It's simpler to check for a set ip. Checks above ensure that if
# ip is there, we're static
[ -z "$ip" ] && continue
# Not good!
die "Server-ip or dhcp for netboot needed, but current arguments say otherwise"
netroot: Add ip= cmdline checker As with other netroot boot arguments ip= lines should be parsed and checked. Having this has the advantage that other cmdline scripts can tell the ip= parser if dhcp or ip=:srv:... is needed, like parse-root.sh (renamed dhcp-fallback) or parse-nfsroot do. The nfs test-suite has one check which uses static ip lines, but the autoconf param is wrong. Fixed this as well.
16 years ago
fi
done
multinic support: Add bootdev cmdline argument This introduces a new cmdline argument bootdev, to support the case where multiple nics need to be up before the netroot handler is called. Cases involved might be bonding, iscsi multipathing, bonding, ... This argument is required to decide which interface is the primary to use for dhcp root-path, default gw, etc. When multiple ip= items are present on the cmdline, the ip= parser now enforces the presence of <dev> further demands that the new argument bootdev contains the name of the primary interface. Configurtion if of course still delegated to netroot but in is enhance to ensure that netroot "waits" for all required interfaces to be up. Example: root=dhcp ip=eth0:dhcp ip=client-ip:::netmask::eth1:off bootdev=eth0 First, the ip= cmdline parser ensures that all ip items contain a <dev> then checks the ip items and checks as well that an ip= item for the given bootdev was found. When the first netroot starts, probably for eth1, it checks wheter interface configuration for all interfaces is available. If not it exits. The second start of netroot (eth0, which was a bit delayed because of dhcp) sees that all interfaces are present, configures them and continues.
16 years ago
# This ensures that BOOTDEV is always first in IFACES
if [ -n "$BOOTDEV" ] && [ -n "$IFACES" ] ; then
IFACES="${IFACES%$BOOTDEV*} ${IFACES#*$BOOTDEV}"
IFACES="$BOOTDEV $IFACES"
fi
# Store BOOTDEV and IFACES for later use
[ -n "$BOOTDEV" ] && echo $BOOTDEV > /tmp/net.bootdev
[ -n "$IFACES" ] && echo $IFACES > /tmp/net.ifaces
netroot: Add ip= cmdline checker As with other netroot boot arguments ip= lines should be parsed and checked. Having this has the advantage that other cmdline scripts can tell the ip= parser if dhcp or ip=:srv:... is needed, like parse-root.sh (renamed dhcp-fallback) or parse-nfsroot do. The nfs test-suite has one check which uses static ip lines, but the autoconf param is wrong. Fixed this as well.
16 years ago
multinic support: Add bootdev cmdline argument This introduces a new cmdline argument bootdev, to support the case where multiple nics need to be up before the netroot handler is called. Cases involved might be bonding, iscsi multipathing, bonding, ... This argument is required to decide which interface is the primary to use for dhcp root-path, default gw, etc. When multiple ip= items are present on the cmdline, the ip= parser now enforces the presence of <dev> further demands that the new argument bootdev contains the name of the primary interface. Configurtion if of course still delegated to netroot but in is enhance to ensure that netroot "waits" for all required interfaces to be up. Example: root=dhcp ip=eth0:dhcp ip=client-ip:::netmask::eth1:off bootdev=eth0 First, the ip= cmdline parser ensures that all ip items contain a <dev> then checks the ip items and checks as well that an ip= item for the given bootdev was found. When the first netroot starts, probably for eth1, it checks wheter interface configuration for all interfaces is available. If not it exits. The second start of netroot (eth0, which was a bit delayed because of dhcp) sees that all interfaces are present, configures them and continues.
16 years ago
# We need a ip= line for the configured bootdev=
removed warning "No ip= argument(s) for netroot provided..."
16 years ago
[ -n "$NEEDBOOTDEV" ] && [ -z "$BOOTDEVOK" ] && die "Bootdev Argument '$BOOTDEV' not found"