Bug 217015

Summary:	knetworkmanager ignoring 'restrict to interface' settings
Product:	[Unmaintained] Network Management	Reporter:	David Sutton <kantras>
Component:	knetworkmanager	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED FIXED
Severity:	normal	CC:	blueowl, lamarque
Priority:	NOR
Version First Reported In:	0.9
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description David Sutton 2009-12-02 04:24:55 UTC

Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    openSUSE RPMs

I've just installed OpenSUSE v11.2 via the KDE LiveCD on a Dell desktop with two network cards (onboard and an additional PCI card). Using KNetworkManager, I set up two static wired profiles, with A being restricted to eth0 and B restricted to eth1. Whenever knetworkmanager starts, it uses profile B for both eth0 and eth1. I can switch eth0 over to use A and it will use that profile. 

I've removed the profiles, rebooted and re-added the entries and it acted the same. I also confirmed that the restriction settings were correct.

Comment 1 Will Stephenson 2009-12-02 23:09:01 UTC

Found the problem; I had simply not completed or tested this code, the part that puts wired mac-address specifiers on the bus for NM was commented out.  Also the wireless mac address serialization is broken.

Comment 2 Jirka Klimes 2010-09-27 14:23:41 UTC

A patch fixing the issue is attached to bug 238046.

Comment 3 Lamarque V. Souza 2011-03-15 22:48:38 UTC

Jirka Klimes, can I close this bug then?

Comment 4 Jirka Klimes 2011-03-16 08:48:16 UTC

Sure, close please.
It's been tested in Fedora and is upstream now as well.