Native IPv6 from Telekom using GPON and PPPoe [solved]
-
As I mentioned above, my ISP will only assign me a /64.
-
I called them today, and they said that the best they can do is /64.
That's really too bad. They should not deploy IPv6 at all until they get a clue.
The generally best answer to a moronic ISP is to use a /48 from www.tunnelbroker.net until your ISP comes to their senses.
-
@bbusa said in Native IPv6 from Telekom using GPON and PPPoe:
As I mentioned above, my ISP will only assign me a /64.
That wasn't my question. It was do they support DHCPv6-PD? That's the way many ISPs provide DHCPv6, even for a /64, as my ISP did initially. They now provide a /56. Incidentally, the WAN interface does not need a routeable address. Link local addresses are often used for routing with IPv6.
-
I'm uncertain what kind of delegation method they are using, when I called them on the phone, the only thing they could tell me about this ipv6 connection is that they can see that I've got a /64 subnet assigned to my connection, and they wished me luck in configuring it. My question is, would I have difficulty with other hardware/software also with this?
I had perfectly good LAN (all my devices got a routable ipv6 address) without pfsense (only had firewall issues) and thats why I went with pfsense. But if pfSense is not compatible with this kind of routing, I think its better for me to look for an alternative solution. Anyone would have any tips maybe? -
@JKnott you mentioned that if they are using DHCPv6-PD then it will work with /64 or larger prefix. Could you please share what kind of configuration would I need to have in order to get it working?
-
Setting the DHCP6 configuration on WAN to pull the /64 delegation in the Client Configuration
Setting one and only one inside interface to Track Interface with an IPv6 Prefix ID of 0.
-
@Derelict This was the original config that I've tried.
"What I did is for WAN I used PPPoe for ipv4 (fully working) and set DHCPv6 for ipv6. When I scroll down I have used delegation size of /64, and left everything else unticked, except "Request a Ipv6 prefix/infromation through the ipv4 connectivity link". Without having this ticked, even my router won't get an IPv6.
For the LAN I've used Static IPv4 addressing (which also works here), and used track interface for ipv6 and set my WAN as the tracked interface."See the original post.
This didn't result with success. -
@bbusa Set the DHCP client debugging on on WAN.
Look at the DHCP logs filtering on command dhcp6c
If they are actually putting an interface address on your WAN (link-local or not) and delegating a /64 you should be able to get one interface working.
If they are putting a /64 on WAN and that's it, they are stupid and you'll need to do something else.
-
@bbusa said in Native IPv6 from Telekom using GPON and PPPoe:
@JKnott you mentioned that if they are using DHCPv6-PD then it will work with /64 or larger prefix. Could you please share what kind of configuration would I need to have in order to get it working?
As I mentioned, ISPs often use DHCPv6-PD to assign IPv6. The "PD" part is what provides the subnet. You have to configure the WAN interface to use DHCPv6 and then There's also a setting on the LAN tab to select track interface and with a /64, you'd have to specify your prefix as 0. There's a bit more than that, but this should get you started, if your ISP supports DHCPv6-PD.
-
Telekom uses / 56 prefixes in the retail package, usually not using other constructions in the business package.
I asked my Telekom close acquaintances what they know about the prefixes used in the business package. Maybe on Monday, I will receive an answer that will probably be the same as the packages in the residential package.
With /56 prefixes, you can formed 256 /64 subnets, 256 interfaces can be addressed. -
After further discussion and checking, indeed Telekom was giving out /56 prefixes, and that has solved the issue. Now everything is working.
They had misinformation on the phone, and that created the confusion. -
@bbusa said in Native IPv6 from Telekom using GPON and PPPoe [solved]:
They had misinformation on the phone, and that created the confusion.
Misinformation from an ISP? WOW, that's a first!!! Yeah, right.
IPv6 from my ISP worked well from the start, three years ago, until I ran into a problem around New Years. With my own testing, I had determined the problem was at the ISPs office and later was even able to identify the failing system. It took me 3 months to get the problem resolve and I often found myself having to teach the support people how IPv6 worked. Hopefully, the support will improve, as ISPs get more experience with IPv6.
