OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • English Forums »
  • General Discussion »
  • Latency issues
« previous next »
  • Print
Pages: [1]

Author Topic: Latency issues  (Read 1289 times)

halcyon

  • Newbie
  • *
  • Posts: 7
  • Karma: 0
    • View Profile
Latency issues
« on: November 23, 2019, 02:36:30 am »
Cable Modem --> IGB0(WAN) --> IGB1 (Vlan10/20 Trunk) --> 3750 Trunk Port 52 -->everything on network

I am having a very strange issue.

When I attach my main desktop to the network, I get flapping on vlan 10. If I attach my Surface to the same link (Gig 1/0/8) it flaps on vlan 10.
If I move to Gig 1/0/9, either computer, it flaps on vlan 10.

953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8
*Mar  3 01:51:32.793: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8
*Mar  3 01:51:47.742: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/8 and port Gi1/0/52
*Mar  3 01:52:03.109: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8
*Mar  3 01:52:17.966: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8
*Mar  3 01:52:33.476: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8
*Mar  3 01:52:49.784: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8
*Mar  3 01:53:10.294: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8
*Mar  3 01:53:18.271: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8
*Mar  3 01:53:34.780: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8
*Mar  3 01:53:51.775: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8
*Mar  3 01:54:02.865: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8
*Mar  3 01:54:19.609: %SW_MATM-4-MACFLAP_NOTIF: Host 14da.e913.953c in vlan 10 is flapping between port Gi1/0/52 and port Gi1/0/8

Now where it gets funny, if I unlink the OPNSense router from the cisco switch, the flapping stops completely.

I'm not sure if I have a cisco issue or an OPNSense issue.

Additionally, I am tearing my hair out trying to figure out wtf is causing this. I have tried everything I could find, engaging bpduguard, disengaging, going for rapid pvst, standard, portfast, and so forth. Nothing is changing how this is flapping.


eply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64
Reply from 172.20.10.254: bytes=32 time<1ms TTL=64

Its maddening. I'm not sure if its because of the opnsense, or if there's something that is wrong with the switch, but this issue did not exist while we were using the 5520ASA as a router.

Help please? :(
« Last Edit: November 23, 2019, 04:40:02 am by halcyon »
Logged

halcyon

  • Newbie
  • *
  • Posts: 7
  • Karma: 0
    • View Profile
Re: Latency issues
« Reply #1 on: November 23, 2019, 04:41:16 am »
So, after an exhausting review of the network infrastructure, I located the problem. One particular punch down (going to this particular computer) was broken. Tying into a completely different drop and running a 100ft cable fixed the problem (apparently).

*sigh*
Logged
  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • English Forums »
  • General Discussion »
  • Latency issues
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy     | XHTML | RSS | WAP2