IPv6 Roll Out

Hi there, so on the AX3 router there's no way to set a custom ipv6 dns server? I use nextdns to filter out ads but I noticed that may only be the case because it links to the ipv4 address? So far I haven't seen ads but is that because I'm being served ads on ipv4 and it's getting filtered out? I don't think I can disable ipv4 to test this (Also, I don't quite understand how it works)
 
GreenCardigan said:
Hi there, so on the AX3 router there's no way to set a custom ipv6 dns server? I use nextdns to filter out ads but I noticed that may only be the case because it links to the ipv4 address? So far I haven't seen ads but is that because I'm being served ads on ipv4 and it's getting filtered out? I don't think I can disable ipv4 to test this (Also, I don't quite understand how it works)
Click to expand...
Tinuva said:
Set the ipv4 server statically, it will serve both ipv4 and ipv6 address translation. Ie. Block ads on both v4 and v6.
Click to expand...

https://www.reddit.com/r/pihole/comments/pnzxf0

Mr Scratch said:
Happy chappy

CvxH7Ak.png
Click to expand...
 
I am having trouble setting up IPv6 on my TP-Link AX1800. I have to reboot the router several times to get assigned an address, and often this gets dropped within a few seconds. Pinging any IPv6 address from any device does not work, it only yields "Network is unreachable" codes. Any advice?
 

Attachments

  • Screenshot from 2023-11-05 17-16-50.png
    Screenshot from 2023-11-05 17-16-50.png
    77.7 KB · Views: 29
  • Screenshot from 2023-11-05 17-16-50.png
    Screenshot from 2023-11-05 17-16-50.png
    77.7 KB · Views: 28
  • Screenshot from 2023-11-05 17-23-41.png
    Screenshot from 2023-11-05 17-23-41.png
    75.5 KB · Views: 28
RichterRSA said:
I am having trouble setting up IPv6 on my TP-Link AX1800. I have to reboot the router several times to get assigned an address, and often this gets dropped within a few seconds. Pinging any IPv6 address from any device does not work, it only yields "Network is unreachable" codes. Any advice?
Click to expand...

With tplink you need to select get ip 6 non address.
 
Hey all, I have been trying to get IPv6 going on my Mikrotik, but I have not had much luck.
Hoping someone can shine some light on the process.
Im on Openserve and I see an IPV6 address is assigned to the PPPOE connection.
It appears to be a local link address (FE80) which is not routable from what I have read.
I was under the impressions that I needed to setup a DHCPv6 Client to receive a prefix which is used to assign IPV6 addresses to the rest of the network.
I get no response when I do so.
Anyone have a working MT config that I could reference?
 
Vaporized said:
Hey all, I have been trying to get IPv6 going on my Mikrotik, but I have not had much luck.
Hoping someone can shine some light on the process.
Im on Openserve and I see an IPV6 address is assigned to the PPPOE connection.
It appears to be a local link address (FE80) which is not routable from what I have read.
I was under the impressions that I needed to setup a DHCPv6 Client to receive a prefix which is used to assign IPV6 addresses to the rest of the network.
I get no response when I do so.
Anyone have a working MT config that I could reference?
Click to expand...

I've had IPv6 working on my Mikrotik router on Afrihost/Openserve fibre line for a while now. Here's my tips:

1) Make sure IPv6 is enabled - In Winbox go to IPv6 -> Settings. Make sure "Disable IPv6" is unchecked. "IPv6 Forward" should be checked. Accept Redirects -> yes if forwarding disabled, Accept Router Advertisements -> yes if forwarding disabled

2) Restart your Mikrotik if IPv6 was previously disabled and you've just reenabled it in 1 above. For some reason a restart is sometimes required if IPv6 is reenabled

3) Go to IPv6 -> DHCP Client. Delete any previously configured clients. Add a new DHCPv6 client with the following settings:

Interface: Select the PPPOE interface that you're using to connect to Afrihost
Request: info - unchecked, address - unchecked, prefix - checked
Pool Name: AfrihostIPv6Pool (or whatever you want to call it)
Pool Prefix Length: 64
Prefix Hint: "::/60" (without the quotes)
Use Peer DNS - I prefer unchecked but you may want to check this
Use Interface DUID - unchecked
Rapid Commit - unchecked
Add Default Route - checked

Click Ok and the client should then connect and get a prefix starting with "2c0f".

Now you have to tell Mikrotik to use the pool to assign addresses to your network. In Winbox go to IPv6 -> Addresses. Click on the plus button to add a new address. In the new address form fill in the following:

Address - ::/64
From Pool - Select the pool you created above - AfrihostIPv6Pool
Interface - select the interface that your internal LAN runs on
EUI64 - unchecked
Advertise - checked
No DAD - unchecked

Click add and the LAN interface of your interface on Mikrotik will now be allocated a subprefix and will start advertising addresses to clients.

Repeat the above if you have other interfaces like for IOT, cameras, etc.
 
deweyzeph said:
I've had IPv6 working on my Mikrotik router on Afrihost/Openserve fibre line for a while now. Here's my tips:

1) Make sure IPv6 is enabled - In Winbox go to IPv6 -> Settings. Make sure "Disable IPv6" is unchecked. "IPv6 Forward" should be checked. Accept Redirects -> yes if forwarding disabled, Accept Router Advertisements -> yes if forwarding disabled

2) Restart your Mikrotik if IPv6 was previously disabled and you've just reenabled it in 1 above. For some reason a restart is sometimes required if IPv6 is reenabled

3) Go to IPv6 -> DHCP Client. Delete any previously configured clients. Add a new DHCPv6 client with the following settings:

Interface: Select the PPPOE interface that you're using to connect to Afrihost
Request: info - unchecked, address - unchecked, prefix - checked
Pool Name: AfrihostIPv6Pool (or whatever you want to call it)
Pool Prefix Length: 64
Prefix Hint: "::/60" (without the quotes)
Use Peer DNS - I prefer unchecked but you may want to check this
Use Interface DUID - unchecked
Rapid Commit - unchecked
Add Default Route - checked

Click Ok and the client should then connect and get a prefix starting with "2c0f".

Now you have to tell Mikrotik to use the pool to assign addresses to your network. In Winbox go to IPv6 -> Addresses. Click on the plus button to add a new address. In the new address form fill in the following:

Address - ::/64
From Pool - Select the pool you created above - AfrihostIPv6Pool
Interface - select the interface that your internal LAN runs on
EUI64 - unchecked
Advertise - checked
No DAD - unchecked

Click add and the LAN interface of your interface on Mikrotik will now be allocated a subprefix and will start advertising addresses to clients.

Repeat the above if you have other interfaces like for IOT, cameras, etc.
Click to expand...

Thanks!

That helped alot.
I found the reason I was not getting a response on my DHCPv6 client was because I had non standard filter rules.

add action=drop chain=forward connection-state=invalid
add action=accept chain=forward connection-state=established,related,untracked
add action=accept chain=forward connection-state=new in-interface=Lan_Bridge
add action=drop chain=forward log=yes log-prefix=IPV6_
add action=drop chain=input connection-state=invalid
add action=accept chain=input dst-port=546 protocol=udp src-address=fe80::/10 <--- It appears I was missing this.
add action=accept chain=input connection-state=established,related,untracked
add action=accept chain=input connection-state=new in-interface=Lan_Bridge
add action=drop chain=input log=yes log-prefix=IPV6_

Works like a charm now!
 
Vaporized said:
Thanks!

That helped alot.
I found the reason I was not getting a response on my DHCPv6 client was because I had non standard filter rules.

add action=drop chain=forward connection-state=invalid
add action=accept chain=forward connection-state=established,related,untracked
add action=accept chain=forward connection-state=new in-interface=Lan_Bridge
add action=drop chain=forward log=yes log-prefix=IPV6_
add action=drop chain=input connection-state=invalid
add action=accept chain=input dst-port=546 protocol=udp src-address=fe80::/10 <--- It appears I was missing this.
add action=accept chain=input connection-state=established,related,untracked
add action=accept chain=input connection-state=new in-interface=Lan_Bridge
add action=drop chain=input log=yes log-prefix=IPV6_

Works like a charm now!
Click to expand...

Awesome, yeah those default ipv6 firewall rules are generated by default when you reset the Mikrotik. It's a very different beast to IPv4.
 
deweyzeph said:
I've had IPv6 working on my Mikrotik router on Afrihost/Openserve fibre line for a while now. Here's my tips:

1) Make sure IPv6 is enabled - In Winbox go to IPv6 -> Settings. Make sure "Disable IPv6" is unchecked. "IPv6 Forward" should be checked. Accept Redirects -> yes if forwarding disabled, Accept Router Advertisements -> yes if forwarding disabled

2) Restart your Mikrotik if IPv6 was previously disabled and you've just reenabled it in 1 above. For some reason a restart is sometimes required if IPv6 is reenabled

3) Go to IPv6 -> DHCP Client. Delete any previously configured clients. Add a new DHCPv6 client with the following settings:

Interface: Select the PPPOE interface that you're using to connect to Afrihost
Request: info - unchecked, address - unchecked, prefix - checked
Pool Name: AfrihostIPv6Pool (or whatever you want to call it)
Pool Prefix Length: 64
Prefix Hint: "::/60" (without the quotes)
Use Peer DNS - I prefer unchecked but you may want to check this
Use Interface DUID - unchecked
Rapid Commit - unchecked
Add Default Route - checked

Click Ok and the client should then connect and get a prefix starting with "2c0f".

Now you have to tell Mikrotik to use the pool to assign addresses to your network. In Winbox go to IPv6 -> Addresses. Click on the plus button to add a new address. In the new address form fill in the following:

Address - ::/64
From Pool - Select the pool you created above - AfrihostIPv6Pool
Interface - select the interface that your internal LAN runs on
EUI64 - unchecked
Advertise - checked
No DAD - unchecked

Click add and the LAN interface of your interface on Mikrotik will now be allocated a subprefix and will start advertising addresses to clients.

Repeat the above if you have other interfaces like for IOT, cameras, etc.
Click to expand...

Thanks!

That helped alot.
I found the reason I was not getting a response on my DHCPv6 client was because I had non standard filter rules.
add action=drop chain=forward connection-state=invalid
add action=accept chain=forward connection-state=established,related,untracked
add action=accept chain=forward connection-state=new in-interface=Lan_Bridge
add action=drop chain=forward log=yes log-prefix=IPV6_
add action=drop chain=input connection-state=invalid
add action=accept chain=input dst-port=546 protocol=udp src-address=fe80::/10 <--- It appears I was missing this.
add action=accept chain=input connection-state=established,related,untracked
add action=accept chain=input connection-state=new in-interface=Lan_Bridge
add action=drop chain=input log=yes log-prefix=IPV6_

Works like a charm now!
deweyzeph said:
Awesome, yeah those default ipv6 firewall rules are generated by default when you reset the Mikrotik. It's a very different beast to IPv4.
Click to expand...

It really is!
Now I have to play around with subnetting it to the various networks I have or whatever the equivalent is in IPV6.
 
w1tw0lf said:
Anyone else ipv6 stopped working last night ? Nothing changed on my side, excepted that my public ipv4 changed for the first time as well. @Afrigirl @AfriNatic
Click to expand...

I have requested IPv6 to be enabled again. We don't currently have the ability to enable IPv6 on the portal for Vumatel clients. Ipv6 is added by Vxnext in the back end.
 
blunt said:
@Vaporized @deweyzeph how are you configuring IPv6 dns, just via the usual IP -> DNS as v6's in the list of resolvers?
Click to expand...

There's no need to configure IPv6 DNS, it will use whatever DNS server you have configured for IPv4 via the IPv4 DHCP server on your Mikrotik. In my case I have a PiHole server running on my local lan on a private 192.168.x.x address and it works fine for both IPv4 and IPv6.
 
Leno said:
I have ipv6 on Opeserve with Websquad, not sure whats not supported

Edit: I think the "newer" ISP's have a slightly different implementation on Openserve (a guess from my side)
Click to expand...
AfriNatic said:
Tunneling IPv6 over IPv4 is possible and that is likely what other ISPs are doing. We are not looking at that implementation just yet.

I'm also exploring option to best go about bug reporting. Setting up a ticket queue for ipv6 queries can work but we want clients to ideally see what bugs are there and see what solutions can be found.

I was thinking about https://flarum.org

I do like the layout. Very modern and allows us to keep track of all the issues add tags to them that is clearly visible and move them to solved category once resolved.

Any suggestions what platform would be ideal for you guys to go about discussing and reporting issues?
Click to expand...
Not to hijack this thread. Our v6 over Openserve is native and isn't tunnelled (over both OBC and LNS networks). It's a dual stack implementation too. We just tunnel over Vuma trenched for the time being. Will drop you a PM :)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X