hi,

I would like to know if there anyone seeing this problem with the IPv6 DHCP.

I was making some tests to enable IPv6 on my network, but got the 
problem described below. I´ve made my tests with versions 1.3 and 1.32, 
and both gave the same results.

After enabling IPv6, I went to the "Services: DHCP server" page to make 
the proper configurations. According to what´s written in the DHCP 
server page: "**The DNS servers entered in System: General setup  (or 
the DNS forwarder, if enabled) will be assigned to clients by the DHCP 
server". So, I didn´t worry about setting my IPv6 DNS address.

The problem is, I have my IPv6 DNS addresses (first one is IPv4, second 
and third are IPv6) set in the DNS servers field of the System: General 
Setup page, but the clients behind Monowall are not receiving any IPv6 
DNS addresses, only the monowall LAN IPv4 address.

To verify if the DNSs are IPv6 reachable to the Debian client installed 
  behind monowall, I used the command "host -6 <name> <DNS IPv6 
address>", and it worked fine. "host -6 <name>" died with a timeout.  I 
also tried removing all IPv4 DNS from the System: General setup page, 
leaving only IPv6 addresses. After a DHCP renew, the client still solves 
names only via IPv4, using the Monowall IPv4 LAN address.  Forcing the 
IPv6 DNS address in the "host -6 <name> <dns server>" command works, 
using both the IPv6 LAN Monowall address (so the monowall DNS server is 
working properly both for IPv4 and IPv6) and also directly the DNS address.

So, everything is indicating to me that there is a bug in the IPv6 dhcp 
code that is not forwarding IPv6 DNS addresses to the clients. Anyone 
else seen this?

Tks,

Roberto

-- 
   -----------------------------------------------------
                 Marcos Roberto Greiner

    Os otimistas acham que estamos no melhor dos mundos
     Os pessimistas tem medo de que isto seja verdade
                                   James Branch Cabell
   -----------------------------------------------------