Problem automatically bringing eth0 up with new baselayout

divined · Apprentice Joined: 23 Jul 2004 Posts: 165

I emerged baselayout-1.11.12-r4 today. I did all the necessary changes in /etc/conf.d and finally changed the /etc/init.d/net config file to the following :

taipan67 · Posted: Thu Jun 09, 2005 9:21 pm Post subject:

I don't think you need to do anything to any of the files in /etc/init.d/ - they're not config-files. It looks like you should only need the line

radfoj · Posted: Thu Jun 09, 2005 9:31 pm Post subject:

I upgraded baselayout too today, but didnt change anything in /etc/init.d/ . But after emerging, I found postmerge notice:

seppelrockt · Guru Joined: 14 May 2004 Posts: 423

@ radfoj: Did you run etc-update? Sounds like you didn't and this might lead to some problems in the feature or at least you will not benefit from new baselayout features. baselayout changes 20+ files in /etc with etc-update.

Does anybody know whether there is a summary of new baselayout features and how to configure it properly?

radfoj · Posted: Thu Jun 09, 2005 10:21 pm Post subject:

Ok, correction, insteed etc-update I am using cfg-update. You are right, many changes in /etc/* today

drumz · Apprentice Joined: 10 Nov 2002 Posts: 213

divined:

In the first post you list the broadcast included in the config_eth0 line. In looking at the handbook and the sample file (/etc/conf.d/net.example) they don't have it. Try taking it out and seeing if it makes a difference:

This:

MickKi · Veteran Joined: 08 Feb 2004 Posts: 1173

Just to add to the problems reported here:

Upon booting I now get the following errors:

xentric · Guru Joined: 16 Mar 2003 Posts: 410 Location: Netherlands

divined · Apprentice Joined: 23 Jul 2004 Posts: 165

I checked /etc/inti.d/ to see what is going on with the intializatino scripts. Here is what I`ve got :

xsteadfastx · Posted: Fri Jun 10, 2005 6:28 am Post subject:

Wim VDM · n00b Joined: 12 Dec 2004 Posts: 21

I had the same problem after using cfg-update.

I fixed it like this:
rm /etc/init.d/net.lo /etc/init.d/net.eth0 (remove the bad scripts)
emerge baselayout (reemerging baselayout creates the correct scripts)
etc-update (just to make sure every script is up to date, didn't do a thing though)

Hope this works for you...

divined · Apprentice Joined: 23 Jul 2004 Posts: 165

That did it. I only used

Wim VDM · n00b Joined: 12 Dec 2004 Posts: 21

It must be a bug with cfg-update and symlinks as xentric says.

If cfg-update was written without considering that a file might be a link, I can see how that could srews things up.

MickKi · Veteran Joined: 08 Feb 2004 Posts: 1173

Thanks guys,

I'll try it when I get home. BTW I used dispatch-conf which evidently did not do it right. Is cfg-update much different?
_________________
Regards,
Mick

seppelrockt · Guru Joined: 14 May 2004 Posts: 423

For the hostname / domainname messages on boot - after setting those two in /etc/conf.d/hostname and /etc/conf.d/domainname you can savely delete /etc/hostname and /etc/dnsdomainname - and the messages will magically disappear ;-)

For all those who have troubly it might be worse mentioning that the network section of the gentoo handbook was updated for the new baselayout and describes very detailed how to set everything right - including WLAN. Did this last night and it just works (tm).

MickKi · Veteran Joined: 08 Feb 2004 Posts: 1173

OK, I am reading the file /etc/conf.d/domainname and it says:

MickKi · Veteran Joined: 08 Feb 2004 Posts: 1173

Updating /etc/conf.d/hostname and /etc/conf.d/domainname partly did the trick, but I am still getting the gateway error as shown above:

drumz · Apprentice Joined: 10 Nov 2002 Posts: 213

When I did all of my updated, I used etc-update to handle the files except for a few that I hand-edited, so that may be one reason why my change over was a little bit less strenuous than what some of you experienced.

MickKi: That line for the routes looks ok, but try changing the 'via' to 'gw'. The handbook says to use 'via', but the net.example file uses 'gw' instead. I started out using the 'via' thing, but had some problems, read the handbook, changed it, didn't see any change (after a /etc/init.d/net.eth0 stop/start) so I then rebooted and all was well.

MickKi · Veteran Joined: 08 Feb 2004 Posts: 1173

Thanks drumz,

I always start my eth0 by hand (after the machine has booted up). I've tried changing the "via" to "gw" as you suggest, but neither seem to work. :evil:

The same error shows up every time as if the /etc/conf.d/net is not being read, or as if "via" and "gw" do the same thing.

I even tried:

drumz · Apprentice Joined: 10 Nov 2002 Posts: 213

Here are the only two lines I have in my /etc/conf.d/net:

xentric · Guru Joined: 16 Mar 2003 Posts: 410 Location: Netherlands

This is what I have in /etc/conf.d/net

MickKi · Veteran Joined: 08 Feb 2004 Posts: 1173

Thanks guys!

Something is wrong with my box. My /etc/conf.d/net indeed has the same two lines like yours:

drumz · Apprentice Joined: 10 Nov 2002 Posts: 213

The only thing I can think of is to try grepping through /etc for your router IP address:

MickKi · Veteran Joined: 08 Feb 2004 Posts: 1173

Thanks again drumz!

This is what I get:

Conditional_Zenith · Posted: Mon Jun 13, 2005 1:14 am Post subject:

MickKi: I had the same problem as you. It seems that setting the gateway in /etc/conf.d/net should only be done for static IP's. Comment out your gateway lines and dhcpcd should set the gateway for you. What was happening before (I think) is that dhcpcd was setting the gateway, and then the init script was trying to set it again, but got an error as that route was already set.

If you want to check that the gateway is set, run /sbin/route and you should see something like this: