There is ntp.org in the IPv6 wall of shame, to no one’s surprise: Why No IPv6?
2 Likes
Nobody likes IPv6….but you started something they hate me for it in here.
I hate IPv6 as it’s a stupid protocol.
It’s too complicated and nobody understands it.
Not even the insiders know how it works. Nobody can explain it….song of FleedWoodMac 
It takes courage to post this on an IPv6 enabled platform.
4 Likes
Nothing the pool system can change will change ntp.org being in that list, as I understand their criteria.
You do?
They have nothing to do with the pool. I do not even understand what they do apart from passing time form 1 machine to another.
We know that, we all do it….but what do they do? I have no clue. Do we need them?
What about Chrony, that is by far better for most. Sorry I do not get it at all.
Why are they asking money? Will it change time?
I do not get it. Am I missing something?
As before: You don’t seem to understand it, and some other people probably don’t, either. But that does not mean that nobody understands it.
Sorry, again not true. There’s a whole bunch of people in the world, many not even “insiders”, who do understand it.
1 Like
Ok, please explain as you seem to understand.
I do not mean, you got it working, as most got that after struggle.
How does IPv6 works….in total…please enlighten us all!
I could not find ANY website that knows, not a single one.
Again, why do you speak for other people by asking to enlighten “us all”? If you look through the forum, people have tried to explain it to you. So at least those people seem to have understood it.
Look though this forum, and you’ll see people explaining various aspects of it. Again, you not understanding it (and you’re not alone, and that is perfectly ok) does not mean nobody understands it.
Please stop speaking for other people, though, when clearly many people do not agree with your views. On this and various other topics. At least I object to you making statements implicitly on my behalf.
4 Likes
You hate it so much because you don’t understand it. If you did, you wouldn’t hate it so much. I’ve been running IPv6 smoothly for the past 15 years and had very few issues with it. And yes, I understand it for the most part 
3 Likes
I was using Hurricane Electrics IPv6 tunnel back in my ADSL days, which was back in the early 2000’s. So probably close to a quarter of a century I’ve been dabbling with and using IPv6. Yeah, I’m old. 
Best way to get into and learn about IPv6 is to use a dedicated Firewall/Router OS that actually supports IPv6 natively, like Opnsense or pfSense. The vast majority of ISP supplied routers have crap implentations of IPv6 support if they support IPv6 on thier network to begin with, and even consumer routers you can get from big box stores/Amazon have limited configuration options that may or may not work with your ISPs implmentation of IPv6, hence the “problems” with IPv6.
And that’s probably the crux of Bas’ issue with IPv6, since in the posts he’s complained about IPv6, he’s mainly working with Fritzbox or similar hardware, only trying Opnsense (or was it pfSense?) for a very short time and giving up on it before even getting to know it.
Going to give it another shot.
I got it working in the past, but was more luck then anything else.
But that was a Fritzbox, maybe it’s easier with my DrayTek.
Update: I can not manage to punch 1 hole in the firewall to allow just 1 port, the DrayTek will not listen. It opens ALL ports or closes ALL in the IPv6 adresses.
Tried everything. Weird. Maybe a bug in it. No matter what I do, it’s all open or nothing.
Also, have been reading all their documentation, as well as searched their forum….found no usefull information. Also read Reddit, got some tips, it doesn’t help.
I can’t afford to have everything exposed. IPv6 is enabled local, I have to contact DrayTek about this.
Anybody here that knows what I’m doing wrong? I really want to support IPv6. But it seems routers hate me 
Looks like I got it working by listing IPv6 123 as ANY type and not just UDP.
Can somebody check if this is the only port open?
2a07:3145:81d:6801::50
As remote portcheckers do not always check correctly, typical not UDP.
You have my permission to scan my IP for faults. Thanks.
Edit: Never mind, as soon as IPv6 worked, IPv4 stopped working 
Routers really hate me.
Your router should usually advertise a prefix (most likely a /64) on the LAN. You can check if it’s there with “ip -6 r”. If so, you can add a semi-static IPv6 address like:
sudo ip -6 addr add <your_prefix>::b00b/64 dev eth0
(Replace <your_prefix> with the prefix, example: 2620:fe:f0::b00b/64)
The gateway is usually advertised by RA (router advertisement) and often begins with “default via fe80”
you can check if all is set with ping -6 google.com
(you may want to write a script for adding the semi-fixed address)
This is what I have here
2a02:a03f:8b33:3d00::/64 dev eth0 proto kernel metric 256 expires 3567sec pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fe80::d601:c3ff:fe41:e8bb dev eth0 proto ra metric 1024 expires 1767sec hoplimit 64 pref medium
The top line is the prefix from the router, bottom one “defautl via…” is the gateway advertised by router via RA.
Set the router to only acquire a prefix from the ISP, no IPv6 address.
1 Like
I had that with IPv6, and I got it working, but them ipv4 stopped working.
I know how IPv6 is supposed to work, I know how IPv4 works.
I do believe DrayTek f-ed up the IPv6 firewall.
Why is this so problematic? Looks to me not a single router manufacturer knows what to do.
As far as I understand, IPv6 does not need a gateway, you do not need to specify it.
And that worked, but then it dropped ALL ipv4 traffic, why?
Of course IPv6 needs a gateway, but it’s advertised by the router itself and not by DHCP like in IPv4 - ie, you do not have to add it manually. I do not know how your Draytek works, but can you bring down the IPv6 firewall and see if then both v4 & v6 work?
On MikroTik, it’s really not that difficult. I ask Proximus/MV for a /56 prefix, it gives me that and then I can use its /64 on all my devices. IPv6 firewall is really not that different from IPv4.
No it doesn’t you not need to give a gateway.
It doesn’t use it.
That is what I mean.
IPv6 routers may send Router Advertisement messages which look like this in tcpdump:
22:50:53.084030 IP6 fe80::bb > fe80::a395:565a:5ae6:7630: ICMP6, router advertisement, length 24
“route -6n” shows the routing table:
Destination Next Hop Flag Met Ref Use If
2001:db8:a301:1cca::1/128 :: U 100 1 0 enp1s0
fe80::/64 :: U 1024 3 0 enp1s0
::/0 fe80::bb UG 100 5 0 enp1s0
Here “fe80::bb” is the gateway address. The fe80::/10 network is for special link-local addresses, ie. addresses which are only used locally for local routing purposes.
I did not configure this gateway address manually, but it’s still a gateway.
1 Like
Yes, it does! Stop being stubborn. You do not need to give it because it is automatically received by the device from the router via RA (router advertisement).
1 Like
That is what I said, you do not have to tell it the gateway. I didn’t and it works. Unlike ipv4 where you must specify it.
Ok, found my problems.
Believe it or not, my ISP gave me a static-IP, yep, but only IPv4 not IPv6.
So every reboot of the router gives me a new IPv6 range….pfffff….no wonder I have so much problems.
1 Like