krb5kdc fails to start with vlan network interface

[Jason Holland]

Hello,

I'm having a curious problem with a Fedora core 1 box and krb5-1.3.4-7.
This box is part of a cluster where it needs access to multiple networks.
Instead of putting 4 or 5 nics in it, we have assigned vlan's to the nics
to get onto the appropriate subnets.  Interfaces are named eth1.100,
eth1.41 and so on.  I'm able to build the above krb5 version in Fedora
core 1 without problems, and kadmin starts up fine.  But krb5kdc will not
start.  The following shows up in the log...

Dec 10 10:40:40 spot krb5kdc[27939](info): setting up network...
Dec 10 10:40:40 spot krb5kdc[27939](info): setting up network...
Dec 10 10:40:40 spot krb5kdc[27939](info): skipping unrecognized local address family 17
Dec 10 10:40:40 spot krb5kdc[27939](info): skipping unrecognized local address family 17
Dec 10 10:40:40 spot krb5kdc[27939](info): skipping unrecognized local address family 17
Dec 10 10:40:40 spot krb5kdc[27939](info): skipping unrecognized local address family 17
Dec 10 10:40:40 spot krb5kdc[27939](info): skipping unrecognized local address family 17
Dec 10 10:40:40 spot krb5kdc[27939](info): skipping unrecognized local address family 17
Dec 10 10:40:40 spot krb5kdc[27939](info): skipping unrecognized local address family 17
Dec 10 10:40:40 spot krb5kdc[27939](info): skipping unrecognized local address family 17
krb5kdc: Address already in use - Cannot bind server socket to port 750
address 10.1.1.1
krb5kdc: Address already in use - Cannot bind server socket to port 750
address 10.1.1.1
Dec 10 10:40:40 spot krb5kdc[27939](info): set up 0 sockets
Dec 10 10:40:40 spot krb5kdc[27939](info): set up 0 sockets
krb5kdc: no sockets set up?
krb5kdc: no sockets set up?

And the interfaces

eth0      Link encap:Ethernet  HWaddr 00:30:48:23:0F:15
          inet addr:10.1.1.1  Bcast:10.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:957285 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1337204 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:89716556 (85.5 Mb)  TX bytes:947699162 (903.7 Mb)
          Interrupt:31 Base address:0xd800 Memory:feafd000-feafd038

eth0.41   Link encap:Ethernet  HWaddr 00:30:48:23:0F:15
          inet addr:172.16.0.1  Bcast:129.7.41.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:544962 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1328485 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:69007761 (65.8 Mb)  TX bytes:940298138 (896.7 Mb)

eth0.100  Link encap:Ethernet  HWaddr 00:30:48:23:0F:15
          inet addr:192.168.100.239  Bcast:192.168.100.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:412357 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8725 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:20708795 (19.7 Mb)  TX bytes:7401022 (7.0 Mb)

eth1      Link encap:Ethernet  HWaddr 00:04:76:F5:BC:A5
          inet addr:192.168.101.239  Bcast:192.168.101.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3629804 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2247545 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:315189603 (300.5 Mb)  TX bytes:369809280 (352.6 Mb)
          Interrupt:24

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:13042738 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13042738 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1538429291 (1467.1 Mb)  TX bytes:1538429291 (1467.1 Mb)


I have tried this same krb5 version on other systems that don't have vlan
interfaces setup and it works fine.  There is nothing listening on these
interfaces that would interfere with the daemon starting up either.

Can someone offer some help as to why this might be behaving like this?
Am I even on the right track thinking the vlans are the issue?

It there a way to force binding to a specific interface?  Not that it
matters, just curious.


Thanks for any help,
Jason