| 1 |
Hi, |
| 2 |
|
| 3 |
I am using the stable udev: |
| 4 |
|
| 5 |
[I] sys-fs/udev |
| 6 |
Available versions: 114 115-r1 119 ~122-r1 124-r1 ~125-r2 ~130-r1 ~133 ~135 ~135-r1 ~135-r2 {selinux} |
| 7 |
Installed versions: 124-r1(12:32:32 08/10/08)(-selinux) |
| 8 |
Homepage: http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html |
| 9 |
Description: Linux dynamic and persistent device naming support (aka userspace devfs) |
| 10 |
|
| 11 |
The only active interface is eth0. |
| 12 |
|
| 13 |
I can activate DHCP manually after login by: |
| 14 |
|
| 15 |
nadav@nadav ~ $ dhcpcd eth0 |
| 16 |
|
| 17 |
I suspect that, for some reasons, dhcp daemon is not called at the initialisation sequence, but I have no idea how to trace it. |
| 18 |
|
| 19 |
Nadav. |
| 20 |
|
| 21 |
-----הודעה מקורית----- |
| 22 |
מאת: news בשם Duncan |
| 23 |
נשלח: ב 22-דצמבר-08 20:21 |
| 24 |
אל: gentoo-amd64@l.g.o |
| 25 |
נושא: [gentoo-amd64] Re: DHCPCD does not start on boot |
| 26 |
|
| 27 |
Nadav Horesh <nadavh@×××××××××××.com> posted |
| 28 |
1229955300.25872.4.camel@×××××××××××××××××.il, excerpted below, on Mon, |
| 29 |
22 Dec 2008 16:15:00 +0200: |
| 30 |
|
| 31 |
>> 2008/12/16 Nadav Horesh <nadavh@×××××××××××.com>: |
| 32 |
>> > We have a network with a windows dhcp server. Few weeks ago dhcpcd |
| 33 |
>> > did not function at the boot, and since them I have to bring it up |
| 34 |
>> > manually: |
| 35 |
|
| 36 |
I just remembered something else... |
| 37 |
|
| 38 |
What version of udev do you have? Newer (at least for ~arch, they may |
| 39 |
not have hit stable yet) udev has changed the persistent network |
| 40 |
handling. The ebuild spit out a warning about it, which with newer |
| 41 |
portage should have been displayed at the end of the emerge (even if |
| 42 |
several packages were merged), but if you missed it... |
| 43 |
|
| 44 |
To list all the network interfaces available, including ones that are |
| 45 |
currently down, use ifconfig -a . If your interface of interest has |
| 46 |
changed name, that would be why it isn't coming up, but you should see it |
| 47 |
in the ifconfig -a output and be able to figure out what name it changed |
| 48 |
to. |
| 49 |
|
| 50 |
If it changed, go back and read the warnings from your last couple udev |
| 51 |
merges. That should give you the info you need to change it back, or you |
| 52 |
can instead update the network config to match. |
| 53 |
|
| 54 |
FWIW, here it changed eth0 to eth1, because it double-detected the |
| 55 |
interface but the first one it detected wasn't the real interface, so the |
| 56 |
real one got bumped to eth1. Deleting the |
| 57 |
/etc/udev/rules.d/70-persistent-net.rules file as suggested didn't help |
| 58 |
as the new dynamic detection ended up doing the same thing, so I ended up |
| 59 |
following the instructions therein, changing the appropriate NAME= key to |
| 60 |
eth0, so I got my normal eth0 interface back. |
| 61 |
|
| 62 |
But as I said, I think this is ~arch only right now. If you're running |
| 63 |
stable udev, I doubt this is the problem. but it never hurts to check. |
| 64 |
If it does turn out to be the problem, once you get the interface |
| 65 |
straightened out again, you should of course be able to return to |
| 66 |
whatever dhcp client you were using before, if desired. |
| 67 |
|
| 68 |
-- |
| 69 |
Duncan - List replies preferred. No HTML msgs. |
| 70 |
"Every nonfree program has a lord, a master -- |
| 71 |
and if you use the program, he is your master." Richard Stallman |
Archives