Quote from: pfry on <strong>Today</strong> at 09:36:42 PMDiddling the offloads may be helpful. I'd do one at a time, and test. EEE is garbage, but it usually results in link failures, which should be pretty obvious. Can't hurt to disable it, and see if it makes any difference. I would not fix speed and duplex unless autonegotiation fails to deliver proper speed and duplex.
Any other symptoms? What does the CPU widget (or better, top from a shell) indicate? How about various netstat displays ("Interfaces: Diagnostics: Netstat" or shell) - any bad counters incrementing?
Quote from: Mr.SmartEpants on <strong>Today</strong> at 07:46:25 PMIs there a recommended "start here" setup config to get Sonos speakers working from a separate vLAN? I have my "trusted" devices on 'LAN' interface and "untrusted" on 'IoT' interface (separate SSIDs). LAN IP range: 192.168.0.*, IoT IP range: 192.168.33.*
Here's my current config, but it doesn't work. My phone with the Sonos app is on LAN, Sonos speakers are on IoT. When I switch the phone to the IoT SSID then everything works.