On Wed, 2005-04-06 at 18:49 +1000, Anand Kumria wrote:
> On Sun, Apr 03, 2005 at 03:15:23PM +0200, Thomas Hood wrote:
> > # ip addr show ethp_0
> > 8: ethp_0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
> >     link/ether 00:80:c7:ee:88:d6 brd ff:ff:ff:ff:ff:ff
> >     inet 192.168.1.8/24 brd 192.168.1.255 scope link ethp_0
>                                                   ^^^^
>                                                /
>               That is a concern, that address -
>               should really have global scope.
> 
> Was this address alocated via zeroconf? If so, that is a grave failure
> and I would appreciate knowing more about your setup/configuration if
> possible.


That configuration was applied by ifupdown (iface <name> inet static)
followed by zeroconf run twice from the command line, IIRC.  I am sure
that I didn't configure anything by hand (using ifconfig or ip).
Tonight I can perform that test again.

I am now at work where I connect the same machine using a Wi-Fi card.
Here is the log of an experiment.  Note that when i run zeroconf the
first time it fails.  It succeeds on the second attempt.  The wifi0
interface can be ignored; the airo driver creates it as a duplicate of
eth0.  I have ifrename set up to rename eth0 to wlanp_0.  To begin with
zeroconf has _not_ been run since bootup.

[EMAIL PROTECTED]:~$ sudo ip addr show
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
12: wlanp_0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:07:0e:b3:89:8e brd ff:ff:ff:ff:ff:ff
    inet 130.161.177.123/26 brd 130.161.177.127 scope global wlanp_0
13: wifi0: <BROADCAST,MULTICAST> mtu 2312 qdisc noop qlen 100
    link/ieee802.11 00:07:0e:b3:89:8e brd ff:ff:ff:ff:ff:ff
[EMAIL PROTECTED]:~$ sudo /usr/sbin/zeroconf -i wlanp_0
RTNETLINK answers: Cannot assign requested address
[EMAIL PROTECTED]:~$ sudo /usr/sbin/zeroconf -i wlanp_0
[EMAIL PROTECTED]:~$ sudo ip addr show
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
12: wlanp_0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:07:0e:b3:89:8e brd ff:ff:ff:ff:ff:ff
    inet 169.254.5.26/16 scope link wlanp_0
    inet 130.161.177.123/26 brd 130.161.177.127 scope global wlanp_0
13: wifi0: <BROADCAST,MULTICAST> mtu 2312 qdisc noop qlen 100
    link/ieee802.11 00:07:0e:b3:89:8e brd ff:ff:ff:ff:ff:ff


The 130.161 address is still global scope, which is good.


> Since the specification does note that IPv4LL and IPv4 global scope will
> be in use simultaneously and has merely a 'SHOULD NOT' prohibition (i.e.
> don't do it if you don't know what you are doing) I believe configuring
> zeroconf address via the if-up.d approach is correct.


OK

-- 
Thomas Hood <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to