I don't think this is a duplicate of #5364 (which is about static IPs). On my Intrepid installation with a wired and wireless card, NM first connects to the wired network using DHCP. A while later (I haven't been able to spot the logic, sometimes it never happens) it also connects to the wireless network.
nm-tool reports both as 'state: connected'. The routing table looks like
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
That is, 192.168.1.0 traffic now has two destinations.
I don't think this is a duplicate of #5364 (which is about static IPs). On my Intrepid installation with a wired and wireless card, NM first connects to the wired network using DHCP. A while later (I haven't been able to spot the logic, sometimes it never happens) it also connects to the wireless network.
nm-tool reports both as 'state: connected'. The routing table looks like
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
That is, 192.168.1.0 traffic now has two destinations.