| 1 |
On 11/02/15 00:43, Philip Webb wrote: |
| 2 |
> 150210 Mick wrote: |
| 3 |
>> Your desktop hasn't. When the link comes up again nothing kicks in |
| 4 |
>> to either request an IP address from the DHCP server |
| 5 |
>> or to self-configure one temporarily. Either enable IPv4LL |
| 6 |
>> or install ifplug/netplug to achieve the same end result. |
| 7 |
>> On Tuesday 10 Feb 2015 22:36:00 Philip Webb wrote: |
| 8 |
>>> Thanks for the suggestion, but I still don't know how to proceed. |
| 9 |
>> If you are using dhcpcd it is enabled by default, |
| 10 |
>> unless you use -L (-- noipv4ll) in /etc/conf.d/net |
| 11 |
>> Have you disabled this in your desktop, or are you not using dhcpcd? |
| 12 |
> Thanks for your patient help (big smile). |
| 13 |
> AFAICS the config of both machines is the same. |
| 14 |
> What I have realised (red face) is that while there is a difference, |
| 15 |
> it is not in resuming the connection after an un/replug, |
| 16 |
> but in starting Dhcpcd after a reboot : |
| 17 |
> both machines automatically pick up the connection again after an unplug, |
| 18 |
> but the netbook starts Dhcpcd automatically after each boot, |
| 19 |
> whereas the desktop needs to be told to do so via 'dhcpcd'. |
| 20 |
> |
| 21 |
> I've searched again for something different between the machines |
| 22 |
> which would explain why one starts Dhcpcd without being told, |
| 23 |
> but the other doesn't : I can't see any difference. |
| 24 |
> 'grep -r dhcp *' in /etc gives the same 2 lines in both machines ; |
| 25 |
> the netbook's syslog shows it starting Dhcpcd immediately after boot, |
| 26 |
> while the desktop's syslog shows nothing till I enter 'dhcpcd'. |
| 27 |
> |
| 28 |
> IIRC the change happened after the recent update of the netbook, |
| 29 |
> which I try to keep as close to the desktop system as is possible |
| 30 |
> (the hardware is different & the netbook doesn't use KDE apps etc). |
| 31 |
> |
| 32 |
> Can anyone suggest what mb starting Dhcpcd automatically ? |
| 33 |
> The logs just show it happening & Htop doesn't show it depending on anything. |
| 34 |
> |
| 35 |
|
| 36 |
using openrc you can just leave /etc/conf.d/net blank and it should |
| 37 |
start dhcp for you when the interface is started |
| 38 |
you do have a difference in versions between dhcpcd on desktop and netbook |
| 39 |
according to the gentoo wiki [1] you are to use either/or dhcpcd and |
| 40 |
openrc dhcp but this is not clearly spelled out |
| 41 |
i've never had to |
| 42 |
# /etc/init.d/dhcpcd start |
| 43 |
but i have always |
| 44 |
# emerge dhcpcd |
| 45 |
i vaguely recall that openrc started it's own version of dhcp client not |
| 46 |
requiring dhcpcd, but this is not what the handbook [2] says |
| 47 |
|
| 48 |
the easy way forward i guess is to just add dhcpcd to default runlevel |
| 49 |
on the desktop |
| 50 |
# rc-update add dhcpcd default |
| 51 |
|
| 52 |
the confusing bits are that gentoo can use hotplug detection from udev |
| 53 |
to start/stop interfaces for you magically |
| 54 |
also netplug/ifplug will detect carrier changes and start/stop magically |
| 55 |
what would be useful is if you could dump us from desktop and netbook |
| 56 |
# rc-status |
| 57 |
|
| 58 |
[1] http://wiki.gentoo.org/wiki/Network_management_using_DHCPCD |
| 59 |
[2] |
| 60 |
http://wiki.gentoo.org/wiki/Complete_Handbook/Configuring_the_system#Manging_network_with_Gentoo_net..2A_scripts |
Archives