Re: NetBSD-current amd64 with dhcpcd connects only partially

To: current-users%netbsd.org@localhost
Subject: Re: NetBSD-current amd64 with dhcpcd connects only partially
From: "Thomas Mueller" <mueller6724%bellsouth.net@localhost>
Date: Tue, 13 Jun 2017 21:20:24 +0000

from Roy Marples and my previous post:

> > Using dhcpcd or dhclient makes me rusty on directly setting internet interface; any suggestions for improvement on what I did are welcome.
 
> > But directly configuring internet interface uncripples an otherwise crippled NetBSD installation.
 
> > I think I could also have expressed netmask as 0xffffff00 or ...inet 192.168.0.4/24 ?

> None of this actually helps us diagnose or fix any problem with re(4) or
> dhcpcd(8) you have encountered.

It uncripples re(4) but might not help fix problems with dhcpcd or dhclient.

> Steps to help:

  *  Add the debug directive to /etc/dhcpcd.conf, or set it in
     /etc/rc.conf as dhcpcd_flags="-qdM"

  *  Set dhcpcd to log it it's own file if it's a boot up issue
     (as it starts before syslog). Put this in /etc/dhcpcd.conf:
     logfile /var/log/dhcpcd.log
     Then attach this log in a reply

  *  Post the output of these command after running dhcpcd
     dhcpcd -U4 re0
     ifconfig re0
     netstat -nrf inet
     If you can, tell us how this output is wrong vs your expectations.

I did what you asked, saved the log files.

I don't run dhcpcd or anything like that from /etc/rc.conf but ran 
dhcpcd -dM re0 :

Jun 13 20:05:47 [423]: dhcpcd-7.0.0-rc1 starting
Jun 13 20:05:47 [423]: re0: disabling Kernel IPv6 auto link-local support
Jun 13 20:05:47 [423]: re0: disabling Kernel IPv6 RA support
Jun 13 20:05:47 [423]: re0: executing `/libexec/dhcpcd-run-hooks' PREINIT
Jun 13 20:05:47 [423]: re0: executing `/libexec/dhcpcd-run-hooks' CARRIER
Jun 13 20:05:47 [423]: DUID 00:01:00:01:1c:d4:31:ea:d4:3d:7e:97:17:e2
Jun 13 20:05:47 [423]: re0: IAID 7e:97:17:e2
Jun 13 20:05:47 [423]: re0: adding address fe80::5f73:2954:b072:bae
Jun 13 20:05:47 [423]: re0: pltime infinity, vltime infinity
Jun 13 20:05:47 [423]: re0: delaying IPv6 router solicitation for 0.8 seconds
Jun 13 20:05:47 [423]: re0: delaying IPv4 for 0.8 seconds
Jun 13 20:05:47 [423]: re0: carrier lost
Jun 13 20:05:47 [423]: re0: executing `/libexec/dhcpcd-run-hooks' NOCARRIER
Jun 13 20:05:47 [423]: re0: carrier acquired
Jun 13 20:05:47 [423]: re0: executing `/libexec/dhcpcd-run-hooks' CARRIER
Jun 13 20:05:47 [423]: re0: IAID 7e:97:17:e2
Jun 13 20:05:47 [423]: re0: delaying IPv6 router solicitation for 0.6 seconds
Jun 13 20:05:47 [423]: re0: delaying IPv4 for 0.4 seconds
Jun 13 20:05:48 [423]: re0: reading lease `/var/db/dhcpcd/re0.lease'
Jun 13 20:05:48 [423]: re0: discarding expired lease
Jun 13 20:05:48 [423]: re0: soliciting a DHCP lease
Jun 13 20:05:48 [423]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 3.4 seconds
Jun 13 20:05:48 [423]: re0: soliciting an IPv6 router
Jun 13 20:05:48 [423]: re0: delaying Router Solicitation for LL address
Jun 13 20:05:48 [423]: re0: sending Router Solicitation
Jun 13 20:05:51 [423]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 8.8 seconds
Jun 13 20:05:52 [423]: re0: sending Router Solicitation
Jun 13 20:05:53 [423]: re0: probing for an IPv4LL address
Jun 13 20:05:53 [423]: re0: using IPv4LL address 169.254.213.226
Jun 13 20:05:53 [423]: re0: adding IP address 169.254.213.226/16 broadcast 169.254.255.255
Jun 13 20:05:56 [423]: re0: sending Router Solicitation
Jun 13 20:05:58 [423]: re0: DAD completed for 169.254.213.226
Jun 13 20:05:58 [423]: re0: adding route to 169.254.0.0/16
Jun 13 20:05:58 [423]: re0: adding default route
Jun 13 20:05:58 [423]: re0: executing `/libexec/dhcpcd-run-hooks' IPV4LL
Jun 13 20:05:58 [423]: forking to background
Jun 13 20:05:58 [423]: forked to background, child pid 136
Jun 13 20:06:00 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 15.9 seconds
Jun 13 20:06:00 [136]: re0: sending Router Solicitation
Jun 13 20:06:00 [136]: re0: no IPv6 Routers available
Jun 13 20:06:16 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 31.3 seconds
Jun 13 20:06:45 [136]: re0: Router Advertisement from fe80::3a4c:90ff:fe65:ce67
Jun 13 20:06:45 [136]: re0: adding address 2607:fcc8:ab8c:cc00:6e83:8fca:ef51:9992/64
Jun 13 20:06:45 [136]: re0: pltime 3600 seconds, vltime 3600 seconds
Jun 13 20:06:45 [136]: re0: adding route to 2607:fcc8:ab8c:cc00::/64
Jun 13 20:06:45 [136]: re0: adding default route via fe80::3a4c:90ff:fe65:ce67
Jun 13 20:06:45 [136]: re0: waiting for Router Advertisement DAD to complete
Jun 13 20:06:45 [136]: re0: requesting DHCPv6 information
Jun 13 20:06:45 [136]: re0: delaying INFORM6 (xid 0x3d6d58), next in 0.2 seconds
Jun 13 20:06:45 [136]: re0: broadcasting INFORM6 (xid 0x3d6d58), next in 1.0 seconds
Jun 13 20:06:46 [136]: re0: Router Advertisement DAD completed
Jun 13 20:06:46 [136]: re0: executing `/libexec/dhcpcd-run-hooks' ROUTERADVERT
Jun 13 20:06:46 [136]: re0: broadcasting INFORM6 (xid 0x3d6d58), next in 1.9 seconds
Jun 13 20:06:48 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 63.3 seconds
Jun 13 20:06:48 [136]: re0: broadcasting INFORM6 (xid 0x3d6d58), next in 3.7 seconds
Jun 13 20:06:51 [136]: re0: broadcasting INFORM6 (xid 0x3d6d58), next in 7.7 seconds
Jun 13 20:06:59 [136]: re0: broadcasting INFORM6 (xid 0x3d6d58), next in 15.7 seconds
Jun 13 20:07:15 [136]: re0: broadcasting INFORM6 (xid 0x3d6d58), next in 32.2 seconds
Jun 13 20:07:47 [136]: re0: broadcasting INFORM6 (xid 0x3d6d58), next in 66.9 seconds
Jun 13 20:07:51 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 63.5 seconds
Jun 13 20:08:54 [136]: re0: broadcasting INFORM6 (xid 0x3d6d58), next in 129.4 seconds
Jun 13 20:08:55 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 63.1 seconds
Jun 13 20:09:58 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 63.2 seconds
Jun 13 20:11:01 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 65.0 seconds
Jun 13 20:11:03 [136]: re0: broadcasting INFORM6 (xid 0x3d6d58), next in 254.5 seconds
Jun 13 20:12:06 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 64.1 seconds
Jun 13 20:13:10 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 64.0 seconds
Jun 13 20:14:14 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 64.0 seconds
Jun 13 20:15:18 [136]: re0: broadcasting INFORM6 (xid 0x3d6d58), next in 489.6 seconds
Jun 13 20:15:18 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 63.2 seconds
Jun 13 20:16:21 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 63.9 seconds
Jun 13 20:17:25 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 64.3 seconds
Jun 13 20:18:30 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 63.4 seconds
Jun 13 20:19:33 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 64.6 seconds
Jun 13 20:20:38 [136]: re0: sending DISCOVER (xid 0xfcf83f6d), next in 63.3 seconds

I ran other commands and got

dhcpcd -U4 re0 produces

broadcast_address=192.168.0.255
dhcp_lease_time=3600
dhcp_message_type=5
dhcp_server_identifier=192.168.0.1
domain_name_servers='209.18.47.61 209.18.47.62'
host_name=amelia2
ip_address=192.168.0.4
network_number=192.168.0.0
routers=192.168.0.1
subnet_cidr=24
subnet_mask=255.255.255.0

ifconfig re0 shows

re0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	capabilities=3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx>
	capabilities=3f80<UDP4CSUM_Rx,UDP4CSUM_Tx>
	enabled=0
	ec_capabilities=3<VLAN_MTU,VLAN_HWTAGGING>
	ec_enabled=0
	address: d4:3d:7e:97:17:e2
	media: Ethernet autoselect (1000baseT full-duplex)
	status: active
	inet 169.254.213.226/16 broadcast 169.254.255.255 flags 0x0
	inet6 fe80::5f73:2954:b072:bae%re0/64 flags 0x0 scopeid 0x2
	inet6 2607:fcc8:ab8c:cc00:6e83:8fca:ef51:9992/64 flags 0x0

netstat -nrf inet shows

Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use    Mtu Interface
default            link#2             UCS         -        -      -  re0
127/8              127.0.0.1          UGRS        -        -  33624  lo0
127.0.0.1          lo0                UHl         -        -  33624  lo0
169.254/16         link#2             UC          -        -      -  re0
169.254.213.226    link#2             UHl         -        -      -  lo0


Sorry if this is too verbose (you don't need to quote everything in your reply).

host news.individual.net didn't find news.individual.net

IP address 169.254.213.226 looks screwy.

I got a couple of crashes along the way, right while I was typing.

But now I am  on directly-configured connection, non-dhcpcd/dhclient.

Mounting /home from other computer by NFS, I don't want to crash.

Tom

Follow-Ups:
- Re: NetBSD-current amd64 with dhcpcd connects only partially
  - From: Thomas Mueller
- Re: NetBSD-current amd64 with dhcpcd connects only partially
  - From: Robert Elz
- Re: NetBSD-current amd64 with dhcpcd connects only partially
  - From: Thor Lancelot Simon

References:
- NetBSD-current amd64 with dhcpcd connects only partially
  - From: Thomas Mueller
- Re: NetBSD-current amd64 with dhcpcd connects only partially
  - From: Robert Elz
- Re: NetBSD-current amd64 with dhcpcd connects only partially
  - From: Thomas Mueller
- Re: NetBSD-current amd64 with dhcpcd connects only partially
  - From: Roy Marples

Prev by Date: Re: NetBSD-current amd64 with dhcpcd connects only partially
Next by Date: Re: NetBSD-current amd64 with dhcpcd connects only partially
Previous by Thread: Re: NetBSD-current amd64 with dhcpcd connects only partially
Next by Thread: Re: NetBSD-current amd64 with dhcpcd connects only partially
Indexes:

Home | Main Index | Thread Index | Old Index