No worries, I’d engage with the ISP and see if they can help you get it resolved. I know it wouldn’t be the first time I’ve talked to an ISP and they’ve found an issue in their IGP or some other component. Some ISPs are learning right along with us.
Let us know how it goes.
In the meantime I’d encourage you to grab a tunnel from a tunnel broker like Hurricane Electric. This will give you IPv6 access and if necessary you can segment off onto a VLAN that is only used for testing / playing so it doesn’t mess up with any geographical blocking for streaming services and what not. While you have the tunnel you can get more comfortable with IPv6 and how it works.
When you just receive the prefix - all the traffic to that prefix will go to your device that acquired the prefix. This route ensures that while you have not assigned address from the prefix in your network it properly responds that network is unavailable (as per flags at the route, specifically U flag)
When you just receive the prefix - all the traffic to that prefix will go to your device that acquired the prefix. This route ensures that while you have not assigned address from the prefix in your network it properly responds that network is unavailable (as per flags at the route, specifically U flag)
hi, I understood that. I think my problem is because I receive from my ISP a /64 network and I cannot use the same prefix to my subnet and route that to Internet. I’m newbie in IPv6, but each day this is obviously to me or my comment is wrong?
ISPs who give only a single /64 network to their clients are a bit clueless, but it would work when you can
put that /64 on the LAN and use a local address on the link to the provider.
When they don’t allow that either, that basically means you can’t use a router.
Ask them to give you a /60 or more… I get a /48 from my provider.
When I first learned that my ISP (Comcast) offers native IPv6, I configured my router with it, and by default, Comcast only gives a single /64.
(I later learned that you can use prefix-hint to obtain a /60 but that’s another story)
With a single /64, it works just fine. You apply this /64 prefix to the LAN interface. The router does not need any public IPv6 address on the WAN interface at all.
When the router only has a single /64 public interface, it will use that interface’s address to interact with the world just fine. The WAN interface is more than happy operating with just a link-local interface, since its only function is forwarding packets to/from your LAN. In IPv6, devices only need public routable addresses if they communicate directly with the world.
I’ll go read your config now to see if anything jumps off the page at me…
I have added this to ether12 ::2 , set a route to the default gateway ::1 via ether 12. —> I can ping WWW no problem…
However, I have many Mikrotik Routers across my network. Many CCRs acting as PPPOE servers, using OSPF. Anyway… If i set the following on say VLAN Interface between the two routers (2b02:29a0:8004:3::8/64 & 2b02:29a0:8004:3::9/64) I can ping each other. But i cannot ping the outside world. Why can’t they ping the world! I have turned off the firewall to test!
I have also set some of the clients on the main router to obtain IPv6 via PPPOE, the clients routers grabs it no problem. Set up a basic DHCP Client and Server. But I cannot get their devices to route properly, but I can sometimes get the clients router to PING the outside world.
Could someone please advise me on what i’m doing wrong… FYI, I don’t have much confidence in my providers setup. As they told me they have only 3 customers with IPv6!!!
You should not set the /48 address on your local ethernet interface, but only a /64 out of it. (you could just change the /48 to /64).
Then, you can use the 65535 other subnets you got on other interfaces.
2b02:29a0:8004:1::/64 2b02:29a0:8004:2::/64 etc
Of course you need the routes in the route tables of all your own routers pointing the right way… on leaf nodes this can be only
a default route but at least on your central router you need routes for the /64s you assigned on the leaf nodes to point to the right place.