when i added static arp, next-hop type became ucst on R4.
Removed static arp entry and monitored interface on R2 while R4 pinging. It seems like R2 is sending reply back.
root@R2# run monitor traffic interface ge-0/0/1 verbose output suppressed, use <detail> or <extensive> for full protocol decode Address resolution is ON. Use <no-resolve> to avoid any reverse lookup delay. Address resolution timeout is 4s. Listening on ge-0/0/1, capture size 96 bytes Reverse lookup for 224.0.0.5 failed (check DNS reachability). Other reverse lookup failures will not be reported. Use <no-resolve> to avoid reverse lookups on IP addresses. 10:19:27.446000 In IP 172.27.0.6 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:28.049920 Out IP truncated-ip - 20 bytes missing! 172.27.0.5 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:36.746038 In IP 172.27.0.6 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:38.009929 Out IP truncated-ip - 20 bytes missing! 172.27.0.5 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:41.306398 In arp who-has 172.27.0.5 tell 172.27.0.6 10:19:41.306422 Out arp reply 172.27.0.5 is-at 00:05:86:71:18:01 10:19:46.486545 In IP 172.27.0.6 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:46.679947 Out IP truncated-ip - 20 bytes missing! 172.27.0.5 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:54.155897 In IP 172.27.0.6 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:56.019957 Out IP truncated-ip - 20 bytes missing! 172.27.0.5 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:56.306439 In arp who-has 172.27.0.5 tell 172.27.0.6 10:19:56.306461 Out arp reply 172.27.0.5 is-at 00:05:86:71:18:01 ^C 12 packets received by filter 0 packets dropped by kernel
But, on R4 i can't see request coming in from R2
root@R4# run monitor traffic interface ge-0/0/0 verbose output suppressed, use <detail> or <extensive> for full protocol decode Address resolution is ON. Use <no-resolve> to avoid any reverse lookup delay. Address resolution timeout is 4s. Listening on ge-0/0/0, capture size 96 bytes Reverse lookup for 224.0.0.5 failed (check DNS reachability). Other reverse lookup failures will not be reported. Use <no-resolve> to avoid reverse lookups on IP addresses. 10:18:34.985199 Out IP truncated-ip - 20 bytes missing! 172.27.0.6 > 224.0.0.5: OSPFv2, Hello, length 60 10:18:35.141415 In IP 172.27.0.5 > 224.0.0.5: OSPFv2, Hello, length 60 10:18:42.865164 Out IP truncated-ip - 20 bytes missing! 172.27.0.6 > 224.0.0.5: OSPFv2, Hello, length 60 10:18:43.891872 In IP 172.27.0.5 > 224.0.0.5: OSPFv2, Hello, length 60 10:18:46.265122 Out arp who-has 172.27.0.5 tell 172.27.0.6 10:18:50.525114 Out IP truncated-ip - 20 bytes missing! 172.27.0.6 > 224.0.0.5: OSPFv2, Hello, length 60 10:18:52.265930 In IP 172.27.0.5 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:00.045122 Out IP truncated-ip - 20 bytes missing! 172.27.0.6 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:01.553796 In IP 172.27.0.5 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:03.065103 Out arp who-has 172.27.0.5 tell 172.27.0.6 10:19:09.542082 In IP 172.27.0.5 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:09.695157 Out IP truncated-ip - 20 bytes missing! 172.27.0.6 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:18.295119 Out IP truncated-ip - 20 bytes missing! 172.27.0.6 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:19.141162 In IP 172.27.0.5 > 224.0.0.5: OSPFv2, Hello, length 60 10:19:19.465110 Out arp who-has 172.27.0.5 tell 172.27.0.6 ^C 15 packets received by filter 0 packets dropped by kernel