Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
In the absence of any further responses -- thanx again for those so far -- I tried emerging Openrc with 'newnet' 'netifrc' (separately), but (after reboot) neither made any difference : still no auto I/net. Finally, I tried brute force -- 'rc-update add dhcpcd' -- , which worked. So there's some mysterious difference between the behaviour of Openrc on the 2 machines : on the Netbook, it starts DHCPCD without any flags, whereas on the Desktop, neither recommended flag causes it to start. AFAICS both machines have the same config settings in relevant files, both have upto-date stable versions of pkgs, both have similar kernels. Any further suggestions whence the difference might arise are very welcome. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
150211 thegeezer wrote: i vaguely recall that openrc started it's own version of dhcp client http://wiki.gentoo.org/wiki/Network_management_using_DHCPCD/OpenRC_message https://groups.google.com/forum/#!topic/linux.gentoo.dev/D_sFyfaQl2Y Yes, that says all you need is '+newnet' for Openrc it will use its own DHCP to connect to the I/net. However, my netbook has '-newnet -netifrc' still connects automatically ! Below are the 2 versions, which show no significant difference I can see. So I still want to know why Netbook connects automatically would welcome any further advice, so I can bring the Desktop into line. As to the earlier queston re re-plugging the I/net connection, there seems to have been an unannounced change in default c 2013 . IIRC in 2012, when I built the Desktop machine, for both machines I had to shut down Dhcpcd via 'dhcpcd -k' restart via 'dhcpcd' before/after un/plugging the physical connection. In /etc on the Desktop I have a file 'dhcpcd-dft.conf', which is dated 120907, ie when I started installing Gentoo in it, which I renamed after creating the revised version I wanted : that file ends with 2 lines : # dhcpcd ebuild requested no zeroconf noipv4ll The comment is typically obscure to any normal user (wry smile). Both machines' dhcpcd.conf files lack those lines today. Desktop : dft runlevel root:510 etc cd runlevels/default/ root:511 default ls -l total 0 lrwxrwxrwx 1 root root 17 Dec 15 2013 cupsd - /etc/init.d/cupsd lrwxrwxrwx 1 root root 16 Sep 11 2012 dbus - /etc/init.d/dbus lrwxrwxrwx 1 root root 17 Jun 21 2012 local - /etc/init.d/local lrwxrwxrwx 1 root root 20 Jun 21 2012 netmount - /etc/init.d/netmount lrwxrwxrwx 1 root root 16 Sep 9 2012 ntpd - /etc/init.d/ntpd lrwxrwxrwx 1 root root 20 Sep 9 2012 sysklogd - /etc/init.d/sysklogd lrwxrwxrwx 1 root root 22 Sep 9 2012 vixie-cron - /etc/init.d/vixie-cron root:512 default Desktop : rc.log rc default logging started at Wed Feb 11 10:42:56 2015 * Starting D-BUS system messagebus ... [ ok ] * sysklogd - start: syslogd ... [ ok ] * sysklogd - start: klogd ... [ ok ] * Starting cupsd ... [ ok ] * Mounting network filesystems ... [ ok ] * Starting ntpd ... [ ok ] * Starting vixie-cron ... [ ok ] * Starting local ... [ ok ] rc default logging stopped at Wed Feb 11 10:42:57 2015 Desktop : /etc/rc.conf (comments deleted) #rc_parallel=NO rc_interactive=YES rc_shell=/sbin/sulogin #rc_depend_strict=YES rc_hotplug=* rc_logger=YES #rc_log_path=/var/log/rc.log #rc_verbose=no #rc_env_allow=VAR1 VAR2 #rc_start_wait=100 #rc_nostop= #rc_crashed_stop=NO rc_crashed_start=YES #rc_nocolor=NO unicode=YES #rc_fuser_timeout=60 #extra_net_fs_list= #SSD_NICELEVEL=-19 #rc_ulimit=-u 30 #rc_config=/etc/foo #rc_need=openvpn #rc_use=net.eth0 #rc_after=clock #rc_before=local #rc_provide=!net #rc_foo_config=/etc/foo #rc_foo_need=openvpn #rc_foo_after=clock #rc_foo_bar_config=/etc/foo-bar #rc_foo_bar_need=openvpn #rc_foo_bar_after=clock #rc_net_tap0_provide=!net #rc_sys= rc_tty_number=12 #rc_controller_cgroups=YES # rc_cgroup_cpu= # cpu.shares 512 # #rc_cgroup_blkio= #rc_cgroup_cpu= #rc_cgroup_cpuacct= #rc_cgroup_cpuset= #rc_cgroup_devices= #rc_cgroup_memory= #rc_cgroup_net_prio= # rc_cgroup_cleanup=NO Desktop : openrc root:516 etc eix ^openrc$ [I] sys-apps/openrc Available versions : 0.12.4{tbz2} 0.13.8{tbz2} 0.13.9{tbz2} ** {audit debug ncurses +netifrc newnet pam prefix selinux static-libs tools unicode ELIBC=glibc KERNEL=FreeBSD linux} Installed versions : 0.13.9{tbz2} ( [2015-02-07 11:18:46] ) (ncurses unicode -debug -netifrc -newnet -pam -prefix -selinux -static-libs -tools ELIBC=glibc KERNEL=linux -FreeBSD) Netbook : syslog : latest lines # netbook started w/o conn'n 16:40:22 localhost kernel: REISERFS (device sda6): Using r5 hash to sort names 16:40:22 localhost dhcpcd[799]: version 6.4.7 starting 16:40:22 localhost dhcpcd[799]: dev: loaded udev 16:40:22 localhost dhcpcd[799]: no interfaces have a carrier 16:40:22 localhost dhcpcd[799]: forked to background, child pid 822 16:40:22 localhost kernel: atl1c :01:00.0: Unable to allocate MSI interrupt Error: -38 16:40:22 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready 16:40:22 localhost dhcpcd[822]: enp1s0: waiting for carrier 16:40:22 localhost dhcpcd[822]: enp1s0: carrier acquired 16:40:22 localhost dhcpcd[822]: DUID 00:01:00:01:03:c3:b8:97:00:26:18:79:64:16 16:40:22 localhost dhcpcd[822]: enp1s0: IAID 18:79:64:16 16:40:22 localhost dhcpcd[822]: enp1s0: carrier lost 16:40:23 localhost dhcpcd[822]: enp1s0: waiting for carrier # plugged in 16:44:06 localhost dhcpcd[822]: enp1s0: carrier acquired 16:44:06 localhost kernel: atl1c :01:00.0: atl1c: enp1s0 NIC Link is Up100 Mbps Full Duplex 16:44:06 localhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready 16:44:06 localhost dhcpcd[822]: enp1s0: IAID 18:79:64:16 16:44:07 localhost dhcpcd[822]: enp1s0: rebinding lease of 192.168.1.3
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
On Tue, 10 Feb 2015 19:43:22 -0500, Philip Webb wrote: Can anyone suggest what mb starting Dhcpcd automatically ? net.eth0 starts dhcp by default, unless is is configured to get its address some other way. -- Neil Bothwick Fill what's empty, empty what's full, scratch where it itches. pgpqanSxMJeEt.pgp Description: OpenPGP digital signature
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
On 11/02/15 00:43, Philip Webb wrote: 150210 Mick wrote: Your desktop hasn't. When the link comes up again nothing kicks in to either request an IP address from the DHCP server or to self-configure one temporarily. Either enable IPv4LL or install ifplug/netplug to achieve the same end result. On Tuesday 10 Feb 2015 22:36:00 Philip Webb wrote: Thanks for the suggestion, but I still don't know how to proceed. If you are using dhcpcd it is enabled by default, unless you use -L (-- noipv4ll) in /etc/conf.d/net Have you disabled this in your desktop, or are you not using dhcpcd? Thanks for your patient help (big smile). AFAICS the config of both machines is the same. What I have realised (red face) is that while there is a difference, it is not in resuming the connection after an un/replug, but in starting Dhcpcd after a reboot : both machines automatically pick up the connection again after an unplug, but the netbook starts Dhcpcd automatically after each boot, whereas the desktop needs to be told to do so via 'dhcpcd'. I've searched again for something different between the machines which would explain why one starts Dhcpcd without being told, but the other doesn't : I can't see any difference. 'grep -r dhcp *' in /etc gives the same 2 lines in both machines ; the netbook's syslog shows it starting Dhcpcd immediately after boot, while the desktop's syslog shows nothing till I enter 'dhcpcd'. IIRC the change happened after the recent update of the netbook, which I try to keep as close to the desktop system as is possible (the hardware is different the netbook doesn't use KDE apps etc). Can anyone suggest what mb starting Dhcpcd automatically ? The logs just show it happening Htop doesn't show it depending on anything. using openrc you can just leave /etc/conf.d/net blank and it should start dhcp for you when the interface is started you do have a difference in versions between dhcpcd on desktop and netbook according to the gentoo wiki [1] you are to use either/or dhcpcd and openrc dhcp but this is not clearly spelled out i've never had to # /etc/init.d/dhcpcd start but i have always # emerge dhcpcd i vaguely recall that openrc started it's own version of dhcp client not requiring dhcpcd, but this is not what the handbook [2] says the easy way forward i guess is to just add dhcpcd to default runlevel on the desktop # rc-update add dhcpcd default the confusing bits are that gentoo can use hotplug detection from udev to start/stop interfaces for you magically also netplug/ifplug will detect carrier changes and start/stop magically what would be useful is if you could dump us from desktop and netbook # rc-status [1] http://wiki.gentoo.org/wiki/Network_management_using_DHCPCD [2] http://wiki.gentoo.org/wiki/Complete_Handbook/Configuring_the_system#Manging_network_with_Gentoo_net..2A_scripts
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
On Wed, 11 Feb 2015 10:38:27 +, thegeezer wrote: the confusing bits are that gentoo can use hotplug detection from udev to start/stop interfaces for you magically also netplug/ifplug will detect carrier changes and start/stop magically ifplugd/netplug should not be configured to start interfaces. They just need to be installed so openrc can use them. -- Neil Bothwick ... I dropped my toothpaste, Tom said, Crestfallen. pgppItPUn8PbQ.pgp Description: OpenPGP digital signature
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
On 11/02/15 11:09, Neil Bothwick wrote: On Wed, 11 Feb 2015 10:38:27 +, thegeezer wrote: the confusing bits are that gentoo can use hotplug detection from udev to start/stop interfaces for you magically also netplug/ifplug will detect carrier changes and start/stop magically ifplugd/netplug should not be configured to start interfaces. They just need to be installed so openrc can use them. ah yeah quite right i should have been clearer re: netifrc start and interface start --- they add inactive to the status when there is no connection so the states go /etc/init.d/net.blah start stopped inactive started and only trigger the netifrc start process when going from inactive started but they do stop from a netifrc perspective the interface when going started inactive i.e. routes and IP addresses are added/removed, but the interface is still up (but unplugged) better to use hotplug imo but different use cases need different things
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
On 11/02/15 10:38, thegeezer wrote: i vaguely recall that openrc started it's own version of dhcp client yes it did [3] http://wiki.gentoo.org/wiki/Network_management_using_DHCPCD/OpenRC_message [4] https://groups.google.com/forum/#!topic/linux.gentoo.dev/D_sFyfaQl2Y not requiring dhcpcd, but this is not what the handbook [2] says the easy way forward i guess is to just add dhcpcd to default runlevel on the desktop # rc-update add dhcpcd default the confusing bits are that gentoo can use hotplug detection from udev to start/stop interfaces for you magically also netplug/ifplug will detect carrier changes and start/stop magically what would be useful is if you could dump us from desktop and netbook # rc-status [1] http://wiki.gentoo.org/wiki/Network_management_using_DHCPCD [2] http://wiki.gentoo.org/wiki/Complete_Handbook/Configuring_the_system#Manging_network_with_Gentoo_net..2A_scripts
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
On Tuesday 10 Feb 2015 03:36:19 Philip Webb wrote: Dec 31 19:00:29 localhost dhcpcd[1346]: enp1s0: using IPv4LL address 169.254.91.169 Your netbook has it enabled. It self-configures an IP address and then every so many seconds broadcasts on the wire to find if there is a DHCP server listening. When it finds one it requests an IP address from it. Your desktop hasn't. When the link comes up again nothing kicks in to either request an IP address from the DHCP server, or to self-configure one temporarily. Either enable IPv4LL, or install ifplug/netplug to achieve the same end result. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
On Wednesday 11 Feb 2015 00:43:22 Philip Webb wrote: 150210 Mick wrote: Your desktop hasn't. When the link comes up again nothing kicks in to either request an IP address from the DHCP server or to self-configure one temporarily. Either enable IPv4LL or install ifplug/netplug to achieve the same end result. On Tuesday 10 Feb 2015 22:36:00 Philip Webb wrote: Thanks for the suggestion, but I still don't know how to proceed. If you are using dhcpcd it is enabled by default, unless you use -L (-- noipv4ll) in /etc/conf.d/net Have you disabled this in your desktop, or are you not using dhcpcd? Thanks for your patient help (big smile). AFAICS the config of both machines is the same. What I have realised (red face) is that while there is a difference, it is not in resuming the connection after an un/replug, but in starting Dhcpcd after a reboot : both machines automatically pick up the connection again after an unplug, but the netbook starts Dhcpcd automatically after each boot, whereas the desktop needs to be told to do so via 'dhcpcd'. I've searched again for something different between the machines which would explain why one starts Dhcpcd without being told, but the other doesn't : I can't see any difference. 'grep -r dhcp *' in /etc gives the same 2 lines in both machines ; the netbook's syslog shows it starting Dhcpcd immediately after boot, while the desktop's syslog shows nothing till I enter 'dhcpcd'. IIRC the change happened after the recent update of the netbook, which I try to keep as close to the desktop system as is possible (the hardware is different the netbook doesn't use KDE apps etc). Can anyone suggest what mb starting Dhcpcd automatically ? The logs just show it happening Htop doesn't show it depending on anything. Just checking: are your hotplug settings the same between the two machines in /etc/rc.conf? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
150210 Mick wrote: On Tuesday 10 Feb 2015 03:36:19 Philip Webb wrote: Dec 31 19:00:29 localhost dhcpcd[1346]: enp1s0: using IPv4LL address 169.254.91.169 Your netbook has it enabled. It self-configures an IP address and then every so many seconds broadcasts on the wire to find if there is a DHCP server listening. When it finds one it requests an IP address from it. Your desktop hasn't. When the link comes up again nothing kicks in to either request an IP address from the DHCP server or to self-configure one temporarily. Either enable IPv4LL or install ifplug/netplug to achieve the same end result. Thanks for the suggestion, but I still don't know how to proceed. I assume that the absence of the line above + this line Dec 31 19:00:29 localhost dhcpcd[1346]: enp1s0: adding route to 169.254.0.0/16 results in the desktop machine killing the Dhcpcd process : # PP : 'ioff', remove conn'n dhcpcd[11404]: sending signal ARLM to pid 997 dhcpcd[11404]: waiting for pid 997 to exit dhcpcd[997]: received signal ALRM from PID 11404, releasing dhcpcd[997]: enp5s0: removing interface dhcpcd[997]: enp5s0: releasing lease of 192.168.1.2 dhcpcd[997]: enp5s0: deleting route to 192.168.1.0/24 dhcpcd[997]: enp5s0: deleting default route via 192.168.1.1 dhcpcd[997]: exited which then has to be restarted via 'dhcpcd' after replugging the conn'n. However, even after searching thro' /etc again, Googling etc, AFAICS there's no difference in config files between the 2 machines. So how do I enable IPv4LL' (smile) ? -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
On Tuesday 10 Feb 2015 22:36:00 Philip Webb wrote: 150210 Mick wrote: On Tuesday 10 Feb 2015 03:36:19 Philip Webb wrote: Dec 31 19:00:29 localhost dhcpcd[1346]: enp1s0: using IPv4LL address 169.254.91.169 Your netbook has it enabled. It self-configures an IP address and then every so many seconds broadcasts on the wire to find if there is a DHCP server listening. When it finds one it requests an IP address from it. Your desktop hasn't. When the link comes up again nothing kicks in to either request an IP address from the DHCP server or to self-configure one temporarily. Either enable IPv4LL or install ifplug/netplug to achieve the same end result. Thanks for the suggestion, but I still don't know how to proceed. I assume that the absence of the line above + this line Dec 31 19:00:29 localhost dhcpcd[1346]: enp1s0: adding route to 169.254.0.0/16 results in the desktop machine killing the Dhcpcd process : # PP : 'ioff', remove conn'n dhcpcd[11404]: sending signal ARLM to pid 997 dhcpcd[11404]: waiting for pid 997 to exit dhcpcd[997]: received signal ALRM from PID 11404, releasing dhcpcd[997]: enp5s0: removing interface dhcpcd[997]: enp5s0: releasing lease of 192.168.1.2 dhcpcd[997]: enp5s0: deleting route to 192.168.1.0/24 dhcpcd[997]: enp5s0: deleting default route via 192.168.1.1 dhcpcd[997]: exited which then has to be restarted via 'dhcpcd' after replugging the conn'n. However, even after searching thro' /etc again, Googling etc, AFAICS there's no difference in config files between the 2 machines. So how do I enable IPv4LL' (smile) ? If you are using dhcpcd it is enabled by default, unless you use -L (-- noipv4ll) in /etc/conf.d/net Have you disabled this in your desktop, or are you not using dhcpcd? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
150210 Mick wrote: Your desktop hasn't. When the link comes up again nothing kicks in to either request an IP address from the DHCP server or to self-configure one temporarily. Either enable IPv4LL or install ifplug/netplug to achieve the same end result. On Tuesday 10 Feb 2015 22:36:00 Philip Webb wrote: Thanks for the suggestion, but I still don't know how to proceed. If you are using dhcpcd it is enabled by default, unless you use -L (-- noipv4ll) in /etc/conf.d/net Have you disabled this in your desktop, or are you not using dhcpcd? Thanks for your patient help (big smile). AFAICS the config of both machines is the same. What I have realised (red face) is that while there is a difference, it is not in resuming the connection after an un/replug, but in starting Dhcpcd after a reboot : both machines automatically pick up the connection again after an unplug, but the netbook starts Dhcpcd automatically after each boot, whereas the desktop needs to be told to do so via 'dhcpcd'. I've searched again for something different between the machines which would explain why one starts Dhcpcd without being told, but the other doesn't : I can't see any difference. 'grep -r dhcp *' in /etc gives the same 2 lines in both machines ; the netbook's syslog shows it starting Dhcpcd immediately after boot, while the desktop's syslog shows nothing till I enter 'dhcpcd'. IIRC the change happened after the recent update of the netbook, which I try to keep as close to the desktop system as is possible (the hardware is different the netbook doesn't use KDE apps etc). Can anyone suggest what mb starting Dhcpcd automatically ? The logs just show it happening Htop doesn't show it depending on anything. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
150209 Neil Bothwick wrote: On Sun, 8 Feb 2015 19:54:07 -0500, Philip Webb wrote: I discovered that my ASUS EEE connects automatically to the Internet when the physical connection is plugged in, while my desktop machine (AMD + Gigabyte mobo) has to be told by 'dhcpcd'. I've checked /etc/runlevels/default/etc/udev in both machines, but can't see anything different between the two. Check /etc/rc.conf, especially the hotplug section. There's no difference. Also check whether you have ifplugd or netplug installed on your laptop but not on the desktop. Neither has either installed. Looking at a 'gvimdiff' of the 2 extracts from 'syslog', I notice 3 differences : (1) when the connection is broken, the desktop machine receives an ALRM signal, which causes a process to exit (PID 997), whereas the netbook shows only carrier lost, deleting route ; (2) when the connection is restored, the netbook says carrier acquired then there's a kernel msg re a NIC link, whereas the desktop is blank ; (3) the kernel msgs refer to different chips 'r8169' 'atl1c'. Does any of this ring a bell for anyone ? Thanks so far. Desktop msgs : Feb 8 09:26:09 localhost dhcpcd[980]: version 6.6.7 starting Feb 8 09:26:09 localhost dhcpcd[980]: dev: loaded udev Feb 8 09:26:09 localhost dhcpcd[980]: no interfaces have a carrier Feb 8 09:26:09 localhost dhcpcd[980]: forked to background, child pid 997 Feb 8 09:26:09 localhost dhcpcd[997]: enp5s0: waiting for carrier Feb 8 09:26:09 localhost kernel: r8169 :05:00.0 enp5s0: link down Feb 8 09:26:09 localhost kernel: r8169 :05:00.0 enp5s0: link down Feb 8 09:26:09 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready Feb 8 09:26:11 localhost dhcpcd[997]: enp5s0: carrier acquired Feb 8 09:26:11 localhost kernel: r8169 :05:00.0 enp5s0: link up Feb 8 09:26:11 localhost kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready Feb 8 09:26:11 localhost dhcpcd[997]: DUID 00:01:00:01:1a:1b:b4:7e:50:e5:49:c6:10:3a Feb 8 09:26:11 localhost dhcpcd[997]: enp5s0: IAID 49:c6:10:3a Feb 8 09:26:11 localhost dhcpcd[997]: enp5s0: rebinding lease of 192.168.1.2 Feb 8 09:26:14 localhost dhcpcd[997]: enp5s0: NAK: from 192.168.1.1 Feb 8 09:26:14 localhost dhcpcd[997]: enp5s0: soliciting a DHCP lease Feb 8 09:26:16 localhost dhcpcd[997]: enp5s0: offered 192.168.1.2 from 192.168.1.1 Feb 8 09:26:21 localhost dhcpcd[997]: enp5s0: leased 192.168.1.2 for 86400 seconds Feb 8 09:26:21 localhost dhcpcd[997]: enp5s0: adding route to 192.168.1.0/24 Feb 8 09:26:21 localhost dhcpcd[997]: enp5s0: adding default route via 192.168.1.1 Feb 8 09:26:22 localhost ntpd[837]: Listen normally on 2 enp5s0 192.168.1.2:123 ... # PP : 'ioff', remove conn'n Feb 8 18:54:26 localhost dhcpcd[11404]: sending signal ARLM to pid 997 Feb 8 18:54:26 localhost dhcpcd[11404]: waiting for pid 997 to exit Feb 8 18:54:26 localhost dhcpcd[997]: received signal ALRM from PID 11404, releasing Feb 8 18:54:26 localhost dhcpcd[997]: enp5s0: removing interface Feb 8 18:54:26 localhost dhcpcd[997]: enp5s0: releasing lease of 192.168.1.2 Feb 8 18:54:26 localhost dhcpcd[997]: enp5s0: deleting route to 192.168.1.0/24 Feb 8 18:54:26 localhost dhcpcd[997]: enp5s0: deleting default route via 192.168.1.1 Feb 8 18:54:26 localhost dhcpcd[997]: exited ... Feb 8 18:54:35 localhost kernel: r8169 :05:00.0 enp5s0: link down ... # PP : restore conn'n Feb 8 19:18:11 localhost kernel: r8169 :05:00.0 enp5s0: link up # PP : Firefox can't find site Netbook msgs : Dec 31 19:00:23 localhost dhcpcd[1323]: version 6.4.7 starting Dec 31 19:00:23 localhost dhcpcd[1323]: dev: loaded udev Dec 31 19:00:23 localhost dhcpcd[1323]: no interfaces have a carrier Dec 31 19:00:23 localhost dhcpcd[1323]: forked to background, child pid 1346 Dec 31 19:00:23 localhost kernel: atl1c :01:00.0: Unable to allocate MSI interrupt Error: -38 Dec 31 19:00:23 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready Dec 31 19:00:23 localhost dhcpcd[1346]: enp1s0: waiting for carrier Dec 31 19:00:23 localhost dhcpcd[1346]: enp1s0: carrier acquired Dec 31 19:00:23 localhost dhcpcd[1346]: DUID 00:01:00:01:03:c3:b8:97:00:26:18:79:64:16 Dec 31 19:00:23 localhost dhcpcd[1346]: enp1s0: IAID 18:79:64:16 Dec 31 19:00:23 localhost dhcpcd[1346]: enp1s0: carrier lost Dec 31 19:00:29 localhost dhcpcd[1346]: enp1s0: using IPv4LL address 169.254.91.169 Dec 31 19:00:29 localhost dhcpcd[1346]: enp1s0: adding route to 169.254.0.0/16 Dec 31 19:00:33 localhost dhcpcd[1346]: enp1s0: soliciting a DHCP lease ... Feb 8 18:54:59 localhost dhcpcd[1346]: enp1s0: carrier acquired ... Feb 8 18:54:59 localhost dhcpcd[1346]: enp1s0: IAID 18:79:64:16 Feb 8 18:54:59 localhost dhcpcd[1346]: enp1s0: soliciting a DHCP lease Feb 8 18:55:07 localhost dhcpcd[1346]: enp1s0: offered 192.168.1.3 from 192.168.1.1 Feb 8 18:55:11 localhost dhcpcd[1346]: enp1s0: leased 192.168.1.3 for 86400 seconds Feb 8 18:55:11
Re: [gentoo-user] netbook connects to Internet automatically, desktop doesn't
On Sun, 8 Feb 2015 19:54:07 -0500, Philip Webb wrote: By accident during my update of my ASUS EEE (now successfully completed), I discovered that it connects automatically to the Internet when the physical connection is plugged in, while my desktop machine (AMD + Gigabyte mobo) has to be told by 'dhcpcd'. I've checked /etc/runlevels/default/etc/udev in both machines, but can't see anything different between the two. Check /etc/rc.conf, especially the hotplug section. Also check whether you have ifplugd or netplug installed on your laptop but not on the desktop. -- Neil Bothwick Angular Momentum Makes The World Go 'Round pgpHNxsy_url4.pgp Description: OpenPGP digital signature