3

I have an interesting problem. An ISP of ours started providing native IPv6 on their network. They provided us with a /56 prefix and a /126 linking segment (::1 being their endpoint and ::2 being ours). However, the ISP's DSLAM does not support Neighbor Discovery, so they asked us to provide our router's MAC address to manually enter in their neighbor table and provided us with theirs.

We are using Mikrotik's RouterOS 5.2 on our router and we have not been able to figure out how this can be done. For IPv4, it is simple, we can create a mapping under /ip arp, but for IPv6 the neighbor list (/ip neighbor) seems to be read-only.

We tried to work this around, by setting a fe80:: link-local address with the ISP's router's MAC address encoded in the EUI-64, but when we sent packets to that destination, RouterOS tried to resolve the address using ND nevertheless.

I am asking if there is a way to either create a static mapping IPv6 address -> MAC address or to create a route directly to a MAC address and the interface, so we can stop using tunnels for our IPv6 needs.

MDMarra
  • 100,183
  • 32
  • 195
  • 326

2 Answers2

0

The proper way to do this in Linux is via the "ip neigh..." command you mentioned. It is possible that the ipv6 subsystem has some of the functionality stripped from it to make the OS leaner, though I cannot comment as I haven't run RouterOS specifically.

Just as a sanity check, the user that is logged in has the ability to do other commands that would require root access, right?

Peter Grace
  • 3,446
  • 1
  • 26
  • 42
  • Thank you for you response! Actually, RouterOS seems to be using a heavily modified Linux kernel and access to a shell is not possible. I am also certain that tools such as `ip` are not included. The only way to interact with RouterOS is via its own command line interface with its own set of commands. I am **NOT** certain, but I think that it's even using a custom networking stack to make use of special hardware on RouterBOARD machines. –  Aug 19 '11 at 13:04
0

The Mikrotik support confirmed that this is impossible to do as of version 5.18. There are not really any workarounds, so we will have to wait for Mikrotik to implement this.