[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    [BusyBox] ifupdown.c problems
From:       Michael Sternberg <michael () dragon ! boscom ! com>
Date:       2003-01-29 6:47:03
[Download RAW message or body]

Latest busybox from CVS, PPC platform, following configuration:
CONFIG_IFCONFIG, CONFIG_IFUPDOWN, CONFIG_FEATURE_IFUPDOWN_IP,
CONFIG_FEATURE_IFUPDOWN_IPV4, CONFIG_IP, CONFIG_FEATURE_IP_ADDRESS,
CONFIG_FEATURE_IP_LINK, CONFIG_FEATURE_IP_ROUTE, CONFIG_ROUTE

/etc/network/interfaces contains:

auto lo
iface lo inet loopback
up route add -net 127.0.0.0 netmask 255.0.0.0 dev lo
down route del -net 127.0.0.0 netmask 255.0.0.0 dev lo
#
auto eth0
iface eth0 inet dhcp
address 172.17.4.202
netmask 255.255.0.0
gateway 172.17.1.10


~> ifconfig
~> ip address show
1: lo: <LOOPBACK> mtu 16436 qdisc noop
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100
    link/ether 12:34:56:78:02:02 brd ff:ff:ff:ff:ff:ff
~>
~>
~> ifup -an
ifup: udhcpc -n -p /var/run/udhcpc.eth0.pid -i eth0
ifup: ip link set lo up
ifup: ip addr add 127.0.0.1 dev lo
ifup: route

   - only first word from "route add..." performed

~> ifup -a
...
~> ifdown -an
ifdown: kill -9 `cat /var/run/udhcpc.eth0.pid`
ifdown: ifconfig eth0 down
ifdown: route
ifdown: ip addr flush dev lo
ifdown: ip link set lo down

   - why to use `ifconfig` if CONFIG_FEATURE_IFUPDOWN_IP was defined ?
   - only first word from "route del..." performed
   - if no udhcpc running, `kill` returns misleading error message
   - /var/run/udhcpc.eth0.pid should be removed after ifdown ?


                   Thanks, Michael.

-- 



[prev in list] [next in list] [prev in thread] [next in thread]