Package: bootparamd
Version: 0.17-10
Severity: normal
Dear Maintainer,
I was attempting to use rarpd/tftp/bootparamd/nfs to do a solaris
jumpstart installation. When running "rpc.bootparamd -d" I could see
requests directly to the host (testing via callbootd), but requests
sent broadcast (both 192.168.1.255/24 and 255.255.255.255) never reached
bootparamd.
I found adding the remote call option (-r) in /etc/default/rpcbind
caused bootparamd to start seeing broadcast messages.
I see this behavior is documented in /usr/share/doc/rpcbind/README.Debian
but I'm wondering if you think there should be a information in
rpc.bootparamd(8) or other docs to indicate broadcasts may be ignored
by default because it's not obvious rpcbind may be involved.
-- System Information:
Debian Release: 10.2
APT prefers stable-debug
APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages bootparamd depends on:
ii libc6 2.28-10
ii rpcbind [portmap] 1.2.5-0.3+deb10u1
bootparamd recommends no packages.
bootparamd suggests no packages.
