[arch-general] Request help with wired network config after initial install and reboot
I did a base install last night on a machine with only a wired connection - using the arch iso from 2013-01-04 - the install seemed to go fine and I had a network connection using dhcp during the install and once chrooted into /mnt everything seemed fine. At that stage I set up a wired "static ip" connection (following the beginners guide) using ifplugd - but the service does not start from within the chroot during the install - but when I rebooted at the completion of the install I have no network connection and I cannot see any network device (was eth0 during the install) - is it possible this may be due to the systemd-197 package that was installed with the interface naming changed? It seems that the ifconfig command is not available once rebooted into the install and I don't know how to proceed. Can anyone give my any advice on how to get the network up on the newly installed system? I could not find anyone who had the same problem in the forums or searching on the net. Thanks in advance. -- mike c
On Fri, Jan 18, 2013 at 09:31:14AM +0000, Mike Cloaked wrote:
I did a base install last night on a machine with only a wired connection - using the arch iso from 2013-01-04 - the install seemed to go fine and I had a network connection using dhcp during the install and once chrooted into /mnt everything seemed fine.
At that stage I set up a wired "static ip" connection (following the beginners guide) using ifplugd - but the service does not start from within the chroot during the install - but when I rebooted at the completion of the install I have no network connection and I cannot see any network device (was eth0 during the install) - is it possible this may be due to the systemd-197 package that was installed with the interface naming changed?
Interfaces are, on new installs, not `wlan0` or `eth0`. They are now dictated by udev [1][2]. My wired and wireless devices are now enp0s25 and wlp3s0.
It seems that the ifconfig command is not available once rebooted into the install and I don't know how to proceed.
Run `ip l`. [1] https://mailman.archlinux.org/pipermail/arch-dev-public/2013-January/024231.... [2] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... -- William Giokas | KaiSforza GnuPG Key: 0xE99A7F0F Fingerprint: F078 CFF2 45E8 1E72 6D5A 8653 CDF5 E7A5 E99A 7F0F
On Fri, Jan 18, 2013 at 9:38 AM, William Giokas <1007380@gmail.com> wrote:
On Fri, Jan 18, 2013 at 09:31:14AM +0000, Mike Cloaked wrote:
I did a base install last night on a machine with only a wired connection - using the arch iso from 2013-01-04 - the install seemed to go fine and I had a network connection using dhcp during the install and once chrooted into /mnt everything seemed fine.
At that stage I set up a wired "static ip" connection (following the beginners guide) using ifplugd - but the service does not start from within the chroot during the install - but when I rebooted at the completion of the install I have no network connection and I cannot see any network device (was eth0 during the install) - is it possible this may be due to the systemd-197 package that was installed with the interface naming changed?
Interfaces are, on new installs, not `wlan0` or `eth0`. They are now dictated by udev [1][2]. My wired and wireless devices are now enp0s25 and wlp3s0.
It seems that the ifconfig command is not available once rebooted into
the
install and I don't know how to proceed.
Run `ip l`.
[1] https://mailman.archlinux.org/pipermail/arch-dev-public/2013-January/024231.... [2] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface...
Thanks William - I have just managed to get the network up using the sequence: ip link - which gave the new interface name. Then using the new name: ip link set enp0s25 up ip addr add 10.0.0.10/24 dev enp0s25 ip route add default via 10.0.0.135
Then edited /etc/resolv.conf to get a working network. However once I have completed the rest of the install and configuration I want to have the network come alive with a static ip address at boot. What is the current recommended best method? Is it netcfg, ifplugd or something else? This will be a desktop that runs on its own in a relative's home where there is only a single wired router. Thanks for any advice. -- mike c
On Fri, Jan 18, 2013 at 9:38 AM, William Giokas <1007380@gmail.com> wrote:
On Fri, Jan 18, 2013 at 09:31:14AM +0000, Mike Cloaked wrote:
I did a base install last night on a machine with only a wired connection - using the arch iso from 2013-01-04 - the install seemed to go fine and I had a network connection using dhcp during the install and once chrooted into /mnt everything seemed fine.
At that stage I set up a wired "static ip" connection (following the beginners guide) using ifplugd - but the service does not start from within the chroot during the install - but when I rebooted at the completion of the install I have no network connection and I cannot see any network device (was eth0 during the install) - is it possible this may be due to the systemd-197 package that was installed with the interface naming changed?
Interfaces are, on new installs, not `wlan0` or `eth0`. They are now dictated by udev [1][2]. My wired and wireless devices are now enp0s25 and wlp3s0.
It seems that the ifconfig command is not available once rebooted into
the
install and I don't know how to proceed.
Run `ip l`.
[1] https://mailman.archlinux.org/pipermail/arch-dev-public/2013-January/024231.... [2] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface...
I have had a chance to sort this all out now - and it turns out that once the initial install is complete it was necessary for me to do the following: 1) Install both ifplugd and netcfg 2) From within /etc/network.d take the example file ethernet-static and put it in /etc/network.d/ and configure the address parameters for my system 3) Edit /etc/ifplugd/ifplugd.conf as it inherited the interface name "eth0" and needs to be changed to the correct "enp0s25" name 4) Edit /etc/conf.d/netcfg as it inherited the interface name "eth0" and needs to be changed to the correct "enp0s25" name Now when doing systemctl restart net-auto-wired it does set up the wired network correctly - and of course systemctl restart net-auto-wired is required for the service to start after the next and subsequent bootups. I presume that the February archiso file will be built with systemd-197 so this problem would not arise once that is released - and the problem I had today is presumably a temporary one due to the interface naming scheme being changed after the January iso was built with the old names but installs the system with new names yet copying configs into the standard files with the previous names. Anyway this is resolved now and I hope this post may help anyone else who finds they end up with the same issue. Of course I have not done an install with a laptop with wireless but I guess there may be corresponding issues with that - and with dhcp assigned networking? Maybe others will report if that is a non-issue for installs done with the January archiso but executed after the systemd-197 release? -- mike c
On Fri, Jan 18, 2013 at 4:14 PM, Mike Cloaked <mike.cloaked@gmail.com>wrote:
On Fri, Jan 18, 2013 at 9:38 AM, William Giokas <1007380@gmail.com> wrote:
[...] and of course systemctl restart net-auto-wired is required for the service to start after the next and subsequent bootups.
I assume you mean `systemctl enable net-auto-wired`, don't you? -- Rodrigo
On Fri, Jan 18, 2013 at 7:25 PM, Rodrigo Rivas <rodrigorivascosta@gmail.com>wrote:
On Fri, Jan 18, 2013 at 4:14 PM, Mike Cloaked <mike.cloaked@gmail.com
wrote:
On Fri, Jan 18, 2013 at 9:38 AM, William Giokas <1007380@gmail.com> wrote:
[...] and of course systemctl restart net-auto-wired is required for the service to start after the next and subsequent bootups.
I assume you mean `systemctl enable net-auto-wired`, don't you?
-- Rodrigo
Actually that enables it for next boot - but if it was supposed to start and the configs were wrong and the network is not working - then after fixing the configs I restarted it and it is then running - next boot it should start on its own. -- mike c
It seems that the ifconfig command is not available once rebooted into the install and I don't know how to proceed.
Can anyone give my any advice on how to get the network up on the newly installed system?
Because it hard to get rid of a good old habit: lano1106@hpmini ~ $ pkgfile ifconfig core/net-tools ________________________________ CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
On Mon, Jan 21, 2013 at 4:16 PM, LANGLOIS Olivier PIS -EXT < olivier.pis.langlois@transport.alstom.com> wrote:
It seems that the ifconfig command is not available once rebooted into
the
install and I don't know how to proceed.
Can anyone give my any advice on how to get the network up on the newly installed system?
Because it hard to get rid of a good old habit:
lano1106@hpmini ~ $ pkgfile ifconfig core/net-tools
Indeed - thanks. -- mike c
participants (4)
-
LANGLOIS Olivier PIS -EXT
-
Mike Cloaked
-
Rodrigo Rivas
-
William Giokas