Re: NFS root doen't work on next68k after NetBSD 9.2

[Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>]

> > Somehow NetBSD/next68k 10.99.2 GENERIC works with ip_do_randomid=1,
> > but is there any possible workaround for this issue on netbsd-9?
> 
> Very strange.

Maybe because there are many changes around rnd(9), cprng(9) and
other entropy code on HEAD?

> Have you tested tip of netbsd-9? I have booted diskless netbsd-9 machines
> (but no m68k one so far).

I'll test the latest netbsd-9 later.

> Any chance to do packet traces on the NFS server to see more details of
> what goes wrong?

tcpdump says on the timeout:
---
04:26:36.280814 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:0f:00:b6:a9 (oui Unknown), length 548
04:26:36.281160 IP 192.168.20.1.bootps > 192.168.20.77.bootpc: BOOTP/DHCP, Reply, length 316
04:26:37.290149 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:0f:00:b6:a9 (oui Unknown), length 548
04:26:37.290438 IP 192.168.20.1.bootps > 192.168.20.77.bootpc: BOOTP/DHCP, Reply, length 316
04:26:39.304764 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:0f:00:b6:a9 (oui Unknown), length 548
04:26:39.305110 IP 192.168.20.1.bootps > 192.168.20.77.bootpc: BOOTP/DHCP, Reply, length 316
04:26:42.324484 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:0f:00:b6:a9 (oui Unknown), length 548
04:26:42.324832 IP 192.168.20.1.bootps > 192.168.20.77.bootpc: BOOTP/DHCP, Reply, length 316
04:26:46.349283 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:0f:00:b6:a9 (oui Unknown), length 548
04:26:46.349616 IP 192.168.20.1.bootps > 192.168.20.77.bootpc: BOOTP/DHCP, Reply, length 316
04:26:51.426544 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:0f:00:b6:a9 (oui Unknown), length 548
04:26:51.426892 IP 192.168.20.1.bootps > 192.168.20.77.bootpc: BOOTP/DHCP, Reply, length 316
04:26:56.503479 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:0f:00:b6:a9 (oui Unknown), length 548
04:26:56.503817 IP 192.168.20.1.bootps > 192.168.20.77.bootpc: BOOTP/DHCP, Reply, length 316
04:27:01.580462 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:0f:00:b6:a9 (oui Unknown), length 548
04:27:01.580801 IP 192.168.20.1.bootps > 192.168.20.77.bootpc: BOOTP/DHCP, Reply, length 316
---

So NeXT sent BOOTP request and the NFS server replies to it,
but no further packets are sent from NeXT client.

With ip_do_randomid=0, it goes:
---
04:35:26.926882 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:0f:00:b6:a9 (oui Unknown), length 548
04:35:26.927169 IP 192.168.20.1.bootps > 192.168.20.77.bootpc: BOOTP/DHCP, Reply, length 316
04:35:26.931254 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:00:0f:00:b6:a9 (oui Unknown), length 548
04:35:26.931511 IP 192.168.20.1.bootps > 192.168.20.77.bootpc: BOOTP/DHCP, Reply, length 316
04:35:28.056839 ARP, Request who-has 192.168.20.77 tell 0.0.0.0, length 46
04:35:29.608234 ARP, Request who-has 192.168.20.77 tell 0.0.0.0, length 46
04:35:30.808616 ARP, Request who-has 192.168.20.77 tell 0.0.0.0, length 46
04:35:32.820834 ARP, Request who-has 192.168.20.77 tell 192.168.20.77, length 46
04:35:33.243213 ARP, Request who-has 192.168.20.1 tell 192.168.20.77, length 46
04:35:33.243229 ARP, Reply 192.168.20.1 is-at 00:25:22:d2:0f:be (oui Unknown), length 28
---
Izumi Tsutsui