Fresh install, working with wired connection to single ethernet connection.
The day I installed SuSE 13.2, wireless stopped working on my router.didn’t understand that, took me a week until I noticed my small switch going crazy with traffic across it. began monitoring with iftop, and using conky. machine sending constant stream of outbound packets to m-cast, ~180Kbs out, inbound was almost nil (6bps). unplugged nic, wireless began working again, and traffic on switch and router went to almost nil with other machines still plugged in
Plugged nic back in, traffic increased again, wireless dropped for all other devices on my network, back to ~180Kbs again. This is with nothing in the foreground on the system. opened yast, networking, changed from wikid to network manager, NOW down to 11-638bps with this browser and site running, and wireless connects with all devices again. What in wicked is causing this, how can I stop it, and if cannot stop it, how to get rid of wicked altogether as something about it is continuously communicating with igmp.mcast.net (per my iotop checks)
You can switch to NetworkManager in YaST, otherwise I see no way to “get rid of wicked”.
That said, I cannot really believe that wicked itself “is continuously communicating with igmp.mcast.net”…
But switching to NetworkManager should also rule out or confirm wicked as culprit.
Maybe try to find out with “netstat” which process is really causing the traffic.
Yes, igmp.mcast.net points to multicasts on the local LAN.
But what process is doing those multicasts?
Again, I very much doubt that wicked itself is sending out multicasts, and it’s actually the first time I even hear about such a problem…
A candidate would be avahi (zeroconf) I suppose.
Does it help if you stop/disable avahi-daemon.service and avahi-daemon.socket?
I have no idea whether Debian based distros use any nonsense or not.
But what do you mean now with “nonsense”?
If Wicked, then no, that’s (open)SUSE-specific, and specifically developed by SUSE to replace ifup.
Debian-based distributions do use avahi though, if that’s the culprit…
And as I already suggested, you could switch to NetworkManager to see whether wicked is actually involved or not.
Btw, I don’t see any problem like you describe here, neither with NetworkManager nor with wicked.
Alright, so now, I have destroyed the original DVD based installation, gone to the KDE live cd, installed. using NM instead of Wicked. no network saturation whatsoever. Went ahead and turned off avahi on your suggestion, although no network spikes were occurring on the new installation. Outbound network load ~1.5 Kib/s Unsure what was doing it, but the reinstallation has rid the system of whatever was running away with with outbound sending.
You wouldn’t have had to reinstall.
You can switch between Wicked and NetworkManager on the fly in YaST->Network Devices->Network Settings->Global Options.
