Re: NM-0.3.3-1.cvs20050112.3 still adds double default route with SMC AP

[Bill Moss <bmoss clemson edu>]

I turned off starting NM at boot to look at the routing table along the 
way. I do not run the network service. I let NM bring up the interfaces.

1. After boot.
[root localhost ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface

2. After starting the NM service.
[root localhost ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface

3. After starting NMInfo and NMapplet shows a connection.
[root localhost ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use 
Iface
192.168.2.0     *               255.255.255.0   U     0      0        0 eth1
default         192.168.2.1     0.0.0.0         UG    0      0        0 eth1

Is your network connection functional? I still think some service 
besides NM is responsible for the link-local address. The only services 
I run are acpid, anacron, apmd, atd, autofs, cpuspeed, crond, cups, 
cups-config-daemon, gpm, haldaemon, iptables, lm_sensors, messagebus, 
pcmcia, readahead, readahead_early, smartd, syslog, xinetd

One possibility is cups. By default cups has browsing turned on. This 
may be the source of the link-local address. Try editing 
/etc/cups/cups.conf. Set

Browsing Off

and reboot.

Jens Lautenbacher wrote:

> On Thu, 2005-01-13 at 18:32 -0500, Bill Moss wrote:
>
>  
>
> > I see the same thing at the office. The default line in
> >
> > [~] $ /sbin/route
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> > 192.168.2.0     *               255.255.255.0   U     0      0        0 eth1
> > 169.254.0.0     *               255.255.0.0     U     0      0        0 lo
> > default         192.168.2.1     0.0.0.0         UG    0      0        0 eth1
> > default         *               0.0.0.0         U     0      0        0 eth1
> >
> > may be generated by whatever application is generating the link local 
> > address 169.254.0.0.
> >    
>
>
> No, I don't think so. I did repeated calls top /sbin/route while NM does
> it's discovery and configuration. This is how it looks before NM brings
> up eth1 
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 169.254.0.0     *               255.255.0.0     U     0      0        0 lo
>
> then comes
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 169.254.0.0     *               255.255.0.0     U     0      0        0 lo
> default         *               0.0.0.0         U     0      0        0 eth1
>
> and finally 
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 192.168.2.0     *               255.255.255.0   U     0      0        0 eth1
> 169.254.0.0     *               255.255.0.0     U     0      0        0 lo
> default         192.168.2.1     0.0.0.0         UG    0      0        0 eth1
> default         *               0.0.0.0         U     0      0        0 eth1
>
> So I strongly suggest that it's NM at work here. (first and last displays are maybe 5 seconds apart)
>
> 	jtl
>
>
>  

--
Bill Moss
Professor, Mathematical Sciences
Clemson University