RE: 1.32 and IPv6

I can second that, with a slightly different configuration. In my case I
have set Monowall to use IPv6 tunnel mode, specified the AAISP IPv4 tunnel
end point on Monowall, and my allocated IPv4 address specified from the
AAISP end. I have to run a tunnel since ADSL/Modem combination don;t seem
to be IPv6 capable.

I did find that configuring a /64 subnet on the LAN interface allowed the
router advertising feature to work. Using a /48 subnet on the LAN
interface provoked Monowall to complain that it could not advertise the
prefix because it was too long (might not have details right - I was in a
hurry). Configring /48 facing AAISP and /64 facing in to my LAN works
fine.

Regards

> Whilst I can't answer your specific questions, I can tell you that I am
> running m0n0wall 1.32 with native IPv6 from Andrews & Arnold in the UK and
> everything works as expected.
>
> More info on their implementation is available here:
>
> http://www.aaisp.net.uk/kb-broadband-ipv6.html
>
> In m0n0wall we set the IPv6 WAN option to PPP, configure our allocation
> under the LAN settings, tweak the firewall rules, and it "just works".
>
> Thanks
>
> -----Original Message-----
> From: Egbert Jan [mailto:[email protected]]
> Sent: 20 April 2010 11:32
> To: 'mono'
> Subject: [m0n0wall] 1.32 and IPv6
>
> Hi, I have a question with regard to IPv6. I'm taking part in a pilot for
> native IPv6 (unnumbered, /48 Prefix delegation) orgaized by XS4ALL, a
> Dutch
> ISP that goes a bit further than most others...
>
> The question is: does monowall honor all DHCPv6 advertisements/requsts as
> client on the WAN port? In this pilot we get a /48 delegated and the v6
> address of a DNS server. Maybe more. I do not know all ins and outs of the
> xs4all setup. Someone om the ipv6 mailing list mentioned that monowall
> does
> not listen to the advertisements on the WAN and consequently dos not picks
> up the /48 prefix.
>
> 1.32 has several IPv6 enhancements but the release info is a bit short,
> hence my question.
>
> TIA
> Egbert Jan (NL)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>