The new OpenRC networking script

[d2_racing]

@gerard82, do you use the oldnet use flag or not ?

[gerard27]

I do not have that flag in /etc/make.conf.
I tried emerge -pv openrc and that didn't show that flag either.
Hope this answers your question.
Gerard.

[d2_racing]

Can you post this :

Code: Select all

# emerge -av openrc

[Etal]

It was removed, and oldnet is now set for everyone.

Code: Select all

[ebuild     U ] sys-apps/openrc-0.5.1-r1 [0.5.1] USE="ncurses pam unicode -debug (-oldnet%*)" 0 kB

Code: Select all

*openrc-0.5.1-r1 (15 Oct 2009)

  15 Oct 2009; Mike Frysinger <vapier@...org> +openrc-0.5.1-r1.ebuild,
  openrc-9999.ebuild:
  Rewrite the oldnet handling and make it the default for everyone.

[pappy_mcfae]

So right now, do you have a working lan card and what about your Wifi card ?

Can you tell us more about your experiment ?

Yes, I have a working wired LAN connection. The machine on which I set this up is core-too, and it doesn't have wireless. For the moment, I'm going to experiment a bit more with it, and update another machine. I want to make sure that this is both stable, and set to be around a while before I set up pappy-lap to use it. I'd have to completely rethink my automatic networking setup. At the moment, I'm not that inspired.

As to what I found out with my experiment:

1. If you're going to do it, make sure you emerge openresolv first. It will be called by the script. If it's not there, the script, and your networking, will fail.
2. If you're going to use the new scripting, add -oldnet to your /etc/make.conf USE flags list, or add the line sys-apps/openrc -oldnet to /etc/portage/package.use. This will keep openrc from rewriting the script if you reemerge openrc.
3. move the following files somewhere where they won't get in the way:
a. /etc/conf.d/net
b. /etc/conf.d/net.eth0
c. /etc/runlevels/default/net.eth0
d. /etc/runlevels/boot/net.lo
e. /etc/init.d/net.lo
4. modify the script below to fit your system.

Code: Select all

#!/sbin/runscript
# Copyright 2009 Funtoo Technologies, LLC
# All rights reserved. Released under the 2-clause BSD license.

IP=192.168.0.130
NM=255.255.255.0
GW=192.168.0.1
INT=eth0
DOM=no.org
NS1=65.68.49.50
NS2=65.68.49.51
NS3=192.168.0.1

depend() {
        provide net
        after net.lo
}

start() {
        ebegin "Bringing up network interface $INT"
        ifconfig $INT $IP netmask $NM up && \
        route add default gw $GW $INT && \
        resolvconf -a $INT << EOF
domain $DOM
nameserver $NS1
nameserver $NS2
nameserver $NS3

EOF
        eend $?
}

stop() {
        ebegin "Shutting down network interface $INT"
        resolvconf -d $INT && \
        route del default gw $GW $INT && \
        ifconfig $INT down
        eend $?
}

5. make the script executable, and place it in /etc/init.d
6. rc-update add <net_script_name> default, where <net_script_name> is the name you give your finalized script.
7. rc-update add network boot.
8. reboot.

[below edited for correctness.]

Upon reboot, it should be noted that if done properly, you will only see the interface declared as INT in the above script. In the case of my machine, I saw Bringing up network interface eth0.... There was no other mention of network activation.

If you see networking warning messages, that means something wasn't done correctly (most likely the script itself). Trust me, I just set up my second machine, and I had some issues with the script. Once those were fixed, the problems went away.

[ /edit]

Notes and observations so far:

a. if you are using kweather, you need to make sure that one of your nameservers is the same as the default gateway. If you don't do this, kweather will not update properly. Note that one of the three name servers is the default gateway.
b. You can name the script anything you desire. You just have to make sure that the script is executable.
c. You can start and stop the interfaces by simply typing /etc/init.d/<network_script_name> start or /etc/init.d/<network_script_name> stop. No more fancy incantations required.
d. for reference, see this article.

Note that the only divergence I've seen from the article in what I did is naming the script. The article seems to want to maintain the net.eth0 naming standard, yet naming the script net.eth0 will make openrc throw an error message during emerge. The message can be ignored as long as things are starting and running properly.

Blessed be!
Pappy

[gerard27]

@d2racing,
Makes no difference.
The posts before this explain what's happening.
Gerard.

[Evileye]

pappy_mcfae, thanks for posting that information. I am about to take the plunge and try out openrc-0.5.1-r1

I have 3 question....

My computer currently has net.eth0 AND net.eth1. net.eth0 connects to the internet while net.eth1 connects to my network. The script you posted above only mentions INT=eth0 . Do I use that script again but just changed it to say INT=eth1 Then give both scripts different names, make executable, place in /etc/init.d and configure to run at boot?

Does this also apply to wireless networking, just use INT=wlan0?

What about Ethernet bridging (net.br0)?

Thanks in advance

[pappy_mcfae]

pappy_mcfae, thanks for posting that information. I am about to take the plunge and try out openrc-0.5.1-r1

I have 3 question....

My computer currently has net.eth0 AND net.eth1. net.eth0 connects to the internet while net.eth1 connects to my network. The script you posted above only mentions INT=eth0 . Do I use that script again but just changed it to say INT=eth1 Then give both scripts different names, make executable, place in /etc/init.d and configure to run at boot?

Good question. Between you and I, and everyone else reading, I don't know. My assumption is that you would make an individual script for each interface you wish to bring up, and load them all into /etc/runlevels/default.

UberLord, if you read this, is this assumption correct?

Does this also apply to wireless networking, just use INT=wlan0?

Yes, there are several scripts available. The unfortunate thing is they're in new stage3's from funtoo. Fortunately for all concerned, I downloaded a recent funtoo stage-3, and I have all the scripts. I would have to untar the tarball again to get them, but when I do, I will post them on my server, and make a URL available.

What about Ethernet bridging (net.br0)?

Thanks in advance

Yes, there is a bridging script. Please allow me about a half hour or so to respond to other emails, and I will get the scripts and make them available.

Blessed be!
Pappy

[pappy_mcfae]

Alright. I've got it all set. Point your browser to http://www.kernel-seeds.org/funtoo-nets ... .1.tar.bz2 . Download the tarball (2.2k), untar, and check them out. They aren't well documented, but then again, they are very self-explanatory.

Blessed be!
Pappy

[UberLord]

Again no, scripts should be portable across kernels and tools where possible.
I see no benefit in ignoring ifconfig for this

Across kernels I agree, if Gentoo want's pure linux init scripts it can provide them itself. But across tools is exactly the old net.lo approach. So I was wondering myself why the current script "network" doesn't come as three different scripts. As net.loopback, net.ifconfig, net.iproute2 for example. This would also allow neater configuration files I guess.

You can use /etc/ifconfig.eth0 if you like
Yes, that's not the normal Gentoo way, but it also means we're configuration compatible with some of the BSD based RC systems.

[Evileye]

pappy_mcfae, thanks for posting that information. I am about to take the plunge and try out openrc-0.5.1-r1

I have 3 question....

My computer currently has net.eth0 AND net.eth1. net.eth0 connects to the internet while net.eth1 connects to my network. The script you posted above only mentions INT=eth0 . Do I use that script again but just changed it to say INT=eth1 Then give both scripts different names, make executable, place in /etc/init.d and configure to run at boot?

Good question. Between you and I, and everyone else reading, I don't know. My assumption is that you would make an individual script for each interface you wish to bring up, and load them all into /etc/runlevels/default.

UberLord, if you read this, is this assumption correct?

UberLord, do you know if that assumption is correct? (This is from pappy_mcfae's post 3 posts up)

[costel78]

I have in /etc/conf.d/network:

Code: Select all

ip_eth0="192.168.2.2/24; 10.0.1.5/8"
ip_eth1="192.168.5.4/24"
defaultroute="192.168.2.1"

I have few questions:
1. What is the keyword for add a route/interface ? Something like old style found in /etc/conf.d/net routes_ethX=" gateway_ip "
2. Is there (with new style) a way for specify MTU/interface ? (mtu_eth0="1492")
3. I deleted /etc/init.d/net.eth0, /etc/init.d/net.eth1 (were symlinked to net.lo), /etc/conf.d/net, edited /etc/conf.d/network and added network script to boot level (rc-update add network boot). Am I correct ?
1. 2. - for now I'm using /etc/conf.d/local.start to proper set everything, but it not seems to be right way.

Thank you!

Edited: path correction

[pappy_mcfae]

costel78,

before we go further, please post the results of emerge --info.

Blessed be!
Pappy

[UberLord]

pappy_mcfae, thanks for posting that information. I am about to take the plunge and try out openrc-0.5.1-r1

I have 3 question....

My computer currently has net.eth0 AND net.eth1. net.eth0 connects to the internet while net.eth1 connects to my network. The script you posted above only mentions INT=eth0 . Do I use that script again but just changed it to say INT=eth1 Then give both scripts different names, make executable, place in /etc/init.d and configure to run at boot?

Good question. Between you and I, and everyone else reading, I don't know. My assumption is that you would make an individual script for each interface you wish to bring up, and load them all into /etc/runlevels/default.

UberLord, if you read this, is this assumption correct?

Here's my take on it - if you want to roll scripts in whatever way you want and it works for you then got for it!
OpenRC-0.5.x. init.d/network is meant to be single use - ie configures all static interfaces. It's mean to be used alongside dhcpcd-5.x as that handles a lot of dynamic foo the old net.xxx scripts did.

Or putting it another way, pappy_mcfae doesn't really bring anything to the table that /etc/init.d/network doesn't have.
openresolv can be configured directly, no need for a script.

[Evileye]

Or putting it another way, pappy_mcfae doesn't really bring anything to the table that /etc/init.d/network doesn't have.
openresolv can be configured directly, no need for a script.

Am I correct in understanding that I don't need to use the script that was posted by pappy_mcfae for eth0 or eth1 and the other script pappy_mcfae posted for download for br0?

[pappy_mcfae]

Or putting it another way, pappy_mcfae doesn't really bring anything to the table that /etc/init.d/network doesn't have. openresolv can be configured directly, no need for a script.

It was my intent, at the request of d2_racing, to set this up on my machine, and put together a loose how-to for the folks on the Gentoo Quebec forums. There was a lot of buzz, but no information. I did so, and I think I did an admirable job, in comparison to all the other information there is about this on the Gentoo Forums. Oh that's right this thread is the only one that contains a how-to.

I didn't post a script for openresolv. I posted my /etc/resolvconf.conf. That does have to be modified, unless I missed something in the documentation. Did I?

You're the expert. I'm just a guy who can read things, translate them out of digitalese, and make them understandable to others. If doing that isn't bringing something to the table, then what is?

Perhaps when others ask questions, and you sit silently, you might take time to thank me for the effort of at least trying to get YOUR setup out to the masses. I thought that was the idea in the first place.

Thanks.

Blessed be!
Pappy

[d2_racing]

It was my intent, at the request of d2_racing, to set this up on my machine, and put together a loose how-to for the folks on the Gentoo Quebec forums. There was a lot of buzz, but no information. I did so, and I think I did an admirable job, in comparison to all the other information there is about this on the Gentoo Forums. Oh that's right this thread is the only one that contains a how-to.

That's right, I read all the threads from gentoo-dev list and man that openRc thread was a real flamewar. Vapier removed the new stuff so that everyone can have a working network without reading the actual code of openRc or the Funtoo doc.

[UberLord]

I didn't mean to cause offence
If I seem quiet it's because I'm very busy, I don't tend to ignore these forums.

Anyway, you can do this in conf.d/network

Code: Select all

ifconfig_eth0="192.168.0.130 netmask 255.255.255.0"
defaultroute="192.168.0.1"

There is no clean way of interacting with resolvconf here, but we could write this

Code: Select all

ifup_eth0="printf \"nameserver 65.68.49.50\nnameserver 65.68.49.51\n192.168.0.1\ndomain no.org\" | resolvconf -a \$int"

Or this don't bother with the network script and do this in /etc/dhcpcd.conf (requires dhcpcd-5.x)

Code: Select all

interface eth0
static ip_address=192.168.0.130/24
static routers=192.168.0.1
static domain_name=no.org
static domain_servers=65.68.49.50 65.68.49.51 192.168.0.1

All this was documented in /etc/conf.d/network AND the dhcpcd.conf man page.
If you feel this documentation was lacking in any way or form, then please help me update it!

[UberLord]

It was my intent, at the request of d2_racing, to set this up on my machine, and put together a loose how-to for the folks on the Gentoo Quebec forums. There was a lot of buzz, but no information. I did so, and I think I did an admirable job, in comparison to all the other information there is about this on the Gentoo Forums. Oh that's right this thread is the only one that contains a how-to.

That's right, I read all the threads from gentoo-dev list and man that openRc thread was a real flamewar. Vapier removed the new stuff so that everyone can have a working network without reading the actual code of openRc or the Funtoo doc.

That's not entirely accurate.
The flag controlling the network script was removed, but the old and new style networking scripts are installed by default. So you get to choose what you like on disk.

The flamewar was regarding people expecting their existing configs to work with the new style scripts and whether packages like openrc should be in ~arch right away.

[pappy_mcfae]

I was a bit offended, but I have lived through worse.

I am all about Gentoo Linux. I want to help it grow. I've met some really cool people here, and I feel like I make a difference. When you said what you said, I felt a bit belittled.

I'm really liking the new scripting as well. For use with my setup, it's perfect. It's the first thing I've seen with openrc that even made me consider switching more than one machine. That should say something.

I do what I can to further the community. I hope that the how-to might be adapted, or modified into becoming the official how to. I didn't write it to cause issue. I try very hard to be very mellow in the forums. Please understand that.

FYI, my script came from Daniel Robbins' Funtoo Networking Guide. The only change I did was to add the gateway as a third name server.

Blessed be!
Pappy

[UberLord]

FYI, my script came from Daniel Robbins' Funtoo Networking Guide. The only change I did was to add the gateway as a third name server.

I have a nice long chat with Daniel last night. I made him aware of exactly what dhcpcd-5 can do these days and he was very impressed. So impressed said he was going to re-do a lot of the Funtoo Networking around it. Or at least document it more

[pappy_mcfae]

Does that mean there's even a simpler way?

BB!
P

[costel78]

costel78,

before we go further, please post the results of emerge --info.

Blessed be!
Pappy

emerge --info

Code: Select all

Portage 2.2_rc46 (default/linux/amd64/10.0/desktop, gcc-4.4.1, glibc-2.10.1-r0, 2.6.31-reiser4-r3-costel x86_64)
=================================================================
System uname: Linux-2.6.31-reiser4-r3-costel-x86_64-Intel-R-_Core-TM-_i7_CPU_860_@_2.80GHz-with-gentoo-2.0.1
Timestamp of tree: Sat, 17 Oct 2009 08:00:01 +0000
app-shells/bash:     4.0_p33
dev-java/java-config: 2.1.9-r1
dev-lang/python:     2.6.3, 3.1.1-r1
dev-util/cmake:      2.6.4-r3
sys-apps/baselayout: 2.0.1
sys-apps/openrc:     0.5.1-r1
sys-apps/sandbox:    2.1
sys-devel/autoconf:  2.13, 2.63-r1
sys-devel/automake:  1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2, 1.11
sys-devel/binutils:  2.20.51.0.2
sys-devel/gcc-config: 1.4.1
sys-devel/libtool:   2.2.6a
virtual/os-headers:  2.6.30-r1
ACCEPT_KEYWORDS="amd64 x86 ~amd64 ~x86"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe -march=native -mtune=native -floop-interchange -floop-strip-mine -floop-block"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/lib64/fax /usr/share/X11/xkb /usr/share/config /var/bind /var/lib/hsqldb /var/spool/fax/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/eselect/postgresql /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/splash /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2 -pipe -march=native -mtune=native -floop-interchange -floop-strip-mine -floop-block"
DISTDIR="/usr/portage/distfiles"
FEATURES="assume-digests candy distlocks fixpackages lmirror news nodoc parallel-fetch preserve-libs sfperms strict suidctl unmerge-logs unmerge-orphans userfetch userpriv"
GENTOO_MIRRORS="http://localhost http://mirrors.xservers.ro/gentoo/ http://ftp.roedu.net/pub/mirrors/gentoo.org/ http://mirrors.evolva.ro/gentoo/ http://distfiles.gentoo.org/ http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LANG="ro_RO.UTF-8"
LC_ALL="ro_RO.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--warn-once,--hash-style=gnu"
LINGUAS="ro en en_GB"
MAKEOPTS="-j8 --load-average=10"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_EXTRA_OPTS="--progress --delete-before --human-readable"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/portage/local/added /usr/portage/local/mozilla /usr/portage/local/gnome /usr/portage/local/rusxmms"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X a52 aac acl acpi alsa amd64 apache2 aspell audio berkdb big-tables bluetooth branding bzip2 cairo cdr clamav cleartype cli consolekit cracklib crypt cups curl custom-cflags dbus dhcp directfb dovecot-sasl dri dts dvd dvdr eds emboss encode esd evo extras faac faad fam fbcon fbcondecor ffmpeg firefox flac fontconfig fontforge fortran fuse gd gdbm geoip gif git gmp gnome gnutls gpm graphviz gsm gstreamer gtk hal hddtemp iconv icotools icu idn ieee1394 imagemagick iproute2 ipv6 isdnlog ithreads jack java jpeg jpeg2k justify kde kde3 kdehiddenvisibility kerberos lame lcms ldap libcaca libnotify lm_sensors lzma mad matroska mikmod mmx mng modules mp3 mp4 mpeg mplayer mudflap multilib multipath mysql mysqli ncurses nls nptl nptlonly nsplugin nvidia ogg openal openexr opengl openmp oss pam pango pch pcre pdf perl pg-intdatetime plugins png policykit postgres ppds pppd pulseaudio python qt3support qt4 quicktime rcc readline realms reflection replytolist restrict-javascript rle rrdtool samba sasl schroedinger sdl session sip slang smbclient sndfile snmp socks5 sound spamassassin spell spl sql sqlite sse sse2 ssh ssl startup-notification subversion svg swat symlink sysfs syslog tcl tcpd theora threads thunar tiff tk tools truetype unicode urandom usb utf utf8 v4l v4l2 vdpau vhosts video vorbis wav webdav webkit win64 winetools x264 xattr xcb xcomposite xinerama xml xorg xulrunner xv xvid zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="authn_alias cern_meta charset_lite dumpio log_forensic proxy_ftp version actions alias auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias asis substitute" APACHE2_MPMS="worker" ELIBC="glibc" INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="ro en en_GB" LIRC_DEVICES="hauppauge" NETBEANS_MODULES="apisupport harness ide java nb cnd groovy gsf identity j2ee mobility php profiler soa visualweb webcommon websvccommon xml dlight ergonomics ruby enterprise" USERLAND="GNU" VIDEO_CARDS="nv nvidia" 
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS

Any help it's very appreciated. Thank you!

[sera]

Again no, scripts should be portable across kernels and tools where possible.
I see no benefit in ignoring ifconfig for this

Across kernels I agree, if Gentoo want's pure linux init scripts it can provide them itself. But across tools is exactly the old net.lo approach. So I was wondering myself why the current script "network" doesn't come as three different scripts. As net.loopback, net.ifconfig, net.iproute2 for example. This would also allow neater configuration files I guess.

You can use /etc/ifconfig.eth0 if you like
Yes, that's not the normal Gentoo way, but it also means we're configuration compatible with some of the BSD based RC systems.

I wasn't actually talking about splitting the configuration but the script. Using "/etc/ifconfig.eth0" doesn't feel natural enough for my taste anyway. However, I guess the second argument of neater config files dies with that.

Something else I was wondering. You add two routes for the loopback interface where one ends up unreachable. Neither the old script nor the BSD path do this. Seems like I can't find the answer without already knowing it. At lest the search engines let me down on this matter.

[Etal]

I've began playing with the new network setup, and I am a complete newbie when it comes to networking because it "just worked" and I never bothered to figure out how exactly how...

So, if I want to connect to the wired network using DHCP, is this really the only thing that needs to be run?

Code: Select all

dhcpcd eth0

(That's basically the content of /etc/init.d/dhcpcd)

So if I use DHCP, there's no need to run ifconfig, route or resolvconf? Is it really that simple, or am I going to find a nasty surprise later on? Is this all that it boils down to?