Shame, shame, shame on you!

Good catch! You may want to ask your ISP to make the IPv6 static as well.

Yeah already mailed him.

Maybe he’s not using IPv6 for clients to use static, I just tried to activate IPv6 and it worked.

Never figured it would be dynamic. Oh well, we will get there somehow.

I’m getting better and better at this…baby steps :smile:

1 Like

Yes I can and did, then yes, both work fine.

But I already found the issue, it’s my ISP that only made IPv4 static and IPv6 Dynamic….so I mailed Thomas to fix it for me.

Well fixed, got an /48 block from my ISP.

Ditched the DrayTek router, impossible to get it going.

Went back to the Zyxel DSL-modem + FritzBox 5690Pro, configured my servers static IPv6 with just this:

auto enp1s0f0
iface enp1s0f0 inet static
        address 192.168.1.50
        netmask 255.255.255.0
        gateway 192.168.1.1
        dns-nameservers 192.168.1.1 1.1.1.1 8.8.8.8

iface enp1s0f0 inet6 static
        address 2a07:3145:1000::50/48

And hoppa, IPv6 is working!!! Yes!!! Finally :heart_eyes:

I must say, AVM did a lot of work on IPv6, as it’s now very simple.

Don’t know why DrayTek is making it so hard to configure.

2 Likes

If your DrayTek supports sending a custom DUID, you will always get the same prefix, regardless if your ISP offers dynamic or static. Mine gives me dynamic IPv6, but since my DUID is always the same, I always get the same v6 prefix. So I do not have to contact my ISP to beg for a static prefix. That /56 prefix is then advertised into a /64 by my MikroTik router to all my clients and I can set a semi-static address that doesn’t change unless the prefix changes, but that won’t happen since the DUID is always the same.

1 Like

What Microtik are you using? As I’m thinking of getting one, don’t have fiber yet, but my Zyxel simulates it, by putting VDSL in Bridge. So when connected via PPPoE it dissapears in total.

The DrayTek is too hard on IPv6, you have to create objects that represent machines and ports, then select an online IPv6 IP and put it in the firewall. But also change default rules from allow to block and then it becomes more complex.

The person who build that GUI must have been on crack, it can do everything, but getting there is by far too complex.

The Fritzbox has issues with big UDP tables, so I may want to use MikroTek hardware.

As for a static block, Fastic happily changed it for me, just nocticed they didn’t set a PTR on it, oh well, that is for tomorrow. :grin:

I use an older MikroTik RB3011 router, with 10 1 Gbit/s ports and an SFP. RouterOS is very powerful and it comes with good defaults.

They don’t have that model anymore, so I ordered this one instead:

Seems plenty powerfull to handle large UDP lists.

1 Like

It’s a Marvell-based router! I’m a big fan of Marvell. My RB3011 is a Qualcomm one, which is also very good (Atheros chipset). Remember, eth1 port is your Internet port. The rest act as switch ports. That’s the default config of RouterOS

1 Like

Well I got it working in IPv4 and IPv6…that was some trip to learn this.
My god!

However, it’s well worth it. As my local network isn’t affected by massive UDP requests.

Finally! Now waiting for the monitors to show it on the manage page.

The Vlan stuff of the ISP (many use it in Belgium as you know) is a real issue as the first-time wizzard doesn’t let you set the Vlan in PPPoE.
Getting it via the Vlan filter…pfffff…long day, time for a beer.

2 Likes

Well done Bas! I knew you had it in you!

1 Like

Well, yesterday I wanted to ship it back…after more then 10 hours without any progress.
Starting to know how they do things.

Still some minor problems, like activating the NTP-server/client in it…did everything, it won’t do it’s work.

The NTP server i run on my router (chrony) requires setting specific IP ranges to allow access from those. Did you do that? For example include this in chrony.conf:
allow 0.0.0.0/0
allow ::/0

Also normally access from WAN is blocked, so if you want to check access from WAN you should include the IPv4 / IPv6 address for the chrony instance (localhost) and open port 123 in firewall.

I do not know, yet, what it’s running :rofl:

I’ve been informed that this has now been fixed.

4 Likes