New network naming schema in systemd 197

Dustbin · 2013-01-21 21:22:04

Yeah, but I'm at a loss as to what exactly it is I have to do...

jasonwryan · 2013-01-21 21:33:40

The stickied thread has the details: merging...

fukawi2 · 2013-01-21 22:23:56

The amount of threads/posts about this issue, and the "jarring" change (to quote falconindy), shouldn't someone post a news item about this....?

Dustbin · 2013-01-22 07:22:58

fukawi2 wrote:

The amount of threads/posts about this issue, and the "jarring" change (to quote falconindy), shouldn't someone post a news item about this....?

Agreed...

So, I ran

ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules

The result was

ln: failed to create symbolic link '/etc/udev/rules.d/80-net-name-slot.rules': File exists

and WiFi still doesn't work... I don't even know what my wireless interface new name is...

jasonwryan · 2013-01-22 07:29:27

Dustbin wrote:

I don't even know what my wireless interface new name is...

Read the thread or the wiki: both explicitly reference the commands that you can use to a) identify your device names, and b) enable them on boot.

Dustbin · 2013-01-22 08:31:38

I'm good now...

Turns out brcmsmac wasn't loaded at boot... How that happened all of a sudden is still a mystery, but I've added it to /etc/modules-load.d/ and now everything works as it should...

Edit: changed folder name

Last edited by Dustbin (2013-01-22 11:37:10)

Don Coyote · 2013-01-22 20:00:47

My wired connection is coming up automatically after booting from a live usb, but after installing and rebooting, ping attempts return "connect: network is unreachable". I have downloaded and configured ifplugd as suggested in the Beginners' guide.

It seems i also don't have ifconfig available. I've looked at a bunch of install and network configuration pages but the only reference i'm seeing is an old announcement that it has switched to the iproute2 package. Is it unusual that this isn't included in the base sytem?

ip addr shows only 'lo' for interfaces. Following the Network configuration wiki, lspci shows the kernel driver in use is e1000e. The wiki says to google for the correct module, but didn't lspci just show me it was already loaded? modprobeing e1000e doesn't produce any error message nor an ethernet interface and the wiki explains no further...

roentgen · 2013-01-22 20:52:37

Use ip link to see the interfaces.

chris_l · 2013-01-22 20:59:59

roentgen wrote:

Use ip link to see the interfaces.

yes, do ip link to see the interface, likely is something like enp3s0. Then do

# systemctl enable dhcpcd@enp3s0.service

Last edited by chris_l (2013-01-22 21:00:57)

jasonwryan · 2013-01-22 21:40:31

Merging with the stickied thread...

dougphy · 2013-01-27 06:59:39

Hi all,
I'm new to Arch Linux and I've been attempting to get set up for a couple of days now, I keep having the same issue -- connecting to the internet. I've used the Beginner's Guide wiki completely. Going through the installation I have a connection (using ping -c 3 www.google.com to confirm) but once I'm done, I can't get connected at all.
I've used both methods described in section 2.9.1 of the Beginner's Guide (for dynamic wired connection):
By both methods I mean method 1:

# systemctl enable dhcpcd@<interface>.service

where my interface is eth0.
and method 2:

# pacman -S ifplugd
# cd /etc/network.d
# ln -s examples/ethernet-dhcp .
# systemctl enable net-auto-wired.service

Once the installation is complete and I reboot and log in, internet does not exist according to my machine. I've tried running

# systemctl enable dhcpcd@<interface>.service

again as root but still no luck.
During the whole installation everything is fine. I've googled the hell out of this and I've searched through the forum but haven't been able to find a problem similar enough to mine to help, so any help would be appreciated!
Thanks

the sad clown · 2013-01-27 07:03:04

type

ip link

A new install should have come with the new interface naming paradigm, which means it probably isn't eth0

Stebalien · 2013-01-27 07:05:35

https://bbs.archlinux.org/viewtopic.php?id=156283

jasonwryan · 2013-01-27 07:20:16

Stebalien wrote:

https://bbs.archlinux.org/viewtopic.php?id=156283

Merging with the stickied thread...

earlz · 2013-01-27 22:01:55

dougphy wrote:

Once the installation is complete and I reboot and log in, internet does not exist according to my machine. I've tried running
# systemctl enable dhcpcd@<interface>.service
again as root but still no luck.
During the whole installation everything is fine. I've googled the hell out of this and I've searched through the forum but haven't been able to find a problem similar enough to mine to help, so any help would be appreciated!
Thanks

I'm having this same problem. Not sure how to edit the systemd unit files to make it work. My device is `enp4s0`. So, I do something like this:

systemctl enable dhcpcd@enp4s0.service

But, then it tells me it made a symlink named dhcpcd@eth0.service. Apparently this is a bug? I've tried editing the unit file to directly use my device name instead of %i, but that doesn't seem to work either.

The strange thing is that this works as expected:

systemctl start dhcpcd@enp4s0.service

I don't understand why I can start it after I get logged in, but not get it to automatically start at boot

edit:

Just tried using this command mentioned on page 2 and it works now and correctly runs dhcpcd on boot:

systemctl enable dhcpcd.service

I assume this command will run dhcpcd on every network device available. This is OK for this computer, but I can see quite a few cases where this isn't desirable

Last edited by earlz (2013-01-27 22:05:29)

yu.khanayev · 2013-01-28 11:18:47

Hi!

I have a trouble with network connection in newly installed arch system. I was with nVidia NIC, and with D-Link NIC it's just the same: 'eth0: interface not found or invalid'.

I've tried all commands found at https://wiki.archlinux.org/index.php/Ne … IP_address with absolutely no result. Could you please advise what to do?..

Thank you in advance!

mtangen · 2013-01-28 11:23:24

Hey, Ive seen on some recent archlinux installs that the nic changes name some where from "eth0" to something ..

whats the output of

dmesg | grep eth0

See if its changed its name.

And if it has, check this:

https://wiki.archlinux.org/index.php/Re … interfaces

msthev · 2013-01-28 11:48:14

yu.khanayev wrote:

Could you please advise what to do?..

Search, search, search. Googling "site:archlinux.org no eth0" is enough to find the solution.
https://bbs.archlinux.org/viewtopic.php?id=156283
https://mailman.archlinux.org/pipermail … 24231.html

Last edited by msthev (2013-01-28 11:50:42)

Mr.Elendig · 2013-01-28 12:48:20

`ip l`

Don't assume that your network interface will always be eth0

Last edited by Mr.Elendig (2013-01-28 12:48:44)

yu.khanayev · 2013-01-28 13:08:45

mtangen, msthev - many thanks for the hints. That's right - network interface eth0 was renamed.

Now I'm in search (thanks to msthev for method) for how to deal with renamed interface...

yu.khanayev · 2013-01-28 13:14:21

Mr.Elendig, thanks!

Is there comprehensive method to go just from the point when i know a new interface name (enp0s8)?

yu.khanayev · 2013-01-28 14:29:40

Thank you for your help!
All the thing was the network interface renamed.
ip link showed me its new name. Then i did all as suggested at https://wiki.archlinux.org/index.php/Ne … IP_address ; and now network is up!

Sorry, I could find out how to mark this thread as solved.
Many thanks fo Forum again.

Mr.Elendig · 2013-01-28 15:40:17

Click edit on the first post and change the title. And for the future, please use edit instead of doubleposts.

Last edited by Mr.Elendig (2013-01-28 15:40:28)

TheHebes · 2013-01-28 16:37:50

If it's any help at this point,

# ifrename -i [current name] -n [new name]

will let you rename your interface to whatever you choose.

Feynman · 2013-01-28 16:59:18

Read the beginner's guide twice at minimum.

Arch Linux

#51 2013-01-21 21:22:04

Re: New network naming schema in systemd 197

#52 2013-01-21 21:33:40

Re: New network naming schema in systemd 197

#53 2013-01-21 22:23:56

Re: New network naming schema in systemd 197

#54 2013-01-22 07:22:58

Re: New network naming schema in systemd 197

#55 2013-01-22 07:29:27

Re: New network naming schema in systemd 197

#56 2013-01-22 08:31:38

Re: New network naming schema in systemd 197

#57 2013-01-22 20:00:47

Re: New network naming schema in systemd 197

#58 2013-01-22 20:52:37

Re: New network naming schema in systemd 197

#59 2013-01-22 20:59:59

Re: New network naming schema in systemd 197

#60 2013-01-22 21:40:31

Re: New network naming schema in systemd 197

#61 2013-01-27 06:59:39

Re: New network naming schema in systemd 197

#62 2013-01-27 07:03:04

Re: New network naming schema in systemd 197

#63 2013-01-27 07:05:35

Re: New network naming schema in systemd 197

#64 2013-01-27 07:20:16

Re: New network naming schema in systemd 197

#65 2013-01-27 22:01:55

Re: New network naming schema in systemd 197

#66 2013-01-28 11:18:47

Re: New network naming schema in systemd 197

#67 2013-01-28 11:23:24

Re: New network naming schema in systemd 197

#68 2013-01-28 11:48:14

Re: New network naming schema in systemd 197

#69 2013-01-28 12:48:20

Re: New network naming schema in systemd 197

#70 2013-01-28 13:08:45

Re: New network naming schema in systemd 197

#71 2013-01-28 13:14:21

Re: New network naming schema in systemd 197

#72 2013-01-28 14:29:40

Re: New network naming schema in systemd 197

#73 2013-01-28 15:40:17

Re: New network naming schema in systemd 197

#74 2013-01-28 16:37:50

Re: New network naming schema in systemd 197

#75 2013-01-28 16:59:18

Re: New network naming schema in systemd 197

Board footer