Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install dhcp client by default #101

Closed
kpcyrd opened this issue Jan 27, 2021 · 4 comments
Closed

Install dhcp client by default #101

kpcyrd opened this issue Jan 27, 2021 · 4 comments
Milestone

Comments

@kpcyrd
Copy link
Member

kpcyrd commented Jan 27, 2021

The archiso configures wired network automatically and I therefore skipped the guided network setup.

After rebooting I noticed I don't have working internet, but $ dh<tab> didn't yield any results. Since I don't have working internet to install a dhcp client and since I don't know the default ip range of virtualbox either I was stuck at this step. :)

I think technically systemd-networkd is installed and could do dhcp, but it's not possible to invoke it in one command without writing an actual configuration first: systemd/systemd#14334

The archiso comes with dhclient and dhcpcd, having at least one installed (even if not configured to start automatically) would be nice.

@Torxed
Copy link
Member

Torxed commented Jan 27, 2021

systemd-networkd is always installed with Arch Linux and the systemd package which is a part of base.
You can create your own /etc/systemd/network/20-ethernet.network with something like:

[Match]
Name=enp*
Name=eth*

[Network]
DHCP=ipv4

And you will have network.
I would argue that this is a larger discussion - should we honor Arch Linux KISS Principle or should we install user friendly helpers.

I would argue that during the additional package stage, you could simply add dhclient dhcpcd and you will have what you need.
But I also think, perhaps we should give a red warning text (orange if we can) to users skipping the network step, simply mentioning that Internet/Network won't automatically be enabled in the system unless these packages are added manually by the installing user.

Would that be an acceptable solution?

@kpcyrd
Copy link
Member Author

kpcyrd commented Jan 27, 2021

I see :) How would you feel about:

No network configuration was selected, after reboot no network is going to be available until configured manually!
Do you want to add dhcpcd to the list of packages that should be installed? [Y/n]

@Torxed
Copy link
Member

Torxed commented Jan 27, 2021

I see :) How would you feel about:

No network configuration was selected, after reboot no network is going to be available until configured manually!
Do you want to add dhcpcd to the list of packages that should be installed? [Y/n]

That could be a way forward, I would say that this is very non-intrusive and simply nudges the user to a informed decision, so I'll consider it for the next release! I'll keep this issue open for it!

@Torxed Torxed added this to the v2.1.2 milestone Jan 27, 2021
@grazzolini
Copy link
Member

Well, dhcpcd is not the only dhcp client we have on the repos, so we could possibly add a list. Also, just installing dhcpcd doesn't mean it will get started after rebooting. As long as the user is informed, I think that's ok.

@Torxed Torxed closed this as completed in 61504fc Mar 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants