[suli]

Preferace: I'm currently using a November k3 build (DD-WRT v3.0-r30880 mega). I use DNSMASQ currently for DNS/DHCP assignments on a few vlans.

My current setup, I have setup similar to:

Networking
WAN Port Assignment: vlan15
Network Config vlan1: unbridged, MTU 1491
192.168.A.254/ 255.255.255.0
Network Config vlan11: unbridged, MTU 1491
192.168.B.254/ 255.255.255.0

Mulitple DHCPD Server
vlan11, start: .20, max: 20, lease time: 360 (DHCP 0, 6hr)

Services
-DNSMasq Options (to enable DHCP to function for vlans)
*NOTE: option 3 is gateway
option 6 are dns servers

[JAMESMTL]

how are you getting your ipv6? dhcpv6-pd? What size prefix?

fyi a /120 is not the way to go, normally you would assign a /64 to each interface.

[suli]

I'm getting my IPv6 via DHCPv6-PD.

They're providing a /64
nnnn:nnnn:nnnn:nnnn:hhhh:hhhh:hhhh:hhhh
I checked the nrvarm show |grep ipv6 and the "ipv6_prefix" value validates it's a /64

I wanted to assign each subnet as a range from the provided /64 I get from the ISP so I can assign global addresses (and control it) (aka, each vlan). This way I can get granular control over the routing and allowables through ip6tables just like I do with iptables for v4.

I picked a /120, since I only need 15-20 ip's, and the /120 gives me 254 usable IP addresses.
nnnn:nnnn:nnnn:nnnn:ssss:ssss:ssss:sshh

If I grow these out later, I can easily redo the mask to less than a 120, like a 112.


Two side notes:

-Since I set the vlan15 interface as the WAN, that is what ddwrt assigns my IPv4 address to, but... with IPv6, is assigns it to br0. Not sure how to get that IPv6 address assigned to vlan15.

-I tried a simple ping6 to google and it doesn't work. I left the default ipv6tables rules, so everything outbound is allowed, and inbound is related/established and also icmpv6 are all allowed. It's pretty open. My ip -6 route info has:
[ipv6 prefix from ISP]/64 dev br0 proto kernel metric 256
fe80::/64 dev eth0 proto kernel metric 256
fe80::/64 dev vlan3 proto kernel metric 256
fe80::/64 dev vlan4 proto kernel metric 256
fe80::/64 dev vlan11 proto kernel metric 256
fe80::/64 dev vlan1 proto kernel metric 256
fe80::/64 dev eth1 proto kernel metric 256
fe80::/64 dev eth2 proto kernel metric 256
fe80::/64 dev vlan2 proto kernel metric 256
fe80::/64 dev vlan15 proto kernel metric 256
default via fe80::201:5cff:fe7a:c46 dev vlan15 proto ra metric 1024 expires 1799sec
unreachable default dev lo proto kernel metric -1 error -128

[SmallvilleLA]

I have an R7000

Here's my DNSMasq additional:

dhcp-range=::1,::400,constructor:br0, ra-stateless, ra-names, 4h
dhcp-option=option6:dns-server,[::]
enable-ra

DHCP Server - enable
DNSMasq for DHCP - enable
DNSMasq for DNS - enable
DHCP-Authoritative - enable
Recursive DNS Resolving - disabled
Forced DNS Redirection - enable

IPV6 enabled with DHCPv5 delegation and DNS.watch IPv6 addresses /64

Using DNS.Watch for forwarding DNS

Static DNS 1 - my router IP
Static DNS 2 - DNS.Watch1
Static DNS 4 - DNS Watch2

DNSMasq - Enable
Encrypt DNS - Disable
Local DNS - Enable
No DNS Rebind - Enable
Query DNS in Strict Order - Enable
Add Requestor MAC to DNS Query - Disaable

My set up is Gateway

Your ISP needs to support IPv6 and the modem/router they supply also needs to support it.

These settings pass IPv6 tests and show my internal DNS to be my router IPv4 and IPv6 addresses (ipconfig /all)

No IPLeaks after adding a couple browser extensions

VPN options are next up for me. I had conflicting info about my ISP and their equipment to contend with. After swapping the modem and getting the static DNS order right, it's doing what its supposed to.

Hope this helps

[Per Yngve Berg]

@suli

You should get a 48-60 prefix from your isp and break it up in /64 for each interface.

[suli]

I had other projects, so forgot about this one.

My ISP is only providing a /64, nothing larger.

[Per Yngve Berg]

this is what I use for DHCP6C Custom for 3 sub-nets: