On Sunday 15 November 2009, Dustin Mitchell wrote: >On Nov 14, 2009, at 9:55 PM, Gene Heskett <[email protected]> > >wrote: >> Nor tonight. But in building the 20091114 version, I saw that the >> ./configure script thinks I have a working ipv6 network. Sorry. >> While I do >> have some ipv6 entries in my host file, the _working_ setup here is >> 100% >> ipv4. So you may want to see if some site that has a known ipv6 >> address can >> be ping6'd. I apparently do not even have an ipv6 dns server, or it >> cannot >> get through an x86 version of dd-wrt, my router. > >That just means that the kernel supports ipv6. The only time this can >cause problems is if you have a partial ipv6 config on your system - >for example, if you resolver returns ipv6 addresses but you don't have >your network interfaces set up. In practice this is really only a >problem on some Solaris systems. > >Dustin
I just noted in the messages log, that amanda _is_ using ipv6 in its system logging reports: Nov 14 21:53:17 coyote xinetd[2491]: START: amanda pid=4159 from=::ffff:192.168.71.3 Nov 14 21:53:47 coyote xinetd[2491]: EXIT: amanda status=0 pid=4159 duration=30(sec) Nov 15 00:18:47 coyote ntpd[2503]: synchronized to 66.250.45.2, stratum 2 Nov 15 01:15:01 coyote xinetd[2491]: START: amanda pid=8340 from=::ffff:192.168.71.3 Nov 15 01:20:32 coyote xinetd[2491]: EXIT: amanda status=0 pid=8340 duration=331(sec) Nov 15 01:20:33 coyote xinetd[2491]: START: amanda pid=8813 from=::ffff:192.168.71.3 Nov 15 01:21:33 coyote xinetd[2491]: EXIT: amanda status=0 pid=8813 duration=60(sec) Nov 15 01:21:45 coyote xinetd[2491]: START: amanda pid=8880 from=::ffff:192.168.71.3 Nov 15 01:22:15 coyote xinetd[2491]: EXIT: amanda status=0 pid=8880 duration=30(sec) Nov 15 01:22:15 coyote xinetd[2491]: START: amanda pid=8906 from=::ffff:192.168.71.3 Nov 15 01:51:46 coyote xinetd[2491]: EXIT: amanda status=0 pid=8906 duration=1771(sec) Nov 15 01:51:53 coyote xinetd[2491]: START: amanda pid=9672 from=::ffff:192.168.71.3 Nov 15 02:50:53 coyote xinetd[2491]: EXIT: amanda status=0 pid=9672 duration=3540(sec) Nov 15 02:50:54 coyote xinetd[2491]: START: amanda pid=11522 from=::ffff:192.168.71.3 Nov 15 02:51:24 coyote xinetd[2491]: EXIT: amanda status=0 pid=11522 duration=30(sec) Nov 15 02:51:25 coyote xinetd[2491]: START: amanda pid=11557 from=::ffff:192.168.71.3 Nov 15 02:51:56 coyote xinetd[2491]: EXIT: amanda status=0 pid=11557 duration=30(sec) So, I guess it does work locally. But I don't notice it making a report for the 4 dle's on the shop's emc machine? All addresses above are this machine. Or would that be logged via that machines log? But they are not logged there either, I just looked. Maybe I have a debug level set here that is not set there? It seems to work, but one gets curious & follows the trail with more questions. Maybe it only logs ipv6 usage? I have the shop box defined in hosts as: 192.168.71.4 shop.coyote.den shop ::ffff:192.168.71.4 shop.coyote.den6 shop6 But: [r...@coyote MyGuns]# ping6 shop6 PING shop6(shop.coyote.den) 56 data bytes ping: sendmsg: Network is unreachable So it appears I need to work on my if-cfg-eth0 setups? Someday, all this ipv6 stuff will need to work. But this is probably not the list to ask how to do it on. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) The NRA is offering FREE Associate memberships to anyone who wants them. <https://www.nrahq.org/nrabonus/accept-membership.asp> The last person that quit or was fired will be held responsible for everything that goes wrong -- until the next person quits or is fired.
