-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22/05/12 18:51, AL13N wrote:
>> On 22/05/12 16:59, AL13N wrote: >>>> On 22/05/12 15:08, AL13N wrote: >>> >> Meanwhile, I played with alternatives, knowing that it must be >> something close to what I'd already tried. So, >> >> # ip addr add 192.168.0.20/255.255.255.0 dev eth0 # ip addr show >> eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc >> pfifo_fast > state UP qlen 1000 >> link/ether 1c:75:08:28:bd:e4 brd ff:ff:ff:ff:ff:ff inet >> 169.254.100.1/24 brd 169.254.100.255 scope global eth0 inet >> 192.168.0.20/24 scope global eth0 inet6 >> fe80::1e75:8ff:fe28:bde4/64 scope link valid_lft forever >> preferred_lft forever >> >> So now it appears to have two addresses, preferring the wrong >> one. > > > by preferring, you mean the top one? > I take it that the 169.254.100.1 is the preferred one - by the system, that is. I don't even know where it is getting this now, as I renamed the config file that gave rise to it, so it shouldn't even be read now. > >>> >> # ip route default via 192.168.0.1 dev eth1 proto static default >> via 169.254.100.100 dev eth0 metric 10 default via 192.168.0.1 >> dev eth1 metric 10 169.254.100.0/24 dev eth0 proto kernel >> scope link src 169.254.100.1 metric 10 192.168.0.0/24 dev eth1 >> proto kernel scope link src 192.168.0.101 > 192.168.0.0/24 dev eth0 proto kernel scope link src > 192.168.0.20 > > > whoa, 3 default routes? over different interfaces... > > you have 192.168.0.0/24 network, both reachable over eth1 and eth0, > i hope that is what you want... > I don't want 169.254.100.0/24 at all. The other two I do want - I simply stop the wireless one when I have a convenient cabled connection. The cabled connection has a static IP, the wireless one has dhcp (the static address is not in the dhcp range). > >> Last question, then, is whether this is a permanent change? > > ip command is never permanent, you have to change the config files > if you want permanent changes (ie: after reboot). > But...but...but... ifcfg-eth0:temp is now ifcfg-eth0:temp.sav so shouldn't be being read. I'm going to delete it altogether now. ifcfg-eth0 is currently EVICE=eth0 BOOTPROTO=static IPADDR=192.168.0.20 NETMASK=255.255.255.0 GATEWAY=192.168.0.1 ONBOOT=yes METRIC=10 MII_NOT_SUPPORTED=no USERCTL=yes DNS1=212.23.3.100 DNS2=212.23.6.100 RESOLV_MODS=no IPV6INIT=no IPV6TO4INIT=no ACCOUNTING=no NM_CONTROLLED=no UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 NAME="System eth0" ifcfg-eth1 is DEVICE=eth1 BOOTPROTO=dhcp ONBOOT=no METRIC=35 MII_NOT_SUPPORTED=no USERCTL=yes DNS1=212.23.3.100 DNS2=212.23.6.100 RESOLV_MODS=yes WIRELESS_MODE=Managed WIRELESS_ESSID=xxxxx WIRELESS_ENC_KEY=s:xxxxx WIRELESS_WPA_DRIVER=wext WIRELESS_WPA_REASSOCIATE=no IPV6INIT=no IPV6TO4INIT=no ACCOUNTING=no NM_CONTROLLED=yes DHCP_CLIENT=dhclient NEEDHOSTNAME=no PEERDNS=no PEERYP=yes PEERNTPD=no You'll see that I have now set this to not connect on boot. When the current batch of files finish copying over I'll reboot, with the temporary cfg deleted and the change to ifcfg-eth1. I'll let you know what happens. Anne -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+72jIACgkQj93fyh4cnBex3wCfcRXxPmy2COty8CjcQE11AVYN q54AoIPZgYVInWZl93ehSB4rm5NQPfZl =nIRF -----END PGP SIGNATURE-----
