Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 40 subscribers
  • Views 1781 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

XG v18 HA - Availability peer address from primary unit

Jaroslav Faldik

Hello everybody,

Can I access the auxiliary unit over the primary unit?

I have an XG v18 HA Active-Passive mode. Both of IPs for primary and auxiliary unit are avaliable from another device in a administration subnet. But from the primary unit cannot ping to the auxiliary unit and the primary unit does not contain a valid ARP record for the auxiliary unit.

The primary unit has an address 172.16.16.16, the auxiliary unit 172.16.16.17 and Mikrotik 172.16.16.100.

Here are ARP logs from the units:

Primary unit:
XG310_WP02_SFOS 18.0.0 GA-Build339# ping -c 10 172.16.16.17                     
PING 172.16.16.17 (172.16.16.17): 56 data bytes                                 
                                                                                
--- 172.16.16.17 ping statistics ---                                            
10 packets transmitted, 0 packets received, 100% packet loss                    
XG310_WP02_SFOS 18.0.0 GA-Build339# arp -i Port3                                
? (172.16.16.100) at 00:0c:42:c0:66:c1 [ether]  on Port3                        
? (172.16.16.17) at   on Port3                                      
XG310_WP02_SFOS 18.0.0 GA-Build339


Auxiliary unit:
XG310_WP02_SFOS 18.0.0 GA-Build339# ping -c 10 172.16.16.16                     
PING 172.16.16.16 (172.16.16.16): 56 data bytes                                 
64 bytes from 172.16.16.16: seq=0 ttl=64 time=0.043 ms                          
64 bytes from 172.16.16.16: seq=1 ttl=64 time=0.066 ms                          
64 bytes from 172.16.16.16: seq=2 ttl=64 time=0.033 ms                          
64 bytes from 172.16.16.16: seq=3 ttl=64 time=0.040 ms                          
64 bytes from 172.16.16.16: seq=4 ttl=64 time=0.034 ms                          
64 bytes from 172.16.16.16: seq=5 ttl=64 time=0.079 ms                          
64 bytes from 172.16.16.16: seq=6 ttl=64 time=0.020 ms                          
64 bytes from 172.16.16.16: seq=7 ttl=64 time=0.077 ms                          
64 bytes from 172.16.16.16: seq=8 ttl=64 time=0.075 ms                          
64 bytes from 172.16.16.16: seq=9 ttl=64 time=0.075 ms                          
                                                                                
--- 172.16.16.16 ping statistics ---                                            
10 packets transmitted, 10 packets received, 0% packet loss                     
round-trip min/avg/max = 0.020/0.054/0.079 ms                                   
XG310_WP02_SFOS 18.0.0 GA-Build339# arp -i Port3                                
? (172.16.16.100) at 00:0c:42:c0:66:c1 [ether]  on Port3                        
XG310_WP02_SFOS 18.0.0 GA-Build339#

I have temporary solution for acces to the auxiliary unit using Mikrotik DNAT+SNAT (masquerade). Direct access from the primary unit port cannot be accessed.

It is a HA mode property in a V18 or a bug?



This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hi Jaroslav Faldik,

    If you have ICMP allowed within a zone, it should work. I would suggest you to check if ICMP is blocked by internal switch.

    If possible please PM me the HA configuration screenshots and network details.

    Thanks,

  • 0 in reply to FormerMember

    The HA Slave will use his "physical" MAC address for his administration IP. Master will use the shared virtual MAC (VMAC). 

    There was an issue, that the Master appliance could not work with the MAC Address of the Slave, but i assumed, it got fixed in at least in V18. Not Sure about that.

    What do you want to archive? I would recommend to work with the direct link (HA Port). 

    You can ping and access the slave appliance over this link directly (SSH / Ping). Therefore you do not have to use the switch. 

     

    I would recommend to troubleshoot this: Login via ssh admin@HAIPofSlave   Use the admin password. 

    Dump on the Slave on the Port you try to ping (tcpdump -ni PortX arp) Check if you see the ARP requests and if the XG is responding correctly. 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    Thanks for answer.

    According to tcpdump the slave does not respond to arp master requests. But responds correctly to Mikrotik requirements. Maybe it is an intention and not a mistake...

    Master (Primary) unit:

    XG310_WP02_SFOS 18.0.0 GA-Build339# tcpdump -ni Port3 arp
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on Port3, link-type EN10MB (Ethernet), capture size 262144 bytes
    20:49:25.233720 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:26.241009 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:27.265010 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:29.233821 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:30.241006 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:31.269012 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:33.233975 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:34.240999 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:35.265011 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:37.234120 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:38.241008 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:39.264999 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:41.234340 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:42.244998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:43.269005 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:45.234438 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:46.245008 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:47.265010 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:49.234568 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:50.244998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:51.269004 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:53.234743 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:54.240998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:55.265008 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:57.234838 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:58.241010 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:59.265005 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:01.234969 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:02.244998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:03.148944 Port3, IN: ARP, Request who-has 172.16.16.16 tell 172.16.16.100, length 46
    20:50:03.148971 Port3, OUT: ARP, Reply 172.16.16.16 is-at c8:4f:86:fc:00:06, length 28
    20:50:03.269009 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:05.235138 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:06.245013 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:07.265116 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:07.981448 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.100, length 46
    20:50:08.352999 Port3, OUT: ARP, Request who-has 172.16.16.100 tell 172.16.16.16, length 28
    20:50:08.353060 Port3, IN: ARP, Reply 172.16.16.100 is-at 00:0c:42:c0:66:c1, length 46
    20:50:09.235276 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:10.244998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:11.264998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:13.235414 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    ^C
    42 packets captured
    42 packets received by filter
    0 packets dropped by kernel
    1 packet dropped by interface
    XG310_WP02_SFOS 18.0.0 GA-Build339#

    Slave (Auxiliary) unit:

    XG310_WP02_SFOS 18.0.0 GA-Build339# tcpdump -ni Port3 arp
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on Port3, link-type EN10MB (Ethernet), capture size 262144 bytes
    20:49:25.036736 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:26.044039 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:27.068037 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:29.036854 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:30.044050 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:31.072054 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:33.037029 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:34.044052 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:35.068073 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:37.037180 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:38.044082 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:39.068071 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:41.037422 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:42.048082 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:43.072089 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:45.037535 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:46.048107 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:47.068118 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:49.037687 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:50.048112 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:51.072119 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:53.037887 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:54.044128 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:55.068146 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:57.037976 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:58.044163 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:59.068156 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:01.038128 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:02.048160 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:02.952095 Port3, IN: ARP, Request who-has 172.16.16.16 tell 172.16.16.100, length 46
    20:50:03.072176 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:05.038306 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:06.048191 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:07.068292 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:07.784616 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.100, length 46
    20:50:07.784655 Port3, OUT: ARP, Reply 172.16.16.17 is-at c8:4f:86:05:47:ea, length 28
    20:50:09.038471 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:10.048191 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:11.068189 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:13.038621 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:14.044208 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:15.068249 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    ^C
    42 packets captured
    42 packets received by filter
    0 packets dropped by kernel
    XG310_WP02_SFOS 18.0.0 GA-Build339#

Reply
  • 0 in reply to LuCar Toni

    Thanks for answer.

    According to tcpdump the slave does not respond to arp master requests. But responds correctly to Mikrotik requirements. Maybe it is an intention and not a mistake...

    Master (Primary) unit:

    XG310_WP02_SFOS 18.0.0 GA-Build339# tcpdump -ni Port3 arp
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on Port3, link-type EN10MB (Ethernet), capture size 262144 bytes
    20:49:25.233720 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:26.241009 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:27.265010 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:29.233821 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:30.241006 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:31.269012 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:33.233975 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:34.240999 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:35.265011 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:37.234120 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:38.241008 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:39.264999 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:41.234340 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:42.244998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:43.269005 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:45.234438 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:46.245008 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:47.265010 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:49.234568 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:50.244998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:51.269004 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:53.234743 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:54.240998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:55.265008 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:57.234838 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:58.241010 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:49:59.265005 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:01.234969 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:02.244998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:03.148944 Port3, IN: ARP, Request who-has 172.16.16.16 tell 172.16.16.100, length 46
    20:50:03.148971 Port3, OUT: ARP, Reply 172.16.16.16 is-at c8:4f:86:fc:00:06, length 28
    20:50:03.269009 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:05.235138 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:06.245013 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:07.265116 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:07.981448 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.100, length 46
    20:50:08.352999 Port3, OUT: ARP, Request who-has 172.16.16.100 tell 172.16.16.16, length 28
    20:50:08.353060 Port3, IN: ARP, Reply 172.16.16.100 is-at 00:0c:42:c0:66:c1, length 46
    20:50:09.235276 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:10.244998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:11.264998 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    20:50:13.235414 Port3, OUT: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 28
    ^C
    42 packets captured
    42 packets received by filter
    0 packets dropped by kernel
    1 packet dropped by interface
    XG310_WP02_SFOS 18.0.0 GA-Build339#

    Slave (Auxiliary) unit:

    XG310_WP02_SFOS 18.0.0 GA-Build339# tcpdump -ni Port3 arp
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on Port3, link-type EN10MB (Ethernet), capture size 262144 bytes
    20:49:25.036736 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:26.044039 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:27.068037 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:29.036854 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:30.044050 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:31.072054 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:33.037029 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:34.044052 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:35.068073 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:37.037180 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:38.044082 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:39.068071 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:41.037422 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:42.048082 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:43.072089 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:45.037535 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:46.048107 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:47.068118 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:49.037687 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:50.048112 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:51.072119 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:53.037887 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:54.044128 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:55.068146 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:57.037976 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:58.044163 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:49:59.068156 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:01.038128 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:02.048160 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:02.952095 Port3, IN: ARP, Request who-has 172.16.16.16 tell 172.16.16.100, length 46
    20:50:03.072176 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:05.038306 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:06.048191 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:07.068292 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:07.784616 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.100, length 46
    20:50:07.784655 Port3, OUT: ARP, Reply 172.16.16.17 is-at c8:4f:86:05:47:ea, length 28
    20:50:09.038471 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:10.048191 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:11.068189 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:13.038621 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:14.044208 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    20:50:15.068249 Port3, IN: ARP, Request who-has 172.16.16.17 tell 172.16.16.16, length 46
    ^C
    42 packets captured
    42 packets received by filter
    0 packets dropped by kernel
    XG310_WP02_SFOS 18.0.0 GA-Build339#

Children
No Data
Unfiltered HTML