A bit of history:
My assertion from my first post is false
bit wrote
dhcpcd is listening on port 68 (bootpc) which it hadn't before
As I've noted later I wasn't sure if dhcpcd was enabled by default
Hence the emphasis on the word: think.
bit wrote
don't *think* it was the case before
I now realize I was wrong, dhcpcd was indeed not enabled by default
Even if it had of been, connman does the same job.
A bit of additional history:
dhcpcd hadn't worked after restarting the pc. As I've said before
bit wrote
but since I -Rsun'd connman I assume it lost the configuration
(it would explain why dhcpcd couldn't connect)
dhcpcd worked fine before restarting because by theory it used the
same network lease as set before by connman[0] but since it defaults to
its own (bianry) lease after restart, perhaps it is having trouble
reading it(?)
taco@ zen ~ % cat /var/lib/dhcpcd/dhcpcd-enp3s0.lease
NgPIcSc563QHome
The only way I can explain this mystery is that dhclient works
after each restart instead with a much cleaner lease file
taco@ zen ~ % cat /var/lib/dhclient/dhclient.leases
lease {
interface "enp3s0";
fixed-address 192.168.1.103;
option subnet-mask 255.255.255.0;
option routers 192.168.1.1;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option domain-name-servers 192.168.1.1;
option dhcp-server-identifier 192.168.1.1;
option domain-name "Home";
renew 5 2016/03/18 10:27:55;
rebind 5 2016/03/18 20:44:27;
expire 5 2016/03/18 23:44:27;
}
Because there's no other way I can explain how dhcpcd doesn't work after restart
because it doesn't have any sign of error from the logs
2016-03-17_23:08:45.89938 dhcpcd-6.10.1 starting
2016-03-17_23:08:45.89940 dev: loaded udev
2016-03-17_23:08:45.89940 enp3s0: executing
`/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
2016-03-17_23:08:45.89941 enp3s0: executing
`/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
2016-03-17_23:08:45.89941 enp3s0: delaying IPv4 for 0.6 seconds
2016-03-17_23:08:45.89941 enp3s0: using hwaddr 50:e5:49:ca:c4:17
2016-03-17_23:08:45.89942 enp3s0: reading lease
`/var/lib/dhcpcd/dhcpcd-enp3s0.lease'
2016-03-17_23:08:45.89942 enp3s0: rebinding lease of 192.168.1.103
2016-03-17_23:08:45.89942 enp3s0: sending REQUEST (xid 0xab217abb), next
in 4.0 seconds
2016-03-17_23:08:45.89943 enp3s0: acknowledged 192.168.1.103 from
192.168.1.1
2016-03-17_23:08:45.89943 enp3s0: leased 192.168.1.103 for 86400 seconds
2016-03-17_23:08:45.89944 enp3s0: renew in 43200 seconds, rebind in
75600 seconds
2016-03-17_23:08:45.89944 enp3s0: writing lease
`/var/lib/dhcpcd/dhcpcd-enp3s0.lease'
2016-03-17_23:08:45.89944 enp3s0: adding IP address 192.168.1.103/24
2016-03-17_23:08:45.89945 enp3s0: adding route to 192.168.1.0/24
2016-03-17_23:08:45.89945 enp3s0: adding default route via 192.168.1.1
2016-03-17_23:08:45.89945 enp3s0: executing
`/usr/lib/dhcpcd/dhcpcd-run-hooks' BOUND
2016-03-17_23:08:45.89946 forking to background
2016-03-17_23:08:45.89946 forked to background, child pid 9553
2016-03-17_23:08:46.00348 sending signal TERM to pid 9553
2016-03-17_23:08:46.00351 waiting for pid 9553 to exit
2016-03-17_23:08:47.01301 zen
A bit of news and disocvery:
I've learned that bootpc is needed to lease the ip address for the duration set by dhcpcd/dhclient, which according to the log is around 24 hours. However after that time dhcpcd/dhclient don't close the port. Connman on the otherhand gracefully closes the listening port for dhcp after the ip lease is established from the router. Thus I've came to the
conclusion that I will not be using dhcpcd or dhclient for my network connection, not that it shouldn't listen on port 68, It is needed by its design. However I don't like ports listening for a long time. Therefore I've found a solution for this, I could establish the connection with "ip {link,addr,route}" in rc.local/rc.d so that way there isn't a need for dhcpcd,dhclient or connman :)
eric wrotePerhaps if I manually assigned an IP with dhcpcd, would it go away???
Thanks for the help anyway, I'm just a newbie network admin ... lol xD
[0]
https://01.org/connman/blogs/pflykt/2014/connman-1.17