From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] openrc 0.9.4 : opaque warnings
Date: Wed, 30 Nov 2011 06:43:40 +0000 [thread overview]
Message-ID: <201111300643.49457.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20111129114157.GA3067@ca.inter.net>
[-- Attachment #1: Type: Text/Plain, Size: 1804 bytes --]
On Tuesday 29 Nov 2011 11:41:57 Philip Webb wrote:
> A further question: since I had previously updated /etc/conf.d/net ,
> I was given a router by my ISP & therefore started to use DHCP.
> The new net.example file suggests I might make further changes in 'net'
> & simplify my configuration files. What I have now in 'net' is :
>
> # For a static configuration use eg :
> # PP 111129 : drop Bash syntax to avoid start-up warning
> #config_eth0=( "192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
> ) config_eth0="192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
> # You need to create the PPP net script yourself:
> # do it via 'cd /etc/init.d ; ln -s net.lo net.ppp0'
> # We have to instruct ppp0 to actually use ppp
> config_ppp0=( "ppp" )
First of all you should not use brackets in the new format.
Second, why do you need PPP, unless this is a router that also authenticates
into your ISP's adsl radius server?
> # Each PPP interface requires an interface to use as a "Link"
> link_ppp0="eth0" # PPPoE requires an ethernet interface
Ditto.
> # Specify what pppd plugins you want to use: available are:
> # pppoe, pppoa, capi, dhcpc, minconn, radius, radattr, radrealms, winbind
> plugins_ppp0=( "pppoe" )
No brackets in the new file format as previous message advised and as I said
above, think again if you need PPP authentication performed by your Gentoo box
(because your new router does this now).
> # PPP requires at least a username.
> # It will use the password specified in /etc/ppp/*-secrets
> username_ppp0='****@***'
> #pppd_ppp0=( "debug" "updetach" "noauth" "defaultroute" "usepeerdns"
> "persist" ) pppd_ppp0=( "updetach" "defaultroute" )
Don't need these at all.
HTH.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-11-30 6:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 10:17 [gentoo-user] openrc 0.9.4 : opaque warnings Philip Webb
2011-11-28 10:29 ` Pandu Poluan
2011-11-28 10:40 ` Pandu Poluan
2011-11-28 10:50 ` Neil Bothwick
2011-11-28 11:50 ` Pandu Poluan
2011-11-28 20:01 ` Mick
2011-11-29 1:35 ` Dale
2011-11-29 1:48 ` Neil Bothwick
2011-11-29 2:54 ` Pandu Poluan
2011-11-29 3:08 ` Dale
2011-11-29 7:16 ` Dale
2011-11-29 11:41 ` Philip Webb
2011-11-30 6:43 ` Mick [this message]
2012-01-08 2:15 ` Philip Webb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201111300643.49457.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox