Bug 96994
Summary: | second ip address won't start at boot unless the first does | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Joseph Shraibman <jks> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-30 19:01:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joseph Shraibman
2003-06-08 04:33:59 UTC
That didn't work. What I do a network start after saving the config with that rechat-config-network this happens: Bringing up interface home-internal: Missing config file ../networking/profiles/homedsl/ifcfg-home. [root@jks-laptop ~]# ls /etc/sysconfig/networking/profiles/homedsl/ hosts ifcfg-home-external ifcfg-home-internal network resolv.conf ... and after I rebooted and the network didn't come up, I tried to start redhat-config-network to activate the network again, it caused a kernel panic! $ ls /etc/sysconfig/network-scripts [root@jks-laptop /home/jks]# ls /etc/sysconfig/network-scripts ifcfg-eth0 ifdown-isdn ifup-ippp ifup-routes ifcfg-eth0:1 ifdown-post ifup-ipv6 ifup-sit ifcfg-lo ifdown-ppp ifup-ipx ifup-sl ifdown ifdown-sit ifup-isdn ifup-wireless ifdown-aliases ifdown-sl ifup-plip init.ipv6-global ifdown-cipcb ifup ifup-plusb network-functions ifdown-ippp ifup-aliases ifup-post network-functions-ipv6 ifdown-ipv6 ifup-cipcb ifup-ppp Are you sure this won't cause a kernel panic? When I ran it I got this message: Changed the following Nicknames due to the initscripts: home-external -> home_externalhome-internal -> home_internal You need a newline in there or something. /etc/rc.d/init.d/network start seems to work, but stop only brings down the lo interface. I'll try actually rebooting the machine now. applications don't cause kernel panics... bad kernel modules do... OK that worked at the time (guess I forgot to update, sorry) but I since upgraded my redhat-config-network to 1.2.15-1 and its broken again huh? what is borken? /etc/rc.d/init.d/network start does not bring up any eth0 interfaces. It is supposed to bring up eth0:1. After I installed the rpm from comment #5 it worked, but then a while ago I upgraded redhat-config-network to the current errata version. Yesterday I changed my config to bring up both eth0 and eth0:1, then changed it back to bring up only eth0:1, and I'm back to my original problem. hmmm... sounds like an initscripts issue... but can you please attach your current /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/network-scripts/ifcfg-eth0:1 /etc/sysconfig/network-scripts]$ cat ifcfg-eth0\:1 # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. GATEWAY=192.168.0.1 TYPE=Ethernet DEVICE=eth0:1 HWADDR=00:08:02:4c:55:6c BOOTPROTO=none NETMASK=255.255.0.0 ONBOOT=yes IPADDR=192.168.0.2 USERCTL=no PEERDNS=yes NETWORK=192.168.0.0 BROADCAST=192.168.255.255 There is no ifcfg-eth0 Did you deactive the checkbox in the list? Hmm... you shouldn't do that! Another consistency check for r-c-n. Please activate the checkbox and edit eth0. Then _de_select "Activate device when computer starts". Edit eth0:1 and make sure: "Activate device when computer starts" is active I thought I was supposed to uncheck the checkbox. Anyway I did what you said and it still doesn't work. Now: /etc/sysconfig/network-scripts]$ cat ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none ONBOOT=no IPADDR=64.36.42.194 NETMASK=255.255.255.248 USERCTL=yes PEERDNS=no GATEWAY=' 64.36.42.193' TYPE=Ethernet NETWORK=64.36.42.192 BROADCAST=64.36.42.199 /etc/sysconfig/network-scripts]$ cat ifcfg-eth0:1 # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. GATEWAY=192.168.0.1 TYPE=Ethernet DEVICE=eth0:1 HWADDR=00:08:02:4c:55:6c BOOTPROTO=none NETMASK=255.255.0.0 ONBOOT=yes IPADDR=192.168.0.2 USERCTL=no PEERDNS=yes NETWORK=192.168.0.0 BROADCAST=192.168.255.255 hmm... then the initscripts cannot cope with eth0:1 active and eth0 not? reassigning to the initscripts... Bill? Well like I said you had this fixed at one point, but then I upgraded my redhat-config-network and broke it. Hm, yes, ifcfg-eth0:1 won't be brought up on boot if ifcfg-eth0 isn't brought up at all. For aliases, if you have one you want to be brought up at all times, make it the primary address for now. Now I have the opposite problem. Both are coming up, when I only want one to. The other one has ONBOOT=no but it still starts up For aliases, set ONPARENT={yes,no}. Aliases don't support ONBOOT at the moment. Shouldn't redhat-config-network take care of that? Should I file a seperate bug for that? ONBOOT may be added for aliases in a future release, so maybe not. Of course, in future-future releases, the specific alias device framework will probably be deprecated in favor of just adding more IP addresses to devices. But that's not going to happen in the next month or two. :) Closing bugs on older, no longer supported, releases. Apologies for any lack of response. Realistically, I don't see any issues left here: - aliases don't operate fully independent of the parent (parent must be up for any alias to run) - ONPARENT=(yes|no) is the defined means of changing this. |