syslogd starting before IPv6 network is up

Nicolas Blais nicblais at
Sat May 23 19:57:35 UTC 2009

On Sat, May 23, 2009 at 3:51 PM, Willem Jan Withagen <wjw at>wrote:

> Nicolas Blais wrote:
>> I migrated one of my 8-CURRENT (Thu May 21) box to IPv6 and since then, I
>> get the following message at boot:
>> syslogd: bind: Can't assign requested address
>> syslogd: bind: Can't assign requested address
>> syslogd:
>> child pid 250 exited with return code 1
>> and syslogd obviously fails to start. Apparently this problem has been
>> reported before, but no actual solution other than start syslogd from
>> rc.local was given.
> It is not because  net.inet6.ip6.v6only is off?
> Because than you otherwise get ip4 in ip6 mapping.
> It should be of in recent releases, but in 5.x I remember it being on.
> --WjW
Perhaps you are right, but that interface requires ip4 to connect to the
tunnel broker and become ip6-capable. I don't understand why that sysctl
should have an effect on the rcorder. I checked and net.inet6.ip6.v6only: 1

Here's my dmesg:

/etc/rc: WARNING: failed to start syslogd
Starting Network: lo0 em0.
May 22 15:59:53 pflogd[620]: [priv]: msg PRIV_OPEN_LOG received
pf enabled
add net ::ffff: gateway ::1
add net :: gateway ::1


em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        inet6 fe80::221:9bff:fe34:a235%em0 prefixlen 64 scopeid 0x1
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        inet6 fe80::20a:5eff:fe20:c915%xl0 prefixlen 64 scopeid 0x2
plip0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
pflog0: flags=141<UP,RUNNING,PROMISC> metric 0 mtu 33152
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
pfsync0: flags=41<UP,RUNNING> metric 0 mtu 1460
add net fe80::: gateway ::1
add net ff02::: gateway ::1
IPv4 mapped IPv6 address support=NO
Configuring keyboard:
DHCPREQUEST on em0 to port 67


bound to -- renewal in 1800 seconds.


More information about the freebsd-current mailing list