Bug 119000 - if-up.d scripts are not started for wireless
Summary: if-up.d scripts are not started for wireless
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Christian Zoz
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-27 12:27 UTC by Stanislav Brabec
Modified: 2005-09-27 12:38 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stanislav Brabec 2005-09-27 12:27:36 UTC
Reading documentation, scripts in /etc/sysconfig/network/if-up.d should be
started, whenever any interface gets up.

I have a Wi-Fi connection wlan0, which needs to start dashboard login script
after getting getting IP via DHCP. Besides this, I have eth0 (static address),
lo, usb0 (not configured) and ppp0 (manually started, not configured).

I wanted to add dashboard login script to /etc/sysconfig/network/if-up.d. But it
seems, that for wireless it is not started.

How to reproduce:

Creating /etc/sysconfig/network/if-up.d/test script containing

#! /bin/sh

echo "=== test $@ ==="

(Note: In my case this file is a symlink to another location.)

You see, that the script is started for all interfaces except wlan0.

I don't know, whether it is a but, but at least it does not behave as documented.

utx:~ # /etc/init.d/network restart
Shutting down network interfaces:
    eth0      device: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
    eth0      configuration: eth-id-00:50:fc:33:ce:ba
done
    usb0
    usb0      No configuration found for usb0
              Nevertheless the interface will be shut down.
    usb0      configuration:
done
    wlan0     device: Intersil Corporation Prism 2.5 Wavelan chipset
(rev 01)
    wlan0     configuration: wlan-id-00:60:b3:6b:d3:c5
done
Shutting down service network  .  .  .  .  .  .  .  .  .  .  .  .  .
done
Hint: you may set mandatory devices in /etc/sysconfig/network/config
Setting up network interfaces:
    lo
    lo        IP address: 127.0.0.1/8
=== lo lo -o rc ===
done
    eth0      device: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
    eth0      configuration: eth-id-00:50:fc:33:ce:ba
    eth0      IP address: 192.168.0.1/24
=== eth-id-00:50:fc:33:ce:ba ===
ethdone rc
    usb0
    usb0      No configuration found for usb0
unused
    wlan0     device: Intersil Corporation Prism 2.5 Wavelan chipset
(rev 01)
    wlan0     configuration: wlan-id-00:60:b3:6b:d3:c5
    wlan0     warning: using NO encryption
    wlan0     (DHCP) . . . . . IP/Netmask: 10.2.29.55 / 255.255.25 done
    ppp0
error: Can't handle ifcfg-file ifcfg-ppp0.
    ppp0      failed to bring interface ppp0 up
error: Can't handle ifcfg-file ifcfg-ppp0.
    ppp0      failed to bring interface ppp0 up
=== ppp0 ppp0 -o rc ===                                              failed
Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  done
Comment 1 Christian Zoz 2005-09-27 12:38:43 UTC
That test is misleading. The difference between the interfaces is that only wlan
uses dhcp. And in this case the post scripts will not be executed directly from
ifup, but later via a dhcpcd hook script (The postup scripts should be executed
after the interface got it's address.). The output from the script will be
swallowed by dhcpcd. Modify your test and use e.g. logger.