I have a test network with a couple of routerboards (ROS 5.6). I am running just ipv6 on these routers no ipv4. When I try to set all the interfaces to arp=disabled all ipv6 local connections on the lan fail. I can't ping, winbox to the ipv6 ip. When I mac winbox into a device I see in the ipv6 neighbor list the other ipv6 addresses say status "incomplete" then "failed".
Is arp required on 5.x for ipv6 to work? From what I have read ipv6 doesn't need arp because it uses icmp6 to do neighbor discovery. I'm still looking at wireshark packet captures and it looks like the devices are exchanging icmp6.
Has anyone else run into this? Any suggestions?
Re: Disable ARP on interface and ipv6 stops working
ARP is an IPv4 protocol, and is unnecessary for IPv6. I don't see how even a bug would make it possible for IPv6 to rely on ARP. IPv6 and IPv4 are like ships in the night, they don't know about each other at all.
I've tried disabling ARP and I can't reproduce your problem between an RB750G and an RB433, both running 5.6. Here the devices:
I've turned off ARP on all the RB433 ethernet interfaces, as well as the RB750G interface that serves as the RB433 uplink:
Here's an IPv6 address on a loopback on the 433:
I can ping that from the RB750G, as well as from a laptop behind a different port on the RB750G:
Granted, I didn't turn off ARP on ALL interfaces on the RB750G, but it's off on the RB433 completely (and IPv4 did stop working) as well as its uplink on the other side.
I did get interface flaps when changing ARP modes on the interfaces, it looks like the router tears down the interface on a PHY level, changes the setting, and then brings it back up. The logs show the interface going down and then back up, and the routing protocols between the two routes converging again. Is it possible that when you changed ARP modes for some reason the interfaces just stayed down on PHY and never came back up? Do you have console access to both routers to check interface status?
I've tried disabling ARP and I can't reproduce your problem between an RB750G and an RB433, both running 5.6. Here the devices:
Code: Select all
[felix@rb433] > /system resource print
uptime: 19h5s
version: 5.6
free-memory: 49908KiB
total-memory: 62196KiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 300MHz
cpu-load: 1%
free-hdd-space: 29468KiB
total-hdd-space: 61440KiB
write-sect-since-reboot: 158
write-sect-total: 398070
bad-blocks: 0%
architecture-name: mipsbe
board-name: RB433
platform: MikroTik
[felix@rb750g] > /system resource print
uptime: 19h38s
version: 5.6
free-memory: 16588KiB
total-memory: 29708KiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 680MHz
cpu-load: 2%
free-hdd-space: 32072KiB
total-hdd-space: 61440KiB
write-sect-since-reboot: 1202
write-sect-total: 2224448
bad-blocks: 0%
architecture-name: mipsbe
board-name: RB750G
platform: MikroTikCode: Select all
[felix@rb433] > /interface ethernet print
Flags: X - disabled, R - running, S - slave
# NAME MTU MAC-ADDRESS ARP MASTER-PORT SWITCH
0 R 750 1500 00:0C:42:77:95:97 disabled
1 ether2 1500 00:0C:42:77:95:98 disabled none switch1
2 ether3 1500 00:0C:42:77:95:99 disabled none switch1
[felix@rb750g] > /interface ethernet print where name=433
Flags: X - disabled, R - running, S - slave
# NAME MTU MAC-ADDRESS ARP MASTER-PORT SWITCH
2 R 433 1500 00:0C:42:70:12:9A disabled none switch1 Code: Select all
[felix@rb433] > /ipv6 address print where interface=loopback0
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local
# ADDRESS INTERFACE ADVERTISE
0 G fd8a:ed9a:41f5:ffff::2/128 loopback0 no Code: Select all
[felix@rb750g] > /ping fd8a:ed9a:41f5:ffff::2 count=4
HOST SIZE TTL TIME STATUS
fd8a:ed9a:41f5:ffff::2 56 64 0ms echo reply
fd8a:ed9a:41f5:ffff::2 56 64 0ms echo reply
fd8a:ed9a:41f5:ffff::2 56 64 0ms echo reply
fd8a:ed9a:41f5:ffff::2 56 64 0ms echo reply
sent=4 received=4 packet-loss=0% min-rtt=0ms avg-rtt=0ms max-rtt=0ms
HOST SIZE TTL TIME STATUS
$ ping6 -c 4 fd8a:ed9a:41f5:ffff::2
PING6(56=40+8+8 bytes) 2001:1938:2d2:1:b103:fc48:e2ae:c503 --> fd8a:ed9a:41f5:ffff::2
16 bytes from fd8a:ed9a:41f5:ffff::2, icmp_seq=0 hlim=63 time=1.643 ms
16 bytes from fd8a:ed9a:41f5:ffff::2, icmp_seq=1 hlim=63 time=1.686 ms
16 bytes from fd8a:ed9a:41f5:ffff::2, icmp_seq=2 hlim=63 time=1.735 ms
16 bytes from fd8a:ed9a:41f5:ffff::2, icmp_seq=3 hlim=63 time=1.765 ms
--- fd8a:ed9a:41f5:ffff::2 ping6 statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.643/1.707/1.765/0.047 msI did get interface flaps when changing ARP modes on the interfaces, it looks like the router tears down the interface on a PHY level, changes the setting, and then brings it back up. The logs show the interface going down and then back up, and the routing protocols between the two routes converging again. Is it possible that when you changed ARP modes for some reason the interfaces just stayed down on PHY and never came back up? Do you have console access to both routers to check interface status?
-
-
jacobalberty
just joined
- Posts: 8
- Joined:
Re: Disable ARP on interface and ipv6 stops working
fewi I'm having a similar problem but instead of disabling arp i put the interface's arp into reply-only and it does the same thing as slackR. My ipv6 works for a while then suddenly stops working, I think as long as i'm pinging something via ipv6 to keep the neighbors fresh it'll continue working then when the neighbors go stale it becomes an incomplete neighbor. If you have a windows based machine to test with try disabling arp (or set it to reply only) on the router and do this from an administrator command line. "netsh int ipv6 delete neighbor" then try and see what happens. Or just give it a few minutes with no activity on the machine for the neighbors to be lost.
-
-
jacobalberty
just joined
- Posts: 8
- Joined:
Re: Disable ARP on interface and ipv6 stops working
fewi I'm having a similar problem but instead of disabling arp i put the interface's arp into reply-only and it does the same thing as slackR. My ipv6 works for a while then suddenly stops working, I think as long as i'm pinging something via ipv6 to keep the neighbors fresh it'll continue working then when the neighbors go stale it becomes an incomplete neighbor. If you have a windows based machine to test with try disabling arp (or set it to reply only) on the router and do this from an administrator command line. "netsh int ipv6 delete neighbor" then try and see what happens. Or just give it a few minutes with no activity on the machine for the neighbors to be lost.
-
-
jacobalberty
just joined
- Posts: 8
- Joined:
Re: Disable ARP on interface and ipv6 stops working
fewi I'm having a similar problem but instead of disabling arp i put the interface's arp into reply-only and it does the same thing as slackR. My ipv6 works for a while then suddenly stops working, I think as long as i'm pinging something via ipv6 to keep the neighbors fresh it'll continue working then when the neighbors go stale it becomes an incomplete neighbor. If you have a windows based machine to test with try disabling arp (or set it to reply only) on the router and do this from an administrator command line. "netsh int ipv6 delete neighbor" then try and see what happens. Or just give it a few minutes with no activity on the machine for the neighbors to be lost.
Re: Disable ARP on interface and ipv6 stops working
I have did some more testing and came up with the same results. If I set ARP to anything other than enabled the ipv6 connectivity drops. I even reloaded two of the devices with netinstall and tried again with a minimal config. The only thing I haven't tried is adding a loopback bridge interface like you show in your setup. I did notice the interface flaps when you change the ARP. I did check the interface stats, disabled then enabled. Even rebooted each routerboard with the same results.
I do have console/serial access to all the routerboards. I also built some supout files before and after I have changed ARP on the interfaces and sent them to support.
I do have console/serial access to all the routerboards. I also built some supout files before and after I have changed ARP on the interfaces and sent them to support.
Code: Select all
[slackr@450G] > /system resource print
uptime: 4h54s
version: 5.6
free-memory: 238924KiB
total-memory: 257120KiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 680MHz
cpu-load: 1%
free-hdd-space: 485388KiB
total-hdd-space: 520192KiB
write-sect-since-reboot: 1895
write-sect-total: 1895
bad-blocks: 0.1%
architecture-name: mipsbe
board-name: RB450G
platform: MikroTik
Code: Select all
[slackr@AP-433] > /system resource print
uptime: 7h50m19s
version: 5.6
free-memory: 50180KiB
total-memory: 62196KiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 300MHz
cpu-load: 2%
free-hdd-space: 35972KiB
total-hdd-space: 61440KiB
write-sect-since-reboot: 5185
write-sect-total: 2108199
bad-blocks: 0%
architecture-name: mipsbe
board-name: RB433
platform: MikroTik
Code: Select all
[slackr@450G] /ipv6 neighbor> print detail where status="failed"
Flags: R - router
9 address=2001:470:b0ab::9 interface=ether2 status="failed"
10 address=2001:470:b0ab::8 interface=ether2 status="failed"
Code: Select all
[slackr@AP-433] /ipv6 neighbor> pr
Flags: R - router
0 address=2001:470:b0ab::9 interface=ether1 status="incomplete"
..
Code: Select all
[slackr@AP-433] /ipv6> /ping 2001:470:b0ab::9
HOST SIZE TTL TIME STATUS
2001:470:b0ab::9 timeout
2001:470:b0ab::8 104 64 638ms address unreachable
2001:470:b0ab::9 timeout
2001:470:b0ab::9 timeout
2001:470:b0ab::9 timeout
sent=5 received=0 packet-loss=100%
Re: Disable ARP on interface and ipv6 stops working
I concur. I have verified on both 5.8 & 5.9
I have a:
Windows 7 -> Virtual Wifi -> Bridge -> physical port -> linux box
Soon as ARP is disabled on the bridge port ... all pings drop. If disabled on the virtual wifi port and the physical port ... all seems to continue to operate correctly. The bridge needs ARP for some reason.
The network is IPv6 Only ... no IPv4 addresses.
I have a:
Windows 7 -> Virtual Wifi -> Bridge -> physical port -> linux box
Soon as ARP is disabled on the bridge port ... all pings drop. If disabled on the virtual wifi port and the physical port ... all seems to continue to operate correctly. The bridge needs ARP for some reason.
The network is IPv6 Only ... no IPv4 addresses.
Re: Disable ARP on interface and ipv6 stops working
upgrade to 5.12 when released this problem is fixed, or write to support to get testing release.
Re: Disable ARP on interface and ipv6 stops working
Will be also this issue related to IPv6 ND and ARP mode on interface fixed, please?
http://forum.mikrotik.com/viewtopic.php?f=2&t=56374
Thank you
http://forum.mikrotik.com/viewtopic.php?f=2&t=56374
Thank you
Re: Disable ARP on interface and ipv6 stops working
as i understand it - yes, this is the same issue. IPv6 stopped working with arp=disabled
Re: Disable ARP on interface and ipv6 stops working
Mentioned topic was about that when I configure arp=reply-only, the IPv6 stateless autoconfiguration was not working to clients, also neighbour discovery was not working.
Is there any schedule when will be the final version of 5.12 relased, please?
Thank you
Is there any schedule when will be the final version of 5.12 relased, please?
Thank you
Re: Disable ARP on interface and ipv6 stops working
soon. ND did not work due to problem with ARP that caused IPV6 to not to work at all. Starting with ipv6 LL address in the router.
In the mean time you can get test release if you write request to support.
In the mean time you can get test release if you write request to support.
Re: Disable ARP on interface and ipv6 stops working
The first tests shows that the issue with interface ARP mode reply-only and IPv6 stateless autoconfiguration is solved, I'm looking forward for final release of 5.12 