Changes between Initial Version and Version 1 of Ticket #69


Ignore:
Timestamp:
Sep 26, 2006, 9:07:41 AM (19 years ago)
Author:
Bruno Cornec
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #69

    • Property Status new → assigned

  • Ticket #69 – Description

    initial v1  
    11zeroconf (www.zeroconf.org) apparently adds an IP address from the 169.254.0.0/16 range to an interface. So, with zeroconf installed I get the following outout from 'ip addr':
    22
     3{{{
    341: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
    45    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    … …  
    16174: sit0: <NOARP> mtu 1480 qdisc noop
    1718    link/sit 0.0.0.0 brd 0.0.0.0
     19}}}
    1820
    1921The interesting one here is 2: The 192.168.1.213 address is what is configured as a static address. 169.254.134.104 is what zeroconf adds.
    … …  
    2123Networking in general works fine with this. However, mondoarchive uses ifconfig to obtain the IP address for the NFS config. 'ifconfig' gives:
    2224
     25{{{
    2326eth0      Link encap:Ethernet  HWaddr 00:11:D8:50:E0:80
    2427          inet addr:169.254.134.104  Bcast:169.254.255.255  Mask:255.255.0.0
    … …  
    3942          collisions:0 txqueuelen:0
    4043          RX bytes:20284 (19.8 KiB)  TX bytes:20284 (19.8 KiB)
     44}}}
    4145
    4246which means it only gives the IP address configured by zeroconf. And that address is what is using during restore and of course doesn't work.
    4347
    44 I am not 100% sure what to do here but don't think it is super urgent. I mainly wanted it documented somewhere - maybe we should also put it in the wiki?
     48I am not 100% sure what to do here but don't think it is super urgent. I mainly wanted it documented somewhere - maybe we should also put it in the wiki ?
    4549
    4650One interesting comment I saw is that apparently ifconfig is getting superseded by the ip command. Maybe we need at some stage replace ifconfig with ip.