Use Delegate IPv6 Prefix in LAN

rafael.seeck · Jan 17, 2018, 8:30 PM

Hi,

i use a Zyxel VMG1312-B10A with "Deutsche Telekom" as provider.
I get a Dual Stack IPv4 and IPv6 from my Provider.

The Zyxel shared adress to a test device (Windows 7 Machine) which is directly connected to Zyxel VMG1312-B10A and i have IPv4 and IPv6 internet connection.

But i get only an IPv6 address on my WAN (DHCPv6) port but my LAN get no IPv6 address (Track Interface from WAN with 0)

In the attachments i have add the settings from my Zyxel VMG1312-B10A.

Which setting is wrong or which setting i must set to get ipv6 in my LAN network.

Please help

Thx

Rafael
![2018-01-17 21_23_07-.Welcome to the Web-Based Configurator..png](/public/imported_attachments/1/2018-01-17 21_23_07-.Welcome to the Web-Based Configurator..png)
![2018-01-17 21_23_07-.Welcome to the Web-Based Configurator..png_thumb](/public/imported_attachments/1/2018-01-17 21_23_07-.Welcome to the Web-Based Configurator..png_thumb)
![2018-01-17 21_25_51-.Welcome to the Web-Based Configurator..png](/public/imported_attachments/1/2018-01-17 21_25_51-.Welcome to the Web-Based Configurator..png)
![2018-01-17 21_25_51-.Welcome to the Web-Based Configurator..png_thumb](/public/imported_attachments/1/2018-01-17 21_25_51-.Welcome to the Web-Based Configurator..png_thumb)
![2018-01-17 21_27_43-.Welcome to the Web-Based Configurator..png](/public/imported_attachments/1/2018-01-17 21_27_43-.Welcome to the Web-Based Configurator..png)
![2018-01-17 21_27_43-.Welcome to the Web-Based Configurator..png_thumb](/public/imported_attachments/1/2018-01-17 21_27_43-.Welcome to the Web-Based Configurator..png_thumb)
![2018-01-17 21_28_38-.Welcome to the Web-Based Configurator..png](/public/imported_attachments/1/2018-01-17 21_28_38-.Welcome to the Web-Based Configurator..png)
![2018-01-17 21_28_38-.Welcome to the Web-Based Configurator..png_thumb](/public/imported_attachments/1/2018-01-17 21_28_38-.Welcome to the Web-Based Configurator..png_thumb)

hda · Jan 17, 2018, 9:03 PM

If your ISP supplies you a /56 prefix for instance, then your ZyXEL needs to delegate a prefix (say a /62) to your pfSense machine for one LAN to have its /64.

Then test with DHCP6-PD or Static from pfSense to obtain the desired results.

rafael.seeck · Jan 17, 2018, 9:15 PM

Hi,

thanks for your reply.

Is this settings correctly?

Thx

Rafael

![2018-01-17 22_03_30-m-pfSense.home.local - Interfaces_ VDSLWANMaster.png](/public/imported_attachments/1/2018-01-17 22_03_30-m-pfSense.home.local - Interfaces_ VDSLWANMaster.png)
![2018-01-17 22_03_30-m-pfSense.home.local - Interfaces_ VDSLWANMaster.png_thumb](/public/imported_attachments/1/2018-01-17 22_03_30-m-pfSense.home.local - Interfaces_ VDSLWANMaster.png_thumb)

hda · Jan 17, 2018, 9:36 PM

There is now no need for through the IPv4 link.
And only ask the prefix.

But first it must be allowed from the ZyXEL as a /62 to pfSense. (check their forum)

rafael.seeck · Jan 17, 2018, 9:39 PM

hi,

now i´m in the start situation:

WAN get an IPv6 but LAN get no IPv6. All settings i have add as pictures in the attachments.

Thanks

Rafael

![2018-01-17 22_34_15-m-pfSense.home.local - Status_ Dashboard.png](/public/imported_attachments/1/2018-01-17 22_34_15-m-pfSense.home.local - Status_ Dashboard.png)
![2018-01-17 22_34_15-m-pfSense.home.local - Status_ Dashboard.png_thumb](/public/imported_attachments/1/2018-01-17 22_34_15-m-pfSense.home.local - Status_ Dashboard.png_thumb)
![2018-01-17 22_38_12-m-pfSense.home.local - Interfaces_ HEIMLAN.png](/public/imported_attachments/1/2018-01-17 22_38_12-m-pfSense.home.local - Interfaces_ HEIMLAN.png)
![2018-01-17 22_38_12-m-pfSense.home.local - Interfaces_ HEIMLAN.png_thumb](/public/imported_attachments/1/2018-01-17 22_38_12-m-pfSense.home.local - Interfaces_ HEIMLAN.png_thumb)
![2018-01-17 22_38_30-m-pfSense.home.local - Interfaces_ HEIMLAN.png](/public/imported_attachments/1/2018-01-17 22_38_30-m-pfSense.home.local - Interfaces_ HEIMLAN.png)
![2018-01-17 22_38_30-m-pfSense.home.local - Interfaces_ HEIMLAN.png_thumb](/public/imported_attachments/1/2018-01-17 22_38_30-m-pfSense.home.local - Interfaces_ HEIMLAN.png_thumb)
![2018-01-17 22_38_48-m-pfSense.home.local - Interfaces_ VDSLWANMaster.png](/public/imported_attachments/1/2018-01-17 22_38_48-m-pfSense.home.local - Interfaces_ VDSLWANMaster.png)
![2018-01-17 22_38_48-m-pfSense.home.local - Interfaces_ VDSLWANMaster.png_thumb](/public/imported_attachments/1/2018-01-17 22_38_48-m-pfSense.home.local - Interfaces_ VDSLWANMaster.png_thumb)

rafael.seeck · Jan 17, 2018, 9:48 PM

Hi,

before i open here this topic i had contact with the zyxel support from the configuration site everything is fine.

Thx

Rafael

hda · Jan 17, 2018, 10:08 PM

In Firewall Rules Floating: put in rule IPv6 ICMP (any) anywhere Allow.
Check if System Advanced Networking has: Allow IPv6.
Have an Allow rule on your LAN for IPv6 anywhere.

rafael.seeck · Jan 18, 2018, 11:09 AM

Hi Firewall rules is also set.

How can i debug this problem in pfsense?

hda · Jan 18, 2018, 1:42 PM

Show at Status Interfaces ?

Do
Interfaces WAN DHCP6 Client Configuration Debug > Status System Logs DHCP (or General)

Do
DiagnosticsPacket Capture WAN(LAN) > View Capture (or dwnld & Wireshark)

rafael.seeck · Jan 18, 2018, 6:58 PM

Hi,

here the logs from my pfsense box:

Logs from dhcp:


Jan 18 19:22:09    dhcp6c    52079    Sending Solicit
Jan 18 19:22:09    dhcp6c    52079    unknown or unexpected DHCP6 option vendor class, len 18
Jan 18 19:22:09    dhcp6c    52079    advertise contains NoPrefixAvail status

Logs from paket capture:


19:51:33.387373 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:51:37.030823 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:51:46.389244 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:51:52.512874 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:52:00.397632 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:52:09.273705 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:52:13.525238 IP6 fe80::215:17ff:febc:daa1.546 > ff02::1:2.547: UDP, length 97
19:52:13.527773 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1:ffbc:daa1: ICMP6, neighbor solicitation, who has fe80::215:17ff:febc:daa1, length 32
19:52:13.527813 IP6 fe80::215:17ff:febc:daa1 > fe80::a2e4:cbff:fea4:3dc2: ICMP6, neighbor advertisement, tgt is fe80::215:17ff:febc:daa1, length 32
19:52:13.528522 IP6 fe80::a2e4:cbff:fea4:3dc2.36418 > fe80::215:17ff:febc:daa1.546: UDP, length 144
19:52:13.721413 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:52:18.991170 IP6 fe80::215:17ff:febc:daa1 > fe80::a2e4:cbff:fea4:3dc2: ICMP6, neighbor solicitation, who has fe80::a2e4:cbff:fea4:3dc2, length 32
19:52:18.992042 IP6 fe80::a2e4:cbff:fea4:3dc2 > fe80::215:17ff:febc:daa1: ICMP6, neighbor advertisement, tgt is fe80::a2e4:cbff:fea4:3dc2, length 24
19:52:20.423288 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:52:21.786929 IP6 fe80::215:17ff:febc:daa1 > ff02::2: ICMP6, router solicitation, length 16
19:52:23.534638 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:52:24.446869 IP6 fe80::215:17ff:febc:daa1.546 > ff02::1:2.547: UDP, length 97
19:52:24.448690 IP6 fe80::a2e4:cbff:fea4:3dc2.36418 > fe80::215:17ff:febc:daa1.546: UDP, length 144
19:52:25.574409 IP6 fe80::215:17ff:febc:daa1.546 > ff02::1:2.547: UDP, length 97
19:52:25.576884 IP6 fe80::a2e4:cbff:fea4:3dc2.36418 > fe80::215:17ff:febc:daa1.546: UDP, length 144
19:52:27.658950 IP6 fe80::215:17ff:febc:daa1.546 > ff02::1:2.547: UDP, length 97
19:52:27.660968 IP6 fe80::a2e4:cbff:fea4:3dc2.36418 > fe80::215:17ff:febc:daa1.546: UDP, length 144
19:52:29.981862 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:52:31.647205 IP6 fe80::215:17ff:febc:daa1.546 > ff02::1:2.547: UDP, length 97
19:52:31.649272 IP6 fe80::a2e4:cbff:fea4:3dc2.36418 > fe80::215:17ff:febc:daa1.546: UDP, length 144
19:52:39.783712 IP6 fe80::215:17ff:febc:daa1.546 > ff02::1:2.547: UDP, length 97
19:52:39.785645 IP6 fe80::a2e4:cbff:fea4:3dc2.36418 > fe80::215:17ff:febc:daa1.546: UDP, length 144
19:52:39.899272 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:52:49.420112 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:52:55.063083 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:52:56.118458 IP6 fe80::215:17ff:febc:daa1.546 > ff02::1:2.547: UDP, length 97
19:52:56.120488 IP6 fe80::a2e4:cbff:fea4:3dc2.36418 > fe80::215:17ff:febc:daa1.546: UDP, length 144
19:53:00.546213 IP6 fe80::a2e4:cbff:fea4:3dc2 > ff02::1: ICMP6, router advertisement, length 24
19:53:01.119071 IP6 fe80::a2e4:cbff:fea4:3dc2 > fe80::215:17ff:febc:daa1: ICMP6, neighbor solicitation, who has fe80::215:17ff:febc:daa1, length 32
19:53:01.119111 IP6 fe80::215:17ff:febc:daa1 > fe80::a2e4:cbff:fea4:3dc2: ICMP6, neighbor advertisement, tgt is fe80::215:17ff:febc:daa1, length 24

Please help

thx

Rafael

mrsunfire · Apr 2, 2018, 3:47 PM

I have the same problem. My LAN doesnt get an IPv6. My WAN interface receives one.