OpenRC support thread, 2d Edition

[UberLord]

Ok, updated to openrc-0.5.1 and switched to new network script.
My working br0 vbox0 eth0 bridge example:

Looks good!

Now I searching a nice ppp start/stop wrapper.

When you do, email the Gentoo devs with it

[UberLord]

I also updated to 5.1, but I can't find any info on how to setup ipv6.
My old config looks like this:

Code: Select all

config_eth0=( "192.168.0.8 netmask 255.255.255.0 brd 192.168.0.255"
              "2001:xxx:xxx::8/48" )
routes_eth0=( "default via 192.168.0.1"
              "default via 2001:xxx:xxx::1 dev eth0" )

This may work

Code: Select all

ifconfig_eth0="192.168.0.8 netmask 255.255.255.0; inet6 add 2001:xxx:xxx::8/48"
defaultroute="192.168.0.1"

There is currently no facility to have a default route for ipv6 and ipv4. That will hopefully be fixed soon.

[mv]

OTHER things, such as DHCP, PPP, etc belong in external init scripts

The problem is that the PPP script needs to interfere much more with the init system than usual init scripts: For instance, it is not sufficient that openrdate depends on such an init service unless the service waits until PPP is actually up. How to find that it is up without relying on callbacks which require net.* functionality? One could store/remove a file in /var/run from /etc/ppp/ip-{up,down}.d, but then one runs into problems when PPP crashes. Moreover, how long to wait before giving up? In any case, the waiting slows down the boot process unless one uses parallel booting - it seems that net.* callbacks were the superior solution. Also, it would be better to have a somewhat standard approach to such common tasks than each user having to write such rather complex scripts by himself - otherwise, soon it will not be possible to help each other with network problems.

A lot of the functionality of the net.xxx scripts is now covered by dhcpcd-5

This is true. My system at work which just requires a static adress and a dhcp ran after easy configuration out of the box. From the description I guess that the same is true if you want to setup a network with a fixed wireless server. However, as I understand, if you need a flexible wireless, things get clumsy, i.e. at least judging from the code of iwconfig.sh (and from my failed attempts) I guess it is hard to replace the previous

Code: Select all

modules="iwconfig"
config_wlan0="dhcp"

(correct me, if I am wrong - I really know almost nothing about wireless).

For gui users, dhcpcd-gtk provides per SSID and interface basic config support. It talks to wpa_supplicant.

This is very interesting. I have not tried it yet, but I hope that this might be a solution for the above problem? I suggest you should mention it also somewhere in the network file or openrc docu. Is there a reason why it is not in portage, or do we just have to wait?

The old style net.xxx scripts are not going away, they are just not installed by default

This is also very good to know to have a fallback (I was afraid that they will be there only for one or two more versions and then will be dropped).

I'm bored trying to fix bugs that I don't have the infrastructure to replicate or support

I can understand this very good.

I was so happy that in gentoo (in contrast to ubuntu etc) I was not forced to use networkmanager which badly interfered with any manual configuration, but it seems these good times are changing?

Ah, but with the whole init.d/network it's ALL manual

At least if in a hotel/conference room just a "standard wlan access" (without any further information for the user) is provided, one should be able to use it quickly by just specifying that one wants such a standard configuration (e.g. as by the two lines of code mentioned above). However, if one is forced to use networkmanager for this, this might interfere with the manual configuration fom init.d/network, since networkmanager has its own ideas how to setup routes etc. The previous net.wlan0 is much better in this respect.

[rahulthewall]

I use WICD to manage my network (so not manual or automatic however you want to call it) and everything works as before with USE=-oldnet (no net.* service enabled, but network is at runlevel boot).

[mv]

I use WICD to manage my network

I tried that, too, but got no connection with it, though it seemed to run properly. Maybe I configured something wrong or my hardware has problems, no idea... as I said I also had no success with wpa_supplicant, but only the net.wlan0 with wireless-tools worked (even out of the box).

[Bill Cosby]

Didn't udev rely on net.* scripts? Hotplug seems to have stopped working after the upgrade, and the removal of the net.* scripts?

[mjbjr]

Apache2 won't start:

# /etc/init.d/apache2 start
* Caching service dependencies... [ ok ]
* Bringing up interface eth0
* 192.168.17.20/24...
Error: an inet prefix is expected rather than "192.168.17.20/24/24". [ !! ]
* ERROR: net.eth0 failed to start
* Bringing up interface eth0
* 192.168.17.20/24...
Error: an inet prefix is expected rather than "192.168.17.20/24/24". [ !! ]
* ERROR: net.eth0 failed to start
* ERROR: cannot start netmount as net.eth0 would not start
* ERROR: cannot start apache2 as net.eth0 would not start

# /usr/sbin/apache2ctl start
* Bringing up interface eth0
* 192.168.17.20/24...
Error: an inet prefix is expected rather than "192.168.17.20/24/24". [ !! ]
* ERROR: net.eth0 failed to start
* Bringing up interface eth0
* 192.168.17.20/24...
Error: an inet prefix is expected rather than "192.168.17.20/24/24". [ !! ]
* ERROR: net.eth0 failed to start
* ERROR: cannot start netmount as net.eth0 would not start
* ERROR: cannot start apache2 as net.eth0 would not start

And while 'net.eth0' may not want to start, my net connection
via eth0 is running fine, though possibly, I set it up manually
when it didn't work properly at boot, but I'm not sure at this point.

I went through the net configs, and while I have settings for "192.168.17.20/24",
I don't see any "192.168.17.20/24/24", so it would seem that two settings
are being compounded by a script some place.

(I've been running gentoo for four or five years, now, and except for
the first one, this has been the hardest, by far. I've rebooted so many
times the disks have had forced checks. ) )

running:
# uname -a
Linux localhost 2.6.30-gentoo-r4 #6 SMP Tue Sep 22 21:25:59 PDT 2009 x86_64 Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz GenuineIntel GNU/Linux
baselayout-2.0.1
openrc-0.5.1

This is a new gentoo build, and I'm betting I'll see similiar when I add
more apps. I've spent a couple of days searching all around, and this
appears to be related to openrc and hotplugging. I've seen set blah, and
then in another reply set !blah.

Some suggestions have pointed to 'depscan.sh', but I don't have that,
and haven't been able to determine which package contains it, or maybe
at this point it's deprecated.

At this point, I'm fairly confused about what is going on.

Is there a definitive solution to this net mount problem?

Thanks
.

[sera]

Hi UberLord,

I had the time to look into the current changes regarding networking and I start to like the idea of splitting up the net.lo script.

Currently there is a lack of available init scripts within Gentoo, therefore the confusion in here. So I kindly ask you to install a bunch of them with openrc (e.g under /usr/share/openrc/netscripts) or provide a separate package openrc-netscripts for instance till the gentoo developers catch up.
Candidates are the funtoo-netscripts and the ones from the openrc tarball, namely wpa_supplicant.in works nicely here. I'm sure you know of other useful ones.

This would greatly help many of us even if they were not "fire proof", so I hope I don't ask for to much.

Regards sera.

[UberLord]

I don't generally control what gets installed via the ebuild.

However, the source tarball does contain a collection of init scripts I use that are not in Gentoo - wpa_supplicant for starters.

To get it, do this.

cd /tmp
tar xvjpf /usr/portage/distfiles/openrc-0.5.1.tar.bz2
cd openrc-0.5.1/init.d.misc
make
install wpa_supplicant /etc/init.d

You can browse the list of init scripts here.

[Fran]

So what's the new way to set ypbind? This is my old conf.d/net:

Code: Select all

dns_domain="my_dns_domain"
dns_servers="xx.xx.xx.xx xx.xx.xx.xx"
nis_domain="my_nis_domain"
nis_servers="xx.xx.xx.xx"

config_eth0="xx.xx.xx.31 netmask 255.255.255.0 broadcast xx.xx.xx.255"
routes_eth0="default via xx.xx.xx.1"

This is what I have now:

/etc/conf.d/network:

Code: Select all

ifconfig_eth0="xx.xx.xx.31 netmask 255.255.255.0"
defaultroute="xx.xx.xx.1"

/etc/dhcpcd.conf

Code: Select all

static domain_name=my_dns_domain
static domain_name_servers=xx.xx.xx.xx xx.xx.xx.xx

[the rest is the default config]

/etc/yp.conf

Code: Select all

domain my_nis_domain server xx.xx.xx.xx

But... where do I set the nis domain name? ypbind doesn't start if it isn't set.


(edit) And BTW, what's the difference between setting the fixed IP address in conf.d/network and setting

Code: Select all

static ip_address=xx.xx.xx.xx

in /etc/dhcpcd.conf? And what happens if they conflict?

[Guinpen]

Hi,

Rather than hijacking the thread, I would like to point you to my OpenRC problem: viewtopic-p-6012266.html

Thanks!

[Fran]

Never mind my last question, I see gentoo has decided to force oldnet-style in 0.5.1-r1 .

I suppose that by the time things settle down everything will be easier to configure (at least as easy as they are now).

[mv]

The problem I had with pppd actually is the same with dhcpcd: It is not sufficient that e.g. network depends on dhcpcd. For example, openrdate will be started once dhcpcd and the network have been started. But this does not mean that the network is ready, since dhcpcd need not have yet got its lease. Hence, openrdate will usually fail to start...
I think, either it must be possible to check whether the net is really up in the desired way (and the network script has to wait so long) or some callback solution must be implemented.

[UberLord]

The problem I had with pppd actually is the same with dhcpcd: It is not sufficient that e.g. network depends on dhcpcd. For example, openrdate will be started once dhcpcd and the network have been started. But this does not mean that the network is ready, since dhcpcd need not have yet got its lease. Hence, openrdate will usually fail to start...
I think, either it must be possible to check whether the net is really up in the desired way (and the network script has to wait so long) or some callback solution must be implemented.

This has recently been pointed out to me.
dhcpcd-5.1.2 will have better support for this. The current testing version I have won't daemonise right away if 1 interface as a carrier. If this fails for you then the new -w flag will force a wait for an IP.

I hope to have 5.1.2 out by the weekend.

[UberLord]

/etc/yp.conf

Code: Select all

domain my_nis_domain server xx.xx.xx.xx

But... where do I set the nis domain name? ypbind doesn't start if it isn't set.

http://roy.marples.name/projects/openrc ... 675ab6c043
Fixed

(edit) And BTW, what's the difference between setting the fixed IP address in conf.d/network and setting

Code: Select all

static ip_address=xx.xx.xx.xx

in /etc/dhcpcd.conf? And what happens if they conflict?

network ones will get applied first, then dhcpcd will stamp over it.

[Mike Hunt]

Didn't udev rely on net.* scripts? Hotplug seems to have stopped working after the upgrade, and the removal of the net.* scripts?

You still need the new net.lo which only performs the task of setting up the lo interface.

Code: Select all

$ qfile net.lo
sys-apps/openrc (/etc/init.d/net.lo)

There is no need to add it to any runlevel though. Openrc handles that.

[Kingoftherings]

Having some major clock issues.

Seems like every time I start up Gentoo my clock has changed.
Here is /etc/conf.d/hwclock

Code: Select all

clock="local"
clock_systohc="NO"
clock_args=""

And here is /etc/timezone

Code: Select all

America/Chicago

[dmpogo]

Having some major clock issues.

Seems like every time I start up Gentoo my clock has changed.
Here is /etc/conf.d/hwclock

Code: Select all

clock="local"
clock_systohc="NO"
clock_args=""

And here is /etc/timezone

Code: Select all

America/Chicago

What does your hardware clock show (hwclock --show as root) ? You do not update harware clock to the system one on logout, so if hardware clock shows wrong time, it will be set on every boot.

[Mike Hunt]

Kingoftherings,

are you using net-misc/ntp ?

[Anon-E-moose]

Having some major clock issues.

Seems like every time I start up Gentoo my clock has changed.
Here is /etc/conf.d/hwclock

Code: Select all

clock="local"
clock_systohc="NO"
clock_args=""

And here is /etc/timezone

Code: Select all

America/Chicago

do you have a /etc/adjtime file and if so what is in it?

[d2_racing]

Any info on how to configure a wireless card using wpa_supplicant on dhcp ip adress : http://forums.gentoo.org/viewtopic-p-60 ... ml#6017497

I only saw some example when the wireless is using a static IP adress.

[sera]

Any info on how to configure a wireless card using wpa_supplicant on dhcp ip adress : http://forums.gentoo.org/viewtopic-p-60 ... ml#6017497

I only saw some example when the wireless is using a static IP adress.

6013166

[Mike Hunt]

Any info on how to configure a wireless card using wpa_supplicant on dhcp ip adress : http://forums.gentoo.org/viewtopic-p-60 ... ml#6017497

I only saw some example when the wireless is using a static IP adress.

I'm not sure, but what about in /etc/dhcpcd.conf

Code: Select all

allowinterfaces wlan0

[UberLord]

Any info on how to configure a wireless card using wpa_supplicant on dhcp ip adress : http://forums.gentoo.org/viewtopic-p-60 ... ml#6017497

I only saw some example when the wireless is using a static IP adress.

I'm not sure, but what about in /etc/dhcpcd.conf

Code: Select all

allowinterfaces wlan0

That's wrong - ethernet (inc wireless) interfaces are always allowed by default.
You just configure wpa_supplicant.conf and dhcpcd.conf as needed. Then add dhcpcd to the default runlevel.
You'll then need to grab the wpa_supplicant init script from the OpenRC source as shown above and go with that also.

Good luck!

[Mike Hunt]

Okie dokie, thanks UberLord.