Files
poky/meta/recipes-connectivity/zeroconf/zeroconf/debian-zeroconf
Richard Purdie 29d6678fd5 Major layout change to the packages directory
Having one monolithic packages directory makes it hard to find things
and is generally overwhelming. This commit splits it into several
logical sections roughly based on function, recipes.txt gives more
information about the classifications used.

The opportunity is also used to switch from "packages" to "recipes"
as used in OpenEmbedded as the term "packages" can be confusing to
people and has many different meanings.

Not all recipes have been classified yet, this is just a first pass
at separating things out. Some packages are moved to meta-extras as
they're no longer actively used or maintained.

Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-08-27 15:29:45 +01:00

1.1 KiB

#!/bin/sh

if [ ! -x /usr/sbin/zeroconf ]; then exit 0 fi

IPv4 link-local addresses (zeroconf) are

only applicable on the 'inet' address family

[ "X$ADDRFAM" != "Xinet" ] && exit 0

However there are some methods where it doesn't

make any sense to configure an IPv4LL address

not on loopback

[ "X$METHOD" = "Xloopback" ] && exit 0

not on ppp or wvdial either

[ "X$METHOD" = "Xppp" ] && exit 0 [ "X$METHOD" = "Xwvdial" ] && exit 0

The administrator may have blacklisted interfaces

or only want zeroconf in a fallback situation

[ -f /etc/default/zeroconf ] && . /etc/default/zeroconf

[ -n "$DISABLE" ] && exit 0

for BLACK in $IFBLACKLIST; do case $IFACE in $BLACK) exit 0 ;; esac done

should we only allocate an address if we do not already have one?

if [ -n "$FALLBACK" ]; then /bin/ip addr show $IFACE scope global | grep -q "inet" IP=$? if [ $IP -eq 0 ]; then /bin/ip route add 169.254.0.0/16 dev $IFACE exit 0 fi fi

otherwise, run if we aren't already going

if [ ! -r /var/run/zeroconf.$IFACE.pid ]; then /usr/sbin/zeroconf -i $IFACE fi

exit 0