Re: Still not fixed ipup problem.
Okay, I've been having this exact same problem the last week or two and have had to resort to manually bringing up eth0 with dhclient.
the auto ifup always assigns me that bogus 169.254.x.x address too ... very annoying.
What I think this is related to though for me is a recent aborted install of vmware, in which some sort of virtual bridge was setup to co-exist on eth0.
I'm not familiar enough with how vmware sets up its virtual ip's to know how to prevent this from happening. I've removed the vmware modules, and all the vmware configuration files (that i'm aware of) and all instances of vmnet existing in udev entries so I'm not sure how/why it's weirding out on me still. I'm surprised to find someone with the exact same problem.
On Mon, 04 Jul 2005, Alan Chandler delivered in simple text monotone:
> I am still finding that ipup is failing to bring up my ethernet interface with
> the correct ip address. Its still the same problem I raised approx a month
> ago.
>
> Effectively I get two RTNETLINK answers failures during
> the /etc/init.d/networking start sequence as shown from /var/log/boot snippet
> below.
>
> Mon Jul 4 19:36:54 2005: Setting up IP spoofing protection: rp_filter.
> Mon Jul 4 19:36:54 2005: Configuring network interfaces...RTNETLINK answers:
> Cannot assign requested address
> Mon Jul 4 19:36:55 2005: Internet Software Consortium DHCP Client 2.0pl5
> Mon Jul 4 19:36:55 2005: Copyright 1995, 1996, 1997, 1998, 1999 The Internet
> Software Consortium.
> Mon Jul 4 19:36:55 2005: All rights reserved.
> Mon Jul 4 19:36:55 2005:
> Mon Jul 4 19:36:55 2005: Please contribute if you find this software useful.
> Mon Jul 4 19:36:55 2005: For info, please visit
> http://www.isc.org/dhcp-contrib.html
> Mon Jul 4 19:36:55 2005:
> Mon Jul 4 19:36:56 2005: Listening on LPF/eth0/00:50:da:cf:a5:06
> Mon Jul 4 19:36:56 2005: Sending on LPF/eth0/00:50:da:cf:a5:06
> Mon Jul 4 19:36:56 2005: Sending on Socket/fallback/fallback-net
> Mon Jul 4 19:36:56 2005: DHCPDISCOVER on eth0 to 255.255.255.255 port 67
> interval 3
> Mon Jul 4 19:36:56 2005: DHCPOFFER from 192.168.0.20
> Mon Jul 4 19:36:58 2005: DHCPREQUEST on eth0 to 255.255.255.255 port 67
> Mon Jul 4 19:36:58 2005: DHCPACK from 192.168.0.20
> Mon Jul 4 19:36:58 2005: bound to 192.168.0.21 -- renewal in 10800 seconds.
> Mon Jul 4 19:37:00 2005: RTNETLINK answers: Cannot assign requested address
>
> I can't find any explanation of what these RTNETLINK messages are, and in what
> circumstances they appear. All that happens is the my ipaddress is not set
> to that offered by the dhcp server.
>
> Anybody any ideas of where to look for a solution?
>
>
> --
> Alan Chandler
> http://www.chandlerfamily.org.uk
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
<---Snip--->
Reply to: