[Bug-report] [Lunar Linux 0000307]: The new network init script as listed in news on site does not work for me

[bug-reports at lunar-linux.org]

A BUGNOTE has been added to this bug.
=======================================================================
http://bugs.lunar-linux.org/view_bug_page.php?f_id=0000307
=======================================================================
Reporter:                   amadeus
Handler:                    kc8apf
=======================================================================
Project:                    Lunar Linux
Bug ID:                     0000307
Category:                   moonbase
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
=======================================================================
Date Submitted:             2003-06-19 14:46 GMT
Last Modified:              2003-06-23 04:46 GMT
=======================================================================
Summary:                    The new network init script as listed in news on site does not work for me
Description: 
The new net init scipt is supposed to work for static IP. I have eth0
static and eth1 wireless-static. All was fine with original script (from
iso?) When I switched to the new one, things messed up. Not sure what
happened exactly but it seems that when my net got detected, eth0 was
found but when pcmcia (eth1- wireless) was loaded, is assumed eth0 was my
wireless and overwrote/mixed configurations. It may be unclear. I can
assists in reproducing this if you'd like. Just let me know
=======================================================================

-----------------------------------------------------------------------
 kc8apf - 2003-06-19 17:02 GMT 
-----------------------------------------------------------------------
I need to know exactly what is happening to try and diagnose.  You may be
seeing that the default gateway is being set to one particular card and
this is correct.  Your system should have only one default gateway and it
will be whatever you set it to via lnet.  However, if you are seeing the
IP address or subnet mask on eth0 change when eth1 is coming up, then I
need to know exactly what is happening.

-----------------------------------------------------------------------
 amadeus - 2003-06-19 17:17 GMT 
-----------------------------------------------------------------------
Hmm. I just go the latest moonbase to get the very latest network script
from net-tools to retest and it seems corrupted. It is un unexecutable
binary instead of a shell script.  Thoughts?

-----------------------------------------------------------------------
 kc8apf - 2003-06-21 01:39 GMT 
-----------------------------------------------------------------------
The network script in the moonbase
(/var/lib/lunar/moonbase/net/net-tools/init.d/network) is a shell script. 
You might try doing a lin moonbase to see if you just had a bad download
of it.  It should be a very lengthy, but readable, shell script.

-----------------------------------------------------------------------
 amadeus - 2003-06-21 02:37 GMT 
-----------------------------------------------------------------------
Yes. Must have been a bad download.  This is the result of the test using
old and new. Again I have an internal ethernet on eth0 and a pcmcia
wireless on eth1, bot static IP.

OLD NETWORK SCRIPT:
- init.d/network start:
eth0 is loaded correctly

-init.d/pcmcia start:
ifconfig shows both eth0 and eth1 correctly and iwconfig shows correct
wireless info for eth1

NEW NETWORK SCRIPT
-init.d/network start:
eth0 is loaded correctly

-init.d/pcmcia start:
ifconfig only shows eth0 and iwconfig shows eth1 with wireless info for
eth0 (since eth0 is not wireless it means a blank essid and other info)

In conclusion is appears that the pcmcia is using the eth0 info instead of
eth1 info from lnet. It is confirmed if I add an essid in lnet for eth0.
It will show up on iwconfig.

I'm not sure which script has a booboo but the pair does not work
together. I will try to look at it but it may be obvious to you.

-----------------------------------------------------------------------
 kc8apf - 2003-06-23 04:46 GMT 
-----------------------------------------------------------------------
Well, I just spent an hour looking over the networking script.  For what
you are describing, the only thing I can think of is that your config for
eth1 got changed to a symlink to the config for eth0.

Could you check the config files in /etc/config.d/network?  Make sure
there aren't any symlinks (I'm assuming you're not using the undocumented
profile feature).  If either one is, delete it and run lnet to setup the
device.  Otherwise, open both config files and make sure the settings are
proper for that device.  If not, run lnet and configure that device again.
 Check the config file to make sure it actually updated properly.  Let me
know what happens.

It appears that this is more likely either not an issue or it's an issue
with lnet rather than the network script.