behavior of ifdown command

Hi,

I had a question regarding the way "ifdown" script works in SUSE.

In Suse 9.1, if we make three virtual interfaces, eth0:0, eth0:1 &
eth0:2, in that order itself, and then after some time do an "ifdown
eth0:0", all the three virtual interfaces created above are removed.
But if i do "ifdown eth0:1" OR "ifdown eth0:2", only the specified
virtual interface is removed, rest two of them remain there as it is.

So in summary, if one created 'n' number of virtual interfaces (on a
particular interface) as defined above, and did an ifdown on the
virtual interface made first, all the 'n' virtual interfaces are
removed, whereas if any other (any but first virtual interface) is
removed using ifdown, then only that interface is removed.

This was the behavior on SUSE 9.1.

ON Suse 10.2, the behavior is a bit different.
On 10.2, ir-respective of which virtual interface is created first, if
we do an ifdown on any of the virtual interface created all the virtual
interfaces created on that particular interface are removed.

I was trying to find some documentation on this behavior change of
ifdown to confirm my observations.
Any help in this context will be appreciated.

Also just for info, on red hat & fedora, ifdown command can not be
given for a virtual interface like eth0:0, only for interfaces like
eth0. eth1.. etc.

Thanks in advance.


--
gaurav_globallogic
------------------------------------------------------------------------
gaurav_globallogic's Profile: http://forums.novell.com/member.php?userid=16855
View this thread: http://forums.novell.com/showthread.php?t=326902

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Have you looked at the /sbin/ifup (which is where /sbin/ifdown is
softlinked-to I believe) to see what it is doing? On my SLEd box around
line 430 is a block that shuts down depending interfaces. Perhaps that
is running and, somehow, determining the other interfaces are dependent
on the one you are stopping. It would make sense with eth0:0 that the
others go down but the other way around seems odd. Perhaps try `bash -x
/sbin/ifdown eth0:1` (using your own virtual interface) to see if you
can see where in the processing it is doing what you are seeing.

Good luck.





gaurav globallogic wrote:
| Hi,
|
| I had a question regarding the way "ifdown" script works in SUSE.
|
| In Suse 9.1, if we make three virtual interfaces, eth0:0, eth0:1 &
| eth0:2, in that order itself, and then after some time do an "ifdown
| eth0:0", all the three virtual interfaces created above are removed.
| But if i do "ifdown eth0:1" OR "ifdown eth0:2", only the specified
| virtual interface is removed, rest two of them remain there as it is.
|
| So in summary, if one created 'n' number of virtual interfaces (on a
| particular interface) as defined above, and did an ifdown on the
| virtual interface made first, all the 'n' virtual interfaces are
| removed, whereas if any other (any but first virtual interface) is
| removed using ifdown, then only that interface is removed.
|
| This was the behavior on SUSE 9.1.
|
| ON Suse 10.2, the behavior is a bit different.
| On 10.2, ir-respective of which virtual interface is created first, if
| we do an ifdown on any of the virtual interface created all the virtual
| interfaces created on that particular interface are removed.
|
| I was trying to find some documentation on this behavior change of
| ifdown to confirm my observations.
| Any help in this context will be appreciated.
|
| Also just for info, on red hat & fedora, ifdown command can not be
| given for a virtual interface like eth0:0, only for interfaces like
| eth0. eth1.. etc.
|
| Thanks in advance.
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIIceC3s42bA80+9kRAh/fAJ9hKwoKLmrPPdsL4QBKvb9qgLjK3gCfSrv4
YuUsGrg6y5wJbAGvQNMNGYA=
=/H8l
-----END PGP SIGNATURE-----