Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12670 - [initscripts] dhcp should be enabled by default in rc.conf

Attached to Project: Arch Linux
Opened by Charles Willis (cdwillis) - Sunday, 04 January 2009, 20:19 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 30 June 2009, 21:58 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version 1.5.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

The 'dhcp' option is a better default setting to make many if not most network setups work out of the box. The arbitrary static IP configuration is unlikely to work on too many systems, so I feel it should be left in but commented out.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Tuesday, 30 June 2009, 21:58 GMT
Reason for closing:  Implemented
Additional comments about closing:  In git
Comment by Filip Wojciechowski (fwojciec) - Sunday, 04 January 2009, 20:23 GMT
See also this bbs thread for discussion about the issue: http://bbs.archlinux.org/viewtopic.php?id=62304
Comment by Greg (dolby) - Sunday, 04 January 2009, 20:42 GMT
-1. Someone move it to the correct section.
Comment by Aaron Griffin (phrakture) - Monday, 05 January 2009, 22:52 GMT
Makes sense to me, but the generic IP config stuff should be left as an example
Comment by Dieter Plaetinck (Dieter_be) - Friday, 23 January 2009, 17:41 GMT
shouldn't we strive for updating the target rc.conf to match the settings of the livecd?
Eg: if the user chooses dhcp during installation, write dhcp as default entry, otherwise write the ip/gateway/etc settings selected by the user.

the file can still be edited manually but I think it's nice if we can limit the work that needs to be done manually.
Comment by Loui Chang (louipc) - Monday, 26 January 2009, 02:25 GMT
People that have their modem/routers in bridge mode and dial into their
ISP via pppoe will have to disable dhcp. Otherwise, they won't be able
to connect to the network.

This should be mentioned in the installation guide or something.
Comment by Dieter Plaetinck (Dieter_be) - Monday, 26 January 2009, 19:46 GMT
What exactly do these people need to do? something like this http://wiki.archlinux.org/index.php/PPPoE_Setup_with_pppd ?
Comment by Loui Chang (louipc) - Monday, 26 January 2009, 19:56 GMT
Hmm I'm not sure exactly how it would affect pppoe via pppd but I
know that dhcp does cause problems when using pppoe via rp-pppoe
from first hand experience.

Now say that five times fast.

So, enabling dhcp by default is a good idea, but there should
be some kind of comment or notice for people using pppoe.
Comment by Dieter Plaetinck (Dieter_be) - Saturday, 14 February 2009, 15:18 GMT
So, if the user selected a custom ip,broadcast etc during installation, you still want to write dhcp to rc.conf? I don't understand the point of that.
Comment by Loui Chang (louipc) - Saturday, 14 February 2009, 16:32 GMT
No, it wouldn't make sense in that case. I assumed these defaults are applied
before the user makes any decisions.
Comment by Dieter Plaetinck (Dieter_be) - Saturday, 14 February 2009, 16:43 GMT
Well, what the installer does right now ( see http://projects.archlinux.org/?p=installer.git;a=blob_plain;f=setup;hb=HEAD function auto_network):
if the network was configured in the installer:
- if dhcp -> configure dhcp in rc.conf (it just replaces eth0 by $INTERFACE)
- if static -> configure stuff statically.

If I understand correctly, cdwillis proposed to always use a dhcp config. (correct me if I'm wrong)

I would just keep the behaviour like it is.
Comment by Aaron Griffin (phrakture) - Saturday, 14 February 2009, 23:53 GMT
I don't think this is about the installer at all, but the default state of rc.conf
Comment by Charles Willis (cdwillis) - Sunday, 15 February 2009, 09:27 GMT
This is about the default state of rc.conf. The static IP configuration is enabled by default in rc.conf if you do an install from the core iso. The dhcp configuration is also in rc.conf, but it is commented out. My proposal was to enable the dhcp configuration in rc.conf by default with the static IP configuration commented out. I think it makes sense because more users would be enabling dhcp and commenting out the static IP configuration during installation.
Comment by Dieter Plaetinck (Dieter_be) - Sunday, 15 February 2009, 09:54 GMT
oh.. in that case... yeah, put dhcp and leave a commented out static configuration.
Comment by Dieter Plaetinck (Dieter_be) - Friday, 05 June 2009, 20:57 GMT
Gerardo,
this seems to be about the default state of rc.conf, which has nothing to do with release engineering, nor AIF. but rather the init scripts package. (correct me if i'm wrong)
so imho this should be assigned to the initscripts maintainer (Thomas Baechler), and the project should be changed to Arch Linux, imho.
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 15 June 2009, 00:00 GMT
@Dieter: Yes or as a choice from installer. Anyway agree, moving the task ;)
Comment by Thomas Bächler (brain0) - Monday, 15 June 2009, 07:10 GMT
It is resonable to enable dhcp by default in rc.conf.
Comment by Aaron Griffin (phrakture) - Tuesday, 30 June 2009, 21:58 GMT
Committed and pushed to git
http://projects.archlinux.org/?p=initscripts.git;a=commitdiff;h=ad1e81556aa351fea39ed6eaf6efbed0ba7ce894

Loading...