go to manual conf mode if there is an existing default route

This is in feisty by the way.

Was the 'recent udate' something like feisty beta -> feisty current, or edgy->feisty? You say it connected to the WiFi, but it does not route any packages? After connection, can you please copy&paste the output of these commands (enter them in a terminal):

  iwconfig
  ifconfig
  route

Thank you!

It was from feisty beta -> feisty current.

I also noted that it workes on a network without wep/wpa, so the problem might be around cryptation.

Will do that, but I am on another copmputer right now, so I cant do it yet.

iwconfig:
eth1 IEEE 802.11g ESSID:"hammer"
          Mode:Managed Frequency:2.412 GHz Access Point: 00:0C:6E:9A:A9:00
          Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
          Retry limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=95/100 Signal level=-32 dBm Noise level=-85 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

ifconfig:
eth0 Link encap:Ethernet HWaddr 00:11:25:2C:5D:92
          inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::211:25ff:fe2c:5d92/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:883 errors:0 dropped:0 overruns:0 frame:0
          TX packets:900 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:770418 (752.3 KiB) TX bytes:166870 (162.9 KiB)
          Base address:0x8000 Memory:c0220000-c0240000

eth1 Link encap:Ethernet HWaddr 00:0E:35:65:97:40
          inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::20e:35ff:fe65:9740/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:422 errors:0 dropped:0 overruns:0 frame:0
          TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:65276 (63.7 KiB) TX bytes:5474 (5.3 KiB)
          Interrupt:11 Base address:0x4000 Memory:c0214000-c0214fff

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:88 errors:0 dropped:0 overruns:0 frame:0
          TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7134 (6.9 KiB) TX bytes:7134 (6.9 KiB)

route:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
link-local * 255.255.0.0 U 1000 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

> default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
> default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0

Ah, here is the problem, for some reason you have *two* default routes, so it probably happened to randomly route your packets through the wrong one. Can you please attach your /etc/network/interfaces?

/etc/network/interfaces:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.1.6
netmask 255.255.255.0
gateway 192.168.1.1

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

So network-manager should just go into 'manual configuration' mode if it sees that there is an existing defaultroute with 0 metric (as opposed to avahi-autoipd's 'metric 1000' routes). Thank you for checking!

this was fixed by using a default metric of 100 for ifupdown interfaces in gutsy.