RE: [9fans] cs & sysname

RE: [9fans] cs & sysname

[Tiit Lankots]

> Also, you could have avoided the problem by setting up a real ip
> address before running cs since it preferentially chose such an
> address.

Yes, but then it chose that ip as my sysname, becasuse it looked
either by ip or alternatively by ether, if ip didn't produce anything.
Case 1).

Tiit 

RE: [9fans] cs & sysname

[David Presotto]

I take it then that you don't have a static address but get a dynamicly
assigned one?

RE: [9fans] cs & sysname

[Tiit Lankots]

> I take it then that you don't have a static address but get a 
> dynamicly
> assigned one?

Yep. Luckily for me the server seems to be assigning ip-s
by ethernet addresses.

[9fans] cs & sysname

[Tiit Lankots]

After setting up venti, cs stopped recognising my sysname.
It was because the loopback interface got up first on boot,
and because cs looks first by ip address.

Now, I had two alternative ways to deal with it:
1) Poke around in /sys/src/cmd/ndb/cs.c and edit it to look
by the ethernet address when by ip it did not succeed. 
I did it.
2) Write the ip I get from the dhcp server into /lib/ndb/local.
I did it too.

Now it works. Basically, 2) would've sufficed.
OK, now for the question: Is 2) the "standard" way of dealing
with this? What to do when the ip returned by dhcp
is random?

Tiit

Re: [9fans] cs & sysname

[David Presotto]

[-- Attachment #1: Type: text/plain, Size: 80 bytes --]

I'll fix cs.  It really shouldn't accept the loopback address as the
local one.

[-- Attachment #2: Type: message/rfc822, Size: 2623 bytes --]

From: "Tiit Lankots" <t.lankots@aprote.ee>
To: <9fans@cse.psu.edu>
Subject: [9fans] cs & sysname
Date: Tue, 25 Nov 2003 14:37:27 +0200
Message-ID: <81132473206F3A46A72BD6116E1A06AE056154@black.aprote.com>

After setting up venti, cs stopped recognising my sysname.
It was because the loopback interface got up first on boot,
and because cs looks first by ip address.

Now, I had two alternative ways to deal with it:
1) Poke around in /sys/src/cmd/ndb/cs.c and edit it to look
by the ethernet address when by ip it did not succeed. 
I did it.
2) Write the ip I get from the dhcp server into /lib/ndb/local.
I did it too.

Now it works. Basically, 2) would've sufficed.
OK, now for the question: Is 2) the "standard" way of dealing
with this? What to do when the ip returned by dhcp
is random?

Tiit

Re: [9fans] cs & sysname

[David Presotto]

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

I changed and updated libip's myipaddr to totally ignore loopback.  It used
to return a non loopback address if it found one and failing that the
loopback address if it found one.  Now it just errors out if there is
no non-loopback address.

Also, you could have avoided the problem by setting up a real ip
address before running cs since it preferentially chose such an
address.

[-- Attachment #2: Type: message/rfc822, Size: 4755 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 80 bytes --]

I'll fix cs.  It really shouldn't accept the loopback address as the
local one.

[-- Attachment #2.1.2: Type: message/rfc822, Size: 2623 bytes --]

From: "Tiit Lankots" <t.lankots@aprote.ee>
To: <9fans@cse.psu.edu>
Subject: [9fans] cs & sysname
Date: Tue, 25 Nov 2003 14:37:27 +0200
Message-ID: <81132473206F3A46A72BD6116E1A06AE056154@black.aprote.com>

After setting up venti, cs stopped recognising my sysname.
It was because the loopback interface got up first on boot,
and because cs looks first by ip address.

Now, I had two alternative ways to deal with it:
1) Poke around in /sys/src/cmd/ndb/cs.c and edit it to look
by the ethernet address when by ip it did not succeed. 
I did it.
2) Write the ip I get from the dhcp server into /lib/ndb/local.
I did it too.

Now it works. Basically, 2) would've sufficed.
OK, now for the question: Is 2) the "standard" way of dealing
with this? What to do when the ip returned by dhcp
is random?

Tiit

Re: [9fans] cs & sysname

[Rob Pike]

> Also, you could have avoided the problem by setting up a real ip
> address before running cs since it preferentially chose such an
> address.
>
right.  just yesterday, due to changes in networking, i switched my
fossil/cpu/auth server from static IP to statically defined DHCP.  all i
had to do was delete a bunch of arguments to ip/ipconfig and track
down and updated all the wired-in IP addresses in the boot scripts.

i never used the loopback address (the line was commented out in
bootfl all along), i just made sure the IP addresses were set properly.

-rob