Re: [Sheflug] Changing distro woes

[Lesley Binks <lesley.binks@xxxxxxxxx>]

Alex Hudson wrote:
> On Wed, 2007-05-02 at 14:35 +0000, Lesley Anne Binks wrote:
>> Yes I am fully aware of the Session Manager.
> 
> Maybe, but you didn't say KDE wasn't appearing in the session list :)
Nor did anyone ask ;)
> 
>> Network Manager under Gnome via the nm-applet appears to be reporting
>> the machine to be connected via the link-local address (i.e. connected
>> to itself?) 
> 
> No, link local means "local to the ethernet segment" - basically, it's a
> bit like DHCP except you don't need a DHCP server and the machines work
> it out amongst themselves.

And I have a host of issues with the concept that an unconfigured 
interface should be assigned an IP address by anything.  And why that 
assignment should then block all other routes out on cards that have 
been configured.

I don't have any config for eth1 or eth2 on this particular box nor do I 
plan to assign any at an automatic level.

I reserve the right to manually configure and use either or both of them 
as and when I see fit.  I don't see why the link-local address should be 
assigned to an inactive interface nor why that assignment should then 
screw up specifically assigned interfaces and routes.
> 
>> while the default route out from the box consistently fails to be set
>> - despite it's existence in the interfaces file for eth0.
> 
> That's static configuration, which NetworkManager won't touch - I would
> imagine it's a simple misconfiguration or something. My Debian machine
> has this in /etc/network/interfaces :
> 
> auto eth0
> iface eth0 inet static
>         address 192.168.3.10
>         netmask 255.255.255.0
>         gateway 192.168.3.1
and mine is


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
         address 192.168.23.41
         netmask 255.255.255.0
         network 192.168.23.0
         broadcast 192.168.23.255
         gateway 192.168.23.21
         # dns-* options are implemented by the resolvconf package, if 
installed
         dns-nameservers 192.168.229.1

auto eth0

quite simple and fairly explicit about the route out of the box and 
where to find the nameserver.  Note no config at all, (none, zilch, 
zero, null) for eth1 or eth2.
> 
> Check all the spellings and stuff - it's likely something really simple.
> 
> If it's not in there, it's something deeper and interfaces(5) ought to
> help.
> 
Well I removed the NetworkManager stuff and the default route came up 
correctly on eth0 after a reboot without eth2 being bought up willy 
nilly. ... so I am fairly happy at the moment that it is not my network 
config causing the problem.

Regards

L.

_______________________________________________
        Sheffield Linux User's Group
  http://www.sheflug.org.uk/mailfaq.html
 GNU - The choice of a complete generation