Author
Message
MeMeow DD-WRT Novice Joined: 08 Apr 2018 Posts: 4
Posted: Sun Apr 08, 2018 17:49 Post subject: Setting up Ipv6PD (Linksys WRT3200ACM; DD-WRT v3.0)
Hello!
I'm trying to set up an Ipv6, my provider has dual stack and is using prefix delegation /64.
I tried different radvd configurations from wiki and posts on this forum. Nothing seems to work for me - I only see scope-link addresses.
I don't have a modem, it's a FTTH type connection.
Customer support says "It's supposed to be automatic" and I couldn't get anything else out of them.
I could use any help - I'm stuck and don't know what else to try. Would appreciate any working radvd configurations.
Linksys WRT3200ACM-EU
Using DD-WRT v3.0-r35531 std
Back to top
Sponsor
Per Yngve Berg DD-WRT Guru Joined: 13 Aug 2013 Posts: 6868 Location: Romerike, Norway
Posted: Thu Apr 12, 2018 13:46 Post subject:
Do you get a public ipv4 address on the WAN?
1) If you get a /64 Global address on the WAN, there is a upstream router that have already taken the /64 PD.
2) With a PD, you will get a Global address on br0
Back to top
MeMeow DD-WRT Novice Joined: 08 Apr 2018 Posts: 4
Posted: Thu Apr 12, 2018 14:48 Post subject:
Per Yngve Berg wrote: Do you get a public ipv4 address on the WAN?
1) If you get a /64 Global address on the WAN, there is a upstream router that have already taken the /64 PD.
2) With a PD, you will get a Global address on br0
Yes, sure I do get Ipv4.
Supposedly, I should also get Ipv6, but I don't see anything really on my br0/eth0:
Code: br0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::6238:e0ff:febd:aec1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:32294752 errors:0 dropped:0 overruns:0 frame:0
TX packets:22917407 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18894077606 (17.5 GiB) TX bytes:33260141578 (30.9 GiB)
All the other interfaces look the same, no scope:global anywhere. Same on stock firmware. But my ISP says that I should be getting it...
Back to top
Per Yngve Berg DD-WRT Guru Joined: 13 Aug 2013 Posts: 6868 Location: Romerike, Norway
Posted: Fri Apr 13, 2018 21:17 Post subject:
MeMeow wrote: Yes, sure I do get Ipv4.
Yes, but is it a public address i.e not 10.x.x.x, 172.16-32.x.x or 192.168.x.x?
Back to top
MeMeow DD-WRT Novice Joined: 08 Apr 2018 Posts: 4
Posted: Sat Apr 14, 2018 0:23 Post subject:
Per Yngve Berg wrote: MeMeow wrote: Yes, sure I do get Ipv4.
Yes, but is it a public address i.e not 10.x.x.x, 172.16-32.x.x or 192.168.x.x?
Yes, it is a public address
Back to top
Per Yngve Berg DD-WRT Guru Joined: 13 Aug 2013 Posts: 6868 Location: Romerike, Norway
Posted: Sat Apr 14, 2018 5:32 Post subject:
Try this in dhcp6c custom:
interface eth0 {
send rapid-commit;
send ia-pd 1;
request domain-name-servers, domain-name;
};
id-assoc pd 1 {
prefix ::/64 infinity;
prefix-interface br0 {
sla-id 0;
sla-len 0;
};
};
Check that eth0 is correct for your WAN interface
Back to top
MeMeow DD-WRT Novice Joined: 08 Apr 2018 Posts: 4
Posted: Mon Apr 16, 2018 8:53 Post subject:
Per Yngve Berg wrote: Try this in dhcp6c custom:
interface eth0 {
send rapid-commit;
send ia-pd 1;
request domain-name-servers, domain-name;
};
id-assoc pd 1 {
prefix ::/64 infinity;
prefix-interface br0 {
sla-id 0;
sla-len 0;
};
};
Check that eth0 is correct for your WAN interface
Tried, no luck. After days of struggle I'm starting to believe something could be misconfigured on the provider's side, it shouldn't be that difficult to set it up ):
Back to top