Hi Folks I upgraded one of my firewalls last night to 3.1r2 und ran into a small issue which appears to be a resolver problem. When I have an entry for a remote system in /etc/hosts which is _not_ present in DNS I get first an IPv6 address from the resolver. Mind you, I don't use IPv6.
Could someone verify this in 3.1 final Here some details: innerwall# uname -a Linux innerwall 2.4.34 #1 Tue Jan 23 20:12:21 CET 2007 i686 unknown innerwall# cat /etc/issue LEAF Bering-uClibc 3.1 Rev 2 uClibc 0.9.28 \n \l innerwall# innerwall# uname -a Linux innerwall 2.4.34 #1 Tue Jan 23 20:12:21 CET 2007 i686 unknown innerwall# cat /etc/issue LEAF Bering-uClibc 3.1 Rev 2 uClibc 0.9.28 \n \l innerwall# innerwall# ping chameleon PING chameleon (c0a8:d324:e0f6:ffbf::): 56 data bytes ping: can't create raw socket: Address family not supported by protocol innerwall# nslookup chameleon Server: 192.168.254.31 Address 1: 192.168.254.31 ad1.asp.ruf.ch Name: chameleon Address 1: c0a8:d324:f7:ffbf:: Address 2: 192.168.211.36 chameleon innerwall# cat /etc/hosts 127.0.0.1 localhost 192.168.211.36 chameleon # The following lines are desirable for IPv6 capable hosts #::1 ip6-localhost ip6-loopback #fe00::0 ip6-localnet #ff00::0 ip6-mcastprefix #ff02::1 ip6-allnodes #ff02::2 ip6-allrouters #ff02::3 ip6-allhosts cheers Erich ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
