New answers tagged

0

I'm fairly certain that XenServer uses the weak host model, which explains the behavior you're seeing. You probably have two options: Configure the XenServer to use the strong host model, if possible. Assign a different ip address to the interface in question. For an explanation of the strong and weak host models, have a read here: ...


1

The neighbor cache in the Linux kernel isn't as simple. There are subtle differences between an neighbor cache entry actually falling out of the cache entirely or just being marked as stale/invalid. At some point between base_reachable_time/2 and 3* base_reachable_time/2, the entry will still be in the cache, but it will be marked with a state of STALE. ...


0

This is a really good question for networkengineering.stackexchange.com. But: I have resolved this exact bug in the past by enabling "Untagged Vlan" in the VLAN and IPv4 Addresses section under LAN. Also set the untagged and mgmt vlans to the default of ID 1. Yes, it sounds insane but it solved my problem with Cisco WAPs exhibiting the exact same ...



Top 50 recent answers are included