88 | | None of the above solutions work in my case. The most important fact that hasn't been mentioned here at all: Stuck beacons have hardly any influence on IPv4 traffic, but as far as IPv6 is concerned, they are a terrible nuisance. Each stuck beacon means that all router advertisement (and router solicitation) messages on the interface are blocked either for a very long period of time (usually more than one hour), or permanently. However, no errors are reported by radvd. For the IPv6-only LAN I am running, this is a total disaster. Presumably, tricks with background scans and antennas did not help at all. |
---|
| 88 | None of the above solutions works in my case. The most important fact that hasn't been mentioned here at all: Stuck beacons have hardly any influence on IPv4 traffic, but as far as IPv6 is concerned, they are a terrible nuisance. Each stuck beacon means that all router advertisement (and router solicitation) messages on the interface are blocked either for a very long period of time (usually more than one hour), or permanently. However, no errors are reported by radvd. For the IPv6-only LAN I am running, this is a total disaster. Presumably, tricks with background scans and antennas did not help at all. |
---|