svn commit: r239356 - head/sbin/dhclient

Andrey Chernov ache at FreeBSD.ORG
Wed Aug 22 00:06:51 UTC 2012


On Tue, Aug 21, 2012 at 03:58:12PM +0900, Hajimu UMEMOTO wrote:
> Okay, thanks.

I solve this riddle, thanks to your helpful tips.
Relevant part of my setup are at the end of this messae for anybody who 
may have the same problem.

BTW, I notice that link-local router address behavior is 
strange and inconsistant for both 'host -6' and 'dig -6' commands.
host -6 example.com fe80::<rest of router address>
dig -6 @fe80::<rest of router address> example.com
both hangs, but in the same time
host -6 example.com fe80::<rest of router address>%<iface>
dig -6 @fe80::<rest of router address>%<iface> example.com
works!
host -6 example.com fe80::<rest of router address>%1
dig -6 #fe80::<rest of router address>%1 example.com
works too. Not understanding addresses without %<iface> or %1 looks like 
routing problems, but I don't know where to fix it.
So, I try to use 
nameserver fe80::<rest of router address>%<iface> (or with %1 suffix)
in my resolv.conf, as result
host -6 example.com
dig -6 example.com
(without NS specified) both hangs despite they working when exact the same 
NS address is given in their command lines.
So, I finally decide to use my router addres from IPv6 /64 subnet
(given by my tunnel). It not goes through the whole tunnel, but directly
to the router.
host -6 example.com
dig -6 example.com
both works when it exists in /etc/reslov.conf.
What I don't understand why all that bad things happens with link-local 
router address. To be sure I test it under Win7 and it works normally.

Finally, what is working:

/etc/resolvconf.conf:
name_servers_append=<IPv6 router address from /64 tunnel's subnet>

/etc/rc.conf:
rtsol_flags="-R /etc/eat.sh"

/etc/eat.sh:
#!/bin/sh
/bin/cat > /dev/null

-- 
http://ache.vniz.net/


More information about the svn-src-all mailing list