OPNsense Forum
English Forums => Tutorials and FAQs => Topic started by: elektroinside on February 11, 2018, 09:19:36 am
-
Go through each of this and you will have a working IPv6 from RDS with OPNsense.
Do not apply any settings, just save. When you're done, just reboot OPNsense.
Info: ISP using PPPoE for residential, PPPoE and Static IPs for business consumers. These settings are for PPPoEv6.
More info here: http://www.rcs-rds.ro/internet-digi-net/ipv6/en
Interfaces: [WAN]
General configuration
IPv6 Configuration Type: DHCPv6
DHCPv6 client configuration
Configuration Mode: Basic
Prefix delegation size: 64
Uncheck: Request only a IPv6 prefix, Send IPv6 prefix hint, (optional) Enable debug, Prevent release
Check: Directly send SOLICIT, Use IPv4 connectivity
Use VLAN priority: disabled
[SAVE]
Interfaces: [LAN]
General configuration
IPv6 Configuration Type: Track Interface
Track IPv6 Interface
IPv6 Interface: WAN
IPv6 Prefix ID: 0
[SAVE]
[REBOOT]
Then renew your LAN client's IPs (or just reboot the clients) and then verify if everything is ok here:
https://test-ipv6.com/
or (10x to @phoenix)
https://ipv6.chappell-family.com/ipv6tcptest/
.. and finally test the security:
https://www6.chappell-family.co.uk/cgi-bin6/ipscan-js.cgi
-
You also need to make sure you have an IPv6 LAN firewall rule, and that Firewall>Settings>Advanced Allow IPv6 is checked. Both are there by default, but check anyway if not working.
-
Yes, you're right, thanks. Didn't mention them because they are enabled by default.
-
So I tried it on the OPNsense box and it didn't pass the IPv6 test.
I know the ISP is ok because it works fine on the PFsense box. Which is being decommissioned this coming weekend.
Will try some of the settings later today. Can't reboot right now. I think some of the WAN settings you mentioned may not apply to all ISP's. All the settings were disabled in the PFsense box. Would like to get IPv6 running before I move over to the LAN.
-
Yes, I think some settings are ISP related. It's still just a basic config for RDS PPPoE links, just to bring up IPv6. Might not be perfect, I'm more than happy for any helpful feedback to make it perfect. But, as you already pointed out, might not work at all with other ISPs specific settings...
-
Only enabling 'Use IPv4 connectivity' worked for me. Some of these settings really are ISP specific. I would say start with all disabled, then enable 'Directly send SOLICIT' if IPv6 laggs on startup. Then enable 'Use IPv4 connectivity' if ipconfig does not give an IPv6 address.
Or better yet, get the IPv6 specs from the ISP. LOL
-
The only thing which is not mandatory for IPv6 to work with RDS is the "Prevent release". All the others are, without them checked/unckecked unfortunately you will not get an IPv6 from RDS...
As for the IPv6 specs.. they offer support only for their devices, which frankly suck. I never got any details about anything if their devices were not involved in the support case, except some rare occasions were devices were not needed. So I didn't ask this time :) Although, they always fixed my problems promptly, if their stuff was involved.
-
IPv6 is too unstable. Had to disable it. Yesterday it worked, today it doesn't. And when it's enabled it takes much longer for OPNsense to startup and IPv6 just floods the logs. Shame since it worked fine on the PFsense box for quite a while. I see some issues in another thread too with IPv6. Think I will avoid IPv6 until it really becomes necessary.
-
Neah, I'll keep pushing Franco to fix it until he pushes me out of the forum 😂
-
:)))))))))
You're a senior now, I guess the worst that Franco could do to you is to give you an honorific title in exchange of not posting any more, except maybe for anniversary/ celebration posts.
You will be like Iliescu for PSD (inside joke) around here! :)) :)) ::)
-
That's a good thing! It will (probably, hopefully) also mean I will live 100 years at the very least ;D ;D ;D
-
Only enabling 'Use IPv4 connectivity' worked for me. Some of these settings really are ISP specific. I would say start with all disabled, then enable 'Directly send SOLICIT' if IPv6 laggs on startup. Then enable 'Use IPv4 connectivity' if ipconfig does not give an IPv6 address.
Or better yet, get the IPv6 specs from the ISP. LOL
Your last comment is the key. Many ISP's make it their task in life to make it as difficult as possible to get ipv6 to work. However my task is to try and beat them.
On pf I did a lot of work to get ipv6 to work with Sky UK, they had strange and critical timing requirements to make it work, it may be the same with yours. They also did an odd thing that if you missed the timing sequence the BNG would then reject any subsequent requests, the only way to clear that was disconnect the modem and wait ten minutes for the BNG to reset, there is no other way around it.
I am interested in why you are having issues but this is the wrong thread. If you want to PM me I'll try and help you debug the issues you are having and see if we can find the root cause.
-
As far as IPv6 is concerned, there is a team of 2-4 network designers who decide the exact implementation of it. And then all the hell breaks loose since nobody else gets it, everybody else copy-paste it, and even the design team might be wrong here and there, somewhere, and it takes a while for the feedback to travel from the customers to the design team through all those copy-paste chains, with uncounted and uncountable links in them, and then to travel in a not malformed form!
And all the way back!
Good luck, wherever you might find yourself, good luck, whichever country hosts you now!
:)
-
Sorry to necrobump, but is this tutorial still accurate? I'm asking because I've followed the instructions and IPv6 isn't working for me. I'm trying to assess if the issue is with my configuration or if it's more general. I'm getting the IPv6 only on WAN, but nothing on LAN devices. What's worse, enabling IPv6 seems to be breaking my otherwise functioning HAProxy.