IPv6 Native with Telstra, Australia
-
@derelict said in IPv6 Native with Telstra, Australia:
That doesn't show a DHCP attempt.
You might want to reset to defaults and start over.
Resetting everything related to the WAN DHCP6 should be enough but nobody knows what you've clicked to try to fix this.
I've just re-read this and your comment "that doesn't show a DHCP attempt" intrigues me. Is that a Telstra side issue or a pfsense side issue?
Again, I've factory reset my pfsense, and configured it the way you've asked. Is this a bug with pfsense? I am lost as to what you are suggesting the root cause might be. Is this likely a pfsense config issue or a Telstra issue?
Remember Telstra has stated this:
I can see it sending Ipv6 DHCPv6
13:30:59.553687 In
Juniper PCAP Flags [no-L2, In]
-----original packet-----
PFE proto 6 (ipv6): (hlim 1, next-header: UDP (17), length: 146) fe80::20c:29ff:fe05:a3a1.dhcpv6-server > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 Relay-forwardIt’s also unable to establish Ipv6 neighbours which I suspect is a reason why it’s not functioning correctly
13:31:01.106029 In
Juniper PCAP Flags [no-L2, In]
-----original packet-----
PFE proto 6 (ipv6): (hlim 255, next-header: ICMPv6 (58), length: 32) fe80::20c:29ff:fe05:a3a1 > ff02::1:ff2f:893: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fe80::4e16:fcff:fe2f:893
source link-address option (1), length 8 (1): 00:0c:29:05:a3:a1
0x0000: 000c 2905 a3a113:31:02.073018 Out
Juniper PCAP Flags [no-L2]
-----original packet-----
PFE proto 6 (ipv6): (class 0xc0, hlim 255, next-header: ICMPv6 (58), length: 32) 2001:8003:0:bdf:f0:3:9:0 > ff02::1:ff05:a3a1: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fe80::20c:29ff:fe05:a3a1
source link-address option (1), length 8 (1): 4c:16:fc:2f:08:93
0x0000: 4c16 fc2f 0893 -
@larrikin No. Your side needs to ask for a DHCP6 from the provider.
If you packet capture on the WAN as I described above and edit/save a DHCP6 WAN interface and you do not see DHCP6 packets in the capture, you are very likely doing something completely wrong. No, it's not a bug in pfSense as I have illustrated above. Thousands and thousands and thousands of people are successfully using pfSense and DHCP6. Me included.
Your ISP cannot do anything to stop at least the DHCP6 Solicit packet going out your WAN. If that is not there, you are doing it wrong.
-
@derelict said in IPv6 Native with Telstra, Australia:
@larrikin No. Your side needs to ask for a DHCP6 from the provider.
If you packet capture on the WAN as I described above and edit/save a DHCP6 WAN interface and you do not see DHCP6 packets in the capture, you are very likely doing something completely wrong. No, it's not a bug in pfSense as I have illustrated above. Thousands and thousands and thousands of people are successfully using pfSense and DHCP6. Me included.
Your ISP cannot do anything to stop at least the DHCP6 Solicit packet going out your WAN. If that is not there, you are doing it wrong.
What am I doing wrong? I've following the exact config you suggested precisely. I factory reset the pfsense firewall and then simply configured it as exactly as you instructed. I've even attached the packet capture since doing that above.
-
I don't know. You have yet to produce a packet capture of IPv6/udp/547 on the WAN while a DHCP6 negotiation is going on. No idea if the traffic is there or not, or what it contains. Unfortunately, I can't do it for you.
https://forum.netgate.com/post/826507
-
@derelict said in IPv6 Native with Telstra, Australia:
I don't know. You have yet to produce a packet capture of IPv6/udp/547 on the WAN while a DHCP6 negotiation is going on. No idea if the traffic is there or not, or what it contains. Unfortunately, I can't do it for you.
https://forum.netgate.com/post/826507
How can I capture something that doesn't exist? I literally gave you the packet capture.
-
If it doesn't exist you are doing something wrong. I have no idea what that is.
If you set WAN to DHCP6 and save it, there will be outbound IPv6/UDP/547 traffic. Period.
-
@derelict said in IPv6 Native with Telstra, Australia:
If it doesn't exist you are doing something wrong. I have no idea what that is.
If you set WAN to DHCP6 and save it, there will be outbound IPv6/UDP/547 traffic. Period.Except there isn't. I don't know how to convince you otherwise. There just isn't. I've factory reset pfsense twice, and done that exact packet capture. It isn't there. I even have pfsense configured like you suggested.
So unfortunately in this case, your statement that it will be there isn't true. I wish it were...
-
Ugh. Yes they do. Look at the packet capture settings again.
-
@derelict said in IPv6 Native with Telstra, Australia:
Ugh. Yes they do. Look at the packet capture settings again.
Here are my packet capture settings. Nice and simple. Capture ANY IPv6 traffic. If I just do UDP, NOTHING shows up at all. Nada. Zilch.
So if I pair it back to all IPv6, I get the packet capture that I've attached above.
-
If we screen connect and I fix this, what will you donate to the FreeBSD foundation?
-
@derelict With that exact packet capture rule, here is what I captured using exactly that.
-
Right. You have to start the capture, capturing enough packets to get what you are interested in (say 100000) THEN edit/save WAN to trigger a DHCP6 event.
I did not say to capture all IPv6. I said to capture IPv6 UDP 547. We are not interested in ANYTHING except DHCP6.
-
@derelict said in IPv6 Native with Telstra, Australia:
If we screen connect and I fix this, what will you donate to the FreeBSD foundation?
Mate - take it to the bank that I will. And if you don't, you post in here that you were wrong :) lol.
-
@larrikin said in IPv6 Native with Telstra, Australia:
Mate - take it to the bank that I will. And if you don't, you post in here that you were wrong :) lol.
How much?
-
@derelict said in IPv6 Native with Telstra, Australia:
Right. You have to start the capture, capturing enough packets to get what you are interested in (say 100000) THEN edit/save WAN to trigger a DHCP6 event.
I did not say to capture all IPv6. I said to capture IPv6 UDP 547. We are not interested in ANYTHING except DHCP6.
Well, that work flow I missed :). So I've just done what you've said and you are right, and I am wrong. Here is the packet capture of UDP 547.
But if you fix IPv6 for me and get it going, I'll donate US$50. Fair?
-
So the ISP is not responding. Go back to them with that. I can't do anything about that.
-
@derelict said in IPv6 Native with Telstra, Australia:
So the ISP is not responding. Go back to them with that. I can't do anything about that.
Sweet. I will do exactly that and report back. I'll donate the US$50 once I'm up and running with IPv6 given the time you've spent on this for me. Tell me how I actually do the donation - is there a link?
-
https://www.freebsdfoundation.org/donate/
You said you had someone sympathetic at the ISP. Send them that pcap. Ask why there is no response.
-
@derelict said in IPv6 Native with Telstra, Australia:
https://www.freebsdfoundation.org/donate/
You said you had someone sympathetic at the ISP. Send them that pcap. Ask why there is no response.
Just did exactly that. He is a good guy and actually runs a large part of the network. He'll look into this if he has time (technically this is unsupported but he is a techo at heart and likes to see things working). Basically I'm relying on his good will. Let's see what he says.
-
@derelict said in IPv6 Native with Telstra, Australia:
https://www.freebsdfoundation.org/donate/
You said you had someone sympathetic at the ISP. Send them that pcap. Ask why there is no response.
@Derelict Whilst I think of it, what is going on at the ICMP level where Telstra does respond back to pfsense (neighbor solicit), but pfsense doesn't do anything with Telstra's response? Telstra stated in their email to me that they believe that is part of the problem. What should I say back to Telstra in relation to that?
