Messages

1

20.1 Legacy Series / Re: DHCPv6 doesnt work on vlans

« on: May 27, 2020, 11:10:33 am »

Managed.

Heres what else i've tried -

Lan set to track interface
radvd set to managed
dhcpv6 enabled, range 2407:7000:84ac:ed02:: to 2407:7000:84ac:ed02:ffff:ffff:ffff:ffff
prefix delegation size - 60

2

20.1 Legacy Series / Re: DHCPv6 doesnt work on vlans

« on: May 27, 2020, 10:06:50 am »

The WAN is dhcpv6 (but isp wont change it).

When set to track interface + slaac all works fine, but when i set the interfaces statically, dhcpv6 wont hand out leases to anyone.

3

20.1 Legacy Series / DHCPv6 doesnt work on vlans

« on: May 27, 2020, 05:49:42 am »

I have enabled DHCPv6 on a vlan.

Devices are requesting dhcpv6 addresses, but opnsense refuses to respond (checked with packet capture)

ISP gives me a /56
Assigned a /64 statically to the vlan interface
Enabled dhcpv6

ANy ideas?

4

20.1 Legacy Series / Re: Track interface different subnet

« on: May 25, 2020, 12:33:25 am »

Thanks for the replies.

I noticed the ability to set downstream ipv6-pd in the dhcpv6 options, but wasent working. Presume because I am using track interface but I have to use static.

Downstream v6-pd i dont think is unusual, common for multiple router setups.

5

20.1 Legacy Series / Re: Track interface different subnet

« on: May 24, 2020, 09:34:28 am »

I get a /56 from my isp, my other firewalls never had issues allocating /60 subnets downstream.

There are plenty of reasons for doing this, obviously its not about running out of addresses.

I have several ipv6 networks on different subnets and need a way to do IPv6-PD downstream so that other routers can advertise ipv6 networks.

Relatively straight forward network design for ipv6

6

20.1 Legacy Series / Track interface different subnet

« on: May 24, 2020, 08:44:45 am »

I have several vlans managed by opnsense, with a track interface for ipv6 for each one, all works perfectly.

For one of the vlans, i want to advertise a /60 subnet, instead of a /64, but there doesnt seem to be any option to do this.

Is there any workaround for this? I could advertise a /60 in addition to the track interface using radvd, but will that advertised subnet be routable the same as a track interface.