Hi Martin!You mention a very dark corner of AFS on Linux. I don't know the code, but I also had to fight it. My findings were:
- AFS uses all addresses by enumerating the network devices found by the kernel - The smallest IP number _must_ be on the first device, otherwise nothing works - It depends on pure luck if the internal cluster IPs are published to the outside, causing longish timeouts for client boot procedures.
It would be nice to be able to tell AFS exactly which IPs to use for what.
Concerning your clients question: Linux follows the weak host model, accepting all IPs on all interfaces. The assignment of IPs to interfaces only affects routing and the selection of source IPs to put in new packets (not responses).
On Sep 2, 2005, at 3:50 , Martin MOKREJŠ wrote:
Hi,I have a server with 3 network interfaces. Can I use the server 3 interfaces and put for some clients into CellServDB IP address of eth0 or eth1 or eth2 interfacerespectively?At the moment I thought I use eth2, which corresponds to the hostname.domainname but what happened is that "vos listvldb" shows IP address of wrong interface (at themoment not even connected to the network) phylo ~ # vos listvldb VLDB entries for all servers home RWrite: 536870918 number of sites -> 1 server 192.168.1.254 partition /vicepa RW Site
[snip]
Total entries: 8 phylo ~ # ifconfig -a eth0 Link encap:Ethernet HWaddr 00:11:09:B6:C1:7Ainet addr:192.168.1.254 Bcast:192.168.1.255 Mask: 255.255.255.0UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Base address:0x2400 Memory:d0140000-d0160000 eth1 Link encap:Ethernet HWaddr 00:11:09:B6:C1:7Binet addr:192.168.2.254 Bcast:192.168.2.255 Mask: 255.255.255.0UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Base address:0x2440 Memory:d0180000-d01a0000 eth2 Link encap:Ethernet HWaddr 00:0E:0C:84:83:71inet addr:195.113.57.18 Bcast:195.113.57.255 Mask: 255.255.255.0UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9595 errors:0 dropped:0 overruns:0 frame:0 TX packets:1157 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:699461 (683.0 Kb) TX bytes:182556 (178.2 Kb) Base address:0x3000 Memory:d0220000-d0240000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:649 errors:0 dropped:0 overruns:0 frame:0 TX packets:649 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:123551 (120.6 Kb) TX bytes:123551 (120.6 Kb) phylo ~ # cat /usr/vice/etc/CellServDBphylo.natur.cuni.cz #Cell name195.113.57.18 #phylo.natur.cuni.cz
This is only what the clients try to connect to, right?
Notice how the addresses are listed in enumeration order of the interfaces.phylo ~ # host phylo -bash: host: command not found phylo ~ # cat /etc/hosts 127.0.0.1 localhost # IPV6 versions of localhost and co ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts 195.113.57.18 phylo.natur.cuni.cz phylo [cut] The hostname is phylo. The DNS domain is natur.cuni.cz.The REALM is PHYLO.NATUR.CUNI.CZ (yes, NATUR.CUNI.CZ is used on other machines not under my control).Therefore, cellname is phylo.natur.cuni.cz. Could these problem be result of this a bit unusal setup? Why does "vos listvldb" show wrong interface IP address?Or does it just blindly use eth0? What if I wouldn't have no eth0 at allbut rather have ra0 (WiFi network card interface)? phylo ~ # vos listaddrs 192.168.1.254 192.168.2.254 phylo.natur.cuni.cz
phylo ~ # phylo ~ # vos help changeaddr vos changeaddr: change the IP address of a file serverUsage: vos changeaddr -oldaddr <original IP address> [-newaddr <new IP address>] [-remove] [-cell <cell name>] [-noauth] [-localauth] [- verbose] [-encrypt] [-help]Where: -remove remove the IP address from the VLDB -noauth don't authenticate -localauth use server tickets -verbose verbose -encrypt encrypt commands phylo ~ #
I don't know about this one, maybe someone can enlighten us...
This will just maybe set the IP address to the one I wish but can clients talk to theserver processes listening on other NICs as well? _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
Ciao,
Roland
--
TU Muenchen, Physik-Department E18, James-Franck-Str. 85747 Garching
Telefon 089/289-12592; Telefax 089/289-12570
--
A mouse is a device used to point at
the xterm you want to type in.
Kim Alm on a.s.r.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GS/CS/M/MU d-(++) s:+ a-> C+++ UL++++ P-(+) L+++ E(+) W+ !N K- w--- M
+ !V Y+
PGP++ t+(++) 5 R+ tv-- b+ DI++ e+++>++++ h---- y+++ ------END GEEK CODE BLOCK------
PGP.sig
Description: This is a digitally signed message part
